mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#alttextmeta

0 posts0 participants0 posts today
Replied in thread
@Chris Mills @:neuro: Pixy's Journey :v_bi: Kind of similar here, only that the extra information always goes into the post text itself. That extra information is necessary because I only ever post about extremely obscure topics, and I want people to understand my image posts without having to look anything up themselves.

Whenever I post a wholly original image, I even add two image descriptions, a "short" and purely visual one in the alt-text and an extensive one that includes explanations in the post itself.

And yes, I write my image descriptions myself by hand. I'm on a desktop computer with a hardware keyboard most of the time. Besides, AI can't nearly do what I do.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@vulgalour First of all, "image description" and "alt-text" don't mean the same thing.

Alt-text is what's added directly to the image. It's what screen readers used by blind or visually-impaired people read out loud as they can't "read out loud" an image. It's what people see instead of the image if the image doesn't show for them (text-based client, too slow Internet connection, whatever).

Alt-text should never convey more information than the image which it is a replacement for.

An image description that goes into the post itself is not alt-text.

I don't see any rule or part of the "Fediquette" or "Mastodon culture" that speaks against adding that additional information to a reply.

Whether it works or not depends on whether your customers accept it or not. I guess that 99% of your aspiring customers in the Fediverse will be on Mastodon, only see your start post and not be bothered to check the replies. So my suggestion is to leave room in the original post for tellling your customers that prices can be found in a reply to that post.

But seeing as this will happen to you a lot, it may be worth looking for someplace that offers you more than 500 characters:
  • a Mastodon instance with a raised character limit
  • Pleroma (5,000 characters by default, configurable by the admin)
  • Akkoma (5,000 characters by default, configurable by the admin)
  • Misskey (3,000 characters, hard-coded; just steer clear of misskey.io)
  • the various forks of Misskey and forks of their forks like Iceshrimp or Sharkey (thousands of characters by default, configurable by the admin)

If you need a five-digit character count, the best you can do requires basically re-learning the Fediverse, mastering a significantly steeper learning curve and very likely abandoning dedicated apps. Here we're talking about Mike Macgirvin's creations from Friendica (200,000 characters) to Hubzilla (probably even higher) to (streams) and Forte (over 24,000,000 characters).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #Sharkey #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #AltText #AltTextMeta #CWAltTextMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@vulgalour If the prices can be read in the image, you should add them to the alt-text. A price tag is text, and text must be transcribed.

If the prices are not in the image, they go into the post text. If you only have 500 characters, make room for them. But do not only make them available in the alt-text.

Not everyone can access alt-text. There are people with physical disabilities who cannot open an alt-text. Information that is only available in the alt-text, but neither in the post text nor in the image itself, is inaccessible and lost to them. This means that information must be in the image and the alt-text or in the post text, but never only in the alt-text.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@Garry Knight @qurly(not curly)joe This, by the way, is something that next to nobody in the Fediverse knows, and that many will deny and fight with all they can:

Alt-text must never include exclusive information that is neither in the post text nor in the image itself. Such information must always go into the post itself. If you don't have room in the post, add it to a reply or multiple.

That's because not everybody can access alt-text. Certain physical disabilities can make accessing alt-text impossible, for example, if someone can't use their hands. Money quote from way down this comment thread:

Deborah schrieb den folgenden Beitrag Mon, 10 Jul 2023 23:30:45 +0200 @jupiter_rowland

I have a disability that prevents me from seeing alt text, because on almost all platforms, seeing the alt requires having a screenreader or working hands. If you post a picture, is there info that you want somebody who CAN see the picture but DOESN’T have working hands to know? Write that in visible text. If you put that in the alt, you are explicitly excluding people like me.

But you don’t have to overthink it. The description of the image itself is a simple concept.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility #QuotePost #QuoteTweet #QuoteToot #QuoteBoost
hub.netzgemeinde.euHow far should alt-text for pictures from within virtual worlds go?Super-long rant about accessibility, the length of alt-texts for pictures taken in virtual worlds and incompatibility issues between Mastodon and Hubzilla
Replied in thread
@David Mitchell :CApride:
Mostly, just imagine you’re telling your friend over the phone about image you’re looking at and what they would need to know.


Let's just say I'm a bit critical about that because, in my opinion, it doesn't work in the Fediverse.

Jupiter Rowland schrieb den folgenden Beitrag Fri, 04 Oct 2024 23:30:02 +0200

You can't describe images in Fediverse posts like over the phone

Allegedly, a "good" advice for image descriptions is always to describe images like you'd describe them to someone on a landline phone.

Sorry, but that's non-sense. At least for anything that goes significantly beyond a real-life cat photo.

If you describe an image through a phone, you describe it to one person. Usually a person whom you know, so you've at least got a rough idea on what they need described. Even more importantly, you can ask that person what they want to know about the image if you don't know. And you get a reply.

