Start the spring off right with our next live concert in the homeroutes series, suzievinnick, originally from Saskatoon now living in the Niagara region. Held in the beautiful events room BirdsCanada, come listen to some great music, grab a drink at our bar and meet some like minded people!
(reposted from LongPointBirdOb)
To be fair, full data portability via ActivityPub has only been available in a stable release of
anything for two weeks.
That was when
Mike Macgirvin 's , created in mid-August of 2024 as a fork of his own and the latest member of a family of software that started in 2010 with Friendica, had its very first official stable release.
And, in fact, Forte just uses ActivityPub to do something that (streams) and its predecessors all the way to the Red Matrix from 2012 (known as Hubzilla since 2015) have been doing using the Nomad protocol (formerly known as Zot). It's called . This is technology that's over a dozen years old on software that was built around this technology from the get-go, only that it was recently ported to ActivityPub.
Now, nomadic identity via ActivityPub was 's idea. He wanted to make his nomadic. He started working in 2023. The first conversion of existing non-nomadic server software to nomadic still isn't fully done, much less officially rolled out as a stable release.
If Mastodon actually
wanted to implement nomadic identity, they would first have to wait until Mitra has a first stable nomadic release. Then they would have to wait until nomadic identity on Mitra (and between Mitra and Forte) has become stable and reliable under daily non-lab conditions. (Support for nomadic identity via ActivityPub on (streams) worked nicely under lab conditions. When it was rolled out to the release branch, and existing instances upgraded to it, it blew up in everyone's faces, and it took months for things to stabilise again.)
Then they would have to look at how silverpill has done it and how Mike has done it. Then they would have to swallow their pride and decide to adopt technology that they can't present as their own original invention because it clearly isn't. And they would have to swallow their pride
again and decide
against making it incompatible with Mitra, Forte and (streams) just to make these three look broken and inferior to Mastodon.
And only then they could actually start coding.
Now look at how long silverpill has been working on rebuilding Mitra into something nomadic. This takes a whole lot of modifications because the concept of identity itself has to be thrown overboard and redefined because your account will no longer be your identity and vice versa. Don't expect them to be done in a few months.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Mitra #
RedMatrix #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
DataPortability #
NomadicIdentity This. Let me add Friendica and Hubzilla/(streams)/Forte to the list. Especially Friendica's culture is actually a whole lot older than Mastodon's culture. It was there and firmly established in 2016 when Mastodon was launched, and it was there and firmly established in 2022 when millions of Twitter refugees redefined Mastodon's culture while completely disregarding and ignoring Mastodon's already existing culture.
Also, just because something in the Fediverse that isn't Mastodon has a different culture than Mastodon, doesn't mean that its culture is wrong and needs to be corrected. It's just made for different software with different purposes and, most importantly, different features. And in this case, "different" doesn't mean "wrong" either.
There is no reason why e.g. Hubzilla absolutely must abolish its own culture (that's older than Mastodon's culture, too) and over 90% of its features along with it and fully adopt Mastodon's culture instead that's geared towards a wholly different set of features.
Many Mastodon users act somewhat like European colonists in the New World: They try hard to force the native population to give up their own "primitive"/"barbarian"/"wrong" culture and adopt
their culture and
their rules and
their mannerisms and
their beliefs.
Or else!The only difference is that the European colonists were not convinced that they were there first, and that the natives had arrived after them. For comparison, too many Mastodon users are fully convinced that not only Mastodon was there first, but that stuff from Pixelfed to Lemmy to Friendica was created after they themselves had joined Mastodon, simply because they've first heard of Pixelfed/Lemmy/Friendica only now.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NotOnlyMastodon #
MastodonNormativity #
MastodonCentricism #
FediverseCulture #
MastodonCulture Long Was die Suchergebnisse angeht: Wenn du auf Misskey, Iceshrimp, Sharkey oder einem anderen Misskey-Fork bist, ist das leider normal. Die Suche auf Misskey und allen Forks ist, sagen wir, nicht besonders gut. Iceshrimp.NET wird es hoffentlich besser machen, wenn es fertig ist.
Ansonsten hast du auf keiner Instanz einen berblick ber restlos das ganze Fediverse. Instanzen knnen nur das kennen, was ihre Nutzer selbst reinholen, indem sie jemandem auf einer anderen Instanz folgen. Keine Instanz, nicht mal mastodon.social, kennt alles, was im Fediverse passiert. Das ist technisch auch gar nicht mglich.
Letztlich kann es auch sein, da
- mastodon.berlin gewisse andere Instanzen blockiert hat, deine andere Instanz aber nicht
- umgekehrt deine andere Instanz gewisse andere Instanzen blockiert hat, mastodon.berlin aber nicht
- Instanzen wiederum nur mastodon.berlin oder nur deine andere Instanz blockiert haben
- einzelne Nutzer dein Konto auf mastodon.berlin und/oder dein Konto auf der anderen Instanz blockiert haben
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse Not everyone will want to offer their music on Bandwagon for money. Some may want to give it away for free for various reasons (non-commercial license, German hobbyist artists not wanting to hassle with the German tax system and GEMA etc.), and Funkwhale may not be a viable option for them. At the same time, they may not want to or even be able to pay the same prices for anything beyond basic functionality as musicians or bands who intend to actually make money with their music.
Some features should remain free for music that's offered for free. For example, it shouldn't be lossless downloads that a musician or a band has to pay for as a feature, but charging money for lossless downloads. Having everyone pay for e.g. offering FLAC downloads favours commercial artists, and the anti-capitalist parts of the Fediverse
will criticise you for that.
Alternatively, you could make the license choosable from a pull-down list per song or per album or for an entire account. And when a commercial license (or any license that isn't decidedly non-commercial) is selected, certain features are greyed-out or removed unless they're paid for. At the same time, when a non-commercial license is selected, the UI elements for charging money are greyed out or removed.
Also, if you ever plan to open-source and decentralise Bandwagon, you can't expect all instances to charge the same for the same. Even if you hard-code in what must be paid for, the moment Bandwagon is open-source, there will be at least one fork where certain or all payments are not hard-coded anymore. Not only will some musicians or bands prefer that fork for their own instances, but it's even likely that public instances of such a fork will be launched.
At that point, your pricing calculation will become moot.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Bandwagon IOTA/USDT
Entry: 0.205 - 0.198
Leverage: 10x - 20x
Targets:
1: - 0.210
2: - 0.217
3: - 0.230
Stop Loss: 0.192
Risk Management: Use only 2-3% margin per trade.
Stay ahead with accurate signals!
Join VIP Now
IOTA/USDT
Entry: 0.205 - 0.198
Leverage: 10x - 20x
Targets:
1: - 0.210
2: - 0.217
3: - 0.230
Stop Loss: 0.192
Risk Management: Use only 2-3% margin per trade.
Stay ahead with accurate signals!
Join VIP Now
with very during for
Kenya Airways Returns to Profit in 2024 After Long Struggle
Something that accessibility professional are unaware of, that they're likely to deny, or that they're even likely to try and fight against:
Image description standards are vastly different in the Fediverse than on websites, in blogs, on , on Facebook, on Instagram, on Threads, on Bluesky, on LinkedIn, on TikTok and everywhere else. They were shaped by sighted Twitter-to-Mastodon converts with zero input from accessibility professionals or actually blind or visually-impaired people.
Accessibility professionals are likely to scream in agony when they see an alt-text that's over 125 characters long. Mastodon users celebrate alt-texts that are over 1,000 characters long and include tons of information that's available neither in the image nor in the post.
I guess you can actually be sanctioned by Mastodon users for a 250-character alt-text, not because it's too long, but because someone thinks it lacks some important information.
At the same time, nobody has ever criticised me for my more recent alt-texts that are either precisely 1,500 characters long or only a few characters short of 1,500. And I've hardly ever been criticised for my long image descriptions that I put directly into the post, and that tend to end up longer than several dozen Mastodon toots.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMetaEast End Blinds
Address: 4102 Sunrise Hwy, Oakdale, NY
Phone: 631 573 6316
Email: admineastendblinds.com
When you read exceptional alt text, do you ever compliment its author What is the epitome of alt text, either in general terms or using a specific example
I'd really like to know that myself, also to up my own game further and always stay way ahead of image description quality requirements.
I mean, over the last two years. But I guess I can still learn something new, even if I think I already take care of everything, even if the technical possibilities I have here on Hubzilla for describing images surpass those on Mastodon by magnitudes.
Maybe, if I learn something new from those who reply, I can weave it into the image descriptions for a series of images that I've been working on since late last year (the descriptions, not the images which are ready to go).
Alt text sometimes merely explains what I am viewing other times it draws my attention to special details in a photo that I would have otherwise missed.
I never explain in alt-text. I do always explain a whole lot because I always have to explain a whole lot. For my original images, it takes me over 1,000 characters alone to explain where an image was made.
But I only ever give explanations in the long, detailed image descriptions that go into the post text body (in addition to shorter and purely visual descriptions in the alt-texts).
Or if there's no additional long image description in the post itself which is the case for my meme posts, I still supply enough explanation in the post text body (still not in the alt-text) for just about everyone in the Fediverse to understand them without having to look anything up themselves. If I can link to external information, e.g. KnowYourMeme for the template I've used, I do so. If I can't, I write the missing explanations right into the post myself.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMetaCO2 laser enables long-range detection of radioactive material
-range
Auf jeden Fall noch vorm Kauf drauf achten, da das Ding nicht mit einem Supervisor-Pawort verdongelt ist. Damit wrdest du nmlich nicht in die UEFI-Konfiguration kommen, um die Bootreihenfolge zu ndern, und normal sind die Dinger so eingestellt, da als erstes vom eingebauten Festspeicher gebootet wird.
ThinkPads der T-Klasse sind sehr oft Leasingrcklufer von greren Kunden, und da ist gerne ein Supervisor-Pawort gesetzt und nie zurckgesetzt worden. Wenn die Vorbesitzer eh nur das vorinstallierte Windows genutzt haben, dann strt sie das nicht nur nicht, sondern meistens merken sie das berhaupt nicht. Und meines Wissens braucht man zum Zurcksetzen des Supervisor-Paworts einen Ltkolben.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
ThinkPadNigerians arrested in Rome, Brescia, Iceland in vice probe TopNews
Das kommt auch davon, da die Mastodon-Neulinge alle am Anfang lernen, da das Fediverse nur Mastodon ist. Oder gar, da das Netzwerk Mastodon heit, und genau gar nichts ber das Fediverse.
Und dann kommt die Mastodon-Community an und verteidigt das auch noch gegen die Nicht-Mastodon-Nutzer, die jedem von Anfang an erklren wollen, da das Fediverse mehr ist als nur Mastodon. Angeblich ist das bergriffig, und das berfordert die Neulinge nur, und das mssen die nicht gleich wissen, und das finden die sowieso irgendwann noch raus, blafasel.
Die Folge ist aber, da diese Mastodon-Neulinge sich in der Zwischenzeit an ein Fediverse gewhnen, in dem alles Mastodon ist. Und das wird fr sie zum Social-Media-Ideal, zum besten vorstellbaren sozialen Netzwerk. Sie fangen an, Software zu entwickeln, die in jeglicher Hinsicht nur zu Mastodon kompatibel ist. Sie ziehen Dienste auf, die auch nur mit Mastodon gehen, schreiben aber "Fedi" dran.
Allerhchstens fordern sie neue Features "im Fediverse", die buchstblich alles, was nicht Mastodon ist, schon ewig hat. Noch eher aber sind sie gegen die Einfhrung gewisser solcher Features "im Fediverse".
Dann aber erfahren sie auf die harte Tour, da das Fediverse nicht nur Mastodon ist. Also nicht, indem ihnen jemand von PeerTube und Pixelfed erzhlt, sondern indem ihnen ein Friendica-Nutzer antwortet und sich dabei keine Mhe gibt, die Antwort wie einen Mastodon-Trt aussehen zu lassen. Ein oder mehrere Teilzitate, Textformatierung und vor allem deutlich ber 1000 Zeichen.
Nicht wenige von denen drehen dann komplett frei und wollen mit Gewalt ihr Nur-Mastodon-Fediverse wiederhaben. Etwas, wovon sie weder wissen noch wahrhaben wollen, da es das nie gab. Denn "bekanntlich" hat Eugen Rochko das Fediverse erfunden.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon Was strt's die deutsche Eiche, wenn sich die Sau an ihr reibt
Was strt's den Friendica-Nutzer, wenn der Riesennode, auf dem er ist, von 8000 Mastodon-Instanzen blockiert wird, weil Friendica Mastodons Quote-Post-Opt-In/Opt-Out nicht bercksichtigt Und auf ber 700 *key-Instanzen, weil deren Admins gar nicht wissen, warum zum Fediblock dieses Node aufgerufen wurde, aber vorsichtshalber mal mitmachen
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteTrt #
QuoteTrts #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebatte #
QuoteTrtDebatte #
FediblockMeta Quote-Posts.
Drkos bzw. Drukos.
Auf Friendica, Hubzilla & Co. das Teilen von Posts, das seit 2010 im Grunde die Standardmethode ist und die meiste Zeit die einzige verfgbare Methode war, um Posts an andere Leute weiterzuleiten.
Die Twitter-nach-Mastodon-Konvertiten, die aber den berwiegenden Teil der Fediverse-Nutzer ausmachen, kennen das als Quote-Tweets, aber auch nur als Methode, um Farbige, Schwule usw. auf Twitter zu drangsalieren. Das ist der einzige Verwendungszweck, den sie dafr kennen. Einen anderen knnen sie sich auch gar nicht vorstellen. Das kommt in der Twitter-Kultur so nicht vor.
Die 60% sind eben die Twitter-nach-Mastodon-Konvertiten. Und von diesen 60% "wissen" mindestens 59, da es im Fediverse keine Quote-Posts gibt. Und mindestens 35, da das Fediverse nur Mastodon ist.
Jetzt hat Mastodon die Einfhrung von Quote-Posts angekndigt. Die 60% flippen jetzt natrlich ihren Shit, vor allem die Angehrigen von Minderheiten, die auf Twitter mit Quote-Tweets drangsaliert werden.
Aaaaaber: Mastodon hat auch angekndigt, da es einen Opt-Out- oder Opt-In-Schalter fr Mastodon-Profile geben wird. Damit sollen Mastodon-Nutzer kontrollieren knnen, ob andere Mastodon-Nutzer ihre Trts quote-posten knnen oder nicht.
Wie gut kennst du Hubzilla Stell dir eine Berechtigungseinstellung "Darf meine Beitrge wiederholen und teilen" vor. Nur da Mastodon kein Berechtigungssystem hat.
Und nur da das ein Eigengezcht von Mastodon sein wird, das keinerlei Grundlage in ActivityPub hat, geschweige denn in irgendwas, was schon irgendwo implementiert ist.
Heit mit anderen Worten: Pleroma und seine Forks, Misskey und seine Forks, Friendica und seine Forks usw. usf., die werden weiterhin allesamt Trts von jedem Mastodon-Nutzer widerstandslost quote-posten knnen, egal, ob sie das qua Mastodon-Kontoeinstellungen drfen oder nicht. Weil sie gar nicht wissen knnen, ob sie das drfen oder nicht.
Auf Mastodon glaubt aber beinahe ausnahmslos jeder, dieser Opt-In oder Opt-Out ist absolut wasserdicht. Es glaubt ja auch beinahe ausnahmslos jeder, da Mastodon die erste und dann einzige Fediverse-Software sein wird mit Quote-Posts.
Wir haben im Grunde geschtzt folgende Aufteilung:
- 35%, die das Fediverse fr nur Mastodon halten.
- 15%, die schon mal von Misskey und/oder Friendica gehrt haben, sich aber nicht vorstellen knnen, da die mit Mastodon verbunden sind, weil das doch ganz was anderes ist.
- 9%, die wissen, da Misskey, Friendica & Co. mit Mastodon verbunden sind, die aber nicht wissen, da Misskey, Friendica & Co. Mastodon-Trts quote-posten knnen.
- 1%, die wissen, da andere Fediverse-Serveranwendungen Mastodon-Trts quote-posten knnen. Entweder, weil sie Leuten wie , Der Pepe (Hubzilla) und mir aufmerksam zugehrt haben, oder weil sie selbst mal was anderes als Mastodon ausprobiert haben, und zwar etwas intensiver, oder weil sie noch etwas anderes als Mastodon nebenher nutzen.
- 40%, die primr etwas anderes als Mastodon nutzen und wissen, da Quote-Posts im Fediverse eben nicht bswillig genutzt werden. Schon gar nicht ausschlielich. Und die auch ganz genau wissen, da so ein Opt-Out oder Opt-In auf Mastodon sie nicht daran hindern knnen wird, Mastodon-Trts zu quote-posten.
So, dann kommst du und teilst einfach mal einen interessanten Post von Mastodon. Was du nicht weit: Der Nutzer, der das gepostet hat, hat in seinem Mastodon-Konto eingestellt, nicht gequote-postet werden zu drfen. Kannst du nicht wissen. Kann auch Friendica nicht wissen. Aber trotzdem quote-postest du den.
Da kannst du mir glauben, der wird
aber mal so richtig hart austicken. Der wird ja gar nicht wissen, da du auf Friendica bist. Woher auch Mastodon zeigt das nicht an. Und auf Mastodon geht auch keine Sau auf die lokalen Profile von Leuten und guckt, wo die sind. Keine Sau.
Zwei Dinge seien noch erwhnt. Zum einen: Wenn Friendica-, Hubzilla-, (streams)- oder Forte-Nutzer Mastodon-Trts quote-posten, werden die Trter darber benachrichtigt. Zum anderen, noch einmal: Auf Mastodon gelten Quote-Posts immer als Akt der Aggression. Immer.
Der wird also glauben, da du entweder auf einer gehackten Mastodon-Instanz bist oder auf irgendwas anderem, was explizit und mit Vorsatz so ausgelegt wurde, da es den Mastodon-Quote-Post-Opt-In/Opt-Out umgeht.
Und dann wird das Geschrei losgehen. Bestenfalls wird gefordert, einen der beiden Friendica-Hauptentwickler (also dich) zu fediblocken, also da du auf allen Fediverse-Instanzen (zumindest denen, die mitmachen), dauerhaft vom Admin gesperrt wird.
Schlimmstenfalls wird das gefordert fr den ganzen Friendica-Node, auf dem du drauf bist, also inklusive allen anderen Nutzern. Warum Weil Pirati.ca bse ist. Weil Pirati.ca Mastodon-Trts quote-posten kann, auch wenn das gar nicht erlaubt ist.
Unvorstellbar Unrealistisch
Dann mchte ich noch einmal daran erinnern, da dereinst von einer Mastodon-Nutzerin geblockt wurde, weil die glaubte, da er ein bser Black-Hat-Hacker ist und Friendica ein bses Black-Hat-Hackertool, mit dem er sich illegalerweise und mit boshafter Intention ins Mastodon-Fediverse reingehackt hat, das von Gargron so entwickelt worden ist, da nur Mastodon-Server sich miteinander verbinden knnen.
Frag ihn. Ist in echt so passiert. Also gibt's solche Leute auch in echt.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon #
Pleroma #
Misskey #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteTrt #
QuoteTrts #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebatte #
QuoteTrtDebatte Best bets for Nations League clash
Shy Green
Another long exposure and also using the solar filter (the filter used usually to observe solar eclipses), but this time, coupled with my modified camera a camera that is tinkered with to be able to take a full-spectrum images (with the help of other filters). Again, I'm using here the Rokinon 8mm fisheye lens, which is completely manual, and the solar filter was taped to the back of the lens.
I was quite surprised for the exposure here. I was expecting something in the range of 3-5 hours because I did so with a regular camera few days prior to this, but unexpectedly, the calculated exposure time here was about 42 minutes and 50 seconds, so approximately 43 minutes. The general look here looks like a scene that I'd get from using an infrared filter on the lens with a low threshold (650700nm). It seems that the solar filter might block most of the visible (and maybe the ultraviolet) range of light, but when it comes to infrared, it is quite permissible!
-exposure Some may have moved to Bluesky because it is what they've been looking for in Mastodon: literally Twitter without Musk.
Some may have moved to other Mastodon instances.
Some may have moved to other places in the Fediverse that are not Mastodon. Maybe they needed more characters and more features and found them on Iceshrimp or Sharkey or Akkoma. Maybe they also wanted to move away from Facebook, got themselves a Friendica account, and then they discovered that a) Friendica is much more powerful, and b) you can follow Mastodon accounts from Friendica and vice versa. And they decided that their Mastodon account was now superfluous because Friendica can do just about all the same and a whole lot on top. Maybe they were even daring enough to tackle Hubzilla's massive learning curve to be rewarded with Hubzilla's massive set of features.
Either way, in the cases in the above paragraph, they couldn't mark their Mastodon accounts as moved to some other specific place, so you won't know.
Still, I think it's bad manners not to tell anyone where you've gone.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Bluesky #
Fediverse #
Mastodon #
Akkoma #
Iceshrimp #
Sharkey #
Friendica Hubzilla
Wow, from the year 2025: use for scripts! Apparently, typing a few extra characters will save the world from and mayhem. How did we ever survive without this wisdom
Use Long Options in Scripts
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 The only talk about a Discord "alternative" in the Fediverse comes from people who want 1:1 clones of all kinds of commercial stuff with an absolutely identical UX, but free and open-source and decentralised with ActivityPub.
Otherwise, for just simply chatting, including multi-user chatrooms, there are Matrix (iOS/Android: Element) and XMPP (iOS: Monal IM, Android: Conversations). They are not part of the Fediverse, but they are free, open-source and decentralised. And they are alternatives to iMessage, Telegram and WhatsApp as well.
For discussion groups/forums, and very much in the Fediverse as in connected Mastodon, there are
- Lemmy (Reddit clone)
- Mbin (like Reddit, but better)
- PieFed (like Reddit, but better)
- Friendica (like Facebook, but better and more powerful)
- Hubzilla (like Facebook, but much better and much, much more powerful)
- (streams) (like Facebook, but much better and more powerful)
- Forte (like Facebook, but much better and more powerful)
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Discord #
DiscordAlternative #
XMPP #
Jabber #
Matrix #
Groups #
Lemmy #
Mbin #
PieFed #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte 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 Why Swinging TOO Long is DESTROYING Your Golf Swing
Hans van Zijst The Comment Control app on (streams) and Forte lets you
- disallow comments on a specific post
- limit comments on a specific post to only your approved connections
- allow comments on a specific post only until a certain date and time in the future
In addition, even without that app, you can generally limit commenting permissions to
- everyone in the Fediverse
- only your approved connections
- only you yourself plus connections whom you specifically give that permission by connection settings/permission role (for those who don't know Hubzilla and its descendants, this means that you can allow some of your mutual followers/followed to reply to you and disallow it for all your other mutual followers/followed while those who follow you without you following them back are not allowed to reply)
You can define a number of days for which people can comment on your posts after sending them.
And you still have Hubzilla's option to "moderate" comments that are, technically speaking, not allowed. (This means that you and only you see them at first. You have two buttons under them. One is for accepting them. In this case, you officially add them to the conversation, and your Friendica, Hubzilla, (streams) and Forte connections will fetch it from your channel. The other one is for rejecting them which also deletes them.)
I don't think that any of this has any influence on whether someone can quote-post ("share") any of your posts or comments. That is, quote-posts are only allowed in public threads anyway. And if there was a permission for quote-posting, it would be defined by the start post for the whole thread because individual comments cannot have individual permissions.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
ReplyControls #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate #
Hubzilla #
Streams #
(streams) #
Forte #
Security #
FediverseSecurity #
PermissionsIntroducing Simon Tathams Puzzles & Tips On Dominosa
I've brought up Simon Tatham's Puzzle Collection here before. It was then, and still is now, one of the great wonders of the World Wide Web, a completely, utterly free, in both beer and libre, collection of randomly-generated puzzles of 40 different
Read The Best 3 S&P 500 Index Funds for 2025: A Complete Analysis by Albert Tan on Medium:
-term investing, &p 500 ETFs, -investing style, creation, planning
That's not what I asked. So if you're not going to answer the question, we'll just go with: "assuming everyone takes one shot."
Lil Bit Sexy Booty
The surprisingly connected origins of "Lent" and "long".
This may come as a surprise, but: is not an abstract concept or a science-fiction idea for the Fediverse.
It is reality. It exists. Right now. In stable, daily-driver software that's federated with Mastodon. And it has been for over a decade.
I'm literally replying to you here from a nomadic channel that simultaneously exists on two servers.
Nomadic identity was invented by
Mike Macgirvin (formerly American software developer of about half a century who has been living in rural Australia for decades now) in 2011 and first implemented in 2012. Almost four years before Mastodon was first launched.
In 2010, he had invented the Facebook alternative , originally named Mistpark and based on his own DFRN protocol.
Over the months, he witnessed lots of privately operated public Friendica nodes shut down with or without an announcement and the users on these nodes lose everything. He added the possibility to export and import Friendica accounts. But that would only help if a permanent shutdown was announced. It did not protect you against shutdowns out of the blue.
There was only one solution to this problem. And that was for someone's identity to not be bound to one server, but to exist on multiple servers simultaneously. The whole thing with everything that's attached to it. Name, settings, connections, posts, files in the file storage etc. etc., everything.
So in 2011, Mike designed a whole new protocol named Zot around this brand-new idea of what he called "nomadic identity" back then already.
In 2012, Mike forked Friendica into something called Red, later the Red Matrix, and rebuilt the whole thing from the ground up against Zot. Red was the first nomadic social networking software in the world, almost four years before Mastodon.
In 2015, ten months before Mastodon was first released, the Red Matrix became , the Fediverse's ultimate Swiss army knife.
I am on Hubzilla myself. is constantly being mirrored between its main instance on and its clone on . Anything that happens on the main instance is backed up on the clone. I can also log into the clone and use that, and whatever happens there is backed up on the main instance.
could go down, temporarily, permanently, doesn't matter I still have my channel, namely the clone. And I can declare the clone my new main instance.
Well, Mike didn't stop at Hubzilla and its original version of the Zot protocol. He wanted to refine it and advance it, but in ways that wouldn't be possible on daily-driver software.
Zot went through several upgrades: Zot6 in 2018 (backported to Hubzilla in 2020, along with OpenWebAuth magic single sign-on). Zot8 in 2020. Zot11 in 2021 which had become incompatible with Zot6 and therefore was renamed to Nomad. Today's Nomad would be Zot12.
Also, in order to advance and test Zot, Mike created a whole bunch of forks and forks of forks. Osada and Zap for Zot6 in 2018, followed by another short-lived Osada in 2019. A third Osada, Mistpark 2020 (a.k.a. Misty) and Redmatrix 2020 in 2020 for Zot8. Roadhouse for
Zot11 Nomad in 2021. All Osadas, Zap, Misty, Redmatrix 2020 and Roadhouse were discontinued on New Year's Eve of 2022.
The most recent software based on Nomad is from October, 2021. It can be found in . It is officially and intentionally nameless and brandless, it has next to nodeinfo code that could submit statistics, and it is intentionally released into the public domain. The community named it after the code repository.
I also have two (streams) channels, one of which is cloned so far.
The newest thing, and that's what the Friendica and Hubzilla veteran
Tim Schlotfeldt referred to, is nomadic identity using nothing but ActivityPub, no longer relying on a special protocol.
This was not Mike Macgirvin's idea. This came from , the creator and developer of the microblogging server application . He wanted to make Mitra nomadic, make it resilient against server shutdown. But he didn't want to port it to Nomad. He wanted to achieve it with nothing but ActivityPub.
So he hit up Mike. The two came to the conclusion: This is actually possible. And they began to work on it. Amongst the results were several FEPs coined by silverpill.
This time, Mike did not create another fork to develop nomadic identity via ActivityPub. He did it all on the
nomadic branch of the streams repository while silverpill did his part on a special development branch of Mitra.
In mid-2024, after enough sparring between (streams) instances, between Mitra instances and between (streams) and Mitra, Mike was confident enough that his implementation of support of nomadic identity via ActivityPub was stable enough. He merged the
nomadic branch into the
dev branch which ended up being merged into the stable
release branch in summer.
Now, at this point, (streams) didn't use ActivityPub for nomadic identity. It still used the Nomad protocol for everything first and foremost, including cloning. But it understood nomadic identity via ActivityPub as implemented on experimental Mitra.
However, while it worked under lab conditions, it blew up under real-life conditions. At this point, (streams) had to handle so many different identities that it confused them, and it couldn't federate with
anything yet.
In mid-August, while trying to fix the problem, Mike eventually forked the streams repository into . It got a name again, it got a brand identity again, it got its nodeinfo back, it was put under the MIT license again.
But most importantly: Any and all support for Nomad was ripped out, also to get rid of a whole number of IDs, namely those for Nomad-actually-Zot12 and for Hubzilla's Nomad-actually-Zot6. Forte only uses ActivityPub for everything. And so, Forte also had to fully rely on ActivityPub for nomadic identity, cloning and syncing.
For almost seven months, Forte was considered experimental and unstable. For most of the time, the only existing servers were Mike's.
But on March 12th, 2025, , the first official stable release of Forte. This is what Tim wrote about. Because this actually made it into Fediverse-wide news.
Not because it's nomadic. Nomadic identity has been daily-driven for over a decade now.
But because it uses ActivityPub for nomadic identity. Which means that you can theoretically make any kinds of Fediverse software nomadic now, all without porting it to the Nomad protocol first.
For the future, Mike and silverpill envision a Fediverse in which one can clone between different server applications. A Fediverse in which one can have one and the same identity cloned across multiple servers of Mastodon, Pixelfed, PeerTube, Mitra, Forte, Mobilizon, Lemmy, BookWyrm etc., all with the same name, all with the same content and settings (as far as the software allows you will certainly not be able to clone your PeerTube videos to Mastodon and Lemmy).
Even if you don't intend to clone, it will make moving instances and even moving from one software to another
dramatically easier.
If you're concerned about your privacy, let me tell you this:
Hubzilla's privacy, security and permissions system is unparalleled in the Fediverse. Except for that on (streams) and Forte which is another notch better.
I can define who can see my profile (my default, public profile on Hubzilla where each channel can have multiple profiles).
I can define who can see my stream and my posts when looking at my channel.
I can define who can see my connections (Hubzilla, (streams) and Forte don't distinguish between follower and followed they aren't Twitter clones).
I can define who can look into my file space (individual permission settings per folder and per file notwithstanding).
I can define who can see my webpages on Hubzilla (if I have any).
I can define who can see my wikis on Hubzilla ().
On Hubzilla, I can define
individually for any of these whether it's
- everyone on the Internet
- everyone with a recognisable Fediverse account
- everyone on Hubzilla (maybe also on (streams) anyone using ActivityPub is definitely excluded here)
- everyone on the same server as myself (AFAIK, only main instances of channels count here, clones don't)
- unapproved (= followers) as well as approved (= mutual) connections
- confirmed connections
- those of my confirmed connections whom I explicitly grant that permission by contact role
- only myself
. And they all have seven or eight permission levels (depending on whether the general non-Fediverse public can be given permission).
On (streams) and Forte, I can define whether things are allowed for
- everyone on the Internet (where applicable)
- everyone with a recognisable Fediverse account
- all my approved connections
- only me myself plus those whom I explicitly grant that permission in the connection settings
Yes, connection settings. Hubzilla, (streams) and Forte give you various ways of configuring individual connections, much unlike Mastodon. This includes what any individual connection is allowed to do.
Hubzilla uses so-called "contact roles" for that, presets with a whopping 17 permissions to grant or deny for any one individual connection. That is, what the channel generally allows, a contact role can't forbid.
(streams) and Forte still have 15 permissions per contact, but they lack some features which Hubzilla has permissions for. These permissions can be set individually for each connection, or you can define permission roles that cover all 15 permissions to make things easier.
Okay, how about posting in public vs in private And when I say "private", I
mean "private". It's "private messages" on Hubzilla, (streams) and Forte, not "direct messages".
Hubzilla, (streams) and Forte let you post
- in public
- only to yourself
- only to your connections ((streams) and Forte only Hubzilla requires a privacy group with all your connections in it for this)
- to all members of one specific privacy group (Hubzilla)/access list ((streams), Forte) that's like being able to only post to those on one specific list on Mastodon
- to everyone to whom one specific non-default profile is assigned (Hubzilla only)
- to a specific group/forum (I'll get back to that later)
- to a custom one-by-one selection of connections of yours
Now, let's assume I have a privacy group with Alice, Bob and Carol in it. I send a new post to only this privacy group. This means:
- Only Alice, Bob and Carol can see the post and the conversation.
- Alice can reply to me, Bob and Carol.
- Bob can reply to me, Alice and Carol.
- Carol can reply to me, Alice and Bob.
- Nobody else can see the post. Not even by searching for it. Not by hashtag either. Not at all.
- Nobody else can see any of the comments.
- Nobody else can comment.
If one of them was on Mastodon, they'd see my post as a DM, by the way, and they could only reply to me. But that's Mastodon's limitation because it understands neither threaded conversations nor permissions.
Or how about reply control This is something that many Mastodon users have been craving for quite a while now. Hubzilla, (streams) and Forte have them. Right now. And they work. They have since 2012.
Hubzilla optionally lets me disallow comments on either of my posts. Users on Hubzilla, (streams) and Forte won't even be able to comment they won't have the UI elements to do so. Everyone else is able to comment locally. But that comment will never end up on my channel. It will never officially be added to the conversation. And at least users on Friendica, Hubzilla, (streams) and Forte will never fetch that comment from my channel as part of the conversation, i.e. never at all.
(streams) and Forte can go even further with all available options. They can disallow comments like Hubzilla. But in addition, they can allow only the members of one particular access list to comment, regardless of who can see the post/the conversation. On top of that, comments can be closed at a pre-defined point in the future. And then you even have a channel-wide setting for how long people can comment on your posts.
Oh, and there's even a setting for who is generally permitted to comment on your posts. And you can additionally allow specific connections of yours to comment on your posts.
Lastly, I've already mentioned groups/forums. Like, you know, Web forums or Facebook groups or subreddits or whatever. Like Guppe Groups on a mountain of coke and with moderation and permission control and optionally private.
Hubzilla has them, and it has inherited them from Friendica. (streams) has them. Forte has them. They're basically channels like social networking channels, but with some extra features. This includes that everything that's send to a group/forum as what amounts to a PM is automatically forwarded to all other members.
On Hubzilla, a forum can be gradually made private by denying permission to see certain elements to everyone but its own members (= connections): the profile, the members, what's going on in it. Depending on what you want or do not want people to see.
On (streams) and Forte, you have four types of forums:
- public, and members can upload images and other files to the forum channel
- public, but members cannot upload images and other files to the forum channel
- like above, but additionally, posts and comments from new members must be manually approved by the admin(s) until their connections are configured to make them full members
- private, non-members can't see the profile, non-members can't see the connections, non-members can't see what's going on in it, but members can upload images and other files to the forum channel
In addition, on all three, a group/forum channel can choose to hide itself from directories. This is always an extra option that's independent from public/private.
What we have here is the most secure and most private Fediverse software of all.
And, once again, at its core, this is technology from 2012. It pre-dates Mastodon by almost four years.
Finally, if you want to know how Hubzilla and (streams) compare to Mastodon:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Mitra #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
ActivityPub #
Zot #
Zot6 #
Zot8 #
Nomad #
NomadicIdentity #
Security #
FediverseSecurity #
Privacy #
FediversePrivacy #
Permissions As a user, () and ().
Why, you ask
tldr: Both Hubzilla and (streams) blow Mastodon out of the water big time in every way possibly conceivable.
- Modular architecture. Features (so-called "apps") can be activated and deactivated server-wide by the admin and then activated and deactivated on individual channels by the users. Third-party app and theme repositories can be added to servers. More and more third-party themes are becoming available for Hubzilla which actually change the layout of the UI. (streams) already has two themes to choose from.
- . Basically bidirectional, near-real-time, live, hot backups of your channels on another server, so-called clones. And the clones can be used just the same as the main instances of my channels. One server shuts down, I lose nothing, I've got at least one clone.
- Channels. One account, one login, multiple fully independent identities.
- Full support for discussion groups/forums, both public and private, both visible in and hidden from directories.
- Full support for threaded conversations by means of .
On Mastodon, a conversation is loosely strung together from posts and more posts. And you're mostly shown piecemeal of single posts. All you ever see is posts that mention you and posts from those whom you follow.
On Hubzilla and (streams), a conversation is the same as on Facebook and Tumblr and every blog out there: one post, any number of comments that totally aren't posts. And you're always shown entire threads with the start post and all comments (unless blocking is in the way). Everyone sees everyone else's comments, always within the context of the conversation. - Mastodon: doomscrolling until you want no more, or until you've got no more time. What you don't scroll down to will remain unread forever. No alternative.
Hubzilla and (streams): unread messages counter plus unread messages list. Click one message on the list, and the whole thread around that message will be displayed, and only that thread, and all unread messages in that thread will be marked read. - No character limit to speak of.
Mastodon: 500 characters, chosen arbitrarily.
(streams): over 24,000,000 characters, limited by the database field size. - Text formatting. Just about all of it. With BBcode on Hubzilla and with BBcode, Markdown and HTML on (streams).
- Spoiler tags. In addition to a summary (which Mastodon misuses for CWs).
- Quotes.
- Quote-posts. (Yes, that's something else than quotes. And yes, Hubzilla and (streams) can quote-post Mastodon toots right now with no problems.)
- Being able to embed images within posts. Not as file attachments, but in-line, right between paragraphs, with text above and more text below. You know, like on a blog.
- Unlimited number of images per post.
- Unlimited number of options per poll.
- The most advanced and fine-grained permissions systems in the whole Fediverse. Well over a dozen individual permissions on up to three levels: for the whole channel, for individual connections, per post/thread. Including reply controls which are even more advanced on (streams) than on Hubzilla.
- Private messages, not direct messages.
- Being able to post only to one specific what-amounts-to-a-list-on-Mastodon-but-on-coke-and-roids. Nobody else can see the post. Nobody else can see the comments thread. And nobody else can comment.
- Regular expressions in filters.
- (Optional on Hubzilla) Individual filters per connection, one whitelist, one blacklist.
- ((streams) only Hubzilla needs filter syntax for this) Declutter your stream by choosing to block boosts either for your whole channel or from individual connections.
- (Optional) Separate text filter that automatically hides posts behind content warnings generated reader-side, easy to configure with only one list of keywords (which supports regular expressions at least on (streams))
- (Optional) Friend zoom/affinity slider that lets you filter your stream by how "close" you are to certain connections (all the way to the left: only you all the way to the right: everyone).
- (Hubzilla only) Connect to diaspora* users.
- (Hubzilla only) Subscribe to RSS and Atom feeds.
- Integrated cloud file space with built-in file manager, permissions management and WebDAV connectivity.
- Integrated event calendar.
- Integrated CalDAV calendar server (which uses the event calendar UI on Hubzilla).
- (Optional on Hubzilla) Integrated CardDAV addressbook server.
- (Hubzilla only optional) Post long-form, formatted, non-federating articles.
- (Hubzilla only optional) Make long-form, formatted, non-federating planning cards.
- (Hubzilla only optional) Built-in wiki engine for multiple wikis per channel with multiple pages each.
- (Hubzilla only optional) Add basic webpages to your channel.
By the way, Hubzilla is older than Mastodon. And Hubzilla even supported ActivityPub before Mastodon.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Hubzilla #
Streams #
(streams) #
NomadicIdentity #
Permissions #
Conversations #
ConversationContainers Have you noticed that there are links in my comments
If it has a different colour from the rest of the content, it's a hyperlink. You're probably used to all hyperlinks always being URLs in plain sight. But , where I am, can not only render, but also generate embedded links where the URL is concealed beneath some other text like on websites and in good blog posts. Mastodon can only show them, but not make them.
All links in my post contain actual in-world pictures. You can't see them immediately. I had to put them all behind summaries plus content warnings because the posts are all extremely long, and Mastodon users may be very sensitive about anything that's longer than 500 characters.
For example:
- . If you're on a phone app, your Web browser will open. I can't help that.
- Tap "View article". The post will unfold from the summary and content warning.
- Scroll down. You'll see:
- the actual post
- the image with alt-text, embedded in the post in-between paragraphs
- over 60,000 characters of long image description
If you
absolutely have to see it in your Mastodon app, search for the hashtag
#UniversalCampus
.
Or:
- . If you're on a phone app, your Web browser will open. I can't help that.
- Tap "View article". The post will unfold from the summary and content warning.
- Scroll down. You'll see:
- the actual post
- the image with alt-text, embedded in the post in-between paragraphs
- over 25,000 characters of long image description
This post is not available on your Mastodon instance, so no chance for you to see it in your Mastodon app. Sorry.
If I were to include images right into this comment, I'd have to add a full set of image descriptions to each image.
I do not have any pictures of halfway realistic buildings at hand. I couldn't post them in the Fediverse anyway. I can't properly describe them, so I can't post them, so it isn't even worth creating the images in the first place.
Beyond my own images, I can recommend two blogs to you: by Thirza Ember a.k.a. and by .
If you want something more artsy, check out the and groups as well as the on Flickr.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Hubzilla #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds I don't even have an app.
As I've said, I post my images on now. There are no desktop or mobile apps for (streams). It doesn't work with Mastodon apps, it never will, and that wouldn't even make sense because they're way too different, and Mastodon apps lack UI elements for critical everyday features on (streams).
In fact, I use (streams) and Hubzilla, to which the same applies, via the built-in Web interfaces in a standard Web browser on a desktop computer running Debian GNU/Linux.
When I scroll an image into such a position that I can get as much alt-text onto the screen as possible when hovering the mouse cursor over it, I may be able to get some 2,800 characters. Something between 3,000 and 3,500 if I go full-screen. But the alt-text pop-up is entirely
below the mouse cursor instead of underneath it. The scroll wheel scrolls the Hubzilla or (streams) UI. There are no scroll bars on the alt-text pop-up. And I can't move the mouse cursor over the alt-text pop-up. Moving the mouse will close the pop-up instead and re-open it below where the mouse cursor is then.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
AltText #
AltTextMeta #
CWAltTextMeta Technically speaking, I've got over 24,000,000 characters for posts and the same over 24,000,000 characters for all alt-texts in a post combined. (if I post any at all), alt-text is not a separate data field but woven into the image embedding code.
Too long alt-text still won't work. The UI can only show so much alt-text at once, and it can always only show the beginning. You can't scroll through alt-text trying it will close the alt-text pop-up.
Besides, alt-text is most important on Mastodon anyway. And as I've already said, Mastodon and its forks (Glitch, Hometown, Ecko etc. etc.) as well as Misskey and its forks (Calckey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon etc. etc.) all cut alt-texts from outside off at the 1,500-character mark and throw the excess characters away.
In my posts, I can go all out. But that leads to extremely long posts. I had before I learned that people do actually prefer externally linked explanations over posts with five-digit character counts due to the many long explanations. And that's without visual descriptions.
On my channel for original virtual world images, I've only got . One image is a fairly simple avatar portrait with hardly any surroundings, the other one is a bit more complex. Altogether, the two long descriptions still exceed 20,000 characters, explanations and text transcripts included.
It could be worse. , but it's complex enough for a 60,000-character description.
In , I've managed to describe one single object in the image with over 3,000 characters and then explain it with another more than 2,500 characters. And that explanation still depends on the explanations earlier in the image description.
This is what happens when the topic is too obscure.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta (berflssige Details auf der einen, fehlende wichtige Info auf der anderen Seite)
Im Endeffekt ist das Beschreiben von Bildern also eine Gratwanderung, um nicht Hochseilakt zu sagen, wo man exakt das Optimum finden mu. Minimal darunter oder darber ist schon sanktionierungswrdig.
Und kopiert es dorthin wo es hingehrt, nmlich in die Medienbeschreibung direkt am Medium.
Damit wre also auch meine Vorgehensweise "illegal": relativ kurze, aber einigermaen detaillierte Beschreibung im Alt-Text plus zustzlich lange, hochdetaillierte Beschreibung inklusive aller notwendigen Erklrungen und inklusive Transkripten aller Texte innerhalb der Grenzen des Bildes im Post selbst (kein erwhnenswertes Zeichenlimit hier). Genau das sehe ich bei meinen eigenen Bildern aber als notwendig an.
Das Problem ist hier nur: Zumindest Erklrungen gehren niemals in den Alt-Text. Manche Menschen haben krperliche Behinderungen, die es ihnen unmglich machen, Alt-Texte aufzurufen. Wenn Informationen nur im Alt-Text zu finden sind und weder im Post noch im Bild, dann sind diese Informationen fr sie verloren.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
AltText #
AltTextMeta #
CWAltTextMeta #
Bildbeschreibung #
Bildbeschreibungen #
BildbeschreibungenMeta #
CWBildbeschreibungenMeta I always explain my image posts extensively because I know they always need extensive explanations, being about very obscure topics and such.
But I don't do so in the alt-text. You should never explain anything in the alt-text. Not everyone can access alt-text. Besides, I'd quickly exceed 1,500 characters which would cause Mastodon, Misskey and their forks to cut my alt-texts off.
Instead, my explanations go into the posts themselves which are almost unlimited. In the case of my original images, the explanations are part of a second, much longer and much more detailed image description in the post.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta