Well yeah, I agree. FOSS apps do lack features like logging in (to a Google account), the recommendation algorithm, etc. On the other hand, ReVanced is not exactly easy to install for new users. Both approaches are valid and get the job done (blocking annoying ads). I appreciate the calm and pleasant conversation.
I know that it exists, I don’t think it’s a particularly good solution on Android though. There are native apps like the ones I mentioned before.
Btw syncing an SQLite database with syncthing sounds painful. How often do you have to deal with sync conflicts?
I just don’t want any proprietary software on my devices (for many reasons, most importantly privacy and user freedom). I can use a VPN to privately connect to the YouTube backend, but things get much harder when the proprietary spyware is actually on my device.
If you want to use YouTube for that, it seems like ReVanced is your only option. But you can also create an account on a Piped instance, and have your playlists synced. LibreTube is the only app that supports this.
I’d say they are objectively better, because are independent, free & open source apps, instead of relying on patching Google’s proprietary software.
I tried Floorp and didn’t like it either, I’m glad there’s a more promising looking project out there now. Still great to see more development in the Firefox/Gecko ecosystem. We don’t need more Chromium garbage.
Supports FF Sync.
They only backport (some) OS patches, the firmware doesn’t get updated after the vendor classifies a device as EOL.
To get Android into a fully patched state, you need both firmware updates that come from your phone’s vendor, as well as OS patches that come from your OS developer (in this case GrapheneOS). GrapheneOS usually only provides OS updates as long as Google provides firmware updates, because they don’t want people to run outdated and potentially insecure devices with old, unpatched firmware. But they have extended update cycles for some EOL devices like the Pixel 4a (5G) and Pixel 5.
Your bank specifically requires Play Protect? That’s odd, I’ve never heard of something like that before. I’d still check this list to see if it might be compatible with GrapheneOS: https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
You can get a Pixel 7a for under 300 EUR, and it is supported until 2028, so you don’t lose out on updates.
Fairphones aren’t even anywhere close to meeting the security requirements of GrapheneOS. Daniel Micay explained this many times, most notably in this Reddit thread (before they left Reddit and switched to their own, self-hosted forum) https://redlib.nohost.network/r/GrapheneOS/comments/10b5x4n/has_anyone_managed_to_install_grapheneos_on_a/j67pbny
They will only support Pixels for the foreseeable future, as these are the only devices that meet their hardware security requirements https://grapheneos.org/faq#future-devices
DivestOS is pretty good. I’d stay away from /e/OS, CalyxOS and LineageOS though, as they have some pretty serious security problems.
The Signal protocol is the de-facto standard for E2EE, and it works just fine even in large group chats. But you refuse to accept this reality. The Signal protocol is used by so many apps, obviously Signal itself, WhatsApp, Facebook Messenger, Instagram direct messages, Google Allo (back when it existed), Google Messages (RCS), Skype, Wire and many others. MTProto is developed by Telegram, only used by telegram, not properly audited and full of flaws. No one should actually use it. And the fact that it doesn’t support group chats is a design choice, because ultimately Telegram doesn’t give a fuck about their users privacy or security. They have repeatedly worked with governments and worked against the interests of their users. Their funding is also pretty unclear and shady, and the entire company just appears scummy. Give me one single reason why anyone should use this trash over a proper E2EE messenger like Signal, Threema, SimpleX or Wire.
Uh you appear not to understand how encryption works? Either something is end-to-end encrypted, and the service provider doesn’t have access to the encryption keys, and thus can’t read the messages, or it is encrypted in transit, the keys are held by the provider and the messages are decrypted on the server. The latter is exactly what Telegram does, even though they falsely try to market it as something else.
Also it seems there is still no proofs those vector attacks are being used at all.
Ah yes, definitely go with a messenger that has known vulnerabilities in its crappy encryption protocol, instead of one with an actual secure E2EE implementation.
no history is being saved in this mode
You can still make encrypted backups of encrypted messages, as can be seen on WhatsApp or Signal
and the desktop client doesn’t support it
I don’t know what you mean, both Signal and WhatsApp have managed to ship desktop clients with full E2EE support for years now. Only Telegram is too incompetent to do that.
Telegram got implemented e2e between 2 users before other messengers got it working in any form of group chats
Just stop lying. Telegram Secret Chats have been introduced in 2017, both Signal and WhatsApp have had E2EE (including for group chats!) for much longer. Signal has had (encrypted) group chats in 2014, back when it was called TextSecure: https://signal.org/blog/the-new-textsecure/ And WhatsApp followed in 2016.
I’ll think about it if they ditch electron.
Are you mad that Signal is focusing on privacy and security by improving their encryption protocol, instead of wasting time on some UI garbage? This shows your priorities really well. Keep using unencrypted Telegram, for the cool stickers and convenient cloud backup, and keep in mind that Telegram can read all of your messages, as well as hand them over to governments.
Stop pretending that Telegram cares about the security of their users, because they clearly aren’t, as can be seen in their shitty encryption protocol, and the fact that by default all messages are stored on their servers in plain text
It doesn’t work, because it relies on Piped/Invidious. Both are currently broken, because Google is trying everything to block third party clients/APIs/proxies for YouTube.