Yes this is a Telegram client and yes it will break the Lemmy's downvote world record but I still find this one very nice and "actively" maintained. There are not many good Telegram FOSS forks without Google integrations and similar stuff out there.
Looks interesting. I don't fully understand how unified push works, though. I'm I right in reading that the author have set up an UP server themselves?
Yes this is a Telegram client and yes it will break the Lemmy’s downvote world record
Because most people live in a echo chamber. Just ignore them.
Thank you for your comment. Since I deactivated Google Play services, I don't get notifications on many apps. I didn't know there were alternatives. Unfortunately, the app server must be compatible, but if I can have it at least for Telegram with this fork, it would be a good start. I'll take time to compare the different alternatives and see if other push servers are compatible with more apps.
For what I understand, there are self hosted push servers, like NextPush that works on Nextcloud, and some that provide you a server, liked ntfy. For the latter, you have to check the privacy policy to see if it's better than the default Google firebase server.
I used this client recently and found it decent. Though for some reason, Google Play Protect always(wrongly I assume) picks it out despite downloading from F Droid.
do any of these forks support E2EE? I don't mean the OG "private chat" thingy that Telegram supports.
I mean like an add-on, the way pidgin had an OTR plugin that enabled private comms over Google's unencrypted XMPP servers.
as a consequence, that would also encrypt everything in the cloud and prevent your chat history being ingested for LLM training and whatnot.
That would require the other user to use the same app as you right? Could be interesting.
well yeah, just a simple private/public key solution for encrypting chat and cloud. transfer your private key to a forked desktop app and access your encrypted chat history from there as well.
just basic stuff, not something for people running from nation-state actors, but to prevent LLM ingestion and mass surveilance. but OP says that's against Telegram's ToS, so no dice here.
E2EE is prohibited by Telegram's TOS (you can't make any feature that requires users to use your client to access it).
Whoa, they not only won't implement it, but will work on not letting anyone else do it. They're more shady than I thought.
They're not shady. They just don't want to lose the market share and I think if they made Telegram really secure, there'd be even more illegal stuff on it and the government wouldn't like it.
I don't trust any of these apps that are used by the DEA and trying to get a phone number out of me one bit
Show
What are you using for the Unified Push setup? I tried using ntfy and could never get notifications to come through on GrapheneOS
I use ntfy and have no problems. It's very reliable. No idea about graphene though
I use LineageOS without any gapps and notifications often work.
I use ntfy on graphene and it works just fine. I had to fully disable battery optimizations but that was it
Have you tried changing server? The default server is overworked.
