I’m not hiding anything, I’m choosing what to share; there’s a difference.

as to your (somewhat naive) perspective, yeah, having your shit out in the open is a credible threat. the solution is have all your shit private by default and not shared with anyone. then, allow leaks on a case-by-case basis.

we’re all done (or should be, at least) with the idea that there are laws and regulations shielding us from the now rampant abuse from various threat actors. instead of relying on the government or whoever to enact those regulations, I find it way better to not allow anyone to be in the position to compromise me.

this is a forever moving target and you’re never going to achieve full security; to paraphrase cory doctorow, that’s a full-time, unpaid job that you’re doing in addition to your existing job. but I’m better off with more security and privacy than without, so I’m ok with the sacrifices I have to make.

saw your other post as well, there’s so much stuff in your stack that you have to narrow your issues down to the malfunctioning item, there’s no way you’re gonna stumble upon someone with your exact setup.

start with existing element x apps communicating over matrix.org (use throwaway accounts if you don’t trust it) and unified push using ntfy.sh. if everything works there, then you can start replacing one by one of these until you achieve full functionality or something breaks.

the other sandwich?

E2EE is explicitly prohibited by Telegram’s ToS so no alternative client is implementing it. seeing as how you’re already breaking it for non-important things, my suggestion is a pedal-to-the-metal approach.

then again, you don’t owe me or anyone anything.

if you’re already breaking ToS, include E2EE. the 17 ways your icons are colorificer and how your rounded corners are fresher interest me a total of zero.