Kevin :v_greyace: :vp:'s latest activity
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@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.
…See more
@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.
See less
@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.
@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.