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.

@WAHa_06x36 @tootapp What are they then? Mastodon sends its IDs as strings too because of JSON integer overflow

@Gargron @tootapp @WAHa_06x36 mastodon ids are sortable strings, new pleroma ids (flake ids) are sortable strings. I think if apps stop working they made assumptions that aren't valid according to the mastodon api docs.

@lain @Gargron @tootapp @WAHa_06x36 if they're still sortable as strings, Tusky will work just fine. Not sure why it should break any other client. Does anyone really convert them to integers?..

@lain @charlag @Gargron @WAHa_06x36 Except Toot!, because you broke a core assumption of the Mastodon client API that I am relying on.

@tootapp @WAHa_06x36 @Gargron @charlag yeah, it's unfortunate. I wish it could be otherwise, but these changes were necessary long term and are (as far as I can tell) still valid according to Mastodon docs.

@lain @charlag @Gargron @WAHa_06x36 Why though? 64 bit is enough for Mastodon, why not for you? There was no problem before, but now you have introduced one.

@lain @charlag @Gargron @WAHa_06x36 The only way Toot will ever work with Pleroma again is if you have a mapping back to 64 bits, though, or if you get back to being compatible with the API as it exists in Mastodon.

Sign in to participate in the conversation
Cybrespace

cybrespace: the social hub of the information superhighway jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal support us on patreon or liberapay!