Hollo's avatar
Hollo

@[email protected]

For those who want to use on @ivory: evolved from the Tweetbot codebase, which was a third-party Twitter client, so it assumes that object IDs are integers. Hollo uses UUIDs for object IDs, so it can't be used with Ivory at this time. We hope that Ivory will support non-integer object IDs in the future!

fedicat's avatar
fedicat

@[email protected] · Reply to Hollo's post

@hollo @ivory same issue with gotosocial and iceshrimp.net I believe

fedicat's avatar
fedicat

@[email protected] · Reply to Hollo's post

@hollo @ivory for your reference

github.com/superseriousbusines

kb.iceshrimp.dev/s/docs/doc/fr

nSonic's avatar
nSonic

@[email protected] · Reply to Hollo's post

@hollo @ivory I thought it evolved from the app.net client (netbot or similar)? But ok, that one surely evolved from Tweetbot.
Strange that with the generalization of the code base the ids are still integer - so app.net had int too back in the days? Interesting. I had assumed everything is UUID because of „easier, no need to remember or read the last id to add one“ etc 😄

Ivory by Tapbots :emoji_wink:'s avatar
Ivory by Tapbots :emoji_wink:

@[email protected] · Reply to Hollo's post

@hollo This will change in the next update. We will soon support alphanumeric post ID’s.