3 ms·

> (you can't actually move your posts) You can export and import, I believe, for some instances but generically re-posting them to a new instance with the old

> (you can't actually move your posts) You can export and import, I believe, for some instances but generically re-posting them to a new instance with the old date isn't currently feasible[0], correct. You also need to re-federate them to get the "links" correct (and probably de-federate the old) which causes confusing results if your client doesn't handle backdated posts correctly (and most of the ones I was using in 2023 didn't.) There's probably a solution[1][2] but I think it's something the ActivityPub people just haven't given much thought to just yet. [0] No date field in https://docs.joinmastodon.org/methods/statuses/#create https://docs.joinmastodon.org/methods/statuses/#create [1] When I was importing a 10 year Twitter history to my Akkoma instance, I just tweaked the code to a) allow backdating posts, b) allow certain accounts to backdate posts and c) not federate backdated posts from those accounts. Doesn't really solve the full problem but worked for me. [2] Obviously there's other problems such as people creating fake history, etc., if you're allowed to post backdated statuses.

simgt 2y ago
> [2] Obviously there's other problems such as people creating fake history, etc., if you're allowed to post backdated statuses. I don't think it's a problem really, but I may be mistaken about what the goal of these platforms is. I can also create a fake history on a blog or news site and backdate posts. But in the odd case where it matters, say for a copyright dispute or something, it'd be very hard to pretend that the history is legit and very easy to find clues that it is not.
- zimpenfish 2y ago
  > I can also create a fake history on a blog or news site Without the implied "authority" of something like Mastodon[0] or Twitter[1], or Facebook, etc. though. You can (currently) point to a post on a $BIGNETWORK and say "I posted that then" and be credibly believed. If you allow backdated (or timestamp-edited) posts, that goes out of the window, surely. [0] Ok, not if you're running your own instance, obviously. [1] Who resisted adding editing for years for similar reasons.

simgt 2y ago

> [2] Obviously there's other problems such as people creating fake history, etc., if you're allowed to post backdated statuses. I don't think it's a problem really, but I may be mistaken about what the goal of these platforms is. I can also create a fake history on a blog or news site and backdate posts. But in the odd case where it matters, say for a copyright dispute or something, it'd be very hard to pretend that the history is legit and very easy to find clues that it is not.

zimpenfish 2y ago
> I can also create a fake history on a blog or news site Without the implied "authority" of something like Mastodon[0] or Twitter[1], or Facebook, etc. though. You can (currently) point to a post on a $BIGNETWORK and say "I posted that then" and be credibly believed. If you allow backdated (or timestamp-edited) posts, that goes out of the window, surely. [0] Ok, not if you're running your own instance, obviously. [1] Who resisted adding editing for years for similar reasons.