cross-posted from: https://fedia.io/m/fedia/t/349909
As you are all painfully aware, kbin has been my nemesis pretty much from the start. Unlike Lemmy, Mastodon, Firefish, writefreely, akkoma, synapse, pixelfed, and peertube, I simply cannot competently run kbin. It's a complete goat rodeo of database errors, kbin and lemmy aren't getting along, and so on. Though I love the idea and trajectory of Kbin, it simply needs a more time to cook in the oven before being ready.
I will contrast lemmy (infosec.pub) with kbin on fedia.io: fedia.io runs an separate app server and database server. Both servers are larger than the single server that infosec.pub runs on, yet infosec.pub has about 10x the traffic, and kbin is struggling under the load.
If this were all I did, I could likely sort out the various database layout issues and make contributions to fix the code, since I am somewhat familiar with php. Unfortunately, I don't. And more than that, I have observed a general slowdown in the rate of contributions to the code base of kbin, leaving me to think that it's not going to get better any time soon.
I don't take this decision lightly, and I kicked the can down the road for a long time hoping to find a way through so that I didn't have to do this, but I have to face facts: it's not getting better and I see nothing that is going to change that.
Most unfortunately, kbin has no options for account migration, which makes this all the more painful. My intention is to shut fedia.io down at the end of November.
I am intending to resurrect it as a lemmy instance, assuming I can sort out how to ensure there are no issues with account keys.
My sincere apologies for this...
Jerry
So the entire Fediverse is illegal throughout EU under GDPR Article 17 then? That seems way too major of an issue that this was just overlooked when developing the protocol.
EDIT: Since the replies were not helpful, I researched myself and got an answer surprisingly fast. Lemmy pull request "after 30 days, replace comment.content and post.body with 'Deleted'" merged into LemmyNet:main on Jun 26. So at least Lemmy is safe in that regard.
This topic has been brought quite a few times earlier.
When you close your Gmail or Outlook email account, can you ask Google or Microsoft to ensure that copies of your emails are deleted to all the recipients you ever sent emails to?
That comparison makes no sense. e-mail is no public forum. In case I've mailed a mailing list and the archive is public, I have only the mailing list owner to ask for deletion from the archive. Private mails cannot legally be published.
I think this will end up being the same case as things that end up on search engines. I.e. you'll need to send hundreds of right to be forgotten requests to every service.
As I've written into edits of my previous comments: Lemmy pull request "after 30 days, replace comment.content and post.body with 'Deleted'" merged into LemmyNet:main on Jun 26. So at least Lemmy is safe in that regard.
GDPR isn't specific to public forums.
The context here is obviously about removing public posts, not private e-mails from the servers of the recipients.
Yes, my point is that context is irrelevant.
No. The servers that host your account comply with GDPR. If you post something on reddit and, for example, archive.org scrapes the post, reddit is not responsible for that. Adding to that, there is no personal information transmitted between Lemmy servers, only the name of your account and the content of the post.
But ActivityPub is push-based. Each Lemmy server is actively pushing its content to other servers that house subscribers.
So is email