@lauren I disagree as @signalapp requires a #PhoneNumber = #PII & cost barrier and they restrict access based off #PhoneNumbers.

• Plus it's illegal in an increasing number if juristictions to gmeven attempt to acquire a phone number or SIM anonymously.

Whereas it's so easy and fast to get #TechIlliterates setup with #XMPP+#OMEMO (which uninke #Signal doesn't demand PII!) that I'd challenge you to a #speedrun with step-by-step documentation for every #TechIlliterate to follow along to setup Signal from scratch vs. me doing #XMPP+#OMEMO on @monocles @gajim.

• Cuz I did that on @cryptoparty / #CryptoParty / #CryptoParties quite often.

Also #Signal being #centralized makes it as vulnerable as any other #SingleVendor & #SingleProvider solution!

• Whereas even if #monocles were to shutdown, one could easily switch over to any other provider or #SelfHosting.

I'd not count on the #Trump-Regime not flexing #CloudAct against anyone they deem undesireable!

@tauon Actually, you want to use a truly secure as in real #E2EE solution like #XMPP+#OMEMO as in @monocles / #monoclesChat and @gajim /#gajim...

• And for those "#TechIlliterate #Normies / #Consoomers" that are too scared to #degoogle or even use @fdroidorg they have a #GlobalSwitchDay #promo right now:https://monocles.social/@monocles/113925173206088469

@bagder Problem with that is (besides occasional bugfixes), most people including myself would see #curl to be functionally complete and anything "nice to have" would be considered not worth the balooning in #complexity and #size.

• I mean, does curl need to be able to do #BitTorrent (magnet:), #IPFS (ipfs://) or god forbid #blockchain (i.e. #EVM) support?

• Do you really want to integrate @torproject / #Tor support natively into curl when using #HTTP (localhost:8118) and #SOCKS5 (localhost:9050) #proxy allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??

In fact if #toybox didn't have a #wget implementation that I could use for OS/1337 I would've merely chosen tiny-curl -o as a global alias or if #tinycurl wasn't an option, curl -o instead.

• Maybe someone who wants to have said functionality like tor support built-in will go and IDK make i.e. #neocurl or sth. along those lines or build something like #ethcurl or #torcurlor #ipfscurl or whatever...

That being said I am glad curl isn't solely maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most "#TechIlliterate #Normies" most likely never heard of but propably use on a daily basis as part of all the #tech they use to #consume media with...

• I consider curl to be "the #vim of downloaders" (tho that's kinda insulting and limiting since curl is more than just a downloader and more intuitive than vim) with wget being "the #vi of downloaders" (tho wget is even simpler to use than vi)...

Either way, curl is awesome...

And no, what #Apple does here isn't #SelfRepair or #RightToRepair but a rotten-to-the-core #Figleaf to bamboozle #TechIlliterate #legislators into believing Corporate #PR aka. #Propaganda #lies!

• Imagine if one would have to call @frameworkcomputer just to be able to use a new #Laptop #battery... But with Apple people seem to accept having their #Phone #RAT'ed for no legitimate reason!

https://www.youtube.com/watch?v=ZzS2vwDUO9U

@GrapheneOS I think both apps are shit as *both #Telegram and @signalapp demand #PII in the form of #PhoneNumbers.

• #Signal at least has their #client's source code published so similar to like #Tarsnap it's more trustworthy by virtue of better #transparency...

OFC Telegram is (by my personal observation) almost exclusively being used by #Scammers and other #TechIlliterate criminals.

• Trusting Telegram is like trusting #EncroChat or #ANØM aka. #OperationIronside aka. #OperationTrøjanShield: It literally has #Govware #Backdoors because the #UAE of all plaves would've swatted their "HQ" if not forved #Durov at gunpoint to integrate it into it if it wasn't there...

@GrapheneOS I think #Apps should not be allowed to request anything to run but what the user allows them to.

• Apps should not be allowed to require tight integrations and users need to pressure those that make Apps to not do that!

#WhatYouAllowIsWhatWill continue applies to #Enshittification like that of #Uber and this shouldn't exist to begin with...

• But you'd rightfully point out that with most #TechIlliterates being users, that ship has sailed 20+ years ago as the same boomers that once belittled young millenials to not overshare are now basically "unofficial collaborators" for #NSAbook at this point.

So at this point I'd only see a few options that boil down to few decisions:

1. Depend on Google making "good hardware" or getting into talks with other vendors to attain the necessary 1st party support from day 0 per design?

2. Bow before #TechIlliterate|s or double down on "security first" even if that means inconveniencing them?

IDK which answers are "correct", I can merely say what I'd choose but it's not my decision where #GrapheneOS goes...

• Either way I only wish Graphene OS and the team behind it as well as it's users only the best...

@hj @radmin @SuperDicq Well, no.

That assumes I'd install such garbage to begin with!

• There's no reason for something like that to require a fucking app when 25+ years ago a goddamn website would do just fine...

But hey go live in the dystopian world where everyone but you is a #TechIlliterate #Zoomer...

I've got.more pressing things to do than debate bs.

@georgetakei Whilst it may seem bad to weaponize #tech against #TechIlliterates at first, as #IT #Sysadmin I can assure everyone that the time and frustration saved by forcing #TechIlliterate relatives onto your tech stack is worth it!

It saves time, money, pain and frustration...

@androcat @JorisMeys

Needless to say that the non-teaching of #TechLiteracy and #MediaLiteracy including #ITsec, #InfoSec, #OpSec & #ComSec isn't an accident but systemically intended.

Because #TechIlliterate and/or #MediaIlliterate people are easy to control without being less productive in terms of taxable income as complete #Illiterates...
https://mstdn.social/@kkarhan/110752123481585671

@heiseonline Oder auch: "Ich bin zu sehr #MediaIlliterate & #TechIlliterate und sehe es nicht ein Leute zu bilden!"

@ancient_catbus also #TechIlliterate politicians...

@foss_android #Enpass (since it's really multi-platform and easy to use for #TechIlliterate "#normies") and #KeePassXC + #KeePassDX.

@atomicpoet @fediversenews I guess for #TechIlliterate shitheads at #Yahoo everything that doesn't run on a single monolithic server inhouse is considered "distributed" even if it's the worst SaaS and comms tool ever released to the world.

@chrisheuer @suzannealdrich @atomicpoet @TechCrunch @fediversenews @WIRED OFC I don't expect the average #TechIlliterate not to host their own @nextcloud / #Nextcloud, #eMail and website - much less their own #Mastodon.

Corporations tho should have these resource...

@godpod yeah, #TechIlliterate and #lazy #normies are complicit in the problem...

@YourAnonNews at this point, it's important to unplug and redirect even the #TechIlliterate #normies to #Mastodon:

And I'll do my part...
https://twitter.com/k3vk4/status/1603563834781978624