Pleroma users should be aware that Pleroma has introduced breaking changes in their implementation of the Mastodon client API, which mean Toot! will no longer work at all with the latest version of Pleroma.
Pleroma is breaking some fundamental assumptions Toot! makes about IDs, and which can't easily be changed.
@tootapp What are they changing?
@WAHa_06x36 @tootapp Is that basically UUIDs? I suppose that really fucks with the ability to calculate toot gaps (although it should still be possible with more effort if their API responses include next/prev links)
That being said, the Mastodon REST API was never intended to be used by anything but Mastodon, so maybe it's a good thing.
@charlag Custom hash table database, as no existing solution worked without massive bloat.
@DarckCrystale Yes. Looking into whether the mapping idea is feasible now.
@feld Are you saying the deva don’t know what their own code actually does?
@sascha Rewriting a custom caching database layer?
@lain Also, Mastodon IDs are *not* sortable strings, they are sortable integers, represented as strings. "9" < "10" in the Mastodon API, which is not true for regular string comparison.
@lain They don't. They are are represented as regular integers, as far as I know. Comparing them as strings is wrong.
@tootapp right, now Toot! can't be used at all to connect to pleroma instances.
@tootapp No problem. I just broke my Pleroma instance last night. 😛
@7even Nothing in this discussion is about the Fediverse, this is about the internal Mastodon client API.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!