@Jain @gingerrroot @gabri
Eeyupp...

Personally, I think that such a "removal" would only work well with a sort-of private #Proxy setup similar to #FrogFind [ http://frogfind.com ] by @ActionRetro

#WebDevs like @fuchsiii would scream at this point since this can be weaponized for #malware and #phishing easily, as it would literally require to perform #MITM attacks!

The best that I can think of would be something like #ShinigamiEyes since that only applies a custom #CSS [colour of font].

@neil @Em0nM4stodon #Signal as well isn't secure.

NO #SingleVendor / #SingleProvider solution can be secure as they all violate #KerckhoffsPrinciple.
https://en.wikipedia.org/wiki/Kerckhoffs's_principle

If you can't do #SelfCustody of the #PrivateKeys and don't have 100% control over these, then consider said #encryption to be easily #MITM'd and / or #backdoored.

@dalfen it can't.

#Balloon or spy plane gives 50x more signal strength. 100x more dwell time. 5000x #SignalToNoise. Plus 1/10th the time of flight (for #MITM and active #sigint or jamming). Countermeasures are expensive.

And 100x more #propaganda and diplomatic leverage. US used to allow Russian #SpyPlanes to surveil our nuke silos (per SALT and other treaties) almost monthy. Public didn't get to see them so nobody cared.

@aprilwright @Mastodon @fuchsiii I mean it is possible to include them by #MITM'ing traffic to extract the #API keys and unlike the workaround requiring #DevKeys like @mariotaku 's #TwidereX, it is ~technically~ not a violation since one doesn't technically have to agree to the Developer ToS'es, but since when does #Twitter actually give a s**t about "due process" or "consistent rule enforcement"...

https://github.com/kkarhan/misc-stuff/blob/main/publications/statements/20221102/hey-twitter.md

Attacco #MitM, sventato un colpo milionario
Recuperati dalla Polizia Postale 1.300.000 Euro
https://www.matricedigitale.it/tech/attacco-mitm-sventato-un-colpo-milionario/