hhmx.de

Föderation EN Do 10.04.2025 13:23:23

I wish you could archive your mastodon posts, like on Pixelfed.

It doesn't delete them, and has federation side effects, but those are hidden to the user until they decide to unarchive the post.

@Claire is this something you would consider?

@dumpsterqueer does GtS support something like this? Maybe we could collab on a FEP for this to improve federation side effects

Föderation EN Do 10.04.2025 13:25:23

@dansup @dumpsterqueer what kind of side effects does it have? what are you doing on the protocol side?

this is not something we have planned for now, but it could be interesting

Föderation EN Do 10.04.2025 13:27:53

@Claire @dumpsterqueer So when you try to fetch an archived post, it will return a 404 which is what I want to address (by maybe placing some object that could say "its here, not deleted but isn't visible")

But for servers that have the post cached, and for remote users that like/comment/share, those actions are still consumed, but we hide notifications in that case.

Föderation EN Do 10.04.2025 13:35:36

@dansup @Claire I don't think it's something that would have to happen on a protocol level, just send out a Delete to remotes as normal and move the post from posts to archived_posts in your db, or set an archived flag on it or something, then return whatever status code you want to deref requests for that post (410 Gone probably)

Föderation EN Do 10.04.2025 13:36:13

@dumpsterqueer @dansup my understanding is that people can un-archive posts at any time, which brings the protocol-level complexity

Föderation EN Do 10.04.2025 13:40:22

@Claire @dansup oh right, well not sure I see the point of that but I suppose the simplest way would be sending out a Hide or Archive activity just like one would send out a Delete, then you can Undo the Hide or Archive later

Föderation EN Do 10.04.2025 13:43:29

@Claire @dansup you could also just send Deletes and let the user republish stuff later by sending out a Create again, I guess. Then you're in like recycling bin / remove from recycling bin territory.

Föderation EN Do 10.04.2025 13:47:24

@dumpsterqueer @Claire You could lose likes/shares and not to mention how some software may not handle reusing the same activity id/uri

I think your Archive activity idea is the best way to preserve the post while allowing to undo at any time without breaking or introducing more complexity regarding re-posting.

Föderation EN Do 10.04.2025 13:43:34

@dumpsterqueer @Claire Yeah the Archive or Hide activity is a great idea, we don't want to break comment threading by sending Deletes.

Föderation EN Do 10.04.2025 13:42:03

@Claire @dumpsterqueer @dansup deleting posts would also have unwanted side effects because most people don't understand Undo Delete

ideally this would be handled with something like a collection for your published posts on a profile, like how youtube does "unlisted" (not the same as mastodon "unlisted"), but that won't get understood either

seems the fallback people will have to accept is that current impls may/will continue to show these posts?

Föderation EN Do 10.04.2025 13:42:15

@Claire @dumpsterqueer @dansup the question is, a unarchived post preserves the old timestamp? If not, it can be published as new. If preserves, mastodon or gts would not put it in the timeline and they will be visible only when stalking a profile. Maybe masto and gts even reject the create activity because it's too old.