All the public Piped instances are getting blocked by YouTube but do small selfhosted instances, that are only used by a handful of users or just yourself, still working? Thinking of just selfhosting it.

On a side note, if I do it, I’d also like to install the new EFY redesign or is that branch too far behind?

Edit: As you can see in the replies, private instances still work. I also found the instructions for running the new EFY redesign here

  • Lucy :3@feddit.orgEnglish
    24·
    25 days ago

    Yes. My private Instance works perfectly, and I’m so happy that I chose to selfhost it rn lol. And currently I’m on the quest to selfhost even more piped components, eg. RYD_Proxy, sponsorblock-mirror, make them buildable as a PKGBUILD and compatible with Unix sockets: https://git.30p87.de/piped

    • Fisch@discuss.tchncs.deOPEnglish
      6·
      25 days ago

      Thanks, I’m gonna selfhost it then. What you said about the piped components sounds interesting, is there like a list of them?

      • Lucy :3@feddit.orgEnglish
        8·
        25 days ago

        Usually you’ll just need the official Docker. It contains the frontend, backend and proxy. Technically, you only need the backend right now. But lifting the load of the official servers by using a selfhosted frontend is probably beneficial too, with no drawbacks. However, the proxy is the thing anonymizing you - accessing youtube always through it, even on the go, will deanonymize you further (kinda, it’s still better than the official app). If you have a list of proxies you can rotate through, you would be anonymous again.
        Then there are other components, that you can find through the larger config file of the main Piped-Backend or TeamPiped’s GH profile itself. But again: Stuff like RYD-proxy will only be anonymous and beneficial with a rotating IP/proxy. But https://github.com/TeamPiped/region-restriction-checker is good to selfhost, as (afaik) it will help decentralize to circumvent censorship (zB. uHrHEbErRecHTsvERletZUnG die Ratten). But in order to configure your instance to use the region-restriction-checker, you’ll need the larger and more complete config file.

        ZL;NG:

        https://github.com/TeamPiped/Piped-Docker reicht eigentlich. Sonst einfach die einzelnen Repos angucken, was sich gut anhört. Proxy Zeug nur selber hosten wenns nicht um Privacy geht oder die IP verschleiert wird.

        • Fisch@discuss.tchncs.deOPEnglish
          2·
          24 days ago

          Wegen dem letzten Part, es geht zwar schon um privacy, aber dadurch, dass ich momentan YouTube direkt nutzen muss, weil die Piped instances nicht funktionieren, ist es halt immer noch besser. Außerdem hab ich angefangen nen GTK 4 Piped client zu schreiben und ich muss das halt auch iwie testen können.

  • chameleon@fedia.io
    9·
    25 days ago

    Gonna add a dissenting “maybe but not really”. YT is really aggressive on this kinda stuff lately and the situation is changing month by month. YT has multiple ways of flagging your IP as potentially problematic and as soon as you get flagged you’re going to end up having to run quite an annoying mess of scripts that may or may not last in the long term. There’s some instructions in a stickied issue on the Invidious repo.

  • mesamune@lemmy.worldEnglish
    8·
    25 days ago

    For me my self hosted version stopped working. From what the GitHub issues are saying, Google is starting to block instances if they get flagged.

  • SirMaple__@lemmy.worldEnglish
    81·
    25 days ago

    My selfhosted instance is still working. I’m the only user which probably helps it from getting flagged. If they manage to kill Piped and the other similar options, YouTube is dead to me.

  • Decronym@lemmy.decronym.xyzBEnglish
    2·
    24 days ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    Git Popular version control system, primarily for code
    HTTP Hypertext Transfer Protocol, the Web
    IP Internet Protocol
    nginx Popular HTTP server

    3 acronyms in this thread; the most compressed thread commented on today has 13 acronyms.

    [Thread #936 for this sub, first seen 24th Aug 2024, 23:05] [FAQ] [Full list] [Contact] [Source code]