Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a disclaimer about federation on sign up #1846

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

sunaurus
Copy link
Collaborator

@sunaurus sunaurus commented Jul 7, 2023

Description

I have seen a lot of users confused about data deletion, what is shared with other servers, etc (especially in context of the GDPR). I think it makes sense to ask for explicit consent regarding federation on user sign up. Feedback welcome!

Depends on LemmyNet/lemmy-translations#81

Screenshots

image

@alectrocute
Copy link
Contributor

I'm tempted to suggest that we add a new page that includes info like this, and link to it from the sign up form instead.

@sunaurus
Copy link
Collaborator Author

sunaurus commented Jul 7, 2023

I think most big instances already have this type of thing in /legal, but the reason I thought of adding this explicit federation consent message is that I think that it's way more user friendly than the separate legal page. My fear is that 99% of users will always skip any privacy policy type links, and thus might not fully understand what they're signing up for.

@alectrocute
Copy link
Contributor

alectrocute commented Jul 7, 2023

I think most big instances already have this type of thing in /legal, but the reason I thought of adding this explicit federation consent message is that I think that it's way more user friendly than the separate legal page. My fear is that 99% of users will always skip any privacy policy type links, and thus might not fully understand what they're signing up for.

Sure, good point, but I’ll counter with: we don’t even have a ‘I agree to…’ checkbox or link to a TOS at all on this sign-up page. I think that would be a clean middle ground.

@wiki-me
Copy link

wiki-me commented Jul 8, 2023

Starting to try to educate users on online privacy is a whole seperate thing IMO, maybe we could link to some other site, for example most users probably don't know services even for big and "successful" companies like google or facebook get hacked, or that information about username and email from multiple hacks can be used to dox them.

Copy link
Member

@dessalines dessalines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about as a good compromise, and a way to keep the signup page clean:

  • Add this disclaimer to the top of the Legal page (and always show the legal page, even if its null).
  • Have a required signup checkbox "I have read the legal page / etc"), like @alectrocute suggested.

@wiki-me
Copy link

wiki-me commented Jul 11, 2023

Have a required signup checkbox "I have read the legal page / etc"), like @alectrocute suggested

I would not like to encourage what was called "the biggest lie on the internet", there was actually a study that made people agree to give their first born.

A suggest linking to "terms of service didn;t read" , also mentioning that other sites can't really guarntee full deletion (web archive is a thing, not to mention backups proprietary sites do), other wise it might scare off people who are vulnerable to decision making biases (e.g. some claim poverty overwhelms critical thinking skills).

@alectrocute
Copy link
Contributor

Where are we at with this? I would still love to see this added as an extra page and accompanying checkbox.

@dessalines
Copy link
Member

Should also add a link to the legal page: LemmyNet/lemmy-translations#81

@Nutomic
Copy link
Member

Nutomic commented Oct 26, 2023

A link to the documentation would also work. Btw the message mentions "instance" a lot but new users might have no idea what that means. So consider changing it to "server" or explaining it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants