NSFW flag for accounts

[Changaco]

Liberapay profiles probably need a “Not Safe For Work” flag that can be set by profile owners and Liberapay admins, similar to the privacy settings but for a different purpose.

[Changaco]

The database schema changes and admin part of this have been implemented in #2024. I've used the word “unsettling” instead of the abbreviation NSFW in the code and the admin interface.

What's left to do:

• Enable users to mark their profiles as NSFW. I suggest renaming the existing /~/edit/privacy page to /~/edit/visibility and putting the new checkbox there.
• Hide profiles marked as unsettling, unless the viewer has opted in to see them.

[longj724]

I am looking to contribute to the repository for the first time. Does this issue still need to be worked on?

[Changaco]

Yes.

[longj724]

I've looked into this task more and am interested in working on it. I understand where users should be able to set their profile as "unsettling", but where users be able to select to opt in to viewing "unsettling" profiles?

[Changaco]

On every page which would show an unsettling profile if the user had already opted-in to see them.

There should probably be two buttons: one to deactivate the NSFW filter for only one page view, and another one to deactivate it permanently (by setting a cookie).

[longj724]

Would something like what is shown in the video work? (this is just a proof of concept) If the user opts in to always seeing unsettling profiles then they will not be shown this prompt whenever they visit an unsettling profile.

Screen.Recording.2021-11-21.at.10.27.43.PM.mov

[Changaco]

It's a good start.

• The profile should be completely hidden as long as the visitor hasn't opted-in to see it, including and especially the avatar.
• I think the warning needs to be more detailed and complete. Something like “This page is marked as containing potentially upsetting or embarrassing content. Viewing it is particularly unrecommended if someone else can see your screen or if you're a minor.”
• The first button should be labelled “View this page” instead of “View unsettling profile”.
• The text of the second button should end with “on this computer” or “in this browser” to clarify the scope of the opt-in, and it should use the word “pages” instead of “profiles” to be more general.
• The two buttons should probably have the btn-warning class instead of btn-primary.
• Once the visitor has opted-in to see the marked profile, there should be a short message (class alert-info or alert-warning) at the top of the page indicating that it's marked as unsettling. The alert should contain a button to cancel the opt-in.

[longj724]

If the profile (including the avatar) should be completely hidden, how should the profile appear in search results and other places where users can access profiles? There are lots of places on the site where you can see a user's avatar before clicking on their entire profile.

[Changaco]

In the exploration pages and search results we should probably blur the NSFW profiles. (I mean blur the whole box, not just the avatar.)

[longj724]

Do want to blur unsettling profiles in every single place they are used on the site? As I am looking through the code I am noticing a lot of spots where avatar_img(...) is used and then the username is listed. I would have to include a lot of checks to make sure both the username and avatar are blurred since the username is often listed separately outside of the avatar_img() macro. I am just trying to avoid making many unnecessary changes. Right now I am blurring unsettling profiles on the exploration pages and search results.