@pinkforest thus the only correct reaction is multiple approaches:

• Refuse to use #centralized, #proprietary, #SingleVendor & #SingleProvider solutions.
• #SelfHost (or pay someone to host it for you!)
• encrypt harder
  • Put your chat on @torproject / #Tor i.e. use #OnionShare)
  • refuse any "#KYC" aka. "#AgeVerification" as a matter of principle!

Otherwiae we get the #Enshittification cycle going...

@freedomofpress #Signal Messenger is still #centralized, it does not let people run their own servers to intercommunicate on the network, it still requires a phone number to use, and it is not transparent with their server code, so the public does not know exactly what is running on the server... so why tell people to use it with all these risks?

There are #decentralized solutions, such as #Matrix, which fit the same use case. If you really do #love someone, then do not tell them to use #SignalMessenger & instead encourage adoption of real #FLOSS.

#ValentinesDay #FOSS

@decryption that's a good deal, m8.

Personally, I want to #DIY myself something like #Tarsnap (which is why I refuse to look at it's source code!) but with custom endpoints to store stuff in...

• Simply because I can't use anything subject to #CloudAct (i.e. #amazon #S3 / #Glacier) and want something uniformly that can do "pull backups" without anything on the machines that I want/need to backup / restore.

  • Plus not being chained to a #centralized. #SingleVendot / #SingleProvider solution is kinda important.

I mean, without #GDPR, #BDSG (if not even stricter rules and a moody US Government) I'd be more inclined just to pay for Tarsnap et. al. cuz @cperciva made a really good service with it...

@zeljkazorz why am I not surprised?

Granted, they target #TechIlliterates that use #centralized bs like #Signal Instead of real #E2EE with full #SelfCustody & #SelfHosting-capability…

@stman @theruran @50htz @vidak @forthy42 @brume @gorekhaa so yeah, we need a modern equivalent of the original PX-1000, something that isn't an overly complex and backdoored shitbox, but that is simple af.

With options for:

• PS/2 [or USB] Keyboard
• serial (thermal) printer
• parallel (20x4) LC-Display (or Braille Screen)
• acoustic modem (AFSK, using 3,5mm TRRS connector and adapters to line in/out and RJ-9 (handset)/RJ-11 (POTS/PSTN) phone.
• IrDA & Consumer-IR & QR-code reader module for public key exchange
• SDR reciever/transmitter (for paging).

Basically a encryption/decryption unit that has:

• User input [PS/2](keyboard, QR-Code reader)
• User output [Screen, Printer]
• Remote input [IR, IrDA, Modem, SDR-Reciever]
• Remote output [IR, IrDA, Modem, SDR Transciever]

Something that just acts as a "Clear Box" (aka. "black box", but transparent) to do critical comms. Something that literally wipes it's memory after use and doesn't store anything on it, but requires the user to keep their key safe!

You know, something that looks like a sleek communicator and isn't a proprietary shitbox that depends on *"#TrustMeBro!" - #centralized, #SingleVendor / #SingleProvider architecture!*…

@Soeren_loeg the fact that @signalapp not only does "#KYC with extra steps" by mandating a #PhoneNumber to this day as well as being solely under #CloudAct whilst basically being a #centralized, #proprietary, #SingleVendor & #SingleProvider solution makes them the ideal candidate for a longterm #HoneyPot like #ANØM aka. #OperationIronside aka. #OperationTrøjanShield.

• By the sheer size of users, it's a statistical inevitability that they got #Subopena'd and since they don't implement real #E2EE (with #SelfCustody of all the keys!) @Mer__edith would be in jail *if there wasn't a #Govware #backdoor as mandated per telco laws in every juristiction (see "#LawfulInterception!")…

Not to mention #Signal ticks way too many "#sus" boxes…