@evangreer @fightforthefuture.org @bsky.app @guardianproject @internetarchive @torproject @signalapp @session @simplex @freedomofpress @eff @privacysafe
#PrivacySafe Locker: Secure file #sharing that disappears.
Upload a file or paste a long text memo — and share it for 24 hours before it self-destructs.
Built to be forgotten and, like PrivacySafe Link, you can use it with #Tor @torproject for max #privacy. https://bitsontape.com/p/email-files-privacysafe-locker

@evangreer @fightforthefuture.org @bsky.app @guardianproject
Save (by OpenArchive): Preserve your media.
Send photos, videos, or #audio to @internetarchive and archive over #Tor @torproject . Metadata is added by you, *not* your phone. Evidence is vital for protection — please try to balance that with personal #privacy
https://guardianproject.info/apps/net.opendasharchive.openarchive.release/

@JessTheUnstill @bohwaz @punkfairie @ajsadauskas @tomiahonen @fuchsiii Exactly...

Coincidentially, that's why #Android (and #iOS) doesn't let users have #root access because billions of devices owned by mostly "#TechIlluterates" thathardly get #SecurityUpdates would be an even bigger risk if they didn't boot a locked-down #ROM image, thus only allowing for #malware in user-privilegued userspace!

• I'd even go so far that I'd wish for @torproject to basically merge fmr. #FirefoxOS / #KaiOS & @tails_live / @tails / #Tails to build a #privacy-focussed #ROM for #Smartphones and #Tablets i.e. "#TailsMobile" or sth.

Cuz having a mobile OS that shoves everything through #Tor and only allows #userspace-Apps in the form modern web technologies would be a big #security and #privacy gain.

• Not to mention #amd64 is on it's way out and inevitably they gotta have to transition to supporting #arm64 and eventually #RISCv-#64bit at some point.

This is undoubtedly the most promising Post-Quantum TLS deployment situation I have seen for #Tor since we started discussing it more actively in the team. Very exciting!

I hope that OpenSSL 3.5, when released, will make it into #Debian Trixie. That would make deployment of this so much more snappy and easy for the Tor network to upgrade, but that may be dreaming. The timelines here look quite difficult for that to happen, but let's hope.

OpenSSL, unlike BoringSSL, did not require us to make any additions to our codebase (BoringSSL required the PQ-KEM to be enabled explicitly via a function call): the ML-KEM is enabled by default, which will do wonders for adoption as OpenSSL 3.5 gets bundled in more and more OS distributions over time.

However, we did need to modify #Tor slightly to be less conservative with which TLS cipher suites it is willing to use. I will talk with the team about what we do here to get this fixed soon.

Lo and behold, #OpenSSL 3.5 (their upcoming LTS release) will come out here at the beginning of April, and it does indeed support some of these hybrid PQC schemes. Their recent beta2 announcement can be read here: https://openssl-library.org/post/2025-03-25-openssl-3.5-beta/ and their roadmap is at https://openssl-library.org/roadmap/index.html

Very excited by this work. Big kudos to the OpenSSL Team here! Already planning on giving this a spin with the C implementation of #Tor later this week to see how it goes!

@signalapp It's not #disinfo when one points out that you demand #PII aka. #PhoneNumbers from Users and that is literally a architectural vulnerability, alongside your #proprietary & #Centralized #Infrastructure.

• #Signal being a #SingleVendor & #SingleProvider #Solution is literally the reason why I consider it #insecure.

Not to mention the lack of @torproject / #Tor support with an #OnionService or the willingness to fulfill #cyberfacist "Embargoes" or shilling a #Shitcoin #Scam named #MobileCoin!

• #KYC is the illicit activity!!!

And don't get me started on the #cyberfacism that is #CloudAct.

• If you were secure, criminals would've used your platform so hard, it would've been shutdown like #EncroChat and #SkyECC.

I may nit have allvthe.evidence yet, but #Signal stenches like #ANØM: #Honeypot-esque!