mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.1K
active users

#contentwarning

4 posts4 participants0 posts today
Continued thread

2/

But — the aggressiveness of those alt-text and CW advocates was (and probably still is) causing people who newly joined the Fediverse to leave —

Because one of these new users' early experiences on the Fediverse feels like they are being yelled at by these alt-text and content-warning advocates. And, don't feel welcomed. And leave.

There is a better way —

Ähmm ist es zu viel verlangt, explizite Beschreibungen von schlimmer Gewalt hinter ein CW zu setzen?!

Ja, ich entfolge, wenn ihr mir sowas ohne Vorwarnung in die Timeline knallt.
Ich lese übrigens regelmäßig Posts, die ein CW haben, aber ich würde gern selbst entscheiden, ob ich das in dem Moment psychisch packe oder nicht.

@Laura @Roni Laukkarinen Depends on the effort per post. It's one thing if it takes you no more than two minutes to describe one image, any image.

But my own current standards for myself require me to invest several hours into description and explanation for a meme post based on a standard template. For one of my original images, I would need two days now. I would because I can't properly describe at least some of my old images. They're pictures of the past. What they show is no longer there. This means that I can no longer source all the detail informations necessary for an image description on my current level.

In fact, my current level, my current standard isn't even really defined. I'm working on a new series of image posts, I have been since last year. And I may or may not try something new, namely long image descriptions (not to be confused with the short image descriptions in the alt-texts) in little HTML files linked into the post. As long as I don't know if that's actually better than putting the long descriptions directly into the post, inflating it to a titanic size, I can't touch older posts anyway.

That is, if I added a full set of image descriptions to each one of my oldest images, I would also have to go and upgrade my more recent image descriptions to my current standard. I don't want the quality of my image descriptions to tank at some point two years ago.

While I'm at it, I'd generally have to upgrade all my old posts in several ways. Placement of hashtags. Choice of hashtags, especially filter-triggering hashtags. Mastodon-style content warnings in the summary field, along with summaries, especially for any and all posts and comments that exceed 500 characters.

Trouble is, Mastodon doesn't understand edits from Hubzilla. All posts would go out to my hundreds of Mastodon connections on countless instances once more as brand-new. This would be extra awkward for posts about events that were years ago.

#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Hubzilla #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread

@Serenus @sandwich

well yes, you can autoexpand #contentWarning

and get an eyeful of #porn or #gore completely unexpectedly and unwantedly at times

sometimes in completely inappropriate settings, like browsing #Mastodon in public

so i disagree: we can't depend upon the Mastodon setting autoexpand content warnings

it's happened to me:

i would use a seemingly benign #tag then i would research the appropriateness of the tag by clicking on it and...

that's a lot of dick i was not expecting

😬