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

NSFW account and instance declaration and NSFW mode #9468

Open
Humblr opened this Issue Dec 8, 2018 · 16 comments

Comments

Projects
None yet
9 participants
@Humblr
Copy link

Humblr commented Dec 8, 2018

As adult instances are becoming more popular and their reach through the fediverse grows, content on those instances are making their way into the lives of those who are not wanting to see it or are at work and have fed timeline open..

I think it would be a good idea to implement NSFW mode which would allow safe browsing of the fed for those not wishing to see such content.

I see tagging Toots with #nsfw already stops that content from showing. And we along with others have implemented Twatter's CW fix for all feds seeing our content to not show it.

Problem is, this only fixes some of the content. It does not take into account the account avatar for example which on our instance is 90% of the time adult themed.

My suggestion is to add safe browsing mode which can be triggered by the user when ever they wish or as default to new users.
Accounts can then add a hash tag of #NSFW to their posts and account profile to disable their content even coming up on the timeline of SFW users.

Might be worth also allowing instances to mark their instance as NSFW and allow them to block NSFW content showing up on fed timeline.

The reason I am suggesting this is that without it. We will likely be blocked my many instances to the point of we might as well just be selective of the instances we (Humblr) network with as every 5 mins we get a report of NSFW content.

It would also be nice for users to allow all content to show even if CW is applied to that post.

Humblr
Humblr.social

@rx65m

This comment has been minimized.

Copy link

rx65m commented Dec 8, 2018

Fully Agree!
How can we help?

@lsmag

This comment has been minimized.

Copy link

lsmag commented Dec 8, 2018

I like this idea. Can I expand it further?

Twitter has a setting that allows users to flag their profile as sensitive. When it's enabled, visitors have to confirm they wish to see the content. Perhaps it'll be useful to add this flag here as well? So that other instances' can easily filter these out as per OP's suggestion.

Then we can have a setting for instance admins to default all new accounts to be marked as sensitive, if so they wish.

I'm on the fence about flagging a whole instance as NSFW because there are definitely some safe profiles among, say, humblr.social and my own. I feel like some flexibility is preferred, but I'm fine with either way.

I have some time off next week, so I can definitely help with coding, once we have a clear decision on implementation.

@Humblr

This comment has been minimized.

Copy link

Humblr commented Dec 8, 2018

@ismag
You find a SFW profile on Humblr and ill eat my hat

@lsmag

This comment has been minimized.

Copy link

lsmag commented Dec 8, 2018

@Humblr fair enough, I take that back. On second thought, flagging the whole instance as NSFW actually does make sense, though I still think profile level flagging is important, particularly for instances that don't have a NSFW focus but do have NSFW profiles.

@Humblr

This comment has been minimized.

Copy link

Humblr commented Dec 8, 2018

@ismag
Both options allow for higher control for the end user. I think profile tagging is the most important but instance wide while selective in terms of who uses it, is also needed.

@earfolds

This comment has been minimized.

Copy link

earfolds commented Dec 8, 2018

The federated timeline will often pick up freshly-made pornographic instances, leading to friction with established communities, especially those where the use of Content Warnings is entrenched. In particular, this will help instance admins who operate family-friendly instances with users under the age of 18. There's been a demonstrated use-case for mastodon in sharing pornographic content, and I don't feel that banning these instances entirely from the federated timeline is the only way to protect minors.

Allowing users to declare they are over 18 in their profiles would be a good way to solve this.

@nightpool

This comment has been minimized.

Copy link
Collaborator

nightpool commented Dec 8, 2018

Twitter has a setting that allows users to flag their profile as sensitive. When it's enabled, visitors have to confirm they wish to see the content. Perhaps it'll be useful to add this flag here as well? So that other instances' can easily filter these out as per OP's suggestion.

Then we can have a setting for instance admins to default all new accounts to be marked as sensitive, if so they wish.

