[RealAgentX]

Downloading now, will update you soon

[Frosty_y08t]

This data is useless for me, it’s not clear how to use it

[ThinkingOne]

This data is useless for me, it’s not clear how to use it

Most of the data posted on BF is useless for me... but I know that the data isn't useful for me. If it isn't clear to me how it is useful, it simply isn't useful for me. Like combolists, phone numbers of people who use a specific app, stuff like that, I could care less about. If I posted every time I saw data that I didn't understand how to use or didn't have a use for, I'd spend all day posting here!

In this case, a lot of the uses won't apply to most people. But this data does have several uses for me. One very practical, and a number of theoretical (e.g. testing/honing my data analysis skills).

[ThinkingOne]

But this data does have several uses for me. One very practical, and a number of theoretical (e.g. testing/honing my data analysis skills).

As an example of something I like to do (a variation of data forensics), I was able to gain an insight into Twitter's user numbering system. Originally, it just started at 1 (or 0)... but they were likely storing the value in 32 bits (or processing it as 32 bits), which maxes out at ~4 billion (or ~2 billion if signed). When they were at user numbers around 1.6 billion, in mid 2013, they started testing using 52 bit user numbers. Yes, 52 bits, which is an unusual number to be picking. But, it looks like they ended up going with 64 bits.

[Osirus]

Thank's, this thread will help me with my work.

[ThinkingOne]

I didn't mention in my earlier post: uncompressed, it's around 400GB of data (+/- depending on whether you count the extra data, and whether you use GB or GiB).

And sure enough, my count of number of records matches exactly what was claimed: 2,873,410,842 Twitter/X accounts.

I did detect at least some duplicate screen names (usernames, the "@" name). But that is to be expected since Twitter allows (or used to allow) changing screen names. I still have more analysis to do!

[ThinkingOne]

As I mentioned, I did detect some duplicate screen names. But over 99% of the screen names are unique. After loading all 2.8B screen names into memory, sorting, and getting counts for each, there were 2,857,762,473 unique screen names.

[termit]

As I mentioned, I did detect some duplicate screen names. But over 99% of the screen names are unique. After loading all 2.8B screen names into memory, sorting, and getting counts for each, there were 2,857,762,473 unique screen names.

Thanks for the analysis, but besides working out analytical scripts, how can this array be useful?

[ThinkingOne]

Thanks for the analysis, but besides working out analytical scripts, how can this array be useful?

Like most stuff posted here, it is valuable to some people and useless to others, depending on individual needs/skills.

Really, the big question is whether there's a dataset out there with emails, phones, or other similar details. My best guess is that a Twitter employee walked out with this, and they may well have had access to more. And if it was an outside job, if someone managed to enumerate usernames, they may well have more. Or if not the person who released this, someone else.

For me, I'm going to index the names, and possibly screen names. That way, if I'm searching for a name, Twitter screen names will appear along with everything else. Not sure yet what else I may do with the data.

I'm sure some people will cross-reference with the previous Twitter leaks (e.g. the one with 200M emails) to expand on them. Others may use it for competitive intelligence (e.g. how many new accounts were created each day).

[Frosty_y08t]

Need to check, thanks