• 8 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • kavin@feddit.rockstoPrivacy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    28
    arrow-down
    1
    ·
    1 year ago

    Author of Piped (and also a member of TeamNewPipe and LibreTube) here.

    I haven’t seen any changes from YouTube recently, the ways we fetch age restricted content still seem to work for most videos. However, this method may not work for all videos as YouTube has different levels of age restrictions afaict. I’ve seen very few videos fall under that category personally.

    If anything were to change in the future, I may consider implementing something similar to what this extension does (or use their API) in Piped.















  • Piped can be more privacy friendly in a few cases, as you don’t need an account for subscriptions or playlists.

    Here are some differences to Invidious:

    • Subscriptions don’t necessarily require an account
    • Playlists don’t necessarily require an account
    • Piped supports Infinite scrolling
    • Piped supports Webm videos
    • Piped can stream videos from Odysee if the same video is available there.
    • Piped is a lot lighter on the server
    • Piped always proxies your traffic to Google’s servers (most Invidious servers don’t proxy videos to YouTube by default)
    • Piped has SponsorBlock integrated (DeArrow will be added soon)
    • Piped has ReturnYouTubeDislike support via RYD-Proxy
    • Piped can only be self-hosted on a server. Invidious on the other hand can work fine on local networks.
    • Piped is a lot easier to administer than Invidious as an instance operator.

    I’ll conclude by saying that I was once an Invidious user. I decided to write Piped at a time when Invidious was riddled with extremely odd bugs and performance issues. Some of these issues still persist to this day. I’ve always kept performance a top priority in Piped. I wanted to create a better alternative to YouTube than Invidious for my use case and threat model. I think I have succeeded in that :)


  • Currently, it scans all posts that are federated with my Lemmy instance (feddit.rocks), however, there are very few communities that it is scanning currently as there are very few users who have subscribed to communities on my instance.

    If more people register on my Lemmy instance and subscribe to more communities, it will scan those communities as well.

    I hope more users register on my instance so it can be listed on https://join-lemmy.org/instances too :) I currently lack the 5 active users requirement for that, unfortunately.

    Alternatively, I could maybe add a way for people to get the bot to subscribe to a community, so people from other instances can add communities to be scanned. 🤔 You can now try sending it a message mentioning communities in the format !community@instance.tld and it will try joining it :)