These two features already exist. Here's what it looks like to a user:
image

And the admin can configure the default setting for this instance in this file: https://github.com/tootsuite/mastodon/blob/master/config/settings.yml

@lsmag

This comment has been minimized.

Copy link

lsmag commented Dec 8, 2018

I already suggest that to be done in my instance, although I wasn't aware it could be set by default, thanks for the tip :)

It still doesn't solve @Humblr's suggestion regarding NSFW avatars, though. Safe browsing mode too.

@lsmag

This comment has been minimized.

Copy link

lsmag commented Dec 8, 2018

I'm pretty sure this is tangential to the original topic but since it was brought up here, I may as well add a response in this thread: @nightpool linked to https://github.com/tootsuite/mastodon/blob/master/config/settings.yml, which states:

# This file contains default values, and does not need to be edited
# when configuring an instance.  These settings may be changed by an
# Administrator using the Web UI.
#
# For more information, see docs/Running-Mastodon/Administration-guide.md

I have actually searched my Admin UI and couldn't find where to change these. Perhaps it's just my instance, or that isn't in the code yet? The documentation it refers to also has no mention of changing these fields: https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Administration-guide.md#administration-web-interface

Nonetheless, this is great advice. I'll fiddle with this file to set default_sensitive: true for all new accounts. Thanks :)

@nightpool

This comment has been minimized.

Copy link
Collaborator

nightpool commented Dec 8, 2018

@lsmag some of those settings are instance settings and some are default user settings. the default user settings are not normally configurable (basically, since there are a lot of them).

@Humblr

This comment has been minimized.

Copy link

Humblr commented Dec 8, 2018

It is not just photos and video though. It is avatars and profile headers that are causing the most issues.
This would be solved with NSFW tagging of profiles and instances.

@Esteth

This comment has been minimized.

Copy link
Contributor

Esteth commented Dec 9, 2018

What would we show for a sensitive avatar in the federated timeline? Show an Identicon instead, or a default Image selected by the instance admin?

I think we should consider what to do for sensitive text posts too - Ideally they don't show up on the federated timeline except for users who want to see it IMO. At that point it would seem safe to show them the sensitive avatar too.

@Humblr

This comment has been minimized.

Copy link

Humblr commented Dec 9, 2018

Just don't show any content tagged as #NSFW (post, account or instance) if the user is in SFW mode.
Showing it blurred or defaulted would be a waste of screen real-estate

@thraeryn

This comment has been minimized.

Copy link

thraeryn commented Dec 9, 2018

That sounds, effectively, like a self-suspend.

I'm not necessarily against that if one instance is decidedly NSFW/sensitive and another is determinedly not–and it still seems a little harsh? At an instance-wide level, though, I guess it makes sense.

@HumblrUser

This comment has been minimized.

Copy link

HumblrUser commented Dec 9, 2018

When I first started on Mastodon, the general instance, I posted adult content with tags on them. After a while, an admin or mod contacted me, telling me, that there are minors on that platform and that I should hide the tags I am using, as they were descriptive on the content I was posting.

I later switched over to humblr.social and added my tags publicly again. On humblr.social that is not a problem. The strange thing happens if someone from the general instance or any other reblogs my posts. By doing so, the tags are visible again to everyone, like minors and "normal" users.

While I am posting my images as sensitive content, many people on humblr do not do that. Moreover, I am sure, that we will not get everyone to use that function. If someone from another instance reblogs that content, everyone can see it. No matter where they are.

That is the reason there should be a workaround for those cases. Whether it is a global flag, where an instance can be flagged as adult (nsfw) and content will only be visible on that instance, even if reblogged from somewhere else, or a switch on the profile, which works global. I have the feeling that this was not thought through. With all due respect!

@sparr

This comment has been minimized.

Copy link

sparr commented Dec 31, 2018

@HumblrUser The responsibility for the content of of a boosted post is on the booster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment