![](/static/497bcadb/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/st9xYggWap.png)
From the blog
Something that I notice said consistently by those who have little experience in Lemmy admin spaces is “why not just contribute then?”
And the answer people try. And this happens. This unfortunately leads into the next point that is the developer teams behavior. As well, highlighted above in the blog post of that Lemmy user who unfortunately had to deal with devs behavior themselves.
From https://programming.dev/post/5180682
I will no longer be able to assist with development nor debugging actual issues with the software… Quite juvenile behavior from the devs. It stemmed from this issue where the devs continuously argued in public by opening and closing an issue. Anyway, thought I would keep y’all apprised of the situation, since these are the people maintaining the software you are currently using.
Root issue: https://github.com/LemmyNet/lemmy/issues/234
1st snowe’s comment
This is a really weird thing to have an argument about. Scheduling client side would be a nightmare, like how Microsoft Outlook handles emails where you schedule an email for the morning, close your laptop, and then the email doesn’t send because your laptop is asleep.
But even then arguing about it through reopening and closing an issue is really weird. Leave the issue open, have a discussion, talk about the pros and cons of putting it in the software, and then make a decision with the community.
2nd snowe’s comment
And then marking the most relevant comment in the thread as off-topic. You’re really alienating your users and server admins with this. Have the discussion like adults.
Full of .
There’s hardly any arguing if you look at the timeline of the 2 devs’s comments. 7 days temp ban to chill looks ok to me.
Software engineer full-time ~70k/year, lemmy dev 24k/year. You should look into the mirror.
And it’s not that the devs won’t fix the issue but there are other issues with more priorities than this. Europe is not the only continent. So just like any other FOSS projects, wait for it or smash money if it’s really important or do it yourself.
Btw based on Nutomic’s comment, it’s fixed next release if you bother to look before making 2 articles back to back.
spoiler
Unfortunately there was some miscommunication in this issue and we failed to get to the root cause. In fact the Lemmy backend has an option to delete all content when an account is deleted. This used to be the default behaviour but was changed in 0.19 so you need to set a parameter delete_content. We failed to add a checkbox for this parameter to lemmy-ui.
However the checkbox is added now in #2385 and will be included in the next Lemmy release. Other frontends and clients may also need to adjust the delete_account api call.