@siblingpastry @QueerMatters @amberage and in case if #TUI browsers like #LynxBrowser it may either show gibberish or not.
curl & cat to ingest data.It's likely more effective to just ban all #GAFAMs' Networks if not migrate to @torproject / #Tor #OnionServices instead.
Before the media fixated on dark web crime stories, .onion services were a refuge for those who valued privacy, free speech, and anonymity. Early adopters of Tor used it to host personal blogs, distribute banned literature, share research in repressive regions, and build decentralized forums where users could speak without surveillance. Activists, journalists, and whistleblowers relied on hidden services to communicate and collaborate safely. It was never about profit. It was about principle. The darknet wasn't born for crime. It was born for freedom.
@koenvh #FunFact: THIS is actually real when it comes to #OnionServices on #Tor / @torproject despite (or rather because of) having a self-routing and self-administrating, self-authentificating namespace utilizing #Pubkeys for addressing.
Mine merely covers a few #BonaFide ones and there are literal #scam businesses when it comes to the kinds of sites I won't name nor list!
@cadey My thoughts on #Anubis after encountering it multiple times as a user:
* mascot is nice, creative and intuitive to understand
* as a user of tor it works! cloudflare and others reject me as a bot, but anubis left me through, thank you
* onion services do not require anubis protection, though, right? Since they have their own proof of work system integrated by default …
https://blog.torproject.org/introducing-proof-of-work-defense-for-onion-services/
… equi-x function based on what Tor uses?
https://pony.social/@cadey/114236263848292147
@aral @EUCommission @nlnet @letsencrypt @cacert not only that, I think we need self-governing namespaces similar to @torproject #OnionServices (even tho they are prone to #typosquatting-esque #sibil/#EvilTwin-style #phishing attacks!)...
@clubchonky personally, I disagree to an extent.
@torproject / #Tor is well battle-tested and combat-hardened and using #OnionServices works just fine, as none of the traffic leaves through #ExitNodes...
Also friendly reminder for #developers of #Apps using @torproject / #Tor and/or accessing #OnionServices using @guardianproject / #Orbot:
You may trust @mullvadnet but even they can't resolve …onion (and likely wouldn't even if it was that simple) because that's how it works!
Seems like the #OnionService for jabber.ccc.de @ m2ylflyeak6i6o4hsfwcrfwcq2bbjxk6nf2rnmm7fu6qiuu3hybenzid.onion is down.
Cc: @ccc@anonsys.net @CCC@social.bau-ha.us @ccc@chaos.social @clubdiscordia @torproject
@not2b @dangillmor I mean, she's just a #cyberfacist like #Zensursula, and the only correct way to deal with these #facists is to "#EncryptHarder!" (with #XMPP+#OMEMO & #PGP/MIME) and tunnel everything through @torproject / #Tor and setup #OnionServices for everything!
"[...] easy to use solutions that are at the same time private and secure. [...]"
It is easier, faster, cheaper and overall simpler to get someone setup with #XMPP + #OMEMO espechally if they don't have a #PhoneNumber and/or #ID to acquire a #SIM.
And if you go and say, "Just buy a [insert country here] [e]SIM!" and expect #TechIlliterates without a #CreditCard, #PayPal or other means of #OnlinePayment to fiddle around with some #eSIM if not having to get some #eSIMcard because they can only afford to maintain one SIM and can't spend triple-digits on a new devices then you completely missed the point!
It's not that I expect anyone to get #TechLiterate within minutes, but similar to setting up a cordless DECT phone it's something one has to do once in 5 years and just have them put the password in a safe spot to retain...
Point is that #Signal #WontFix their setup and that was evidently clear even before @Mer__edith succeeded #MoxieMarlinspike: Their entire operation has a distinct #CryptoAG stench as it's an #unsustainable #VCmoneyBurning party!
A counterexample on how this could've been done are #Tor, #eMail and other truly #OpenSource as in #MultiVendor & #MultiProvider standards.
NOTHING compells Signal to demand PII, run a #Shitcoin #Scam aka. #MobileCoin that even seasoned #TechLiterates and #CryptoBros can't setup properly, and in fact Signal using phone numbers makes it trivial to discriminate against users and easier for them to identify them!
If my reasoning didn't resonate with you, then try helping i.e. undocumented migrants aka. "#SansPapier|s" to get setup with it without violating laws and/or ToS and/or needing an imported SIM which I'm shure most folks don't have on hand!
Whereas it's trivial to get people setup on one of many XMPP servers I've personally tested!
AFAIK Signal doesn't even have an #OnionService / .onion for their Website, much less any #API enpoints to use it with!
You're free to also provide evidence and supporting data to your arguments, rather then neighsaying against proven to be more secure and reliable [by virtue of decentralization] options like XMPP+OMEMO and/or #PGP/MIME.
The proper fix is to actually assess the situation and acknowledge the risks and limitations as well as the very nature of communications, which means upgrading later is exponentially more painful, thus getting people properly setup once is way easier.
Speaking of #monocles: That business is at least #sustainable because it's funded by users (€2 p.m.) which they can pay anonymously
@kasiandra ganz einfach:
Sei es @monocles / #monoclesSearch oder #DuckDuckGo für die Suche!
@ploum instead of @signalapp which also falls under #CloudAct and is also a #Proprietary, #SingleVendor & #SingleProvider solution, consider #XMPP+#OMEMO for real #E2EE with #SelfCustody of all the keys!
Fir #eMail & #Chat, I can recommend @monocles as a paid provider who doesn't run #ads and doesn't fall under Cloud Act or similar laws. (Also they have excellent #Apps that work with basically all providers usibg standard-compliant servers & APIs!)
You may want to consider #Torifying everything by using @guardianproject #Orbot and push everything on #mobile through @torproject / #Tor.
In fact, some providers like cock.li even have #OnionServices to directly connect to them.
#MicrosoftOutlook literally steals your Login #credentials, so using @thunderbird is a necessity anyway. Don't forget to change your logins either way!
#Firefox is okay, but #TorBrowser should be normalized as well.
Consider launching a @cryptoparty to teach other the same.
Nirmalize using @tails_live / @tails / #Tails as your #DailyDriver!
@eniko no, in fact none of that stuff is nevessary and there are a shitload of #OnionServices on @torproject / #Tor that are using clean #HTML without #JavaScript!
@resingm @ada Call me weird but I fail to see where "yet another protocol" instead of #HTTP(S) is of benefit.
#TorProject State of the Onion
https://inv.nadeko.net/watch?v=EODNtLqD7f8 [perfect example, G de-onions]
https://onionmobile.dev #GuardianProject
https://github.com/blueprint-freespeech/gosling
53:16 - #InternetArchive , web.archive.org/
Access to information--and the preservation of it--otherwise difficult to obtain without a congressional staff and the library of congress. #ALibraryNotTheft
https://www.youtube.com/watch?v=HjPdReNmf_g&t=47
#TAILS
6:00 - partition checking (data integrity)
#Onionspray - facilitate making existing websites onion addressed! 15:00 making the addressing human accessible
18:51 - #Vanguards and #Arti
28:00 "conflux" congestion control
[...a whole lot of the internet doesn't work with Vanguards if it even did work with tor in the first place..]
#OnionServices
29:29 - Network Health
#Censorship
45:00 - webtunnel transport
In case you don't know, @cwtch is a decentralized end to end encrypted chat app
there's no servers by default, meaning no central authority
transport is based completely on Tor onion services, which itself is decentralized and provides automatic and transparent end to end encryption
(though @torproject still hasn't deployed any post-quantum cryptography into Tor, Cwtch is not as robust as newer PQ Signal or iMessage)
the profile ID that you share with your people is based on the Tor onion address that your profile is using for communications. if you shut down Cwtch, your Tor onion address also gets shut down, so you can't receive messages while you're offline, by default
it's my opinion that using Tor onion services for chat apps is a no-brainer. everyone with a Cwtch profile is both a client and a server. you are your own server. because of how Tor onion services works, as a reverse proxy, you don't need to host a "public" service on the internet. and e2ee, key management, encryption is all automatic. you can't fuck it up! its crazy to me that apps like Matrix don't take advantage of this. Tor onion services is an extremely powerful tool and so many people ignore or think of FUD
@cryptoparty +9001%
Außerdem geht es darum #Massenüberwachung so kostenintensiv und unrealistisch wie möglich zu machen...
Hier muss die doppelte*" Aggression"* geliefert werden die #Cyberfaschisten uns #Polizeistaat-Fans an den Tag legen!
@dw_innovation okay, maybe not the answer I hoped for given that this means manually dropping security in @torproject / #TorBrowser.
Given upcoming #accessibility requirements in #Germany I'm convinced cross-testing with #LynxBrowser over #Tor will likely be one of those things that'll necessitate changing that.
Hey, @dw_innovation ,
for some reason your OnionService doesn't seem to work and require #JavaScript, which is a big no-go on @torproject / #Tor as #JS can and has been known to be a security issue and big no-no for all serious #OnionServices...
Sadly the #paywalling of #grsec / #grsecurity also killed more #downstream projects like tor-ramdisk which was a minimalist #busybox / #linux #distro designed to host #OnionServices. It was pretty nifty and the #SourceCode is still online and hosted by @torproject on their #gitlab, abeit seemingly abandoned since 2018...
