DelI just discovered something interesting. If I hit reply to a toot, it's the time at which I do that that counts as the time I made the toot, and not when the toot actually sends (when I hit the TOOT button).
erdal@WelshPixie Very interesting, I am.going to try :)
@erdal Did it do it for you? I noticed because I opened a reply to someone, left the box open a while, meanwhile someone else replied, and after their response I wrote mine and entered it, but mine showed up before theirs.
charlag test account@WelshPixie oh, sounds like a bug. No idea why frontend decides this
Ninah Marie 🍅 (Yes, this one.)@WelshPixie 14.21 pm test ... *waits 5 minutes* *toot at 14.25 pm*
@WelshPixie but then again ... isn't that normal? If just tested this at the birdsite and it's the same.
@NinahMarie I have no idea! Just noticed it when replying to someone: started to reply, tabbed out, tabbed back in, someone else had replied, I finished mine and posted and mine showed that it had posted a fewins before the last reply
@WelshPixie oh I've just discovered that it isn't like that for me! And it shows the time when I push the toot button. I'm using Amaroq for iOS. You?
@NinahMarie Just through the Chrome browser on Windoze
Elias Mårtenson@WelshPixie that's strange. How is that possible? It would suggest that you can make a post with a arbitrary creation time.
@WelshPixie that's strange. If that's the case, then the client must be able to set an arbitrary creation time for a message. I've used the API, and it doesn't have that.
SydneyEFalkThat seems like a slight oversight that would likely get rectified, I'd hope. (I mean, I can imagine how to abuse that, and I'm not a knowledgeable exploit finder. I'm sure someone better versed in abusing bugs could go strange places with it.)