Thanks for the idea. I definitely have to give this a bit more thought. I’m not sure I want to implement user signups like Piped/LibreTube do it as I would rather keep using the Newpipe app, so I’ll think of other ways of achieving data syncing.
Thanks for the idea. I definitely have to give this a bit more thought. I’m not sure I want to implement user signups like Piped/LibreTube do it as I would rather keep using the Newpipe app, so I’ll think of other ways of achieving data syncing.
I’m actively working on a web front-end for Newpipe (Tubo) in my spare time. Alhough the core functionality is already there, I have yet a lot of features/nice-to-haves to tackle, as well as many refinements to the UX to make it as close to the Newpipe app as possible.
It does neither atm, it simply serves you the streams as-is. The plan, however, is to eventually proxy all requests so that the services aren’t able to see it was you who made the request but only get the proxy’s IP
deleted by creator
Leaving my project Tubo in case someone finds it useful. Support for it just got merged on Libredirect
deleted by creator
Matrix with mautrix-whatsapp, mautrix-instagram, and mautrix-telegram. I strongly think that protocols should be interoperable for them to succeed, otherwise we’ll create a multitude of silos like Signal, Threema, etc that further separate communication.
I remember this being marketed as the Emacs Org mode + Org Roam combo for the masses, which is totally fine. However, if you want true control over your data and you’re willing to step out of your comfort zone, consider using Emacs + Syncthing
432432$@$#@23
It somewhat can