🇬🇧 Hi, everyone!
It seems the latest pleroma API change broke compatibility with the crossposter. If you are using pleroma, as soon as the API upgrade reaches your instance the crossposter is going to stop working. Sorry about that!
🇧🇷 Oi, gente!
Parece que a última mudança de API do pleroma quebrou a compatibilidade com o crossposter. Se você está usando pleroma, assim que a atualização da API chegar na sua instância o crossposter vai parar de funcionar. Desculpem!
@DarckCrystale I understand the feeling, but following the API development, it was never a string, only defined as so for json constraints. 🤷🏽♂️
@renatolond and therefore, people should have taken it as a string, because it was already broken once when masto passed in 2.0 *and* because ActivityPub does not specify much constraints about this field.
@DarckCrystale the way I see it is that exactly because there are no constraints on activitypub side, it's not activitypub related, it's how Mastodon saves its id. Maybe the problem is me being too close to mastodon development, because since it's bigint in mastodon, it would never be string 🤔
@renatolond so in my opinion, there is only two decent options:
- use Masto doc as a Fediverse standard, and so only use information that are explicitly written in
- create a sub standard to ActivityPub, which is what Pleroma devs are trying to do with (if I remember well its name) LitePub, and use it to dev apps
Other things like "the dev told me that…" or "it were always be this way" are shitty and unstable.
@DarckCrystale I'm all for the second option, though I still think most of the apps will need specialized APIs that are not a standard ActivityPub C2S
@renatolond yes, special cases wouldn't be a problem, but there is a looooot of things that can be standardized and would make federation easier