- user ID and screen name
- number of followers
- number of tweets
- source of last Tweet (e.g. TweetDeck)
- location and timezone
- profile is protected or verified
I'm not sure that headline is very sensible to propagate.
Yes it was removed the UI, but if you browse Twitter with developer tools open to the Network tab you can still find the posting client in the API response JSON when viewing a Tweet.
That's not quite correct.
It is no longer visible on the website itself, or within the mobile clients. But if you inspect the requests, you can still see things like
source: <a href="http://twitter.com/download/iphone" rel="nofollow">Twitter for iPhone</a>
>Their theory that a disgruntled employee leaked the data during the layoffs remains unconfirmed, and there’s no concrete evidence to support it; it is only a plausible hypothesis given the timing and internal mess at X.
This is just information that was publicly visible previously. Someone could see almost all of this on old archive.org pages. The current UI hides some of it but it’s not like this is secret.
Or you could use Bluesky where all the public data can be replicated, by design. Someone is working on showing how a live replica can be implemented on a Raspberry Pi. [1]
(The scale is much smaller than Twitter, though.)
Since it's public anyway, it's hard to say if being able to copy all the data is good or bad. There are tradeoffs.
We allow it for a public git repo. Is social media different? [2].
Clickbait. Leak has irrelevant and useless data. Why anyone would bother to "steal" this data I have no clue. Almost all of it could be collected if you scraped the site over time.
17 comments
[ 2.8 ms ] story [ 36.5 ms ] thread- probably all the data isn't from X
- the data seems to be all public - e.g.
I'm not sure that headline is very sensible to propagate.magnet:?xt=urn:btih:c963982c4ffa264fe76ec5918f83dd775521201b&dn=twitter_users_csv&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.opentrackr.org:1337/announce
I wonder if the public is fully insensitive to these leaks now that we seem to have a big leak every other day.
>Their theory that a disgruntled employee leaked the data during the layoffs remains unconfirmed, and there’s no concrete evidence to support it; it is only a plausible hypothesis given the timing and internal mess at X.
(The scale is much smaller than Twitter, though.)
Since it's public anyway, it's hard to say if being able to copy all the data is good or bad. There are tradeoffs.
We allow it for a public git repo. Is social media different? [2].
[1] https://bsky.app/profile/why.bsky.team/post/3lkwg2djrfk23
[2] The tree ring model of culture and politics - https://vitalik.eth.limo/general/2025/03/29/treering.html
EDIT: That was apparently a mistake. Still, not all of the data in the dump is public or useless.
If this leak proves that more than 80% of Twitter accounts are bots, it should cause some damage