home.social

#cwimagedescriptionmeta — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cwimagedescriptionmeta, aggregated by home.social.

  1. CW: Alt-texts for profile images probably becoming mandatory, image descriptions for images in Mastodon link previews probably becoming mandatory, probably even for non-Mastodon users; CW: long (almost 4,500 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, ableism meta
    More and more Mastodon users are acting like alt-texts for profile images are becoming mandatory Fediverse-wide. Never mind that they're currently being rolled out by and by and only on Mastodon even.

    Here on Hubzilla, they aren't even a thought, also because Hubzilla doesn't know the concept of images having their own dedicated alt-text database field. (Before you ask: Hubzilla handles images and therefore alt-texts in messages vastly differently from Mastodon to begin with.)

    At the same time, more and more Mastodon users are acting like image descriptions for the images in the link previews that are generated automatically in Mastodon timelines are becoming mandatory Fediverse-wide. Never mind that Mastodon itself has barely got enough character capacity to describe these preview images at the high level of detail that so many Mastodon users love, what with its meagre default character limit of 500.

    Also, never mind that you'll have to edit your post to describe the preview image because it only appears after you've tooted your toot, so you can't see it before you toot your toot.

    Also, never mind that everyone outside Hubzilla will get an image description for an image that's entirely absent because they don't have Mastodon-style link previews, because these link previews are a Mastodon-only thing.

    Again, this is even worse here on Hubzilla. Unlike Mastodon, Hubzilla has a preview button that lets you look at your message before you actually send it. But Hubzilla doesn't generate link previews. And Hubzilla's preview button doesn't offer you the option to show you what your message will look like on Mastodon.

    So I'd have to
    • write and send my message as usual
    • switch to a tab with mastodon.social
    • look for my message by using the hashtag search
    • check whether Mastodon has generated a link preview, and if so, which image it has chosen
    • find a copy of the image with the highest resolution possible;
      alternatively, if it's an in-world image from OpenSim, log into OpenSim, travel to that place and take a close look at the place to write a highly detailed image description (takes from five hours to two days)
    • switch back to my Hubzilla tab
    • edit my message
    • add the image description
    • re-count the characters in the message
    • edit the message
    • add a long post content warning with the current character count if there is none, and it isn't a comment; edit the character count of the existing long post content warning if there already is one
    • save the edit
    • discover that Mastodon hasn't recognised my edit as such, and now there are two copies of the same message on Mastodon, the old one without the image description and the new, longer one with the image description

    All just to describe an image that isn't even there for my fellow Hubzilla users. Nor is it there for my contacts on Friendica, (streams), Forte, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, Pleroma, Akkoma, snac2, GoToSocial, Hollo, Socialhome, Mitra, PieFed, Wafrn etc.

    By the way, if a message comes from something else than Mastodon, and there's no actual link in it, Mastodon often creates a link preview for the profile or channel page of whoever has sent the message and picks their profile photo as the image for the link preview. Essentially, I'd have to reliably know when Mastodon does that, write two image descriptions for my profile photo (it's a rendering from OpenSim, and I always describe these twice; besides, people should have a shorter description next to my usual detailed description) and copy-paste both into each post for which Mastodon will generate a link preview for my channel page.

    Fortunately, Mastodon doesn't show Hubzilla profiles or channels like Hubzilla itself shows them, and neither do Mastodon apps. Otherwise, if Mastodon users figure out that the background image of my channel is part of my channel customisation and not a default Hubzilla Web UI element, they may demand I add an alt-text for the background image, lest I be mass-blocked as an ableist.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #Hubzilla #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity
  2. CW: Mastodon culture will declare alt-texts for profile pictures mandatory Fediverse-wide, but most Fediverse software doesn't even support them; CW: long (over 3,500 characters), Fediverse meta, alt-text meta, image description meta
    So there's a new attack vector for Mastodon users against non-Mastodon users in the making.

    Mastodon is rolling out alt-texts for what we on Hubzilla call the profile photo and the cover photo. It won't be long until it becomes mandatory in Mastodon's culture to have alt-texts for both these pictures. Regardless of how new this feature is and how many other features that were introduced between March, 2022 and now have not made it into Mastodon's culture and Mastodon's unwritten rules, by the way.

    At this point, Mastodon's alt-text activists will start attacking anyone and everyone whom they catch without alt-texts for these two pictures. At least they'll lecture them about the importance of alt-texts. Or they'll block them outright.

    What they won't realise:
    • Not everyone in the Fediverse is on Mastodon. Just because you see something on your Mastodon Web UI or in your Mastodon app, doesn't mean it's on or from Mastodon itself.
    • In fact, that particular user might not be on Mastodon.
    • Just because Mastodon rolls out a new feature, doesn't mean everything in the Fediverse rolls out the same feature at the same time. This means that there's a whole lot of Fediverse server software that does not offer alt-texts for profile pictures, and that probably won't offer them for quite a while or ever.
    • Also, Mastodon's culture is not and will never be the culture of the whole Fediverse. Sorry, Mastodon fundamentalists, but some software has been here before Mastodon, its culture is older than Mastodon itself, and it's technologically incompatible with Mastodon's unwritten rules.

    Here on Hubzilla, where I'm posting from right now (in case you really thought I'm on Mastodon just like you), there is no such thing as a dedicated field for alt-texts anywhere. Even if you want to post pictures, there is no alt-text entry mask, and there is no alt-text database field for the images.

    Instead, both images and alt-texts are handled like on a blog: You embed the image somewhere in the post text using markup code. In a sense, you program the image into the post. And if you want the image to have alt-text, you have to program the alt-text into the image-embedding code. If you're afraid of coding, Hubzilla is not for you.

    But if there's no entry mask and no database field for alt-texts in posts, there won't be either for the profile images either. That is, unless Hubzilla adopts the alt-text field from (streams) and Forte where alt-texts can be added to uploaded images in the Photo app so that they're automatically inserted whenever you embed an image in a message. Using that alt-text field for profile images should be trivial then.

    If you want or need the images in my profile described: I don't have a description for my profile photo. For my cover photo, I actually have two. They're both in this post: https://hub.netzgemeinde.eu/display/c796febd-8ce2-472b-a46b-23fdf6b16f18. One is in the alt-text which you probably can't open when you're on a phone; the alt-text is 1,500 characters long, a bit over 1,400 of which are visual description. The other one is in the post text itself. But you'd better have a lot of time at your hand because it's over 60,000 characters long, and it'll probably take you a few hours to read it.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Fediverse #Mastodon #Hubzilla #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity
  3. @Daniel de Kay The biggest cultural difference based on server software has to be between Mastodon on the one hand and the Mike Macgirvin creations Friendica, Hubzilla and (streams) on the other hand.

    Not only do they have vastly different user bases, but they developed independently from one another. When the Mastodon culture developed, those who shaped it didn't even know the other side, so they couldn't adopt any of its culture.

    Said other side's culture dates back to 2010 when Friendica was launched as Mistpark, and since that was almost six years before Mastodon, it couldn't be inspired by Mastodon's culture either.

    Add to that that these respective cultures are greatly shaped by technical features and limitations or the lack thereof.

    Mastodon's culture is largely built around its 500-character limit which is ample for your typical phone-wielding Mastodon user. Friendica, Hubzilla and (streams) don't have any defined character limit whatsoever, and its target audience is largely on desktop or laptop computers, often running Linux, with large screens and full-size hardware keyboards.

    So it's the most normal thing in the world for them to write in one post as much as they want while Mastodon users debate whether threads are good, or you should always limit yourself to 500 characters or less.

    Also, alt-text. Mastodon has many disabled users, including blind or visually-impaired users. And it has a dedicated alt-text field for each image. On top of that, it offers 1,500 characters for each alt-text which, in connection with the 500-character limit for toots, has people write detailed image descriptions and explanations and put them into the alt-text. That's often information that doesn't even belong in alt-text, but there's no room for it elsewhere.

    Friendica, Hubzilla and (streams) have unlimited room, so putting stuff into alt-text because the post text is too limited seems ridiculous. But they don't have a vocal disabled community, so there's little interest in accessibility. And neither of them has a dedicated alt-text field. Alt-text is supported, but it has to be manually grafted into the image-embedding code in the post. And there's no official documentation for that, I think not even for Friendica which is the only one out of the three with actually useful end-user documentation.

    It's similar with content warnings. On Mastodon, they're put into the repurposed summary field, and next to nobody knows that it's a repurposed summary field rather than invented for content warnings from scratch. So since Mastodon has a content warning field, writer-side content warnings are huge, but also cause for drama.

    Mastodon 4.0 has introduced filters that can create reader-side content warnings, but hardly anyone uses them, even fewer people support them with keywords or hashtags, many don't even know this feature exists, and it's generally ignored because it's un-Mastodon.

    The Friendica/Hubzilla/(streams) complex doesn't have a content warning field. Hubzilla and (streams) have a summary field labelled as such. Friendica doesn't even have that; it uses a pair of BBcode tags for that.

    And within their own ecosystem, they don't even need it. They've got the "NSFW app" instead, an over-one-decade-old, optional, simple-as-anything substring filter that automatically hides entire posts with all media and everything behind content warnings if it finds one of the entered keywords or hashtags.

    So they can't understand Mastodon's commotion about content warnings, and Mastodon users can't understand why they don't add Mastodon-style content warnings.

    And then there are all the things that were or are being debated on Mastodon and whether or not it should introduce them. Especially the second-wave Twitter refugees are often staunchly against them.

    Full-text search and quote-tweets are being actively used on Twitter to track down and harass members of minorities who have fled to Mastodon. Of course, they don't want Mastodon to introduce either. That is, in the case of full-text search, Mastodon has found a solution, but one that doesn't really federate to the rest of the Fediverse.

    Quotes and text formatting are seen as bad, too. Many don't know quotes because Twitter doesn't have them, and so they think quotes could be used as tools of harassment. And both are seen as making Mastodon feel less like Mastodon and more complicated.

    Friendica and Hubzilla had all this before there was Mastodon, and (streams) inherited it from its long line of ancestors. Their users have gotten so used to having all this that they don't understand what the problems should be, also because they're so detached from Mastodon's culture. So they keep on using these features unashamedly, even around Mastodon users.

    Some differences are rather simple. Take mentions, for example. Friendica has always used long names for mentions, as does its offspring. Mastodon users may find that freaky. Meanwhile, Friendica, Hubzilla or (streams) users may find Mastodon's mentions cryptic because they use the short name. But even they matter.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseCulture #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #500Characters #CW #CWs #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Quotes #QuotePost #QuotePosts #QuoteBoost #QuoteBoost #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuotedShares #TextFormatting #FullTextSearch