AwoosWhenClose

joined 1 year ago
MODERATOR OF
[–] AwoosWhenClose@yiffit.net 3 points 1 month ago (1 children)

I've checked there, but it only contains documents I've supposedly requested.

[–] AwoosWhenClose@yiffit.net 8 points 1 month ago* (last edited 1 month ago) (4 children)

Damn, that's a shame, although not unexpected at this point. I'll post some thoughts about it later over there, but I think I'd like to think forward.

Assuming it's okay with @crashdoom@pawb.social , I'll probably recreate communities from Yiffit over here and post some of the backlog.

Edit: Is email on pawb's side working? Haven't got an account creation email yet.

[–] AwoosWhenClose@yiffit.net 8 points 5 months ago

Pregnancy.

I don't have the traditional anatomy so, uh, it'll probably hurt a lot during childbirth.

[–] AwoosWhenClose@yiffit.net 2 points 1 year ago* (last edited 1 year ago)

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.

[–] AwoosWhenClose@yiffit.net 8 points 1 year ago* (last edited 1 year ago) (1 children)

/uj For what it's worth, as someone who posts quite a bit of stuff there, I also wish full instance per-user blocks were a thing. I like that stuff, but I understand some people don't and rather not force furry tiddies on them. ;_;

/rj But yes, certainly avoid yiffit.net if you don't like that sort of thing. :P

Edit: To those wondering if their instance is blocking it, afaik lemmy.world and sh.itjust.works do not. You can check the instance list at the bottom of the page. Or I guess check if you can see this comment, since my account is on there.

You also won't see furry porn if you have nsfw off in the settings. Or if you don't linger in r/all for too long (there's only like 5 of us posting regularly, it's easy for it to get drowned out).