3 ms·
Is that a design descision, or just something that's not implemented? Adding an 'originally-posted' field to exports, and allowing mass-posting on the target s
by throwawaymobule 3y ago
Is that a design descision, or just something that's not implemented?
Adding an 'originally-posted' field to exports, and allowing mass-posting on the target should technically work, and non-technically be a tricky problem.
- wlonkly 3y agoTo be honest I'm not sure, I've stayed mostly away from core Mastodon development, happy to just be a user.
- zimpenfish 3y ago> Is that a design descision, or just something that's not implemented? The Mastodon API (currently the defacto API for Fedi clients) has no support for backdated posts (see [1]) and servers will push out any status you create to your followers which would mean a deluge of previously seen content. Backdating and a flag for "do not push out backdated posts" could be added[2] but there's a whole raft of problems that come along with it (resource usage for large accounts, who can use the functionality, how do you stop abuse, etc.) [1] https://docs.joinmastodon.org/methods/statuses/#create https://docs.joinmastodon.org/methods/statuses/#create [2] I fudged this into my Akkoma instance to let me backfill history from a Twitter bot.