4 ms·
> and also open to weird loopholes like some ppl realized you could use an archive of tweets with some scripts from a dev on github and backdate posts into Blu
by BadHumans 2y ago
> and also open to weird loopholes like some ppl realized you could use an archive of tweets with some scripts from a dev on github and backdate posts into Bluesky. Meaning you could write wacky tweets like from Sept 11 2001 etc and they're all sitting there on the network like they 'happened' weirdly with comments from 2024
This sounds like a critical issue that should've been fixed as soon as possible.
- ChrisArchitect 2y agoof course. while I do appreciate the advantages it might offer for quick migration/onboarding...(how great to migrate your entire twitter history into place) to get a bunch of ppl onto the network, but it being abused to change history is a no-no. I'm all for open web/indie web/ability to move your data around but let's not pretend ppl were on Blue Sky for a decade. Sigh.
- jazzyjackson 2y agoI don't want see how it's different than wordpress. I can change my own history. I guess it's about user expectations and media literacy, knowing who published the timestamp. With social media it's the platform time-stamping it, with self published media you have to decide if the source is trustworthy.
- Retr0id 2y agoThis is how the whole rest of the web works, though. I can backdate my self-hosted blog articles to whenever I want. Heck, I can even backdate my git commits to whenever I want. There is a safety issue here in practice and I don't want to downplay it (it violates user expectations), but I don't think it's "obviously" bad.
- BadHumans 2y agoI think the violation of user expectations is much more severe on a micro-blogging platform like Twitter or BlueSky than it would be on git commits and even website blog post because of how that information is consumed.
- pfraze 2y agoYeah I think so too. The application should be giving best-effort witness times.