@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

@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.

@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)

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

@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?