Jump to content

FEITI99

Noob
  • Posts

    5
  • Joined

  • Last visited

Everything posted by FEITI99

  1. FEITI99

    User Security

    Yes 🙌 would love more clarity from Eddie and the team.
  2. FEITI99

    User Security

    I received an email from Stake informing me that my personal data was involved in a breach through one of their third-party providers, Mixpanel. While the message repeatedly reassures users that “funds and passwords are secure,” it raises far more concerns than it answers. Let’s be clear: usernames, emails, phone numbers, and dates of birth were exposed. That’s not harmless metadata - that’s exactly the information scammers need to run targeted phishing attacks, SIM-swaps, and impersonation scams. Saying “your funds are safe” doesn’t undo the fact that our identities were partially handed over. Stake claims their infrastructure wasn’t accessed. Fine. But that leads to a bigger question: why does an analytics company need access to users’ dates of birth and phone numbers in the first place? What business purpose justifies that level of personal data sharing? The breach reportedly happened via an SMS phishing attack and was “stopped that weekend,” yet attackers still managed to export files before containment. How long did they have access? How many users were affected? And why are we only hearing about this after the fact, once the damage was already done? We’re told that “online monitoring services” are in place. That sounds reassuring, but it’s vague. Are users being actively notified if their data appears in breach databases or dark-web markets? Or is this just a box being ticked to say something is being done? What’s especially frustrating is that the burden is once again shifted onto users. We’re told to stay vigilant, avoid scams, and enable passkeys or 2FA - all good advice, but advice that comes after our data has already been exposed. If these protections are now being strongly recommended, why weren’t they pushed harder before a breach occurred? And let’s not ignore the accountability issue. I didn’t choose Mixpanel. I chose Stake. Any third-party risk is still Stake’s responsibility, and users shouldn’t be expected to accept “it wasn’t us” as a satisfactory explanation. Transparency isn’t just admitting something went wrong. It’s explaining why it was possible, what data truly wasn’t necessary to share, and what will change so this doesn’t happen again. Right now, the message feels less like accountability and more like damage control - and users deserve better than that.
  3. Tis the night before Christmas… Trainwrecks takes a deep breath, clears his throat, immediately misreads the next line, blames the font, blames the mic, blames chat, and somehow pivots into a 15-minute rant about variance, slots, and how Santa is definitely down lifetime. The fire’s crackling, the vibes are festive, chat is moving at Mach 10, and the Christmas spirit is slowly replaced by Greek accents, bonus buys, and “ONE MORE SPIN” energy. Somewhere along the way, Rudolph is gambling his red nose, the elves are on payroll, and Santa’s sleigh is sponsored. It’s warm, it’s chaotic, it’s completely unhinged - and honestly, you wouldn’t want it any other way. 🎅 Yours truly, Stake ID; Feiti99
×
×
  • Create New...

Important Information

Privacy Policy Terms of Use