@daniel No. We aren't going to tackle that until we...

Ivory by Tapbots :emoji_wink:'s posts Post Back to profile

@daniel No. We aren't going to tackle that until we are done with all the major features/improvements that affect all users. That will be a huge undertaking.

Like 8 July at 14:27 | Open on tapbots.social

5 comments

Dominic Hopton

@ivory @daniel what’s the context on why/when non-numeric ids will be impactful?

8 July at 14:32 | Open on mastodon.social

Daniel :nixos:

@grork @ivory Short version: It doesn’t affect Mastodon itself, but other server implementations (one ex. being all the Misskey forks) provide a Mastodon-compatible API that uses alphanumeric status IDs, which is the main reason why Ivory doesn’t work with non-Mastodon servers.

The Mastodon spec states that status IDs are not guaranteed to be numeric, they just are in practice: https://docs.joinmastodon.org/entities/Status/#id

8 July at 14:39 | Open on mastodon.kempkens.io

Dominic Hopton

@daniel @ivory oh! Interesting. Thank you!

8 July at 15:26 | Open on mastodon.social

Jiri R.

@ivory @daniel What’s weird (actually good) is that accounts from those instances can be followed and display properly in the timeline. Could we use accounts in those instances maybe in read-only mode? I’m just curious what’s the issue there.

8 July at 14:33 | Open on mastodonczech.cz

Mike Lapidakis

@ivory @daniel Would love to see this as well! Hoping for support for @gotosocial in the future.

8 July at 14:45 | Open on gts.lapidak.is