@pixelfed Why not have a single server feed that is filtered client side?

@pixelfed db queries aside, I changed my mind: as much as the user should be able to choose, at the same time the admin should be able to allow NSFW or not.

Same thing happens on Mastodon.

As long as users can follow another user on a federated instance which allows NSFW, then it's all good.

@pixelfed I do feel like you should still consider a client-side filter here. Making marking content as NSFW universal is a good thing for sure, but a blanket delisting of such content would unfairly hurt discoverability of people who make it.

@pixelfed Couldn't you use the same system used for muting and blocking people to automatically block/mute NSFW posts? The feeds pulled from the cache has to do the block/mute action regardless.

@pixelfed Have you considered a client-side solution where all content is handled the same instant-wise, according to admin preference, but then filtered per logged in user on the UI level?
Also, consider making the admin setting two-fold: one for anonymous users and one for logged-in users, potentially also client-side, in order to protect the passer-by.

@pixelfed No joke, optimize the software better before removing features.

@pixelfed Can’t users decide for themselves by filtering nsfw in their feeds if they don’t want to see it?