A yiffy alt of another lemming who shall not be named.
Male, He/Them.
A kinkwolf, into bdsm, petplay, latex, chastity, hypnosis and other fun stuff. Feel free to make flirty replies at me in responses to my posts, although I may blush.
0 Posts
1 Comment
Joined 1 year ago
Cake day: June 8th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Stumbled upon this and have some thoughts on it; this is something I’ve been thinking about myself for a while.
I agree with Xero’s concerns that the levels seem a bit arbitrary, and I’ve got a “counter proposal” for how a tag based system could work:
The local instance’s community description contains a number of entries like the following:
[](cw:defaultallow:yiff)
[](cw:defaultblock:feral)
[](alwaysblock)
The instance itself will have a list of these tags and what each means available, both for community moderators and remote instance admins.
The remote instance, in its settings, has two lists of tags, a whitelist and a blacklist.
A community is automatically marked as hidden when any of the following are true:
A defaultallow or defaultblock tag apperas in its blacklist.
A defaultblock tag does not appear in its whitelist.
The alwaysblock entry is present.
This would allow remote instance admins to freely customize what they allow and disallow, while giving the local instance the ability to set sensible defaults in case something is missing from the remote’s blacklist. This does put a bit of pressure on the local instance admin to specify what it wants this “sensible default” to be, but that’s something that they already need to do when specifying where they draw the line between what’s NSFW and not NSFW anyway.
Some advantages for this is that it could be expanded to handle content warnings in post titles as well, and allow instances to filter things that wouldn’t traditionally be seen as nsfw (such as politics, bot posts, AI art and so on).
Just some thoughts I had, hopefully it all makes sense.
Stumbled upon this and have some thoughts on it; this is something I’ve been thinking about myself for a while.
I agree with Xero’s concerns that the levels seem a bit arbitrary, and I’ve got a “counter proposal” for how a tag based system could work:
The local instance’s community description contains a number of entries like the following:
[](cw:defaultallow:yiff)[](cw:defaultblock:feral)[](alwaysblock)The instance itself will have a list of these tags and what each means available, both for community moderators and remote instance admins.
The remote instance, in its settings, has two lists of tags, a whitelist and a blacklist.
A community is automatically marked as hidden when any of the following are true:
defaultallowordefaultblocktag apperas in its blacklist.defaultblocktag does not appear in its whitelist.alwaysblockentry is present.This would allow remote instance admins to freely customize what they allow and disallow, while giving the local instance the ability to set sensible defaults in case something is missing from the remote’s blacklist. This does put a bit of pressure on the local instance admin to specify what it wants this “sensible default” to be, but that’s something that they already need to do when specifying where they draw the line between what’s NSFW and not NSFW anyway.
Some advantages for this is that it could be expanded to handle content warnings in post titles as well, and allow instances to filter things that wouldn’t traditionally be seen as nsfw (such as politics, bot posts, AI art and so on).
Just some thoughts I had, hopefully it all makes sense.