I’m talking about this sort of thing. Like clearly I wouldn’t want someone to see that on my phone in the office or when I’m sat on a bus.
However there seems be a lot of these that aren’t filtered out by nsfw settings, when a similar picture of a woman would be, so it seems this is a deliberate feature I might not be understanding.
Discuss.
This whole problem would be solved by adding more tags as per this proposal: https://github.com/LemmyNet/rfcs/pull/4 and enabling more filtering.
but @[email protected] and @[email protected] didn’t look at it for months and I don’t know what is their stance on it. The dev that wanted to implement it doesn’t want to spend energy to push forward for a green light.
I have no idea why is this such a debate.
NSFW is such a loaded term.
There is no need for any “green light”, if there was a problem with the rfc we would have said so from the beginning. From what I can tell the rfc is not completed yet, and when it’s completed someone still needs to step up to implement it. Even my own rfc which was finished months ago is still not merged and not implemented.
What would need to be done to complete it?
Well someone has to write the code.
I know someone that is willing to implement this feature, but they are waiting for merge of rfc to open a Pull Request with initial implementation.
As I understand the RFCs are for defining scope and design requirements for specific feature. And when the design is finalised RFC is merged. Then someone opens a PR to implement it.
If you were imagining some other process it would be beneficial to acknowledge change of development phase from designing to implementing.
P.S. The readme in the repo is supporting my view.
The RFC is merged now!
https://github.com/LemmyNet/rfcs/blob/main/0004-post-tags.md
block .ml, problem solved =D
No, that doesn’t solve the problem. You have to have a merge accepted by the owners of the repo, unless someone wants to start a new fork and maintain that.