Please don’t expect the community to give you answers to your questions which you then delete right afterwards. Those of us who put time into answering your questions are not doing so just to serve your personal needs, we are here to help build a community knowledge base that others can search and reference.
This has become a chronic issue with Lemmy and its starting to feel like it’s a waste of time to answer questions.


Lemmy in general, yes. Here in self hosted at least a couple of times that I’ve seen. Including earlier today. But I don’t interact on every post.
I only find out because sometimes I like to go back to posts I comment on and see what additional information people have offered. (There’s always something to learn.) Then I find the post has been deleted.
Are you sure the post wasn’t modded? Those also show up as “deleted”.
I absolutely detest how on lemmy deleting a post also nukes access to the comments. They’re still there, but there’s no way in many normally lemmy UI to get to them.
I see now there were 3 posts removed in the past that all seen relevant to the community me. Going back I see ones I’ve read and interacted with.
Seems like it might be more mod actions to me, as others have pointed out. Maybe a more general self hosted community if the mod doesn’t want those sorts of (relevant to selfhosters but not specifically selfhost software announcements or whatever) posts here.
Is there any way for a community to disallow post deletion? If not, this seems like a needed feature.
What if I accidentally posted to the wrong community? Or posted something with a username/password in it? Or accidentally selected a picture of my penis wearing a little monocle and top hat to this community?
or maybe a feature where posts cannot be deleted past a time period + amount of engagement.
Good point. If a post is two minutes old with no replies, may as will let folks change clean up their misclicks.
These would have to be added to Lemmy development, because currently I can delete a post of my own on a community on another instance and there isn’t a technical way to prevent it. Reporting and banning for behavior is tricky too unless you manage to remember the username of who posted it.
So, that’s an uphill battle at the development level and the moderation level.