CW: Playing with the idea of circumventing Mastodon's rules by sending Article-type objects; CW: long (almost 9,500 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, CW meta, alt-text meta, image description meta, ableism meta
I had a very tempting idea. One which, I thought, could save me a whole lot of time and effort when posting images.
I'm not talking about posting images here on this Hubzilla channel that I'm posting on right now. (In case you haven't noticed yet: I'm on Hubzilla. And not on Mastodon.) I don't post images here on Hubzilla anymore. I've switched to (streams) because (streams) provides me with a critical safeguard for posting images to Mastodon contacts that Hubzilla lacks. And that's the ability to make Mastodon blank sensitive images out.
So I'm talking about posting images on (streams). Fediverse memes on @Jupiter's Fedi-Memes on (streams), virtual world memes on @Jupiter Rowland's (streams) outlet, virtual world renderings also on @Jupiter Rowland's (streams) outlet. All channels in the Fediverse that can be followed from Mastodon.
I rarely post anything with images anymore because the effort of complying with all the requirements coming from Mastodon (plus some which I expect to come from Mastodon, judging from how at least some of its users behave) is tremendous. A whole bunch of CWs in a field which isn't even for CWs where I am; on both Hubzilla and (streams), it's for a summary. Image descriptions, and their minimum standard on Mastodon is all over the place from "just do it" to "if you mention it, you must describe it" to "full description pls, we've got 10,000 characters of alt-text now". Oh, and many demand explanations for images which not everybody understands along with the descriptions.
A meme post can take me an hour or two or three because the visual description is simple, but I still have to write an explanation. A post with an original virtual world rendering takes anything from eight hours to a bit over two full days because my virtual world renderings need full, highly detailed visual descriptions in addition to extensive explanations. On top of that, I've got over 30 rules that image descriptions must follow.
Now, here's some food for thought.
I've been watching what's going on on Mastodon regarding alt-texts and image descriptions very closely, and I've been watching it for several years now. I guess I can say I know what's going on.
I've often seen Mastodon users slam Mastodon toots for lacking alt-texts. I've also seen Mastodon users slam other Fediverse content that they've discovered in their timelines for lacking alt-texts, probably including posts in their local or federated timeline. But only if that Fediverse content actually showed up in their timelines as such, you know, like a Mastodon toot.
But I've never seen Mastodon users slam blog posts on WordPress or Ghost or Newsmast for lacking alt-texts. Even though they're very much Fediverse content.
That's because they're Article-type objects. Mastodon refuses to render Article-type objects as they are. Instead, it reduces them to the title, the summary and a link to the original. In order to read them, Mastodon users must click or tap the link which takes them to an external website; if they use a dedicated Mastodon app, this even causes their browser to open. But if it takes them out of their Mastodon app, out of their Mastodon environment, it feels like it takes them out of the Fediverse altogether.
If at all, Mastodon users slam the preview because the automatically picked link preview image doesn't offer alt-text. And yes, I keep seeing alt-text fundamentalists complaining about automatically picked link preview images not having alt-texts.
But they do not slam the blog post itself because the images in the blog post lack alt-texts appropriate by Mastodon's standards (or by whatever their personal standards are). Even though the blog post is very much in the Fediverse and, by this logic, should be treated the same as a Friendica post, a Sharkey note or a Mastodon toot. They just don't perceive it as in the Fediverse because they can't read it in their Mastodon timeline.
Now, (streams) gives me the option to send posts with multiple paragraphs as Article-type objects. This means that I could make it so that Mastodon renders them like it renders WordPress blog posts: title, summary, link to the original. Not the actual content of the post.
Given how obscure (streams) is, practically nobody on Mastodon will notice that my post on (streams) is still part of the Fediverse. This means I could probably get away with a whole lot more than if I continued to send Note-type objects directly into Mastodon timelines.
Especially on my virtual world image posts I could save a whole lot of time. I could argue that they're content that isn't interesting for non-sighted people anyway. And I might be able to get away without image descriptions. Again: If I did describe these images, it'd take me hours or days for each image post to get the image descriptions right with sufficient details and sufficient explanations.
A nice side-effect would be that I would no longer annoy Mastodon users with these posts being over 500 characters long. All they'd get is a preview that's very much under 500 characters. And yes, some Mastodon users even take issue when a post hidden behind a summary (= CW on Mastodon) is over 500 characters long.
Granted, there would still be the link preview image which Mastodon automatically picks from the incoming post. It probably chooses the first image in the post, and if there's none, it uses my profile picture. "Probably" because I'm not entirely sure which image Mastodon picks under which circumstances. Either way, this image wouldn't have an alt-text. Mastodon itself has zero support for alt-texts behind link preview images, but it's always the users in whose posts the link preview images have no alt-texts who are called out for it.
In fact, not providing image descriptions even in an Article-type object post which Mastodon does not render is ableist. I mean, one of the reasons why my image descriptions are so extremely detailed is because I expect someone who isn't sighted to be super-curious about my image posts and the images in them. Chances are that they will open that link and find a post with images with no alt-texts. In fact, even the required level of description detail would probably stay the same in an Article-type object.
The only thing that I might be allowed to drop are the extensive explanations. I've never seen Mastodon users demand blog posts provide these, and Mastodon users demanding images be explained on Mastodon is why all my image posts come with lots of explanations. Still, this means hours or days for one image and then tens of thousands of characters of image description for that one image.
Also, sending Article-type objects would have one big disadvantage: I would no longer have any way of hiding sensitive content or have it hidden. And pretty much all of my image posts are sensitive, and be it because there are eyes in them.
I couldn't add hashtags as filter-triggering keywords. They'd end up in the post proper, but not in the preview that Mastodon shows instead. I'd have to squeeze them into the summary and hope for the best.
I couldn't add Mastodon-style CWs. I have to put Mastodon-style CWs into my summary field. But in an Article-type object, Mastodon correctly interprets the summary field as such and puts the summary between the title and the link to the original. As opposed to hiding the preview behind it like it was a CW.
I probably couldn't even hide or blank the image. That is, I could. Within (streams). I could have the visitors who check out my original post click up to four times until they see the image. Mastodon, however, would probably slam the preview image into everyone's faces right away, unblanked, unblurred, not hidden behind a CW or spoiler tag or anything. Unless, of course, I added something like a one-pixel "image" to each one of my image posts just for Mastodon to catch it as the preview image. A single medium grey pixel probably won't trigger anyone, and even the most die-hard alt-text enforcers on Mastodon wouldn't demand an alt-text for it when it's the link preview image, even if it's just because they simply wouldn't notice it (unless Mastodon upscaled it to the usual link preview image size).
If I kept sending Note-type objects, that'd require even more work describing and explaining the image. It'd probably require quite a few CWs in the summary, and yes, I'd also keep it a summary because I'd have to send posts with tens of thousands of characters to Mastodon timelines. But I could hide the post behind a summary and CW. I could trigger filters. And I could blank the image out, even for Mastodon users, which is especially useful for sensitive users on very old Mastodon versions on which CWs only hide the post text and not the images.
Maybe the only real winning move would be to not post certain kinds of images. But that'd render my two image-posting channels largely useless.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityStreams #ArticleType #NoteType #Mastodon #MastodonCulture #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta
I'm not talking about posting images here on this Hubzilla channel that I'm posting on right now. (In case you haven't noticed yet: I'm on Hubzilla. And not on Mastodon.) I don't post images here on Hubzilla anymore. I've switched to (streams) because (streams) provides me with a critical safeguard for posting images to Mastodon contacts that Hubzilla lacks. And that's the ability to make Mastodon blank sensitive images out.
So I'm talking about posting images on (streams). Fediverse memes on @Jupiter's Fedi-Memes on (streams), virtual world memes on @Jupiter Rowland's (streams) outlet, virtual world renderings also on @Jupiter Rowland's (streams) outlet. All channels in the Fediverse that can be followed from Mastodon.
I rarely post anything with images anymore because the effort of complying with all the requirements coming from Mastodon (plus some which I expect to come from Mastodon, judging from how at least some of its users behave) is tremendous. A whole bunch of CWs in a field which isn't even for CWs where I am; on both Hubzilla and (streams), it's for a summary. Image descriptions, and their minimum standard on Mastodon is all over the place from "just do it" to "if you mention it, you must describe it" to "full description pls, we've got 10,000 characters of alt-text now". Oh, and many demand explanations for images which not everybody understands along with the descriptions.
A meme post can take me an hour or two or three because the visual description is simple, but I still have to write an explanation. A post with an original virtual world rendering takes anything from eight hours to a bit over two full days because my virtual world renderings need full, highly detailed visual descriptions in addition to extensive explanations. On top of that, I've got over 30 rules that image descriptions must follow.
Now, here's some food for thought.
I've been watching what's going on on Mastodon regarding alt-texts and image descriptions very closely, and I've been watching it for several years now. I guess I can say I know what's going on.
I've often seen Mastodon users slam Mastodon toots for lacking alt-texts. I've also seen Mastodon users slam other Fediverse content that they've discovered in their timelines for lacking alt-texts, probably including posts in their local or federated timeline. But only if that Fediverse content actually showed up in their timelines as such, you know, like a Mastodon toot.
But I've never seen Mastodon users slam blog posts on WordPress or Ghost or Newsmast for lacking alt-texts. Even though they're very much Fediverse content.
That's because they're Article-type objects. Mastodon refuses to render Article-type objects as they are. Instead, it reduces them to the title, the summary and a link to the original. In order to read them, Mastodon users must click or tap the link which takes them to an external website; if they use a dedicated Mastodon app, this even causes their browser to open. But if it takes them out of their Mastodon app, out of their Mastodon environment, it feels like it takes them out of the Fediverse altogether.
If at all, Mastodon users slam the preview because the automatically picked link preview image doesn't offer alt-text. And yes, I keep seeing alt-text fundamentalists complaining about automatically picked link preview images not having alt-texts.
But they do not slam the blog post itself because the images in the blog post lack alt-texts appropriate by Mastodon's standards (or by whatever their personal standards are). Even though the blog post is very much in the Fediverse and, by this logic, should be treated the same as a Friendica post, a Sharkey note or a Mastodon toot. They just don't perceive it as in the Fediverse because they can't read it in their Mastodon timeline.
Now, (streams) gives me the option to send posts with multiple paragraphs as Article-type objects. This means that I could make it so that Mastodon renders them like it renders WordPress blog posts: title, summary, link to the original. Not the actual content of the post.
Given how obscure (streams) is, practically nobody on Mastodon will notice that my post on (streams) is still part of the Fediverse. This means I could probably get away with a whole lot more than if I continued to send Note-type objects directly into Mastodon timelines.
Especially on my virtual world image posts I could save a whole lot of time. I could argue that they're content that isn't interesting for non-sighted people anyway. And I might be able to get away without image descriptions. Again: If I did describe these images, it'd take me hours or days for each image post to get the image descriptions right with sufficient details and sufficient explanations.
A nice side-effect would be that I would no longer annoy Mastodon users with these posts being over 500 characters long. All they'd get is a preview that's very much under 500 characters. And yes, some Mastodon users even take issue when a post hidden behind a summary (= CW on Mastodon) is over 500 characters long.
Granted, there would still be the link preview image which Mastodon automatically picks from the incoming post. It probably chooses the first image in the post, and if there's none, it uses my profile picture. "Probably" because I'm not entirely sure which image Mastodon picks under which circumstances. Either way, this image wouldn't have an alt-text. Mastodon itself has zero support for alt-texts behind link preview images, but it's always the users in whose posts the link preview images have no alt-texts who are called out for it.
In fact, not providing image descriptions even in an Article-type object post which Mastodon does not render is ableist. I mean, one of the reasons why my image descriptions are so extremely detailed is because I expect someone who isn't sighted to be super-curious about my image posts and the images in them. Chances are that they will open that link and find a post with images with no alt-texts. In fact, even the required level of description detail would probably stay the same in an Article-type object.
The only thing that I might be allowed to drop are the extensive explanations. I've never seen Mastodon users demand blog posts provide these, and Mastodon users demanding images be explained on Mastodon is why all my image posts come with lots of explanations. Still, this means hours or days for one image and then tens of thousands of characters of image description for that one image.
Also, sending Article-type objects would have one big disadvantage: I would no longer have any way of hiding sensitive content or have it hidden. And pretty much all of my image posts are sensitive, and be it because there are eyes in them.
I couldn't add hashtags as filter-triggering keywords. They'd end up in the post proper, but not in the preview that Mastodon shows instead. I'd have to squeeze them into the summary and hope for the best.
I couldn't add Mastodon-style CWs. I have to put Mastodon-style CWs into my summary field. But in an Article-type object, Mastodon correctly interprets the summary field as such and puts the summary between the title and the link to the original. As opposed to hiding the preview behind it like it was a CW.
I probably couldn't even hide or blank the image. That is, I could. Within (streams). I could have the visitors who check out my original post click up to four times until they see the image. Mastodon, however, would probably slam the preview image into everyone's faces right away, unblanked, unblurred, not hidden behind a CW or spoiler tag or anything. Unless, of course, I added something like a one-pixel "image" to each one of my image posts just for Mastodon to catch it as the preview image. A single medium grey pixel probably won't trigger anyone, and even the most die-hard alt-text enforcers on Mastodon wouldn't demand an alt-text for it when it's the link preview image, even if it's just because they simply wouldn't notice it (unless Mastodon upscaled it to the usual link preview image size).
If I kept sending Note-type objects, that'd require even more work describing and explaining the image. It'd probably require quite a few CWs in the summary, and yes, I'd also keep it a summary because I'd have to send posts with tens of thousands of characters to Mastodon timelines. But I could hide the post behind a summary and CW. I could trigger filters. And I could blank the image out, even for Mastodon users, which is especially useful for sensitive users on very old Mastodon versions on which CWs only hide the post text and not the images.
Maybe the only real winning move would be to not post certain kinds of images. But that'd render my two image-posting channels largely useless.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityStreams #ArticleType #NoteType #Mastodon #MastodonCulture #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta