this post was submitted on 11 Jun 2023
1 points (100.0% liked)
/kbin meta
639 readers
1 users here now
Magazine dedicated to discussions about the kbin itself. Provide feedback, ask questions, suggest improvements, and engage in conversations related to the platform organization, policies, features, and community dynamics. ---- * Roadmap 2023 * m/kbinDevlog * m/kbinDesign
founded 1 year ago
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When you create a new post it is first saved on your instance (where your user is registered). Then your post will be pushed to all other instances (servers) where any user has registered the magazine (sub) you are posting to. The instances will then save the post to their database.
If you want a post to be deleted you have to contact the administrator of the original instance (as you said). once the post is deleted there, a delete message should be pushed to all other instances that received the post. The instances will then also delete the post to their database.
So it acts as a mirror if a user here is subscribed to that instance, but that mirror would also reflect a take down by an admin. There's no protection of content possible.
It's more of a "this was deleted, we suggest you do it too". Ultimately it's open source so anyone can modify this stuff to their liking and individual instances can choose to go along with a delete suggestion or not.
You should theoretically also be able to tag something as deleted but only actually delete it after a week (for example). This would comply with regular delete suggestions and keep things synchronized as one would expect but would give a bit of time to defend against an instance going rogue and self destructing.