Ich bin gerade in nach Hbf
Long Here are three examples that I've actually posted into the Fediverse (on another channel than the one I'm replying from now, so don't go looking for them). Mind you, they adhere to the alt-text rules for the Fediverse rather than those for websites and blogs, and yes, .
Example no. 1: Meme directly based on one template with overlaid captions.
Example no. 2: Meme directly based on one template with extra space for captions.
Example no. 3: Self-made collage using multiple templates (contains a Japanese profanity, though, but I didn't want to alter it).
The original posts also have explanations in the post text for those who don't understand the image and the description which I expect to be the norm. They went into the post text because , and because they wouldn't fit into a maximum of 1,500 characters anyway. I would post these explanations as well, but you've only asked for alt-texts, and besides, these explanations tend to be even longer than the alt-texts.
# # # # # # # # # # # # # # # # # # # # # # #
They don't even reject these posts. If they did, I'd be able to see that in the delivery report. But they actually do let these posts in, check the length and then delete them before forwarding them to inboxes, something that Hubzilla, (streams) and Forte don't notice.
I'm not sure if that's limited to Note-type objects, though. But Hubzilla has no way to send Article-type objects, not even optionally, because the devs refuse to re-implement it unless Mastodon starts supporting full HTML rendering with all bells and whistles and gives up that title-summary-and-link-to-the-original hack.
# # # # # # # # Genuine Hubzilla posts (character limit = 16,777,215 = maximum capacity of the database field):
48,977 characters, posted October 27th, 2023, all in one go, guaranteed.
62,514 characters, posted May 16th, 2024, all in one go, guaranteed.
76,780 characters, posted September 24th, 2023, all in one go, guaranteed.
(If you can't open either of these links, say so, and I'll reply with full quote-posts of these three posts.)
All character counts are raw, i.e. the actual number of characters visible. The characters are not counted the Mastodon way (= summary/CW counts into the character count, links are always 23 characters). BBcode markup is not counted in either, nor are the alt-texts, although both internally add to the character count.
Important to know: Local character limits aren't necessarily inbound character limits. For example, Mastodon is hard-coded to a maximum of 500 characters internally, but (AFAIK) it accepts posts coming in from outside up to 100,000 characters.
Likewise, Misskey is hard-coded to 3,000 characters internally. The Forkeys have a configurable internal character limit. But their inbound character limit is higher, hard-coded to ca. 8,000 as has said.
Pleroma and Akkoma have configurable internal character limits that default to 5,000, but AFAIK a hard-coded inbound character limit of 20,000.
In all these cases, longer posts coming in from outside are immediately deleted from the inbox.
# # # # # # # # # # # # # # # # # # # # # # # # # It's generally recommended to give a short summary first and then continue with a detailed description.
That said, I myself would never describe an image on more than two levels of detail. My descriptions of my own original images, all being renderings from very obscure 3-D virtual worlds, tend to become the longest image descriptions in the whole Fediverse by a large margin. I actually have to write two descriptions per image: a long, fully detailed one that goes into the post itself plus a "short" one for the alt-text that still helps fill up the 1,500 characters enforced by Mastodon, Misskey and their respective forks all the way.
I've been recommended to write my long image descriptions on multiple levels of detail. But I'm so very much not going to
I prefer checking and examining each detail only once to checking and examining each detail three or more times over, once for each description pass. So there's a short summary, and then comes one fully detailed description with all necessary explanations and transcripts of all pieces of text.
# # # # # # # # # # # # # # #
...and they're usually only implemented by those who maintain them. These and their works, in turn, mostly stay in the shadows while the bigger players in the Fediverse remain blissfully unaware of them.
Pretty much exactly what has been doing for a while now.
Technology taken over from GoToSocial.
The principle of how these quote-posts are done taken over from Misskey.
And quote-posts themselves were introduced to the Fediverse as early as May, 2010, by what's known as Friendica today.
This is what meant with:
Mastodon presented their quotes as if they had just introduced an all-new, totally revolutionary feature to the Fediverse. In fact, however, the Fediverse had had quote-posts for a decade and a half at that point.
Let's all face it: The main hindrance in Fediverse development is Mastodon. It's a painfully incomplete implementation of a hopelessly outdated version of the ActivityPub spec. At the same time, its cult-like followers see it as the one and only gold standard and the reference implementation of ActivityPub. They believe that Gargron has invented both ActivityPub and the Fediverse because, frankly, that's what the Mastodon folks want everyone to believe.
If the Fediverse had some fair competition, then Mastodon would have to catch up with software like Misskey or Akkoma or Mitra and eventually powerhouses like (streams) or Forte. But what Mastodon lacks in features, it makes up for with sheer market power. The loudest voices that promote the Fediverse don't actually promote the Fediverse they only promote Mastodon.
The features of the non-Mastodon Fediverse are unknown and outright unimaginable both on Mastodon and outside the Fediverse. And just about everyone believes that Mastodon is as perfect and fully-featured Fediverse software as it ever comes. Pretty much the only ones who don't are those who daily-drive non-Mastodon Fediverse software.
This actually goes as far as Mastodon users trying their hardest to force e.g. Friendica users to throw away their own culture, switch to Mastodon's culture and abstain from using some 80% of Friendica's features because they aren't covered by Mastodon's culture. At the same time, Mastodon users staunchly refuse to adopt any part of any non-Mastodon Fediverse culture. This means that even if non-Mastodon Fediverse devs introduce new features, they'd better not let Mastodon users know.
And so Mastodon can get away both with a laughable set of features, with completely ignoring not only FEPs, but also large parts of the ActivityPub spec, with advertising features which just about the whole rest of the Fediverse has had for years as completely new original inventions of their own, and with implementing non-standard stuff and forcing the rest of the Fediverse to implement "proprietary", non-standard Mastodon developments.
CC:
# # # # # # # # # #
Example no. 1: Meme directly based on one template with overlaid captions.
Screen capture from the live-action film The Lord of the Rings: The Fellowship of the Ring, edited into an image macro. It shows a close-up of the actor Sean Bean as the character Boromir. He is speaking with a concerned expression on his face. His right hand has taken the shape of a ring with all fingers with the thumb and and index finger touching. The image has two large pieces of text. The one at the top is, One does not simply, and the one at the bottom continues with, implement FEP-EF61. An explanation of the meme template used in this picture and background information can be found in the post. If you are on Mastodon, Misskey or one of its forks, the post is hidden behind a summary and content warning. If you are on Pleroma, Akkoma, Friendica, Hubzilla or (streams), the explanations follow right below this image.
Example no. 2: Meme directly based on one template with extra space for captions.
Image macro, based on a digital photograph of a fluffy and very chubby calico cat sitting on the floor on its hindquarters and looking upward at the bowl of Fruit Loops in the bottom left corner of the image. At the top of the image, there is a very light grey space with a two-part caption. It starts with: Daniel Supernault:<em> announces a TikTok clone for the Fediverse. This is followed by a blank line and, Fediverse users:. Between the grey space and the image, there is a narrower white space with another caption that has been part of the image for longer than the grey space. The caption speaks for the cat, brther may i have some lps, with the os being umlauts.
Example no. 3: Self-made collage using multiple templates (contains a Japanese profanity, though, but I didn't want to alter it).
Collage of captioned meme images of various kinds in two rows. In the top left, there are two smugly grinning Wojaks, facing half each other, half the audience. The one on the left has the diaspora* logo above his head and his hand on his chin in a pensive gesture. The one to his right is wearing a black tuxedo with a bowtie, and he has the Mastodon logo above his head. These two have a common caption below them: We're beyond such peasantry as that filthy and grubby PHP. We demand only the best: Ruby on Rails. Slightly right of centre, still in the top row, there is a bearded Soyjak with glasses, crying with his mouth wide open, pink eyes and streams of tears running down his cheeks. He is facing towards the left. Above his head is the Pleroma logo. His caption is, in all-caps and ending in five exclamation marks, Noooooooo, Elixir is the way to go and PostgreSQL! In the top right, there is another bearded and bespectacled Wojak, facing towards the left again. This one is angry with the Misskey logo above his head. With the same open mouth as the one to his left, he shouts, Utter heresy, there is no match for TypeScript and Vue.js, baka! The bottom row is taken up by three creepy-looking brownish moths with glowing eyes. The left one is facing towards the right with the Friendica logo above it. The other two are facing towards the left with the logos of Hubzilla and the streams repository above them. Their common caption is, in huge all caps and with an umlaut, Lmp.
The original posts also have explanations in the post text for those who don't understand the image and the description which I expect to be the norm. They went into the post text because , and because they wouldn't fit into a maximum of 1,500 characters anyway. I would post these explanations as well, but you've only asked for alt-texts, and besides, these explanations tend to be even longer than the alt-texts.
# # # # # # # # # # # # # # # # # # # # # # #
Ich bin gerade in nach Hbf zu dem Kickoff vom -term-support
As far as I know, yes.They don't even reject these posts. If they did, I'd be able to see that in the delivery report. But they actually do let these posts in, check the length and then delete them before forwarding them to inboxes, something that Hubzilla, (streams) and Forte don't notice.
I'm not sure if that's limited to Note-type objects, though. But Hubzilla has no way to send Article-type objects, not even optionally, because the devs refuse to re-implement it unless Mastodon starts supporting full HTML rendering with all bells and whistles and gives up that title-summary-and-link-to-the-original hack.
# # # # # # # # Genuine Hubzilla posts (character limit = 16,777,215 = maximum capacity of the database field):
48,977 characters, posted October 27th, 2023, all in one go, guaranteed.
62,514 characters, posted May 16th, 2024, all in one go, guaranteed.
76,780 characters, posted September 24th, 2023, all in one go, guaranteed.
(If you can't open either of these links, say so, and I'll reply with full quote-posts of these three posts.)
All character counts are raw, i.e. the actual number of characters visible. The characters are not counted the Mastodon way (= summary/CW counts into the character count, links are always 23 characters). BBcode markup is not counted in either, nor are the alt-texts, although both internally add to the character count.
Important to know: Local character limits aren't necessarily inbound character limits. For example, Mastodon is hard-coded to a maximum of 500 characters internally, but (AFAIK) it accepts posts coming in from outside up to 100,000 characters.
Likewise, Misskey is hard-coded to 3,000 characters internally. The Forkeys have a configurable internal character limit. But their inbound character limit is higher, hard-coded to ca. 8,000 as has said.
Pleroma and Akkoma have configurable internal character limits that default to 5,000, but AFAIK a hard-coded inbound character limit of 20,000.
In all these cases, longer posts coming in from outside are immediately deleted from the inbox.
# # # # # # # # # # # # # # # # # # # # # # # # # It's generally recommended to give a short summary first and then continue with a detailed description.
That said, I myself would never describe an image on more than two levels of detail. My descriptions of my own original images, all being renderings from very obscure 3-D virtual worlds, tend to become the longest image descriptions in the whole Fediverse by a large margin. I actually have to write two descriptions per image: a long, fully detailed one that goes into the post itself plus a "short" one for the alt-text that still helps fill up the 1,500 characters enforced by Mastodon, Misskey and their respective forks all the way.
I've been recommended to write my long image descriptions on multiple levels of detail. But I'm so very much not going to
- give a summary of 100 characters
- then describe everything roughly in 2,000 characters
- then describe everything again with more details in 10,000 characters
- then describe everything yet again with even more details in 50,000 characters
I prefer checking and examining each detail only once to checking and examining each detail three or more times over, once for each description pass. So there's a short summary, and then comes one fully detailed description with all necessary explanations and transcripts of all pieces of text.
# # # # # # # # # # # # # # #
- Dozens of FEPs under development
...and they're usually only implemented by those who maintain them. These and their works, in turn, mostly stay in the shadows while the bigger players in the Fediverse remain blissfully unaware of them.
Pretty much exactly what has been doing for a while now.
- New work like quote posts from Mastodon
Technology taken over from GoToSocial.
The principle of how these quote-posts are done taken over from Misskey.
And quote-posts themselves were introduced to the Fediverse as early as May, 2010, by what's known as Friendica today.
This is what meant with:
Features that already exist somewhere in Fediverse presented as new inventions.
Mastodon presented their quotes as if they had just introduced an all-new, totally revolutionary feature to the Fediverse. In fact, however, the Fediverse had had quote-posts for a decade and a half at that point.
Let's all face it: The main hindrance in Fediverse development is Mastodon. It's a painfully incomplete implementation of a hopelessly outdated version of the ActivityPub spec. At the same time, its cult-like followers see it as the one and only gold standard and the reference implementation of ActivityPub. They believe that Gargron has invented both ActivityPub and the Fediverse because, frankly, that's what the Mastodon folks want everyone to believe.
If the Fediverse had some fair competition, then Mastodon would have to catch up with software like Misskey or Akkoma or Mitra and eventually powerhouses like (streams) or Forte. But what Mastodon lacks in features, it makes up for with sheer market power. The loudest voices that promote the Fediverse don't actually promote the Fediverse they only promote Mastodon.
The features of the non-Mastodon Fediverse are unknown and outright unimaginable both on Mastodon and outside the Fediverse. And just about everyone believes that Mastodon is as perfect and fully-featured Fediverse software as it ever comes. Pretty much the only ones who don't are those who daily-drive non-Mastodon Fediverse software.
This actually goes as far as Mastodon users trying their hardest to force e.g. Friendica users to throw away their own culture, switch to Mastodon's culture and abstain from using some 80% of Friendica's features because they aren't covered by Mastodon's culture. At the same time, Mastodon users staunchly refuse to adopt any part of any non-Mastodon Fediverse culture. This means that even if non-Mastodon Fediverse devs introduce new features, they'd better not let Mastodon users know.
And so Mastodon can get away both with a laughable set of features, with completely ignoring not only FEPs, but also large parts of the ActivityPub spec, with advertising features which just about the whole rest of the Fediverse has had for years as completely new original inventions of their own, and with implementing non-standard stuff and forcing the rest of the Fediverse to implement "proprietary", non-standard Mastodon developments.
CC:
# # # # # # # # # #
Just hanging out with my penis.
Last updated: 2026-02-24
All text and images © eLoc8.is-fabulous.com