I’m not sure if this is the right place for a discussion, or if I should rather open an issue at Codeberg.

Anyways, some bold soul posted the first link on @nsfw, which I saw browsing All. It was properly tagged as 18+, but the cropped thumbnail already showed some explicit content.

My proposal would therefore be to blur at least the thumbnails in 18+ posts. I’m not sure how to handle this with federated stuff from e.g. Lemmy, as I have no idea if posts from there can even be tagged 18+.

What does everyone think?

  • courts@kbin.socialOP
    2·
    1 year ago

    That’s interesting. The post might already be gone, but I was still able to open it by checking “newest” on All again when I wrote my original post. Maybe it was still cached?

    Anyways, even if porn is banned (which I too think is a sensible approach because moderating that stuff would be a huge headache nobody needs) there might be other articles marked 18+ that should not show up with a potentially graphic image in one’s list.

    I guess this is just an oversight by @ernest, which I don’t blame him for in any way. This project is still alpha.

    As I said, I have no idea how Lemmy handles that stuff.

    • grus@kbin.social
      0·
      1 year ago

      Oh no, no, I might’ve worded my comment wrongly. I still very much can see the NSFW post in question.
      I tried looking for the rulle that said no NSFW content but couldn’t find it - it is very likely I saw that somewhere else and not on kbin.

      Also I see in my settings that you can hide adult content https://i.imgur.com/9fj5lvn.png and after I check that, the post in question no longer shows. (it also doesn’t show if you’re logged out)
      So maybe the intent to hide/censor NSFW content for those that don’t want it was there, but they haven’t gotten to working things out completely/thoroughly?