Conversation

Notices

1. Toot!.app ↙︎↙︎↙︎ (tootapp@mastodon.social)'s status on Sunday, 27-Jan-2019 01:01:19 JST Toot!.app ↙︎↙︎↙︎

   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.

   • Maya Minatsuki :neko_smiley:, らりお・ザ・何らかの?然㊌ソムリエ and rinsuki???????????? repeated this.
   • Eugen (gargron@mastodon.social)'s status on Sunday, 27-Jan-2019 01:03:21 JST Eugen

     in reply to

     @tootapp What are they changing?

     rinsuki???????????? repeated this.
   • Dag Ågren ↙︎↙︎↙︎ (waha_06x36@mastodon.social)'s status on Sunday, 27-Jan-2019 01:03:53 JST Dag Ågren ↙︎↙︎↙︎

     in reply to

     • Eugen

     @Gargron @tootapp IDs are no longer 64-bit integers.

     rinsuki???????????? and らりお・ザ・何らかの?然㊌ソムリエ repeated this.
   • Eugen (gargron@mastodon.social)'s status on Sunday, 27-Jan-2019 01:05:05 JST Eugen

     in reply to

     • Dag Ågren ↙︎↙︎↙︎

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

     rinsuki???????????? and らりお・ザ・何らかの?然㊌ソムリエ repeated this.
   • Dag Ågren ↙︎↙︎↙︎ (waha_06x36@mastodon.social)'s status on Sunday, 27-Jan-2019 01:05:49 JST Dag Ågren ↙︎↙︎↙︎

     in reply to

     • Eugen

     @Gargron @tootapp Base-62 encoded 128-bit integers.

     rinsuki???????????? and らりお・ザ・何らかの?然㊌ソムリエ repeated this.
   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 03:38:04 JST tateisu​ :force:​:r_9a:

     • Eugen
     • Dag Ågren ↙︎↙︎↙︎
     • Charlag
     • sasori

     @lain @charlag @Gargron @tootapp @WAHa_06x36 @dgold @shadowfacts You should have cooperated with more application developers. This situation could be avoided if hearing with the application developer in advance rather than trusting only insufficient documents.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 03:55:06 JST tateisu​ :force:​:r_9a:

     • Eugen
     • Dag Ågren ↙︎↙︎↙︎
     • Charlag
     • sasori

     @miya @charlag @dgold @tootapp @WAHa_06x36 @lain @Gargron @shadowfacts
     We have never expressed Pleroma support, then so the frequency of looking at Pleroma's community is very low. https://mastodon.juggler.jp/@tateisu/101436082701177563

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 10:40:51 JST tateisu​ :force:​:r_9a:

     • Eugen
     • Charlag
     • sasori

     @miya @charlag @lain @Gargron @tootapp
     both of id="9" and id="101485946909733057" are valid id in Mastodon, also it's clear that "9" is older than "101485946909733057" by historical reason. this is not assumption. Pleroma introduce strcmp() instead of numeric compare, it breaks Mastodon API.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 11:51:00 JST tateisu​ :force:​:r_9a:

     in reply to

     • Eugen
     • Charlag
     • sasori

     @miya @charlag @lain @Gargron @tootapp I wrote PR for mastodon API document and it's merged. https://source.joinmastodon.org/mastodon/docs/merge_requests/18/diffs now API document says ID is string representation of 64 bit integer and comparing order is numeric.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 21:54:54 JST tateisu​ :force:​:r_9a:

     • Eugen
     • Dag Ågren ↙︎↙︎↙︎
     • Charlag
     • sasori

     @dgold @lain @miya @charlag @WAHa_06x36 @tootapp @shadowfacts @Gargron You should not use the API document as a disclaimer to force app developers to respond.
     The API document is originally intended to make an application using the API. We do not generate IDs by the application, so it usually is not necessary to describe how the ID should be generated.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 22:11:03 JST tateisu​ :force:​:r_9a:

     • Eugen
     • sasori

     @dgold @lain @shadowfacts @Gargron

     The Mastodon API document is not intended to create compatible APIs. It is intended to create an application using Mastodon's API.
     After seeing your(s) point of view, I felt "part of the information necessary for creating the application is undocumented", so I provided a short 1-line PR.
     I just revealed the undocumented part, so I think that there are no Mastodon applications whose implementation will be changed by this PR.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 22:15:58 JST tateisu​ :force:​:r_9a:

     • Eugen
     • sasori

     @dgold @lain @shadowfacts @Gargron
     As already mentioned by Gargron in this conversation, the Mastodon API is not intended to be used throughout Federation. Mastodon 's ecosystem does not have to take care of changes made by Pleroma.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Sunday, 27-Jan-2019 22:38:31 JST tateisu​ :force:​:r_9a:

     • Eugen
     • sasori

     @Gargron @dgold @lain @shadowfacts
     However, in reality, there are only two options: "Pleroma withdraws breaking ID modification" or "support for Pleroma ID by application developer (who not saying support for Pleroma)"
     If they keep singing "Mastodon API compatible" without retracting anything, that would be bad news for app developers.

   • tateisu​ :force:​:r_9a: (tateisu@mastodon.juggler.jp)'s status on Monday, 28-Jan-2019 12:00:05 JST tateisu​ :force:​:r_9a:

     • Eugen
     • Charlag
     • sasori

     @miya @charlag @tootapp @lain @Gargron既にrevertされた 私のPRですが、それはAPI利用者に必要な記述という範囲の内部です。それまでundocumentedだった部分を記述しただけです。