“Early access” currently but I don’t pay for X or anything and it’s there for me. This comes after X were criticised and had all sorts of “backdoor” conspiracy theories being pushed after they took their private encrypted DMs offline the other day to add improvements.

  • pinball_wizard@lemmy.zipEnglish
    0·
    1 month ago

    When has X under Musk had anything happen to doubt their encryption?

    Musk routinely hires young unqualified technicians, and abused, laid off, or otherwise alienated much of the top talent at Twitter, in the name of cost savings.

    There’s plenty of other stories out there of Musk’s ego interfering with his staff’s ability to do their jobs properly.

    Most recently, the new DOGE has suffered substantial security lapses, associated with under-hiring and under-provisioning against cyber security threats, under Musk’s leadership.

    Even before Twitter was aquired, Twitter had an embarrassing memorable history with public figures suffering from security incidents caused by Twitter’s own staff, training, technology or processes. This was arguably not a huge problem for an almost fully public messaging platform, but could be disasterous for anyone relying on this new E2EE solution, if it is incorrectly implemented.

    The talent needed to correctly implement secure end to end encryption is rare, on a good day, for a good employer with a strong history of loyalty to their staff. X arguably has little to none of that going for it, today.

    There’s very little reason to assume that X, under Musk’s current leadership, has correctly securely implemented end-to-end encryption, and there are reasonable reasons for people to fear that E2EE developed at X may have serious security flaws.

    • FreedomAdvocate@lemmy.net.auOPEnglish
      0·
      1 month ago

      Most recently, the new DOGE has suffered substantial security lapses,

      Did they? What? The made up ones where people claimed that DOGE gave russian hackers access to databases despite DOGE never even requesting access to their systems?

      Even before Twitter was aquired, Twitter had an embarrassing memorable history with public figures suffering from security incidents caused by Twitter’s own staff, training, technology or processes.

      Funny that you say this after you said this:

      Musk routinely hires young unqualified technicians, and abused, laid off, or otherwise alienated much of the top talent at Twitter, in the name of cost savings.

      So twitters staff, training, technology and processes were the source of these embarrassing incidents…but then Musk shouldn’t have gotten rid of them?

      but could be disasterous for anyone relying on this new E2EE solution, if it is incorrectly implemented.

      And there’s nothing to say that it is incorrectly implemented other than hopes and dreams by people who want it to be.

      The talent needed to correctly implement secure end to end encryption is rare, on a good day, for a good employer with a strong history of loyalty to their staff.

      Absolutely not true lol. Secure end to end encryption is a solved problem. It’s not hard to implement.