I just can't get over how BlueSky doesn't have a way to manually mark something as nsfw like. This is kinda all I need to know about the platform.
They made a whole ass AI thing to prevent you from seeing NSFW stuff instead of simply letting you protect other people from accidentally seeing NSFW posts, and it doesn't work, and that tells you how the creators feel about the relationship between technology and people
my favorite piece of "there was an attempt" software engineering will always be the "sensitive content" flags on twitter. first, there was an account-wide sensitive content flag that applied to literally every piece of media you ever posted. then, more than a decade later, they added a second sensitive content flag for specific images -- except it used a completely different internal implementation, so no third-party clients (even TweetDeck, which has been owned by twitter since 2011) would properly recognize it when it was added to media, and you couldn't set the flag from anything but web twitter.
TweetDeck in particular also put "view this image" and "permanently change my content viewing settings to automatically expand all sensitive images" on buttons right next to each other, so even if you turned the sensitive content warning clickthrough on, every couple weeks you would accidentally turn it off, until you saw something which was so obviously flagged that you went "wait did I turn that setting off" and went into the settings to turn it back on.
fun facts:
-
twitter also doesn't have a way to mark one tweet as nsfw. not under the original system, i mean. it supports doing this, but there is no way to do it as a tweet author; it can only be done by twitter in response to a report (or automatically if you, say, post a photo of a sphynx)
-
there's an opt-out for the original system, so if you have a porn account from which you follow other porn accounts and wish to view porn, you can just, do that. there is not an opt-out for the new system, so you have to click through every god damn fucking time
-
tweets flagged under the old system are viewable if you're logged out, with a warning. tweets flagged under the new system require you to log in! i think even youtube-dl can't fetch them without a session cookie.
also i'm pretty sure both systems are completely orthogonal and there is no indication that they have any intention of (a) iterating on either, (b) consolidating them
just completely inexplicable
