Massive X data leak affects over 200 million users
www.techzine.eu
A self-proclaimed data enthusiast calling themselves 'ThinkingOne' has made a huge database containing 201 million pieces of user data from X freely

A self-proclaimed data enthusiast calling themselves ‘ThinkingOne’ has made a huge database containing 201 million pieces of user data from X freely available. The data is said to have come from two previous leaks and includes email addresses, locations and profile data of users of the social media platform.

  • mbirth@lemmy.mlEnglish
    32·
    2 days ago

    My email provider allows for unlimited aliases. So, while I have 600+ email addresses, emails to them all end up in the same mailbox.

    The accounts for all the websites and services (with their specific email address) are in a KeePass database and they all have random passwords, too.

    The only small issue is when you have to contact support of some service. Then, I have to configure the specific email address in my client so they can match that to my account with them. But most email clients allow multiple sender addresses without having to fiddle with the rest of the settings.

    • partial_accumen@lemmy.worldEnglish
      14·
      2 days ago

      My email provider allows for unlimited aliases. So, while I have 600+ email addresses, emails to them all end up in the same mailbox.

      I do this too. The unique email address I create for each is identifiable to the place I’m using it. This has other benefits. If an organization you created and account with sells or has a data breech you know exactly which company it was when you start receiving spam or phishing email directed to that address. This is also nice because you can “black hole” that email address and all the spam goes with it even future spam not sent yet.

      • mbirth@lemmy.mlEnglish
        16·
        2 days ago

        Exactly! I add a random string to each email address, too, so you can’t just guess other addresses. So, it’s usually something similar to lemmy-r4nd0m@mydomain.me. And, whenever a breach happens, I’ll generate a new random part and set that as my email address and invalidate the old one. Until the next breach. (Looking at you, LinkedIn…)