@3psboyd BRB becoming a time traveler.
@3psboyd "what could possibly go wrong"
@3psboyd why is that a thing
@LivingCooki So it does.
@LivingCooki Am I reading the Mastodon API correctly, and that doesn't? https://docs.joinmastodon.org/methods/statuses/#create
@LivingCooki Got it. I didn't know until just now there was a difference.
@LivingCooki@0w0.is @3psboyd@mastodon.social yeah, this is by design in AP because of: deferred posts, servers that were temporarily offline coming back online and getting a load of posts that were made while it was offline, and post importing.
@3psboyd Wwwwhhhyyyyyyyyyyyyyyyy
@3psboyd oh yeah, turns out you don't even need an API... just copy the POST request and throw it in powershell lmao
@3psboyd What could possibly go wrong with that!
@3psboyd hmm, that's concerning
@3psboyd To be completely fair, if bluesky was actually designed to be federated, time is extremely hard to deal with in federated networks. At the end, you just need to trust one side to set those timestamps correctly, and also not rely on them while displaying message / post order. For example, matrix protocol has the same issue.
@3psboyd this alone makes me want to get on bluesky