If you describe an image for a public Fediverse post, you describe it to millions of Fediverse users and billions of Web users. You can't know what they all want, nor can you generalise what they all want. And you can't even ask one of them what they need described before or while describing, much less all of them. In fact, you can't ask at all. And yet, you have to cater to everyone's needs the same and throw no-one under a bus.

If I see a realistic chance that someone might be interested in some detail in one of my images, I will describe it. It won't be in the shorter description in the alt-text; instead, it will be in the long description which I've always put directly into the post so far, but whose placement I'm currently reconsidering. If something is unfamiliar enough to enough people that it requires an explanation, I will explain it in the long description.

Right now, only meme posts are an exception. They don't need as much of a visual description as long as I stick to the template, and a poll has revealed that people do prefer externally linked third-party explanations over my own ones blowing the character count of the post out of proportion. This is the one time that I can safely assume that I actually know what most people want.

@accessibility group @a11y group

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility

CC: @Monstreline @Claire (sometimes Carla) @qurly(not curly)joe

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #QuotePost #QuoteTweet #QuoteToot #QuoteBoost
Replied in thread
@Anna Maier I don't know what constitutes a "good" example in your opinion, but I've got two examples of how bad AI is at describing images with extremely obscure niche content, much less explaining them.

In both cases, I had the Large Language and Vision Assistant describe one of my images, always a rendering from within a 3-D virtual world. And then I compared it with a description of the same image of my own.

That said, I didn't compare the AI description with my short description in the alt-text. I went all the way and compared it with my long description in the post, tens of thousands of characters long, which includes extensive explanations of things that the average viewer is unlikely to be familiar with. This is what I consider the benchmark.

Also, I fed the image at the resolution at which I posted it, 800x533 pixels, to the AI. But I myself didn't describe the image by looking at the image. I described it by looking around in-world. If an AI can't zoom in indefinitely and look around obstacles, and it can't, it's actually a disadvantage on the side of the AI and not an unfair advantage on my side.

So without further ado, exhibit A:

This post contains
  • an image with an alt-text that I've written myself (1,064 characters, including only 382 characters of description and 681 characters of explanation where the long description can be found),
  • the image description that I had LLaVA generate for me (558 characters)
  • my own long and detailed description (25,271 characters)
The immediate follow-up comment dissects and reviews LLaVA's description and reveals where LLaVA was too vague, where LLaVA was outright wrong and what LLaVA didn't mention although it should have.

If you've got some more time, exhibit B:

Technically, all this is in one thread. But for your convenience, I'll link to the individual messages.

Here is the start post with
  • an image with precisely 1,500 characters of alt-text, including 1,402 characters of visual description and 997 characters mentioning the long description in the post, all written by myself
  • my own long and detailed image description (60,553 characters)

Here is the comment with the AI description (1,120 characters; I've asked for a detailed description).

Here is the immediate follow-up comment with my review of the AI description.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AI #LLaVA #AIVsHuman #HumanVsAI
llava.hliu.ccLLaVA
Replied in thread
@sunflowerinrain @Tarnport From what I've read, a digital photograph is considered the default. So for brevity reasons, it must not be mentioned.

Any other media must be mentioned, whether it's a painting, a screenshot from a social media app, a scanned analogue photograph, a flowchart, a CAD blueprint, a 3-D rendering or whatever.

But an alt-text must never start with "Image of", "Picture of" or "Photo of". That's considered bad style and a waste of characters and screen-reading time. If the medium is not mentioned, digital photograph falls into its place as a default.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@Ángela Stella Matutina I'm talking about people who can't access alt-text due to physical disabilities.

People with a strong tremor who cannot move a mouse cursor onto an image and keep it there steadily. They exist. It was one of them who told me that explanations don't belong into alt-text.

Quadriplegic people or amputees. They operate their computers by poking the keyboard with a headpointer strapped to their forehead or with a kind of pen that they hold in their mouth. They have no way of using pointing devices whatsoever. They cannot move a mouse cursor onto an image because they don't have a mouse cursor. They use their computers entirely over the keyboard.

All these people do not necessarily have a way of making alt-text a) appear and b) stay where it is for long enough for them to read it.

If you regularly have a lot to explain in your images, don't put these explanations into the alt-text, just because you've only got 500 characters in your toots. Instead, move someplace in the Fediverse that offers more characters (e.g. Misskey: 3,000; Akkoma: 5,000; Friendica: unlimited).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
#AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@Alt Text Hall of Fame @David Bloom Yes.

Explanations, or any other information available neither in the image nor in the post text, must never ever go into the alt-text. That's because not everyone can access alt-text. And to those who can't access alt-text, any information exclusively available in alt-text is inaccessible and therefore lost.

#AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Shiri Bailem @Gwen, the kween fops :neofox_flag_trans: :sheher: @Ellie That's my suggestion, too: Always describe the meme image as far as necessary. You may repeat yourself, but there may always be someone who is not familiar with that meme template.

What I'm not entirely sure about is how to explain memes, if at all. I mean, if you describe the image in the alt-text, should you also explain it in the post itself, especially if you've got lots of characters to use up? Particularly if your adaptation touches an extremely niche topic that most people won't understand without enough explanation (the Fediverse beyond Mastodon, super-obscure 3-D virtual worlds etc.)?

Should you give explanations for the template? For your adaptation and the topic? For both? Not at all?

Should the template be explained alone or with extra explanations for concepts included in the template (image macro, advice animal, snowclone, reaction image, 4chan, Something Awful...)?

If you can link to external explanations, is it better to do that? Or are external links too inconvenient, and it's better to write all explanations yourself?

Just so you know what can happen when you go all the way: The first time I made a Fediverse meme post for my new meme channel on (streams), I went for what I took for maximum reader convenience. I ended up with one explanation for my adaptation, one for the template, five to explain the template explanations and the template explanation explanations, one for the topic and one to explain the topic explanation. All just so that nobody in the Fediverse would have to look anything up.

I mean, not everyone is familiar with the "One Does Not Simply Walk Into Mordor" template, and next to nobody knows what FEP-ef61 is, right?

But I ended up with some 25,000 characters worth of explanations. And I thought that can't possibly be that more convenient than external links.

Currently, it seems to me like people would love to have explanations for everything readily available in each meme post, but if you tell them how long these explanations will end up, they'll nope out and prefer links all of a sudden.

If my assumptions should be wrong, feel free to tell me.

Anyway, you may look around my meme channel and check the alt-texts and see if the posts are explained and the images are described sufficiently.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes #FediMemes
Replied in thread
@Christina
Please make it descriptive: tell us about colours, what the person looks like, the background, and anything else you can think of.

I've got a few examples of image posts of my own with very detailed image descriptions. These posts are not on Mastodon, but they are very much in the Fediverse in places that are federated with Mastodon, and they all have actually ended up on Mastodon timelines. So I guess Mastodon's accessibility requirements apply to these places just as well.

Would you say they're too descriptive? Or would you even say they aren't descriptive enough yet, and that there are important details missing?

One example is (content warning: eye contact) this post with two images, my most recent one. It is not available on mastodon.online. These images also show a digital avatar, so in a sense, I've described a person.
  • The first image has exactly 1,500 characters of alt-text, 990 are short image description, 509 explain where the long description can be found.
  • The second image has 1,499 characters of alt-text, 989 are short image description, 509 explain where the long description can be found.
  • The long descriptions have almost 11,000 characters in the common preamble, over 2,800 characters specifically for the first image and almost 6,600 characters specifically for the second image because it has more surroundings. All in all, the long descriptions have almost 21,000 characters. It took me eight hours to research for and write them. The visual description of the avatar plus necessary explanations alone takes up almost 7,000 characters.

Another example is this post with one image. You can also find it by searching for the hashtag #UniversalCampus and scrolling to the bottom of the results; there you can see what it looks like on Mastodon.
  • The alt-text is exactly 1,500 characters long, 1,402 of which are the short image description. The note where to find the long description had to be shortened to the point of being half-useless.
  • The long description in the post is over 60,000 characters long. It took me two full days, morning to evening, to research for and write it.
  • I've actually had to limit myself in comparison to earlier image descriptions: There are no longer any detailed descriptions of images within the image, especially not at a higher level of detail than what the images within the image themselves show in-world.
  • This description is outdated because I've used absolute measures rather than measures relative to what people are familiar with, and the descriptions of the colours may not be detailed enough.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility
Replied in thread
@Kagan MacTane Of course, what details need to be described depends on the answer to this question:

Is there a chance that someone who can't see the image might be curious about what an element in the image looks like while definitely not knowing what it looks like?

If the answer is, "Yes," then describing that element is at least justified, if not even mandatory. In this case, inclusion overrules convenience.

Beyond that, I've got four things to criticise about the alt-text in that post.

One, double quotation marks from the keyboard do not belong into alt-text. Two, line feeds do not belong into alt-text either. Just because Mastodon renders both as intended, doesn't mean everything renders them as intended.

Hubzilla renders double quotes from the keyboard as &⁠quot;. (streams) cuts the alt-text off at the first double quote because it internally uses double quotes as alt-text delimiters. When there's a double quote from the keyboard in alt-text, (streams) thinks it marks the end of the alt-text.

Three, URLs don't belong into alt-text because they can't be opened by a browser from alt-text.

