So, very interesting that this account is restricted, is a friend of Lea and was created on 13th July 2020 at 22:49:17UTC, while Lea was created 13th July 2020 at 22:23:03 UTC
Also, I'm assuming you already have a Twitter dev account that you could use for this? I need to check the rate limits for user lookups but scanning an hour or two of time shouldn't take too terribly long.
) & I'm pretty well versed in the ins and outs of the free API , plus I also use Python, so no probs on those fronts ;)
I assume the way to proceed is (broadly) similar to firehose reconstruction?
Yep! Exactly. Basically we would need to create a Python method that reduces the space of user ids by taking advantage of the Snowflake algo. That involves breaking up an id into its epoch time component, server component and sequence id components.