home.social

#techilliterates — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #techilliterates, aggregated by home.social.

  1. @kkarhan @GrapheneOS @tails_live @torproject @signalapp

    "GrapheneOS chose their requirements and they can happily design their own platform instead."

    There's no need to reinvent the wheel. AOSP is a secure, open-source platform that has been around for almost 20 years. I don't want to debate rumors that Google wants to make AOSP proprietary because there is no evidence to support this, especially since it would not benefit them in any way.

    "I just think that their stubbornness"

    It's not stubborness and I explained why.

    "They are the antithesis to #Tails when it comes to #UserFriendly-ness and approachability for #Normies and #TechIlliterates

    It's probably the first time I've seen “Tails” and “Normie” in the same sentence, It's not that Tails is difficult to use, but I'm really not sure that many “normies” use it or even know it exists. The user experience on GrapheneOS is almost identical to Pixel OS, the standard operating system for Google Pixel devices, so using GrapheneOS is likely to seem much simpler and familiar to normies, as they will already be used to it.

    "Espechally since the problems woth #MobilePhones and the underlying technology ain't fixable with an #AndroidROM

    GrapheneOS is not a ROM, Pixel OS is not a ROM, and LineageOS is not a ROM either, theses operating systems are not ROMs.

    "Instead we need to foster a #SecurityCulture and proper #ITsec, #InfoSec, #OpSec & #comsec

    Indeed, and what GrapheneOS does about security is completely appropriate, including informing people and giving them good advice.

    "Otherwise we'll see them fail the same way @signalapp did, which is eitger getting shut down (#EncroChat-style) or being uncovered as a controlled opposition / honeypot (like #ANØM aka. #OperationIronside aka. #OperationTrøjanShield)…"

    Signal did not fail, and mentioning Encrochat, ANON, and honeypots in the same sentence is irrelevant. These things have absolutely nothing in common with Signal, you seem to be believing made-up stories.

  2. Ah yes, the classic saga of epic proportions: #JavaScript and #cookies holding the world's largest #democracy hostage 🤦‍♂️. But don't worry, once you've conquered that technical Everest, you can finally indulge in the riveting discourse on how the real VIPs are actually just entitled techno-illiterates 🍪💻.
    economist.com/asia/2026/02/22/ #TechSaga #TechIlliterates #HackerNews #ngated

  3. @kkarhan @mapto @yawnbox @Mer__edith

    "It's easer, faster, cheaper, more resilient, private and secure to onboard #TechIlliterates woth #XMPP+#OMEMO over @torproject / #Tor using @guardianproject #Orbot @monocles / #monoclesChat..."

    If it's easier, why isn't it as successful and used by the military etc? You seem to have dismissed video calls etc too. You could argue against that functionality for certain use cases, but it's become a core part of secure messaging over time. Maybe they just have different audiences.

    I kind of agree on Moxie's reliance on Intel SGX though. Even at its inception it worried me. But it's not part of the core E2EE protocol so could potentially be replaced.

  4. @kkarhan @mapto @yawnbox @Mer__edith

    "It's easer, faster, cheaper, more resilient, private and secure to onboard #TechIlliterates woth #XMPP+#OMEMO over @torproject / #Tor using @guardianproject #Orbot @monocles / #monoclesChat..."

    If it's easier, why isn't it as successful and used by the military etc? You seem to have dismissed video calls etc too. You could argue against that functionality for certain use cases, but it's become a core part of secure messaging over time. Maybe they just have different audiences.

    I kind of agree on Moxie's reliance on Intel SGX though. Even at its inception it worried me. But it's not part of the core E2EE protocol so could potentially be replaced.

  5. @kkarhan @mapto @yawnbox @Mer__edith

    "It's easer, faster, cheaper, more resilient, private and secure to onboard #TechIlliterates woth #XMPP+#OMEMO over @torproject / #Tor using @guardianproject #Orbot @monocles / #monoclesChat..."

    If it's easier, why isn't it as successful and used by the military etc? You seem to have dismissed video calls etc too. You could argue against that functionality for certain use cases, but it's become a core part of secure messaging over time. Maybe they just have different audiences.

    I kind of agree on Moxie's reliance on Intel SGX though. Even at its inception it worried me. But it's not part of the core E2EE protocol so could potentially be replaced.

  6. @kkarhan @mapto @yawnbox @Mer__edith

    "It's easer, faster, cheaper, more resilient, private and secure to onboard #TechIlliterates woth #XMPP+#OMEMO over @torproject / #Tor using @guardianproject #Orbot @monocles / #monoclesChat..."

    If it's easier, why isn't it as successful and used by the military etc? You seem to have dismissed video calls etc too. You could argue against that functionality for certain use cases, but it's become a core part of secure messaging over time. Maybe they just have different audiences.

    I kind of agree on Moxie's reliance on Intel SGX though. Even at its inception it worried me. But it's not part of the core E2EE protocol so could potentially be replaced.

  7. @kkarhan @mapto @yawnbox @Mer__edith

    "It's easer, faster, cheaper, more resilient, private and secure to onboard #TechIlliterates woth #XMPP+#OMEMO over @torproject / #Tor using @guardianproject #Orbot @monocles / #monoclesChat..."

    If it's easier, why isn't it as successful and used by the military etc? You seem to have dismissed video calls etc too. You could argue against that functionality for certain use cases, but it's become a core part of secure messaging over time. Maybe they just have different audiences.

    I kind of agree on Moxie's reliance on Intel SGX though. Even at its inception it worried me. But it's not part of the core E2EE protocol so could potentially be replaced.

  8. @siguza which IMHO should be illegal #rentseeking by #racketeering as #Apple has no business charging #devs that don't use their infrastructure at all.

    It's Apple's decision to not allow "#sideloading" aka. #Installing Apps outside of their Stores or rather #paywalling that.

    I wished @EU_Commission was actually staffed with competent #TechLiterates instead of #InternetPrinting #TechIlliterates like #Zensursula...

  9. @autonomysolidarity

    1. Alle vollverschlüsseln!
    2. Keine |ed nutzen [, ].
    3. Alle korrekt Ende-zu-Ende verschlüsseln [PGP/MIME für & - für ]
    4. Sichere Passwürter nutzen!
    5. Passwordmanager nutzen um sichere Passwörter zu sichern!

    Das ist so simpel dass ich das bei diversen deployed hab mit 5-15min Einarbeitung der User*innen.

  10. @autonomysolidarity

    1. Alle #Datenträger vollverschlüsseln!
    2. Keine #Backdoor|ed #Govware nutzen [#Windows, #macOS].
    3. Alle #Kommunikation korrekt Ende-zu-Ende verschlüsseln [PGP/MIME für #eMail & #XMPP - #OMEMO für #Chats]
    4. Sichere Passwürter nutzen!
    5. Passwordmanager nutzen um sichere Passwörter zu sichern!

    Das ist so simpel dass ich das bei diversen #TechIlliterates deployed hab mit 5-15min Einarbeitung der User*innen.

  11. @autonomysolidarity

    1. Alle #Datenträger vollverschlüsseln!
    2. Keine #Backdoor|ed #Govware nutzen [#Windows, #macOS].
    3. Alle #Kommunikation korrekt Ende-zu-Ende verschlüsseln [PGP/MIME für #eMail & #XMPP - #OMEMO für #Chats]
    4. Sichere Passwürter nutzen!
    5. Passwordmanager nutzen um sichere Passwörter zu sichern!

    Das ist so simpel dass ich das bei diversen #TechIlliterates deployed hab mit 5-15min Einarbeitung der User*innen.