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:
-
Even having subscribed to several NSFW subs, they are effectively completely missing from my feed.
-
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...).
I don't think it went too far. Not exposing people accidentally to NSFW content takes priority over giving people a better experience consuming NSFW content. If you want to consume NSFW content head over to an instance that focuses on NSFW content. For example, lemmynsfw.com will fulfill all your NSFW needs.
That's the advantage of the fediverse, you can have different instances focusing on different types of content. And having the main sites of kbin.social or lemmy.world focus on Non-NSFW content will make the entire fediverse easier to advertise to the public.
If your solution is to go to a different website instead of subscribing from here and having it served to me here, then what is the point of federation? (Just to clarify I totally understand why people wouldn’t want to be served nsfw when they didn’t opt into it and I don’t mind a bit of an overcorrection for the meantime. I know kbin blew up fast and this can be an expected growing pain that will eventually be worked out)
Federation doesn't mean everything. Each server is allowed to choose how they want to federate, who they want to federate with, and what features they want to support for their users. The entire point is to make it easier to migrate servers, not that servers are discouraged from running how they want.
If you want nsfw primarily, then join a server that values that. They will choose to federate with other nsfw servers. They will choose to include better features for nsfw content. Complaining about the lack of nsfw features here is like complaining about the lack of English federation on a French server.
You aren't paying for anything here. You don't get to dictate how a server is run nor what the developers focus on as far as features. Disagreement is fine but the power you hold is the ability to change servers.
To my knowledge, currently kbin.social federates with all instances. Therefore on this instance kbin.social, where I have opted in to nsfw, I would like nsfw to organically show up on my All. If it isn’t showing up because no one is making any then that is fine, if it is being made and isn’t showing up despite me having opted in that is not fine and I will patiently wait until it is fixed. And just for the record, I have and would encourage everyone else to buy Ernest a coffee https://www.buymeacoffee.com/kbin
I've bought a coffee as well.
As to federation, no Kbin hasn't really taken any stances yet, but that doesn't mean they won't in the future. But feature wise, Kbin is so new that nsfw specific features could be a long way off. I doubt even @ernest knows as I'm sure his life has been thrown a real curveball this month. If we're still here in a couple years and there's no extra nsfw features, then it's reasonable to ask what's up. Right now though? There's so many missing features that you couldn't realistically even list them all.
Hey, thanks :) Yes, that is a known issue. First, I need to address the moderation tools and sensitive content issue for sure. I'm actually working on it right now. But there are so many exciting new things from contributors right now that it's not easy ;)
The most important thing is that we have 331 issues recorded. Now it's just a matter of time :D
https://codeberg.org/Kbin/kbin-core/issues
Hi, ernest!
If this is a known issue that you intend to address, and it's just a matter of priorities, then I'm happy.
Everyone appreciates all the work you've been doing, and I hope you're getting help to ease your burdens.