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 What are they then? Mastodon sends its IDs as strings too because of JSON integer overflow
@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?..
@tootapp l we do it as well for the same reason and I made sure that SQLite will do the thing I need.
https://github.com/tuskyapp/Tusky/blob/3ab78a19bcf9fa9212f27869805ca653d6638bfb/app/src/main/java/com/keylesspalace/tusky/db/TimelineDao.kt#L44
What do you use for such persistence?
@charlag Custom hash table database, as no existing solution worked without massive bloat.
@lain @charlag @Gargron @WAHa_06x36 Except Toot!, because you broke a core assumption of the Mastodon client API that I am relying on.
@tootapp @lain @Gargron @WAHa_06x36 could you... decode this number? It's still a number, right?
@charlag @lain @Gargron @WAHa_06x36 It’s too big to fit the hash table, and of course I have no guarantee Pleroma won’t just change its mind again.
@lain @charlag @Gargron @WAHa_06x36 I did check with Eugen that this is what is intended, and will remain the case for the foreseeable future.
@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.
Tldr: scaling + privacy.
@DetectiveHyde @lain @Gargron @tootapp @WAHa_06x36 hey, please, let's keep it civil. I see that people are annoyed and people have their own reasons to do things the way they do and the real failure is that there's no real spec.
Let's work together to solve this if you want to or do not if you don't.
@DetectiveHyde you're being passive-agressive
@DetectiveHyde no, I'm going to mute you. I'm not a garg fan, far from it
@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.
that's not really a problem: the apps we recommend people use are the ones we have certified as compatible anyway. we have never certified Toot as a Pleroma-compatible app precisely because of this attitude ;)
@DarckCrystale Yes. Looking into whether the mapping idea is feasible now.
>you broke a core assumption of the Mastodon client API that I am relying on.
An assumption that isn’t anywhere in the API spec or docs. It’s your mistake, retard. Your app broke itself. You can fix it like Subway Toot is doing or you can keep throwing a tantrum and while everyone migrates since it breaks federation. No ones going to bend over for your “assumptions”
For iOS, I recommend Amaroq.
@charlag @lain @Gargron @WAHa_06x36 I do, for the cache database layer.