Four, about the URL again, there must never be any information exclusively available in alt-text. Not everyone can access alt-text. Some people are prevented from accessing alt-text due to various physical disabilities. Any information available only in alt-text, but neither in the post itself nor in the image is inaccessible and therefore lost to them.

Explanations of any kind go into the post, regardless of character limits.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #Inclusion #Inclusivity #A11y #Accessibility
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Bernie the Wordsmith Here's some good advice: Don't use the quotation marks on your keyboard in alt-text! They may be mistaken for control characters. I've seen alt-text being cut off at the first quotation mark, for example. Or they may be rendered incorrectly otherwise.

Use typographically correct quotation marks instead.

For English alt-text, that's “ and ”.
Windows: Alt+0147 and Alt+0148.
*nix: 3rd level+B and 3rd level+N.

For Spanish alt-text, that's « and ».
Windows: Alt+0171 and Alt+0187.
*nix: 3rd level+X and 3rd level+Z.

Alternatively, use the character map application of your operating system. Or copy-paste them from this comment.

If that's all too inconvenient, and you absolutely must use what's on the keyboard, use what amounts to single quotes: '.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #FediTips
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Alien_Sunset
But if the op is on a different software, why would they want to edit their posts from masto?
Why wouldn’t they just use the software they used to make the post to edit it?

What I meant was Alice, on Mastodon, wanting to edit Bob's Hubzilla posts because Bob never adds alt-text.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #Mastodon #Hubzilla
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Alien_Sunset
Making editing posts and alt text easier is a thing that could be done.

But you'll still never be able to edit a Friendica or Hubzilla post from Mastodon. They're too different. Trust me, I know, I've been using both for longer than Mastodon has even been around.

Let's push Hubzilla's massive permissions system that wouldn't let you at Hubzilla content anyway aside.

First of all, Friendica and Hubzilla handle images completely differently from Mastodon. On Mastodon, an image is a file attached to a post, and there can only be four of these. Each image has its own dedicated text field for alt-text.

On Friendica and Hubzilla, an image is a file uploaded to the file space that's part of each Friendica account and Hubzilla channel and then embedded into the post inline as a hotlink. With text above the image and text below the image. Like a blog post. And there can be as many images as you want.

There's no alt-text data field either. Alt-text is part of the image-embedding markup code.

All this has been the way it is since July, 2010, when Friendica was launched, five and a half years before the very first Mastodon alpha version. And Hubzilla is older than Mastodon, too.

So if you want to add alt-text to an image in a post from Friendica or Hubzilla, you inevitably have to edit the post itself.

You have to get your hands dirty on raw BBcode with software-specific additions in an editor box that has zero support for any kind of text formatting or markup code.

You have to figure out what in the code of a post or a comment corresponds to which image to which you want to add alt-text.

You have to turn this...
[zrl=https://hub.netzgemeinde.eu/photos/jupiter_rowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295][zmg=800x533]https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpg[/zmg][/zrl]
...into this...
[zrl=https://hub.netzgemeinde.eu/photos/jupiter_rowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295][zmg=https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpg]Digital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery.[/zmg][/zrl]
...all with no WYSIWYG, no documentation at hand, no preview because Mastodon doesn't have a preview button and an editor that may not even support over 500 characters (Friendica and Hubzilla both have no character limits).

And this only covers the UI side. I haven't even talked about what'd have to happen in the background yet.

Again, all this is assuming that Hubzilla lets Mastodon users edit posts in the first place. Which it won't.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Mastodon #Friendica #Hubzilla
@Alien_Sunset Still, it's a suggestion that keeps popping up from the many Mastodon-only bubbles in the Fediverse. And it's being cheered and applauded.

For the record, I'm not an alt-text opponent myself. Rather, I put huge efforts into describing and explaining my images at levels I deem sufficient even for random strangers who happen upon my image posts without knowing anything about the subject. @Stefan Bohacek can probably confirm it.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@Alien_Sunset
3) make it easier to make alt available AFTER a picture has been posted, especially in a way that doesn’t add more burden to the OP or requester if they can’t do it themselves.

Honestly, as someone who doesn't use Mastodon, but something that's very much not Mastodon, I don't like that very popular idea of users being able to edit alt-texts into other users' image posts with no resistance.

Especially since if Mastodon introduced it, only Mastodon would have it. But Mastodon users could try and pop alt-texts into Friendica or Hubzilla or (streams) posts until they're old and grey, but they won't succeed.

Not only because posts from these three are vastly different from Mastodon toots in the way they're built up (no, seriously, they're absolutely nothing like Mastodon toots), but also because especially Hubzilla and (streams) will never a proprietary and non-standard Mastodon feature that lets anyone on Mastodon circumvent their permissions system and mess around with any content coming from there.

CC: @Stefan Bohacek

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla