Returned IDs are too long on android

[retrofoxxo]

User ID's returned in responses like home_timeline.json and verify_credentials.json are too long (official twitter used userIDs that were 8 numbers long and the returned ones are waaay past that) and will cause the twitter app atleast on Android (Twitter 3.3.0) to crash upon signin when loading verify_credentials and home_timeline

Normal
"id": 38895958,
"id_str": "38895958",

Your Server
"id":283395592579709281758564413673324624175827949382450

Also on an possibly related note, your server seems to be missing the id_str field in some responses like verify_credentials and home_timeline

[Preloading]

I've noticed that the android app likes to crash on view on anything, but I wasn't sure why. I do have to make the IDs really long or else I can't have it be an integer, since bluesky IDs need to store for a message the user DID, ID type, and rkey (iirc). I have to add on to these the date it was posted, and if it is a retweet, the retweeted, since bluesky won't give me the repost ID in the timeline.

For it not including id_str, that would probably be partly why. I'll go look at that later.

[retrofoxxo]

Alright, from my earlier attempts it most likely would be idstr missing as the client is very stingy on things missing, however long id's wouldn't really make the sign in crash, albeit long id's do cause crashes whenever for example clicking on posts

[Preloading]

I fixed id_str, but it still would crash. I set all IDs to be randomly generated 64 bit ints, and it no longer crashes. This is very bad.

[Preloading]

Fixed with #27