{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@clacke @atomicpoet That does not seem plausible to me, post content is HTML, plus Mastodon sanitizes it to safe tags, I can’t see how a client implementation could mess that up in a way that only affects a specific origin server software. IDs have always been stringified integers in the Mastodon API though.

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Kevin :v_greyace: :vp:

@Gargron @clacke @atomicpoet Problem was some clients were expecting status IDs to always be castable back to integers even though the Mastodon API doc explicitly states its not guaranteed to be a number. Which caused issues with some non-Mastodon hosts that supported the Mastodon API but used both letters and numbers in their status IDs.

0
1y
Replies