From a90b78c06259120b65ba143184c962afab0b2dea Mon Sep 17 00:00:00 2001 From: =?utf8?q?Joann=20M=C3=B5ndresku?= Date: Wed, 23 Feb 2022 16:59:55 +0200 Subject: [PATCH] Why I can't enable registrations. --- articles/why-i-cant-enable-registrations.md | 47 +++++++++++++++++++++ templates/index_header.html | 2 +- 2 files changed, 48 insertions(+), 1 deletion(-) create mode 100644 articles/why-i-cant-enable-registrations.md diff --git a/articles/why-i-cant-enable-registrations.md b/articles/why-i-cant-enable-registrations.md new file mode 100644 index 0000000..f7e4bde --- /dev/null +++ b/articles/why-i-cant-enable-registrations.md @@ -0,0 +1,47 @@ +Why I can't enable registrations + +If you've used any of my services, you have more than likely have had +to use it as a guest rather than a registered user. There's one simple +reason why I can't allow you to. GDPR... and lack of helping the little +guy with it. + +## The case of Matrix +I love [Matrix](https://matrix.org/) - I would love to contribute to the +wider ecosystem of it with my homeserver, but I've always had to shut +down requests of people wanting to register an account in my homeserver +if I do not know them. + +The annoyance comes from the fact that Element **[only covers their own asses.](https://matrix.org/legal/privacy-notice)** +I would love to add a privacy notice and easy methods to remove all user +data whatsoever. I would love to open registrations for many services. +However, I wouldn't like to get a GDPR fine for being in violation of the +law. You cannot easily readapt the privacy notice for Synapse and Element. +They're written on a scale of a business - the only templates in repositories +are ones for Element themselves. I have tried rewriting one of their GDPR +and privacy notices to no avail - it's full of legalese jargon that is hard +to read for a normal person. + +## Okay? Matrix has a deactivate button. +That isn't GDPR compliant still. It doesn't fully erase all of your data. +It only wipes your profile data, which can still be retrieved from the +channels that the user was partaken in. Not only that, but you cannot remove +data from other homeservers - this is a huge red flag in data sharing. + +## What about this other service you're hosting? +There is even less of a legal notice put up for those. If you find a reasonable +legal notice anywhere that can be adapted by an individual, not a business, +please let me know. + + + +**TL;DR** - GDPR non-compliance if I would enable. No safety net either by +the bigger projects, only to cover businesses. Smaller projects tend +to not even have any documents in first place. + + +Thanks for reading +- Cernodile + +;tags:rant gdpr privacy site future +;description:If you've used any of my services, you have more than likely have had to use it as a guest rather than a registered user. There's one simple reason why I can't allow you to. GDPR... and lack of helping the little guy with it. + diff --git a/templates/index_header.html b/templates/index_header.html index 13cf453..6dca8a7 100644 --- a/templates/index_header.html +++ b/templates/index_header.html @@ -14,6 +14,6 @@ < Last-Modified: Doesn't need to be modified, is perfect as-is.
< Connection: keep-alive

based

-

Quick-links to services I host: Invidious, Searx, Piped.

+

Quick-links to services I host: PeerTube, Searx, Piped.

Hall of Based: ReactOS, Matrix, PostmarketOS, Pine64, Landchad.net

Personal Blog of Cernodile

-- 2.25.1