![](/_next/image?url=https%3A%2F%2Fstorage.googleapis.com%2Fmantic-markets.appspot.com%2Fcontract-images%2Fthe_coproduct%2Fw6bfqsoo0h.jpg&w=3840&q=75)
A supposed leak from Okta (screenshot below) is purported to show that X has a list of users who are exempt from filters which scan for TOS-violating usage of slurs. X has banned the user who initially shared the supposed leak and is tagging posts containing the list as containing manipulated media (ex.: https://x.com/brndxix/status/1816231803973521728).
![](https://firebasestorage.googleapis.com/v0/b/mantic-markets.appspot.com/o/user-images%2Fdefault%2FJRXNKa7jcr.png?alt=media&token=ec0a68c0-deb1-4e88-adc9-b2715bf60a4f)
This market aims to predict whether this list will be proven to be real, proven to be fake, or not conclusively proven to be real or fake until the 31st of August, 2024.
Related questions
🏅 Top traders
# | Name | Total profit |
---|---|---|
1 | Ṁ3,145 | |
2 | Ṁ70 | |
3 | Ṁ62 | |
4 | Ṁ59 | |
5 | Ṁ26 |
I think @yetforever's evidence is sufficient to show that the list is >95% likely to be fake and will resolve accordingly.
@yetforever you've been buying a lot of "proven fake" shares. Any evidence you'd like to share? Because I haven't really seen anything convincing until now.
Sure, here's what I got! The evidence I found is this tweet by Benedict Garman, where he says, "An Okta spokesperson told me, 'We can confirm that this is definitely an invalid url and we confirm the screenshot is fake.'"
Now I first thought that this was just a Twitter rando, but he's actually an independent journalist who contributes to the BBC, among others. Of course, the linked tweet above is in his own name rather than any media outlet, but I think it's fair to assume he's following basic journalistic standards, such as, at a baseline, truthfully reporting what Okta told him. So I think this tweet is nearly as good as an actual news headline saying "Okta spox: Twitter leak is fake", which is about as convincing evidence as you can hope for.
(There's also additional issues with the "leak", in particular the invalid hostname, the bad SSL cert, and the fact that a piece of backend configuration is supposedly stored on Okta, which is an authentication provider. I think these essentially amount to seeing a merged finger and an extra limb in a photo, but the official confirmation from Okta above is what I would count as the most convincing piece of evidence here.)