The best idea I have found out there is to make two separated accounts on two different instances, one for NSFW and another for SFW.

There are three or four other instances that allow nsfw content, but it’s forbidden for most instances because NSFW content is a massive pain in the ass to moderate. Depending what country you’re in you probably have a lot of regulations you need to follow, including in the US where you need to comply with safe harbor regulations so you don’t get in trouble when some asshole uploads a bunch of underage stuff to your server.

Even outside the legal stuff, you’re going to have to deal with a lot of weirdos and negotiate and regulate other people’s sexual fetishes to a significant degree. Most people just don’t want to deal with that, and I can’t blame them.

as long as other instances haven’t blocked federation with this instance you’ll still be able to access it.
you will however need to find the communities first and subscribe to them to have them show up in your feed, as nsfw communities don’t show up on other instances by default as far as i know.

[email protected] is intended as a band-aid for this, but you can also visit this instance and find communities here directly and then sub from another instance.

https://lemmynsfw.com/post/25934

the workflow currently tends to include first searching for the community by url or by !community@instance and then visiting the community url on your instance by putting for example yourinstance/c/[email protected] in your address bar.

this instance also has a custom set of patches applied to make nsfw stuff more accessible to users, including those who aren’t logged in.

deleted by creator