So let me start off by saying that I recognize that there was initially a genuine problem with people who didn’t want NSFW content being exposed to it.

Some of this was due to the fact that not all content was being correctly flagged as NSFW, and some of it was because a lot of users didn’t realize that individual users can choose to completely block an entire instance - which is not only a very easy and fast solution, but also does not require an all-or-nothing approach of defederating from NSFW instances.

A number of changes were made, but some of those lingering changes have meant that people who do want to see NSFW content are not because:

  1. Even having subscribed to several NSFW subs, they are effectively completely missing from my feed.

  2. Most NSFW thumbnails are blurred.

Both of these behaviors should not be occurring if a user has chosen in their settings to NOT hide NSFW content.

However, I will also say that the blurred state is something that deserves its own user setting (i.e. so that a user can choose to NOT hide NSFW, but still want them blurred or not) - preferably with the granularity to set it for various sub-types of NSFW (e.g. porn, gore, etc…).

  •  SCmSTR   ( @SCmSTR@kbin.social ) 
    17•1 year ago

    The correct way is to have an nsfw flag on magazines and as a flag standard on all fediverse post metadata, not suggest the magazines on all, let people make whatever they want, make sure it’s marked nsfw if it is nsfw, and have true/false checkbox settings in client app and linked to home-instance profile settings: show nsfw posts on all, show nsfw posts on subscribed, blur nsfw pictures on all, blur on all, blur on subscribed, blur everywhere. Then you need to have per instance content configs that default to all disabled that you could enable if you want to control for specific instances. And if you aren’t logged in, blur everything by default and probably hide nsfw posts everywhere by default.

    Really it’s not that hard. I could draw up model schemas and wireframes if you have no idea what I’m talking about or what to build. Probably have to see what it is currently first though if you want it compatible or conventionally the same.

    It should all be default hide if not logged in, and have it all be logged in client settings saved on the home instance that the client account is on, mirrored and synced to client apps.

    Apps should be number one priority for this stuff, with existing for profit platform replacement instance framework/apps coming soon, ideally there could be universal fediverse apps that integrate modules of specific ux for different types of fediverse apps (mastodon vs kbin) so that it all makes sense. Then, just have tabs within the universal app that even just containerize existing apps but passthrough data. I don’t know what this stuff is on, kotlin, java, rust, whatever, i just wanna search for an instance and then search for content on that instance. Load instances the same way you join discord servers. Hell, just make a discord-like server app that people can run, have auth and whitelist but is federated, and people can closet host their own low-bandwidth “fedDIScORD” server instance that uses fediverse accounts and chatlogs and hosts whatever quality voip you want.