PSA: you can't delete photos uploaded to #lemmy. So don't (accidentally) upload a nude to lemmy. That would be bad 😱
PSA: you can't delete photos uploaded to #lemmy. So don't (accidentally) upload a nude to lemmy. That would be bad 😱
This article will describe how lemmy instance admins can purge images from pict-rs.
 |
|---|
| Nightmare on Lemmy Street (A Fediverse GDPR Horror Story) |
This is (also) a horror story about accidentally uploading very sensitive data to Lemmy, and the (surprisingly) difficult task of deleting it.
You're viewing a single thread.
You clearly put a lot of effort into writing this blog post, creating the header image and sharing it across dozens of Lemmy communities and Github issues. I only wish you would put even a fraction of this effort into actually resolving some of the mentioned issues. After all you are a programmer and many of them are relatively easy to resolve with a bit of time.
What you dont seem to realize is that Lemmy only has two fulltime developers (Dessalines and me). We are both working every day to fix bugs and implement new features in Lemmy, but there are only so many hours in a day. Whenever we resolve one issue, a new one gets reported so its impossible to resolve all of them. The repos for lemmy and lemmy-ui currently have 750 issues. So there is no other way but to strictly prioritize what we work on, and ignore things we dont have time for. Obviously people will disagree with the exact priorities, that is inevitable.
The only solution is to get more contributors who help work through the issue backlog. Or if you are not willing to do that, switch to a different platform which is backed by venture capital and can pay dozens of developers to work on it.
Did you read the article and the feedback that you've received from your other users?
Any FOSS platform has capacity issues. I run my own FOSS projects with zero grant funds and where I'm the only developer. I understand this issue.
What we're talking about here is prioritization. My point is that you should not prioritize "new features" when existing features are a legal, moral, and grave financial risk to your community. And this isn't just "my priority" -- it's clearly been shown that this is the desired priority of your community.
Please prioritize your GDPR issues.
I bet your project doesnt have 50.000 monthly users so its not comparable at all. Out of all these users only you and one or two others care so much about GDPR (yet not enough to make actual contributions yourself). We really cant change our priorities for a single user out of thousands.