Internazionale by Internazionale Breve guida alla
FediDevs als Ganzes scheint komplett hart gegen Mastodon, nur Mastodon und nichts als Mastodon gebaut zu sein. Oder was auch immer gengend proprietren Mastodon-Kram eingebaut und sich an Mastodon angepat hat, um kompatibel zu sein.
Beispiel 1: Guckt euch mal unter den die Liste der getrackten Instanzen an. Wieviele Nicht-Mastodon-Instanzen sind da, auer einer einzigen Catodon-Instanz (Catodon soll eine Art Mastodon mit einem Rest Iceshrimp-Backend darunter werden, soweit ich das verstanden habe.)
FEDIDevs impliziert doch, fr Entwickler aus dem ganzen Fediverse zu sein. Es schliet aber fast alles aus, was nicht Mastodon ist, und somit auch die Entwickler vieler Serveranwendungen, die nicht Mastodon sind. Die knnen gar nicht teilnehmen, weil das Backend von FediDevs vermutlich nicht mal gegen eine Mastodon-API gebaut ist, sondern direkt gegen Mastodon-Code.
Beispiel 2: ein Starterpack namens "".
Der ist komplett leer. Da ist genau berhaupt nichts drin.
Warum Weil es ganz augenscheinlich technisch vollkommen unmglich ist, irgendwas da einzutragen, was nicht auf Mastodon ist.
Wer auch immer hinter dem Bau von FediDevs steckt, scheint entweder anzunehmen, da das Fediverse nur aus Mastodon besteht. Oder es war einfacher, FediDevs nur gegen Mastodon zu bauen, stattdas eine Promille das eine Prozent die zwei Prozent die knapp 30 Prozent an Fediverse-Nutzern zu bercksichtigen, die nicht auf Mastodon sind.
Ganz offenkundig wei bei FediDevs eine Hand nicht, was die andere tut. Auf der einen Seite gibt's ein Webportal, das nur mit Mastodon funktioniert. Auf der anderen Seite gibt's mit eine Friendica-Gruppe aus denselben Kreisen, wobei die seit einem Dreivierteljahr nicht mehr genutzt wird.
Das, oder dahinter steckt der Vorsatz, das Fediverse (wieder) zu nur Mastodon zu machen, indem alles Mgliche und Unmgliche, was an "Fediverse"-Diensten und -Zusatzfeatures entwickelt und beworben wird, mit voller Absicht gleichzeitig "Fedi" im Namen hat und nur gegen Mastodon gebaut wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #FediDevs
Nicht nur knnte ich ohne groe Schwierigkeiten mit meiner kompletten Identitt und allem, was dazugehrt, umziehen. Sondern ich kann sie auch ber mehrere Serverinstanzen klonen. So liegt sie nicht in einer, sondern aktuell in zwei Hnden. Geht eine Instanz mal offline, oder ist sie gestrt, habe ich einen identischen Klon meines Kanals woanders, und zwar mit allem Content, mit allen Kontakten, mit allen Dateien, mit allen Einstellungen, mit allem Drum und Dran.
Und im brigen kann sich im Fediverse jeder aussuchen,
Wer die technischen Fhigkeiten und Mglichkeiten hat, kann ersteres sogar umschiffen, indem er seine eigene Privatinstanz von was auch immer betreibt, vielleicht gar auf einer Maschine im eigenen Eigentum in den eigenen vier Wnden.
Aber generell habe ich schon genug Erfahrung mit dezentralen Systemen (XMPP, Matrix, OpenSimulator, das Fediverse auch schon seit Anfang der 2010er), da ich sagen kann: So etwas wird sich nie 100% wie ein zentralistisches, kommerzielles Silo anfhlen und auch nie so funktionieren. Und wem das nicht pat, der ist da eben falsch.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadischeIdentitt
Dafr mte Mastodon erst nomadische Identitt einfhren. Dann ginge das ziemlich problemlos. Hubzilla hat das seit Anbeginn, seit 2012. Aber rein ber ActivityPub ist das noch extrem experimentell.
Hufig gestellte Forderung. Aber technisch unrealistisch.
Nehmen wir mal an, ich setze meine eigene (streams)-Instanz auf. Alles konfiguriert, alles startklar. Ich gebe
In diesem Sekundenbruchteil mten alle zigtausend Fediverse-Instanzen sofort von der Existenz meiner (streams)-Instanz wissen. Instantan. Auf der Stelle. (Du hast "wirklich *alle* Server" geschrieben. Also ohne jegliche Ausnahme.)
Das wre nur auf drei Arten und Weisen vorstellbar.
Erstens: Alle zigtausend Fediverse-Instanzen wissen vorher, da ich vorhabe, diese (streams)-Instanz aufzusetzen. Vorstellbar, aber vollkommen unrealistisch.
Zweitens: Meine (streams)-Instanz kennt alle, aber auch wirklich absolut ausnahmslos alle anderen Fediverse-Instanzen, die zu dem Augenblick existieren, wo der Webserver anspringt. Und zwar ohne dezentrale Hilfsmittel.
Das heit: Der Quellcode im streams-Repository enthlt eine nanosekundenaktuelle Liste aller Fediverse-Instanzen. Die Liste wird beim Klonen des Quellcode auf den Webserver mit runtergeladen. Beim ersten Start macht die (streams)-Instanz als allerallererstes einen
So eine Liste mu dann im Quellcode von absolut ausnahmslos jeder Fediverse-Serveranwendung eingebaut sein. Auch wenn jemand gerade erst mit einer ganz neuen Fediverse-Serveranwendung anfngt, mu da sofort diese Liste in vollem Umfang rein.
Und natrlich mu sie aktuell gehalten werden. Das heit, jede startende neue Instanz mu sich selbst in die Listen in den Quellcodes aller Anwendungen eintragen.
Meine (streams)-Instanz mte also alle Fediverse-Serveranwendungen kennen, die es berhaupt gibt. Auch wenn ein Fediverse-Entwickler erst eine halbe Sekunde vorher den allerersten git commit einer ganz neuen Fediverse-Serveranwendung gemacht hat.
Das heit auerdem: Meine (streams)-Instanz mte unmittelbar nach dem Start die Quellcodes von weit ber 100 Fediverse-Serveranwendungen
Jetzt kommt's: Die nderungen mssen ja auch noch gemerget werden. Dafr mte mein (streams)-Instanz sich auf hunderten Git-Repositories volle Maintainer-Rechte verschaffen und die eigenen Commits mergen. Und zwar auch, ja, gerade in Produktivcode.
Ich sage ja nicht, da das potentiell unsicher ist.
Auerdem mu das schnell gehen. Hunderte Repositories klonen, ndern, committen, reinhacken und mergen, alles innerhalb eines Nichtsigstels einer Sekunde, damit die experimentelle Iceshrimp.NET-lnstanz, die jemand eine Zehntelsekunde spter startet, auch von meiner eigenen (streams)-Instanz wei und ihre eigene Instanz meiner (streams)-Instanz mitteilen kann.
Noch einmal: Du hast "wirklich *alle* Server" gesagt. Das heit, eine neue Iceshrimp.NET-Instanz mu zwingend und sofort eine neue (streams)-Instanz kennen, die eine Zehntelsekunde frher gestartet ist.
Ach ja, das ganze Theater ist auch vollumfnglich ntig, wann immer
Jeder Entwickler wird mir besttigen, da das nicht nur komplett unrealistisch ist, sondern absolut haarstrubend. Alleine schon, weil 99,9% der Commits in den meisten Repositories von Fediverse-Instanzen kommen werden und alle Commits, die hndisch von Entwicklern kommen, darunter ersaufen. Und weil kein Entwickler seine eigenen Sachen so schnell rebasen kann, wie neue Commits mit nderungen an der Instanzenliste reinkommen.
Okay, also bleibt als dritte und einzige noch mgliche Lsung eine zentral verwaltete Liste auf einem zentralen Webserver.
Dieser Server mu verpflichtend in alle Fediverse-Serveranwendungen eingebaut sein. Auch die, die eigentlich gar nicht mehr gewartet werden, aber noch laufende Instanzen haben (Calckey, Plume usw.).
Damit wrde sich das ganze Fediverse bis in den allerhinterletzten Winkel absolut und total abhngig von zentraler Infrastruktur machen.
Warum das schlecht ist Stell dir mal vor, diese Liste geht offline aus irgendeinem Grunde. Oder irgendeiner, z. B. Elon Musk oder Jeff Bezos oder Mark Zuckerberg, kauft den Webserver mit der Liste drauf. Der htte dann die totale Kontrolle ber das Fediverse.
Willst du das
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #git
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...
...into this...
...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 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. can probably confirm it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Nachdem sie sich monate- oder jahrelang an ein Fediverse gewhnt haben, das nur aus dem flauschigen Wollmammut besteht. Da es anders sein knnte, ist fr sie gnzlich unvorstellbar.
Dann luft ihnen ein vermeintlicher "Trt" ber den Weg, der so vllig anders ist als all das, was aus ihrer bisherigen reinen Mastodon-Bubble kam. Mehr als 500 Zeichen. Textformatierung. Ein Zitat. Eine Drko oder Druko (also ein "Quote-Trt").
Das ist fr viele so verstrend wie ein H.R.-Giger-Xenomorph in einer Schafherde. Einige glauben erst an eine "bse", "gehackte" Mastodon-Instanz. Wenn sie dann erfahren, da das von etwas ist, das mit Mastodon verbunden ist, also mit ihnen auf Mastodon, das aber selbst nicht Mastodon ist, sind sie nicht selten noch mehr verstrt.
Und dann wollen sie das weghaben. Sie wollen ihr flauschiges reines Mastodon-Fediverse wiederhaben. So Sachen wie Calckey, das nutzt, oder Friendica oder das von mir genutzte Hubzilla nehmen sie als Eindringlinge wahr, die sich gerade erst unrechtmigerweise ins Mastodon-Fediverse reingehackt haben.
Wohlgemerkt, Hubzilla ist je nach Definition entweder zehn Monate oder knapp vier Jahre lter als Mastodon und Friendica fnfeinhalb Jahre. Und Mastodon ist mit beiden so lange verbunden, wie es selbst existiert.
Auch die Mastodon-Kultur, die viele Mastodon-Nutzer zur verpflichtenden Kultur fr das gesamte Fediverse machen wollen, ist so erschaffen worden von Mastodon-Nutzern, die zu dem Zeitpunkt nicht mal ahnten, da das Fediverse vielleicht mehr ist als nur Mastodon. Sie ist komplett und ausschlielich ausgelegt auf die Features von Mastodon 3.x und auch nur auf die.
Es gibt zwischen Mastodon-Nutzern und Nicht-Mastodon-Nutzern in dieser Hinsicht zwei groe Unterschiede.
Zum einen:
Mastodon-Nutzer haben entweder kein Problem, die Mastodon-Kultur zu leben, oder sie tun es lngst. Immerhin ist die Mastodon-Kultur zugeschnitten auf das, was sie eh nutzen.
Fr Nicht-Mastodon-Nutzer bedeutet die verpflichtende Mastodon-Kultur aber die Aufgabe der Kultur dessen, was sie selbst benutzen, und damit auch die Aufgabe von auch mal 90% der Features von dem, was sie selbst benutzen. Denn die Nutzung dieser Features strt die Mastodon-Kultur.
Zum anderen:
Nicht-Mastodon-Nutzer kennen es vielfach, dafr attackiert zu werden, da sie sich nicht ganz genau so verhalten, wie man es auf Mastodon erwartet.
Mastodon-Nutzer knnen sich dagegen vielfach nicht mal vorstellen, da das berhaupt passiert. Denn ihnen passiert das nicht.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon
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:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta Alexander Goeres Die Alternative wre ein Mastodon, das sich wirklich wie Twitter anfhlt. Fully-featured App namens "Mastodon", die genau wie die Twitter-App aussieht, aufs Handy laden und lostrten. Vielleicht noch Nutzername und Pawort. Idealerweise bernimmt die App gleich den Nutzernamen und das Pawort aus einer anderen App, z. B. der -App.
Der Nutzer wird natrlich auf mastodon.social geparkt. Die App guckt in anderen installierten Apps, woran der Nutzer interessiert ist, und folgt sofort mindestens 200 bis 300 anderen Mastodon-Konten. (Wohlgemerkt, ausdrcklich nur Mastodon-Konten.) Folgeanfragen, die erst besttigt werden mssen, forciert die App dabei auf der Seite der Gefolgten.
Die App mu dann eine totale Black Box sein und das Konzept von Instanzen komplett verschleiern. Der Nutzer darf nicht mal wissen, was fr eine Website dahintersteckt.
Dann darf der Nutzer aber auch nicht mit Posts verwirrt werden, die irgendwie Rckschlsse auf die Technik oder das Fediverse zulassen. KI-gesttzte Schlsselworterkennung mu alles an Content vom Nutzer fernhalten, was
Das heit, der Nutzer mu durchgngig verhtschelt werden bis zum Gehtnichtmehr, noch sehr viel mehr als sowieso schon. Wir wollen ihn doch nicht gleich wieder vergraulen, oder
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #UX Well, Mastodon's internal character limits, 500 characters for posts, 1,500 characters for alt-text, are both hard-coded in a file that is being synced by git. It can be changed, but only by modifying what's essentially the source code.
Mastodon's current culture was established in 2022 by people who came in from Twitter in the first migration wave which started in February when Elon Musk announced his intention to take over Twitter. In this migration wave already, so many people came to Mastodon, especially mastodon.social, that it didn't take long for them to only encounter their own likes and hardly come across anyone who had been Mastodon users before 2022. Thus, they created a culture that was completely independent from pre-2022 Mastodon.
Also, not a single one of them knew what the Fediverse really was. For absolutely all of them, the Fediverse was Mastodon and only Mastodon. Vanilla Mastodon with a hard 500-character limit which, in the light of only 280 characters on Twitter, already felt like a lot to them.
They did not know about Misskey with 3,000 hard-coded characters. Or Pleroma and Akkoma with 5,000 configurable characters. Or the various Misskey forks with configurable limits of several thousands of characters. Nor did they know about Friendica, over five years older than Mastodon, or Hubzilla, a Friendica fork that's still almost four years older than Mastodon at its core. These two don't have any arbitrary character limits at all. And especially, they didn't know that all of these were fully, bidirectionally connected to Mastodon and interacting with Mastodon all the time.
In fact, ever since, it has always taken Mastodon newbies quite a while to even learn about Mastodon instances with modified character limits, not to mention Mastodon forks with configurable character limits.
And so it was those recent Twitter-to-Mastodon newbies who defined a whole new culture, based on vanilla Mastodon 3.x, its features and its limitations, but for the entire Fediverse. This culture was set in stone in late October already when the second migration wave started, and Mastodon newcomers who really settled into Mastodon, rather than wanting another Twitter, have been living this culture ever since.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #CharacterLimit #CharacterLimits #AltText #AltTextMeta #CWAltTextMetaThis is going to be one busy day in OpenSim. I'll have to skip the Discovery Grid farewell party, but I've never had close ties to that grid anyway.
OpenSimulator Community Conference starts today Hypergrid Business
HG Safari: Something for the Weekend
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #DiscoveryGrid #OpenSimulatorCommunityConference #OSCC #OSCC2024 #OSCC24 There's no syntax for it on mastodon.social. You simply can't do it there.
Some users have already mentioned Markdown which is supported by a few Mastodon forks, Pleroma, Akkoma, Misskey and its several forks (including but not limited to Firefish, Iceshrimp, Sharkey and Catodon), Mitra, (streams), Forte and optionally also by Friendica, probably also by others.
For completion's sake, Friendica, Hubzilla, (streams) and Forte mainly use BBcode.
The syntax for quotes is either quoteHere goes the quote/quote or quote="Whoever is quoted"Here goes the quote/quote.
Both in-line code and code blocks are delimited with
Lastly, (streams) and Forte even support HTML.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Markdown #BBcode #HTML #TextFormatting Well, what I meant with "do what I do anyway" is not what everyone else does.
My Fediverse meme posts have fairly standard image descriptions. What may make them long and complex are the explanations. They matter in this context because everyone else would explain meme images in the alt-text, but explanations don't belong into alt-text. And meme posts about Fediverse things do need a lot of explanation if they go beyond Mastodon, and mine tend to go way beyond Mastodon.
(Content warning: eye contact) was made under the assumption that Mastodon users prefer explanations given to them on a silver platter, right in the post itself which also contains the image. I was told a while ago that external links are bad and inconvenient and probably not accessible, and it's better to explain everything myself.
I always have to explain the meme template, and especially in this case, I also had to explain the topic. So I ended up with nine explanations on four or five levels with some 25,000 characters altogether, more than half of which went into the two explanations for the topic.
I couldn't imagine that this was actually what people wanted, seeing as it was generally Mastodon users who seemed to want me to explain everything, but at the same time, it's Mastodon users who complain the most loudly about long posts. And so on how people actually wanted meme posts to be explained. At least of the few who voted, nobody wanted explanations in the post if they end up tens of thousands of characters long.
Ever since, I've delegated the meme template explanations to KnowYourMeme which I link to.
As for the topic, (content warning: eye contact, guns) . Sometimes (content warning: eye contact, food) . Sometimes (content warning: eye contact) .
But in cases like (content warning: eye contact, swearing) or (content warning: eye contact, anger, crying, Japanese swearing) , I have to write extensive explanations, even if I can link to a whole lot of external information sources.
For my original images, renderings from very obscure 3-D virtual worlds, I do much more. I always write two image descriptions for each image.
One goes into the alt-text, and it's as long as I can make it within the 1500-character limit imposed by Mastodon, Misskey and their forks. And that's the short description that's mostly only there to satisfy the "every image must have alt-text, no matter what" fundamentalists.
There's also a long description in the post itself which is much, much more detailed. It also contains all necessary explanations which I have to write myself because I can't really rely on external links. And if there's any text anywhere within the borders of the image, legible or not, verbatim transcripts of all these bits of text go into the long description.
My most recent example, already on my new image-posting channel, but from four months ago, is (content warning: eye contact) . I've taken care to have as little scenery or surrounding or anything else in the pictures as possible, and still, I ended up with over 20,000 characters of image description. I explain why portraits are easier to describe.
A few examples with scenery, in chronological order, and much longer descriptions, and I consider them all outdated regardless: (content warning: eye contact, food) , (content warning: eye contact) and (content warning: eye contact) .
The first two links also demonstrate how I used to describe pictures within a picture, even on three levels in the case of the second link. But if I had carried on doing this the same way for the image behind the third link, I would have had to describe over a hundred images in various locations on at least four levels. Besides, I would have described details that not only aren't visible in the image, but that aren't visible either in the place shown in the image. Also, this might have revealed eye contact or another trigger of sorts.
So I decided against describing things that cannot be seen in the shown place. This was the first time that I actually imposed a limitation on myself.
I could post many, many, many more scenery pictures, maybe even with actual scenery and with many more details. But it would always take me days to describe one of them. The last two image posts I've linked to required two days to write descriptions.
For example, a month ago. It would have made for a gorgeous picture report. But it would have taken me at least a week and a half to only describe the four images that Mastodon would let through. In fact, Mastodon would have rejected the post anyway because, with the massive image descriptions, it would have exceeded 100,000 characters by far.
If you're wondering why my descriptions of virtual world images have to be so long and so detailed, .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
I feel bad when I can't describe something in an image the way I'd like to see myself describe it.
I keep coming across scenes that I think might make for nice pictures. But then I start trying to describe them in my head. And when I discover something that I can't properly describe, I don't even take the picture. I couldn't post it anyway without a description that's up to my standards.
I refuse to post images with realistic-looking buildings in them due to how complex they are to describe. After all, I'd have to first research architectural terminology and then explain it to my readers in the long image description.
A bit over a year ago, while working on an image description which, the next day (!), would , I realised that I had to describe three pictures of stellar nebulae. I didn't even really know how. I was about to abandon the whole image-posting project due to this. What I've eventually written still feels like a sub-par kludge, not to mention outdated a few times over.
I've read about people going back and alt-texting their entire backlog of image posts. I've wondered a few times if it is or should be recommended to go back and edit and improve your old image descriptions after you've learned something new in terms of describing images.
What do you think, is this genuine or not
And seriously, I don't even know whom exactly I'm doing all this for because I almost never get any feedback in any form. I do it for whoever comes across one of my image posts. Since my new channel for original images (which I do these monstrous descriptions for) has only got nine followers, and my channel for Fediverse memes (which at least tend to come with extensive explanations) has only seven, it has to be a very rare occurrence that someone who really needs an image description finds one of my image posts.
But I guess the ultimate solution is to forget about "" and do what I think is right until too many people come complaining. Which will probably amount to indefinitely.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility I think that's part of the issue, even if it's unavoidable: There's no one way to please everyone. And the more niche and special your content is, the harder it becomes to please as many disabled people as possible.
There's a saying: "." Don't assume what disabled people may need. Ask them. Talk to them. Listen to them.
But I guess the attitude in the Fediverse is that everything is said, everything is defined, everything is set in stone, and it'll work in 100% of all cases. No need to talk about it. You're expected to know it. Just do it.
I mean, I could just carry on assuming, based on what I've read here and there, even if that's technically the wrong thing. I know that there are at least some people who enjoy what I do, for whom it may be helpful.
I could just go on doing that and improving that, for any definition of improving. I could go on until enough people complain to me that I'm doing it completely wrong, and that staggering level of detail is bad for magnitudes more people than it helps. But this is unlikely to happen, seeing as how little feedback I receive.
I mean, at the end of the day, I can't really know whom I describe my images for. Do blind or visually impaired users even come across my image posts, seeing as they come from two different channels than this one now Do those come across my image posts who demand sanctions for everyone who doesn't describe their images sufficiently Are my extensive image descriptions and explanations useful for anyone
Still, I go on putting huge efforts into describing them for the random stranger who stumbles upon one of them on some federated timeline, regardless of whether they're visually-impaired, blessed with a terribly slow Internet connection or a fully sighted alt-text enforcer.
And I will most likely go on increasing my efforts where I can. I'm currently polishing my way of describing persons or rather avatars. After all, I can see the alt-text quality requirements in the Fediverse be constantly raised, too. I need to stay ahead of them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility Add your location to a Google Map Apparently, accessibility is not about trying as hard as you can. It has to be about trying exactly the right amount of hard without even knowing what the right amount is because the right amount is different for everyone.
For the record: I refuse to post any image without sufficient description. And "sufficient description" may mean two descriptions, a short (and still long) one in the alt-text, a massive one in the post. If I can't describe it properly, I don't post it. And I'm trying to up my game and add new tricks and new elements to my descriptions.
On the one hand, disabled people demand being involved in the topic of accessibility. Before you do something, consult with those whom you want to help. Don't just simply assume what they may need. Ask them. Discuss things with them.
On the other hand, apparently, asking too much will get you branded ableist, all the way to your home instance with over users being on the brink of a fediblock.
Here's a comment I've written on by . I've directed it to a blind user whom I may have asked once too much.
Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Here is his reply in which he claims I'm an ableist who actually doesn't want to describe images. This is far from the truth.
You really don't think I remember you do you You ask this question every single time in an attempt to badger users like me into getting away with *not* providing alt text because you wanna be ableist but try to pass it off as perfectionist. You will *never* please everybody, so to even try and to even is patronizing and ableist all by itself. I consider you to be nothing more than a troll. Look dude, if you don't wanna provide alt text then don't fucking provide it, but don't insult my intelligence with this obvious C lion tactic of I'm a perfectionist. I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.
Here is my reply.
If I didn't care for accessibility, if I didn't want to describe my images, why would I want to satisfy everyone, all the way to random strangers who stumble upon my posts in some federated timeline I shouldn't even want to satisfy anyone!
Why would I spend literal days, morning to evening, Twice per image
Why would I refuse to even take pictures, let alone post them, if they'll be too difficult to describe in a way that I consider sufficient
Why would I pick up any advice on how to describe certain things, like people or colours, and consider any of my image descriptions that don't have this incorporated hopelessly outdated
Why would I transcribe text that's too small for sighted people to read, just because all text in an image has to be described Why would I feel bad about text that I couldn't transcribe and then try to find a source for that piece of text And yes, I do.
Why would I be literally the only one in the entire Fediverse who tries to tell people that and why explanations don't go into the alt-text because people with certain disabilities can't access alt-text, and any information that's only available in alt-text is lost to them
And why would I warn sensitive people about eyes or food that's in the image on a microscopic sub-pixel level if I didn't care And yes, I actually did that. .
Just because I don't just simply shut up and describe my images exactly on point like you personally want them described, doesn't justify insulting me as an ableist.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism
In the meantime, he wrote and sent this post in which he called for a fediblock of either my channel or the entirety of hub.netzgemeinde.eu, the biggest Hubzilla instance.
Link at end. I'm unsure if is on his own instance, but for concerned trolling and ableist behavior by being patronizing to disabled people about alt text. I can't find others on his instance, but every, single time, the person posts the same question over and over and over and over and over and over and over and over and over and over and over again, and expects disabled people to tell this person because you can't describe every thing in an image you don't have to do alt text. Or maybe my temper is just short today, but here's the question. This isn't genuine curiocity because he asks the, same, question, over and over and over and over and over and over and over and over and over again. No answer is to his satisfaction. Nobdoy waste your time with this obnoxious troll. If it turns out I am lashing out of anger and have misjudged, will delete the post but
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteBoost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility #Ableist #Ableism #FediblockMeta
If I didn't care for accessibility, if I didn't want to describe my images, why would I want to satisfy everyone, all the way to random strangers who stumble upon my posts in some federated timeline I shouldn't even want to satisfy anyone!
Why would I spend literal days, morning to evening, Twice per image
Why would I refuse to even take pictures, let alone post them, if they'll be too difficult to describe in a way that I consider sufficient
Why would I pick up any advice on how to describe certain things, like people or colours, and consider any of my image descriptions that don't have this incorporated hopelessly outdated
Why would I transcribe text that's too small for sighted people to read, just because all text in an image has to be described Why would I feel bad about text that I couldn't transcribe and then try to find a source for that piece of text And yes, I do.
Why would I be literally the only one in the entire Fediverse who tries to tell people that and why explanations don't go into the alt-text because people with certain disabilities can't access alt-text, and any information that's only available in alt-text is lost to them
And why would I warn sensitive people about eyes or food that's in the image on a microscopic sub-pixel level if I didn't care And yes, I actually did that. .
Just because I don't just simply shut up and describe my images exactly on point like you personally want them described, doesn't justify insulting me as an ableist.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism
Yes, because by default, Hubzilla always displays entire threads at once. Start post on top,replies comments neatly listed below in chronological order. Just like Facebook does. Just like Tumblr does. Just like a blog does. Just like a forum does. Only that if there are more than three comments, Hubzilla only shows the most recent three until you roll out the whole thread.
The Mastodon piecemeal way of making each reply into its own post and showing them one by one as separate items is optionally available, but I've got my doubts that anyone has actually ever used that feature.
I'd show screenshots, but I don't have enough time to adequately describe them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla
Yes, because by default, Hubzilla always displays entire threads at once. Start post on top,replies comments neatly listed below in chronological order. Just like Facebook does. Just like Tumblr does. Just like a blog does. Just like a forum does. Only that if there are more than three comments, Hubzilla only shows the most recent three until you roll out the whole thread.
The Mastodon piecemeal way of making each reply into its own post and showing them one by one as separate items is optionally available, but I've got my doubts that anyone has actually ever used that feature.
I'd show screenshots, but I don't have enough time to adequately describe them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla On Mastodon, a thread is loosely tied together from posts and more posts. You, as a user, get them one by one. And you only get posts into your timeline
Here on Hubzilla, and actually in the whole family from Friendica to Forte, it's vastly different. Here, a conversation is an enclosed object. A thread, any thread, has exactly one post. That's the start post. Everything else is not a post, it's a comment.
This also means that Friendica, Hubzilla & Co. don't serve you single activities like Mastodon serves you single posts. Threads aren't piecemeal here. Threads come in one piece.
Instead, when you have a post (remember the distinction, "post" only means start post, as in something that isn't a reply to anything else) in your feed/timeline/stream, you also receive all comments on that post. Still under the same post and not as separate activities, not by default anyway.
It's like on Facebook or a blog or in a forum. After all, Friendica, the oldest member of the family, was created as an alternative to Facebook more than five years before Mastodon was made.
There's another big difference between Mastodon on the one side and Friendica, Hubzilla, (streams) and Forte on the other side: The latter four have an unread activities counter and an unread activities list. Mastodon doesn't have either. Mastodon doesn't even have a concept of unread.
On Mastodon, you go to your timeline, and you scroll down until you either hit something that you know you've already read, or you don't have any time anymore, or you don't want anymore. What you don't scroll down to, you will never know you've ever received it.
Here on Hubzilla, I have a counter of unread activities at the top of the the right-hand sidebar. It includes
If I open the counter, I get a list of all unread/unnoticed activities. I can apply a filter that only shows me new posts with one click. It's only a list, though it's not the actual activities like in a Mastodon timeline. It only lists up all these activities so I can load them manually.
So what I usually do first is apply the posts-only filter. Then I scroll down to the oldest item on the list. I click it. In the middle (we were in the right-hand sidebar until now), the post with that activity is shown, complete with all comments known to my stream, like a post on Facebook or a blog post with its comments neatly listed right below.
Now, let's suppose this post came with 68 comments and 11 repeats (that's "boosts" in Mastodonese). That's one unread post, 68 unread comments, 11 unnoticed repeats, all loaded and read/noticed in one fell swoop. The unread activites counter goes down by 1+68+11=80 items.
And then I go on with the next new post.
Once I'm through the new posts, I turn the filter off again, and the unread activities list shows me everything that isn't a new post.
I scroll down again. I click on the bottom-most item. Whatever it is, it loads an entire thread with a post and, if there are any, its comments. And whatever was in this thread that I hadn't paid attention to yet is flagged read and removed from the unread activities list, and the counter goes down by that number again.
Now, my situation as described in the post (again, posts vs comments from a Hubzilla point of view) is that the official Mastodon account or Eugen Rochko or some Mastodon devs (intentionally not mentioning either) tend to post stuff which is then boosted by , and which may receive well over 100 replies.
Now let's suppose Eugen Rochko posts something, and Fediverse Report boosts it, and it gets 280 replies. Let's also suppose I only follow Fediverse Report.
On Mastodon, I'd only receive Eugen's post in my timeline. That's it. Unless, of course, someone mentions me in one of the replies, or someone decides to boost one of the replies to me. Then I also receive that one reply. Separately.
Here on Hubzilla, I receive Eugen's post and all 280 replies in my stream. That's 281 unread activities, and that doesn't even include boosts and edits. That's at least 281 pieces of uninteresting clutter on my unread activities list. Granted, when I click one of them, the whole thread loads, and 281 pieces of uninteresting clutter are marked read and removed from the list, and the unread activities counter goes down by 281. And I no longer have to wade through all that clutter to find the actually interesting content.
But I don't necessarily want to see that gunk. I don't want to click it.
And so I've Superblocked the official Mastodon account and the official Mastodon Development account and Eugen Rochko and some devs. In fact, I've also Superblocked a few more Mastodon users who tend to attract replies like lamps attract moths, just in case someone whom I've given permission to send me their boosts (yes, I can disallow that for individual contacts) boosts something from one of them.
Now I don't receive the actual content anymore. But if someone boosts something from someone Superblocked to me, it still shows up on the unread activities counter. It and all replies to it. If Eugen Rochko (Superblocked) posts something, Fediverse Report (not Superblocked, allowed to send me boosts) boosts it, and it gets 280 replies, that's still 281 unread items on the list.
The catch: Since Eugen Rochko's post is blocked, so is the whole thread. I can't load his post, and I can't load any of the replies either because loading any reply would require loading the post. Remember that replies aren't piecemeal here on Hubzilla, unlike on Mastodon.
And if I can't load them, I can't have them marked read the natural way. Mind you, I do have a "Mark everything read" button. The only way to mark that stuff read. But if I used it, I'd also mark the interesting unread stuff read.
So I have to scroll through a list of hundreds of unread replies to Eugen Rochko's post and boosts of such replies and whatnot to find the halfway interesting stuff, pick it out, click it, load it, read it, interact with it etc. Then more scrolling until I find something interesting again. Wash, rinse, repeat.
Only when everything on the list of unread activities is from threads starting with blocked posts, I can click "Mark everything read".
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte That's good.
I've asked because I've got the feeling that alt-text/image description requirements are constantly being refined and raised in the Fediverse, and more and more existing descriptions won't pass anymore.
See, I usually spend hours on meme posts, both describing the image in the alt-text and explaining it in the post. As for my original images, it can take me days to describe them twice over, once in a "short" description in the alt-text that's actually already fairly long, once in a "long" description the size of an essay or even a short story in the post itself.
And I'm honestly waiting for the first to be so dissatisfied with that that they reply with their own alt-text and order me to both replace my alt-text with theirs and remove the long description from my post or else.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I may not be on Mastodon (seriously, I'm not, open my profile and look at it), but same here. My image posts are usually one every few weeks, sometimes with more than a month in-between.
I can't churn out image posts daily if it takes me hours to write a proper explanation for one meme post or several days to describe and explain one original image in a way I consider sufficient. In fact, it takes long enough to find motives that won't cause me to spend weeks describing and explaining the image.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaWondering whether I should un-Superblock the various official Mastodon accounts. I've blocked them to unclutter my stream and free it from content that I'm not interested in. Still, since their posts come to me as boosts, they end up on my list of unread activities. And so do all comments from after the posts were boosted to me. These posts often have well over 100 comments. And here on Hubzilla, when I receive a post, and that post is being commented on 150 times, this doesn't count as one unread activity. It counts as 151 unread activities. That's two features that Hubzilla has but Mastodon doesn't at once.
I mean, when something from these accounts is being boosted to me, I get a notification for the post and then 100+ notifications for comments either way, regardless of whether they're Superblocked or not. And when I scroll through those notifications of content that I can't access because it's Superblocked, I have to pick out the few notifications in-between about activities from connection that I haven't Superblocked.
I might just as well un-Superblock them. Okay, then I might be tempted to see that propaganda that at least implies Mastodon is either the best there is in the Fediverse or the Fediverse. Not to mention the masses of comments from 99.9% Mastodon users, most of whom think the Fediverse is only Mastodon, most of the rest of whom think there's nothing better in the Fediverse than Mastodon, and none of whom has read even one other comment in the thread because Mastodon has no concept of conversations.
And I might be tempted to comment on 40 comments which essentially say the same because nobody on Mastodon ever reads other people's comments (because nobody receives them in the first place), and which are based on the assumption of there not being much/anything else in the Fediverse except Mastodon.
I might end up being blocked by another few dozen Mastodon users for whom my comment was the very first activity they've received from outside vanilla Mastodon, the very first one with over 500 characters, maybe the first one with text formatting, not to mention the freakish-looking long-name mentions (no, I can't turn them off, they're hard-coded, and they've been since some four years before Mastodon was launched).
I might even end up in another dispute between "the usual suspects" from Calckey, Akkoma, Friendica etc. on the one side and fundamentalists who want the Fediverse to be only Mastodon on the other side.
But at least I can mark over 100 comments read in one fell swoop by actually loading them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonWondering whether I should un-Superblock the various official Mastodon accounts. I've blocked them to unclutter my stream and free it from content that I'm not interested in. Still, since their posts come to me as boosts, they end up on my list of unread activities. And so do all comments from after the posts were boosted to me. These posts often have well over 100 comments. And here on Hubzilla, when I receive a post, and that post is being commented on 150 times, this doesn't count as one unread activity. It counts as 151 unread activities. That's two features that Hubzilla has but Mastodon doesn't at once.
I mean, when something from these accounts is being boosted to me, I get a notification for the post and then 100+ notifications for comments either way, regardless of whether they're Superblocked or not. And when I scroll through those notifications of content that I can't access because it's Superblocked, I have to pick out the few notifications in-between about activities from connection that I haven't Superblocked.
I might just as well un-Superblock them. Okay, then I might be tempted to see that propaganda that at least implies Mastodon is either the best there is in the Fediverse or the Fediverse. Not to mention the masses of comments from 99.9% Mastodon users, most of whom think the Fediverse is only Mastodon, most of the rest of whom think there's nothing better in the Fediverse than Mastodon, and none of whom has read even one other comment in the thread because Mastodon has no concept of conversations.
And I might be tempted to comment on 40 comments which essentially say the same because nobody on Mastodon ever reads other people's comments (because nobody receives them in the first place), and which are based on the assumption of there not being much/anything else in the Fediverse except Mastodon.
I might end up being blocked by another few dozen Mastodon users for whom my comment was the very first activity they've received from outside vanilla Mastodon, the very first one with over 500 characters, maybe the first one with text formatting, not to mention the freakish-looking long-name mentions (no, I can't turn them off, they're hard-coded, and they've been since some four years before Mastodon was launched).
I might even end up in another dispute between "the usual suspects" from Calckey, Akkoma, Friendica etc. on the one side and fundamentalists who want the Fediverse to be only Mastodon on the other side.
But at least I can mark over 100 comments read in one fell swoop by actually loading them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon
Wohlgemerkt:
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Bluesky #Hubzilla #Streams #(streams) #Forte #NomadischeIdentitt Richtig, Mastodon fing eigentlich mal an als alternatives Frontend fr GNU social, genau wie Pleroma. Aber Mastodon wurde schneller zu etwas Eigenstndigem hochgejazzt, zumal es auch nicht alle Features von GNU social untersttzte.
Hubzilla und Mastodon (in der Reihenfolge) waren ja die ersten, die ActivityPub hatten, noch bevor es ein W3C-Standard war. Hubzilla hat es eingebaut, weil es damals eh noch mit sehr viel fderierte, auch wenn es dann zwei Monate die einzige Serveranwendung mit ActivityPub war.
Mastodon hat es vermutlich eingebaut, weil OStatus als Protokoll gelinde gesagt meh ist. Aus demselben Grunde hat vier Jahre vorher identi.ca von OStatus auf pump.io umgestellt, was StatusNet killte.
Nur leider war Mastodons Implementation von ActivityPub von vornherein mindestens so eigenwillig und lckenhaft wie seine Implementation von OStatus. So kam es zu Reibereien zwischen Eugen und Mike die sind brigens der Grund, warum Mastodon Article-Type Objects als Links darstellt und Hubzilla selbst die lngsten, ausgestaltetsten Posts als Note-Type Objects verschickt.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #ActivityPub Nach dieser Logik mte zumindest Hubzilla komplett wieder rausfliegen.
Warum Ganz einfach:
Hubzilla basiert nicht auf ActivityPub. Es hat sein eigenes Protokoll, eine ltere Version von Nomad, auch bekannt als Zot6. Das macht gewisse Features wie nomadische Identitt erst mglich (Stand jetzt). Hubzilla war das allererste Fediverse-Projekt mit ActivityPub, zwei Monate vor Mastodon, aber eine komplette Umstellung auf ActivityPub ist weder mglich noch wnschenswert.
Die ActivityPub-Konnektivitt ist nicht in den Kern eingebaut. Sie ist ein offizielles Add-on namens PubCrawl. Das wird zwar von den Hubzilla-Entwicklern mitgepflegt und mit jeder Hubzilla-Installation mitinstalliert. Aber das ndert nichts daran, da Hubzilla ActivityPub ber ein Add-on spricht.
Noch besser: Das Add-on ist sowohl auf Server- als auch auf Nutzerebene optional. Auf Serverebene ist es standardmig an, aber auf Nutzerebene ist es standardmig aus und mu erst hndisch aktiviert werden, damit ein Hubzilla-Kanal ber ActivityPub kommunizieren kann.
Gem deiner Logik, da nur zum Fediverse zhlt, was nativ und ohne Plug-in ActivityPub spricht, drfte Hubzilla nicht zum Fediverse zhlen, weil es fr ActivityPub ein Plug-in braucht. Das knnte auch Wasser auf die Mhlen derjenigen auf Mastodon sein, die alles an "Strfaktoren" aus dem Fediverse entfernt haben wollen, wenn sie denn wten, da Hubzilla nicht auf ActivityPub basiert.
(BTW: Ich bin hier jetzt gerade auf Hubzilla.)
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #ActivityPub
Zumal Friendica ja auch nicht mit Bluesky so fderiert ist wie mit diaspora* oder Mastodon. Man kann ja nicht sein Friendica-Konto direkt mit Bluesky verbinden. Man braucht statt dessen ein Bluesky-Konto, das in Friendica eingebunden wird.
Auf exakt dieselbe Art und Weise ist Friendica brigens auch schon ewig mit Tumblr und mit verbunden. Kein Witz. Und ab 2012 war es auf die Weise kurzzeitig mit Facebook verbunden. Auch kein Witz.
Sollte irgendjemand argumentieren, da nicht nur Bluesky in das Schaubild gehrt, sondern auch Threads, ja, dann mssen auch und Tumblr mit rein, weil Friendica sich mit denen genauso verbinden kann wie mit Bluesky und sie gleichzeitig so kommerziell und zentralistisch sind wie Threads.
Dann wre es noch eher gerechtfertigt, eine XMPP-Farbe mit einzubauen, einen XMPP-Kreis um Friendica zu ziehen und von da eine Linie zu einem Kreis mit jabberd2, ejabberd, Prosody, Tigase und Openfire drin. Und noch eine Farbe fr die WordPress XMLRPC API mit Kreisen fr WordPress, Friendica und Hubzilla und Linien von Friendica und Hubzilla zu WordPress, weil Friendica und Hubzilla direkt zu WordPress-Blogs crossposten knnen. Von OStatus (mit z. B. GNU social) und RSS und Atom (Friendica und Hubzilla knnen Feeds abonnieren) ganz zu schweigen.
Und ich hre jetzt schon einige sich mokieren, da "diaspora*, was auch immer das ist", in dem Schaubild nichts verloren hat, weil es nicht mit Mastodon fderiert ist.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #diaspora* #Friendica #Hubzilla #Bluesky #Threads #Tumblr #Twitter # #Facebook #XMPP #WordPress
Nur da so eine Liste innerhalb von Tagen wieder veraltet wre. Da kommt ein neuer Stand raus, und kurz darauf bringt wieder jemand eine neue Fediverse-Serveranwendung an den Start.
Und (streams) ist auch dann noch ein Problem. Bei (streams) wird die Kennung ja nicht verflscht. (streams) hat gar keine feste Kennung, denn (streams) hat ganz offiziell und mit voller Absicht keinen Namen und keine Markenidentitt. "Streams" ist der Name des Code-Repository. Die Anwendung ist namenlos. Und die Kennung kann auf der Adminoberflche verndert werden. Meines Wissens gibt es nicht mal einen Default wenn man gar nichts eintrgt, wird die Kennung vom Namen der Instanz abgeleitet.
So kommt es dann, da die einzige wirkliche ffentliche Instanz, die es noch gibt, als Kennung "Get Ready To Rumbly" hat. Die Instanz, die der Entwickler nutzt, und die, auf der die offizielle Supportgruppe sind, haben als Kennung "Y", weil Y nicht X ist. Es gibt auch noch so Kennungen wie "Diversi Spiritus", "Bunny of Doom" usw. Alles vollkommen normal und legitim.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams) Ich bin kein Entwickler, aber meines Wissens ist die einzige Chance, die du hast, eine Fediverse-Instanz zu erkennen, Nodeinfo. Selbst das ist nicht 100% zuverlssig, schon gar nicht, wenn du hndisch eine Liste von Fediverse-Projekten aufsetzt und die mit der Nodeinfo zugreifender Server abgleichen willst.
Es gibt nmlich auch , eine Facebook-Alternative aus derselben Familie wie auch Friendica und Hubzilla vom selben Entwickler. Es ist mit voller Absicht offiziell namenlos, es hat keine Markenidentitt, und mit derselben vollen Absicht ist Nodeinfo fast komplett entfernt worden. Damit gibt es auch keinen vereinheitlichten Identifikator wie "mastodon" oder "hubzilla". Jede Instanz kann nicht nur einen eigenen Namen haben, sondern auch einen eigenen individuellen Identifikator, wo jeder gesunde Mensch von allen Instanzen dasselbe vereinheitlichte "streams" erwarten wrde.
Zum einen mtest du also deine Liste immer nachpflegen, wenn wieder irgendjemand Misskey oder einen Misskey-Fork geforkt hat oder so. Zum anderen mtest du in deiner Liste auch den Identifikator von jeder einzelnen (streams)-Instanz eintragen, der sich brigens auch mal ndern kann.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams) #nodeinfo
This includes not only original renderings from 3-D virtual worlds with two image descriptions each, but also Fediverse memes. For the latter, I've actually launched . It is absolutely part of the Fediverse, it is federated with Mastodon both in theory and in practice, it can be followed from Mastodon, and therefore, it must adhere to the rules of the Fediverse as much as possible with something that isn't Mastodon.
Now, my meme posts aren't usually easy to understand, not even for Fediverse users, because I tend to dive deep into the Fediverse, far beyond Mastodon. Thus, the topics of my posts may require a lot of explanation. Also, I can't always expect everyone to a) be familiar with and b) understand the template(s) I use. So, these require a lot of explanation, too.
My experience of more than one year of improving my image descriptions is that many Fediverse users, especially Mastodon users, love having all kinds of information served to them on a silver platter without them even having to ask. And so I try to provide all information needed to understand my meme posts with next to no prior knowledge.
However, I don't do so in the alt-text. The visual description, complete with full, 100% verbatim transcripts of all texts added in the image macro, goes into the alt-text, yes. But the explanations don't.
First of all, and this is very important: Explanations do not belong into alt-text because not everyone can access alt-text. There can be many reasons why someone can't access alt-text, including a variety of physical disabilities which make it impossible for people to move and hold a mouse cursor over an image. But if they can't access alt-text, information exclusively available in the alt-text and neither in the post nor in the image is inaccessible and therefore lost to them.
In addition, my explanations are too long for alt-text. That is, they aren't too long for alt-text on (streams) which technically has no character limit. But Mastodon, Misskey and their respective forks would chop it off at the 1,500-character mark. And besides, even on (streams) itself, the maximum amount of alt-text that can be read is limited itself, depending on the user interface, because it can't be scrolled.
Finally, my explanations tend to grow too long for screen readers. Having a screen reader read out 1,500 characters of alt-text with no possibility to navigate that chunk of text, e.g. jump back to a certain sentence in the alt-text, is inconvenient. Now imagine using a screen reader to read several tens of thousands of characters.
And so I've decided to do the same with my meme explanations as I do with my long image descriptions for my original images: I put them into the post itself. I don't have any character limit there either, and nothing will truncate my extremely long posts.
This was particularly important for my first attempt at a new meme-posting format, . From what I've caught over the months, the Fediverse in general preferred having all explanations for an image in one place, the same place as the image itself, over links to external explanations. And so I tried to explain that image as in-depth as possible with as few external links as possible for as little prior knowledge as I could expect from Fediverse users.
Of course, I had to explain the image itself. But all by itself, that explanation wasn't exactly comprehensible because it would have required knowledge from two niches, namely about the template and about the topic.
And so I explained the template on a level not much lower than KnowYourMeme. But in order to make that explanation comprehensible, I also had to explain image macros, snowclones and advice animals. In order to make these comprehensible, I had to explain Something Awful, 4chan and imageboards in general in addition. The template explanations alone are over 10,000 characters long.
But would you know what FEP-ef61 is Would you know what nomadic identity is Would you know what (streams) is Probably not. Probably not even by Googling them.
And so I had to explain the topic as well. FEP-ef61. The concept of nomadic identity, what it is, what it does, how it works, what it's good for, why it was even created. The streams repository. Hubzilla. I've even rattled down the whole 14-year history from Mistpark/Friendica to the Red Matrix to Hubzilla to three different Osadas, Zap, another Mistpark and another Redmatrix to Roadhouse to the streams repository to what was the present time then, just so that people who only just recently thought the Fediverse equals Mastodon understand what (streams) is and where it comes from. Another 13,000 characters with a high information density.
Preamble included, the explanation of this one measly image that isn't even that complex clocked in at almost 25,000 characters. So I thought that couldn't possibly be what Mastodon users want. You know, the kind of people who are used to 1/50th of that in one post, not few of whom already go ballistic if you put 600 characters in one post.
So I ran on how people want meme posts to be explained. This time, I also mentioned what would be how long. Nobody really wanted such massive explanations. A few preferred externally linked explanations. Most didn't even want links, probably because they thought I'd put the links into the alt-text, because they couldn't imagine an image being described anyplace else than the alt-text.
Anyway, I still think I owe them explanations, also seeing as what I make memes about tends to be so obscure and/or recent that you really can't Google your explanation together.
So what I currently do is: As for meme templates, I link to the appropriate KnowYourMeme pages. As for the topic, if there's something I can link to, I link to it. Otherwise, if it needs to be explained, I explain it.
This can range from nothing more than mentioning the template and linking to KYM like for to several thousand characters of explanations because the topic is so obscure for or several thousand characters of explanations because I've combined seven meme template with a very complex and techy topic that involves seven Fediverse server applications (and one on the fringe) to make .
As you can see, it's tremendously difficult to make Fediverse meme posts understandable for total normies who think the Fediverse is only Mastodon and at the same time easy and convenient enough to consume for those who do not want to read thousands upon thousands of characters in a meme post.
By the way, if you think that 25,000 characters of explanation are absolutely, incredibly hypermassive: As I've said at the beginning, my original virtual world renderings get two image descriptions. A short one in the alt-text which recently always ends up at exactly 1,500 characters or only a few characters short. And a long one which may exceed (content warning for the link: eye contact, food) or, in one case, characters for one image, including visual descriptions, text transcripts and explanations, also because the explanations cannot be separated from the visual descriptions. And I've actually limited myself in the 60,000-character case.
It's only when I go to great lengths to reduce the details in images that I can make do with something like (content warning for the link: eye contact) . I need the explanations nonetheless. And I've actually decided against making certain images, much less posting them, because the scenery was too complex to sensibly describe and explain.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes
Beispiel 1: Guckt euch mal unter den die Liste der getrackten Instanzen an. Wieviele Nicht-Mastodon-Instanzen sind da, auer einer einzigen Catodon-Instanz (Catodon soll eine Art Mastodon mit einem Rest Iceshrimp-Backend darunter werden, soweit ich das verstanden habe.)
FEDIDevs impliziert doch, fr Entwickler aus dem ganzen Fediverse zu sein. Es schliet aber fast alles aus, was nicht Mastodon ist, und somit auch die Entwickler vieler Serveranwendungen, die nicht Mastodon sind. Die knnen gar nicht teilnehmen, weil das Backend von FediDevs vermutlich nicht mal gegen eine Mastodon-API gebaut ist, sondern direkt gegen Mastodon-Code.
Beispiel 2: ein Starterpack namens "".
Der ist komplett leer. Da ist genau berhaupt nichts drin.
Warum Weil es ganz augenscheinlich technisch vollkommen unmglich ist, irgendwas da einzutragen, was nicht auf Mastodon ist.
Wer auch immer hinter dem Bau von FediDevs steckt, scheint entweder anzunehmen, da das Fediverse nur aus Mastodon besteht. Oder es war einfacher, FediDevs nur gegen Mastodon zu bauen, statt
Ganz offenkundig wei bei FediDevs eine Hand nicht, was die andere tut. Auf der einen Seite gibt's ein Webportal, das nur mit Mastodon funktioniert. Auf der anderen Seite gibt's mit eine Friendica-Gruppe aus denselben Kreisen, wobei die seit einem Dreivierteljahr nicht mehr genutzt wird.
Das, oder dahinter steckt der Vorsatz, das Fediverse (wieder) zu nur Mastodon zu machen, indem alles Mgliche und Unmgliche, was an "Fediverse"-Diensten und -Zusatzfeatures entwickelt und beworben wird, mit voller Absicht gleichzeitig "Fedi" im Namen hat und nur gegen Mastodon gebaut wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #FediDevs
Internazionale by Internazionale
Breve guida alla lunga guerra in Siria
Con la caduta di Assad si conclude larco delle rivolte della primavera araba che hanno ridisegnato la regione. Leggi
Translated:
Short Guide to the Long War in Syria
With the fall of Assad, the arc of the Arab Spring uprisings that have redrawn the region concludes.
Nicht nur knnte ich ohne groe Schwierigkeiten mit meiner kompletten Identitt und allem, was dazugehrt, umziehen. Sondern ich kann sie auch ber mehrere Serverinstanzen klonen. So liegt sie nicht in einer, sondern aktuell in zwei Hnden. Geht eine Instanz mal offline, oder ist sie gestrt, habe ich einen identischen Klon meines Kanals woanders, und zwar mit allem Content, mit allen Kontakten, mit allen Dateien, mit allen Einstellungen, mit allem Drum und Dran.
Und im brigen kann sich im Fediverse jeder aussuchen,
- in wessen Hand er seine Daten gibt, denn nicht alles im Fediverse ist in derselben Hand
- was er da an Features hat, denn nicht alles im Fediverse ist Mastodon
Wer die technischen Fhigkeiten und Mglichkeiten hat, kann ersteres sogar umschiffen, indem er seine eigene Privatinstanz von was auch immer betreibt, vielleicht gar auf einer Maschine im eigenen Eigentum in den eigenen vier Wnden.
Aber generell habe ich schon genug Erfahrung mit dezentralen Systemen (XMPP, Matrix, OpenSimulator, das Fediverse auch schon seit Anfang der 2010er), da ich sagen kann: So etwas wird sich nie 100% wie ein zentralistisches, kommerzielles Silo anfhlen und auch nie so funktionieren. Und wem das nicht pat, der ist da eben falsch.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadischeIdentitt
Ich glaube, dass man schon mal viel gewinnen wrde, wenn man *mit* seinen Beitrgen auf Servern umziehen kann (nimmt Bedenken, sich vielleicht den "falschen" Server auszusuchen)
Dafr mte Mastodon erst nomadische Identitt einfhren. Dann ginge das ziemlich problemlos. Hubzilla hat das seit Anbeginn, seit 2012. Aber rein ber ActivityPub ist das noch extrem experimentell.
und wenn *alle* Server untereinander bekannt wren und die Suche nach Hashtags & Co eben ber wirklich *alle* Server (minus den Geblockten) gehen wrde und nicht nur denen, die irgendwann mal irgendwie Bekanntschaft geschlossen haben.
Hufig gestellte Forderung. Aber technisch unrealistisch.
Nehmen wir mal an, ich setze meine eigene (streams)-Instanz auf. Alles konfiguriert, alles startklar. Ich gebe
#systemctl start httpd ein, und der Webserver erwacht zum allerersten Mal.In diesem Sekundenbruchteil mten alle zigtausend Fediverse-Instanzen sofort von der Existenz meiner (streams)-Instanz wissen. Instantan. Auf der Stelle. (Du hast "wirklich *alle* Server" geschrieben. Also ohne jegliche Ausnahme.)
Das wre nur auf drei Arten und Weisen vorstellbar.
Erstens: Alle zigtausend Fediverse-Instanzen wissen vorher, da ich vorhabe, diese (streams)-Instanz aufzusetzen. Vorstellbar, aber vollkommen unrealistisch.
Zweitens: Meine (streams)-Instanz kennt alle, aber auch wirklich absolut ausnahmslos alle anderen Fediverse-Instanzen, die zu dem Augenblick existieren, wo der Webserver anspringt. Und zwar ohne dezentrale Hilfsmittel.
Das heit: Der Quellcode im streams-Repository enthlt eine nanosekundenaktuelle Liste aller Fediverse-Instanzen. Die Liste wird beim Klonen des Quellcode auf den Webserver mit runtergeladen. Beim ersten Start macht die (streams)-Instanz als allerallererstes einen
git pull, holt sich die nanosekundenaktuelle Liste aller Fediverse-Instanzen und meldet seine Existenz sofort an alle Instanzen auf der Liste.So eine Liste mu dann im Quellcode von absolut ausnahmslos jeder Fediverse-Serveranwendung eingebaut sein. Auch wenn jemand gerade erst mit einer ganz neuen Fediverse-Serveranwendung anfngt, mu da sofort diese Liste in vollem Umfang rein.
Und natrlich mu sie aktuell gehalten werden. Das heit, jede startende neue Instanz mu sich selbst in die Listen in den Quellcodes aller Anwendungen eintragen.
Meine (streams)-Instanz mte also alle Fediverse-Serveranwendungen kennen, die es berhaupt gibt. Auch wenn ein Fediverse-Entwickler erst eine halbe Sekunde vorher den allerersten git commit einer ganz neuen Fediverse-Serveranwendung gemacht hat.
Das heit auerdem: Meine (streams)-Instanz mte unmittelbar nach dem Start die Quellcodes von weit ber 100 Fediverse-Serveranwendungen
git clonen, also herunterladen. Und zwar jeweils alle Branches und alle Forks. Dann die eigene Adresse eintragen, auch wieder in alle Branches. Dann mte sie die nderungen an allen ber 100 Fediverse-Anwendungen als Pull Request git committen. Und jeweils wieder alle Branches und alle Forks. Auch die, die lange nicht maintaint worden sind. Man wei ja nie.Jetzt kommt's: Die nderungen mssen ja auch noch gemerget werden. Dafr mte mein (streams)-Instanz sich auf hunderten Git-Repositories volle Maintainer-Rechte verschaffen und die eigenen Commits mergen. Und zwar auch, ja, gerade in Produktivcode.
Ich sage ja nicht, da das potentiell unsicher ist.
Auerdem mu das schnell gehen. Hunderte Repositories klonen, ndern, committen, reinhacken und mergen, alles innerhalb eines Nichtsigstels einer Sekunde, damit die experimentelle Iceshrimp.NET-lnstanz, die jemand eine Zehntelsekunde spter startet, auch von meiner eigenen (streams)-Instanz wei und ihre eigene Instanz meiner (streams)-Instanz mitteilen kann.
Noch einmal: Du hast "wirklich *alle* Server" gesagt. Das heit, eine neue Iceshrimp.NET-Instanz mu zwingend und sofort eine neue (streams)-Instanz kennen, die eine Zehntelsekunde frher gestartet ist.
Ach ja, das ganze Theater ist auch vollumfnglich ntig, wann immer
- eine Instanz heruntergefahren wird
- eine Instanz sich umbenennt
- ein Hubzilla-Hub oder eine (streams)-Instanz ActivityPub deaktiviert oder wieder aktiviert, denn was interessiert eine Mastodon-Instanz ein Hubzilla-Hub, mit dem sie eh nicht interagieren kann
Jeder Entwickler wird mir besttigen, da das nicht nur komplett unrealistisch ist, sondern absolut haarstrubend. Alleine schon, weil 99,9% der Commits in den meisten Repositories von Fediverse-Instanzen kommen werden und alle Commits, die hndisch von Entwicklern kommen, darunter ersaufen. Und weil kein Entwickler seine eigenen Sachen so schnell rebasen kann, wie neue Commits mit nderungen an der Instanzenliste reinkommen.
Okay, also bleibt als dritte und einzige noch mgliche Lsung eine zentral verwaltete Liste auf einem zentralen Webserver.
Dieser Server mu verpflichtend in alle Fediverse-Serveranwendungen eingebaut sein. Auch die, die eigentlich gar nicht mehr gewartet werden, aber noch laufende Instanzen haben (Calckey, Plume usw.).
Damit wrde sich das ganze Fediverse bis in den allerhinterletzten Winkel absolut und total abhngig von zentraler Infrastruktur machen.
Warum das schlecht ist Stell dir mal vor, diese Liste geht offline aus irgendeinem Grunde. Oder irgendeiner, z. B. Elon Musk oder Jeff Bezos oder Mark Zuckerberg, kauft den Webserver mit der Liste drauf. Der htte dann die totale Kontrolle ber das Fediverse.
Willst du das
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #git
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/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=800x533https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpg/zmg/zrl...into this...
zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpgDigital 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 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. can probably confirm it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Mein Standpunkt ist das viele es schon merken werden ( auch ich hab das am Anfang nicht geblickt).
Nachdem sie sich monate- oder jahrelang an ein Fediverse gewhnt haben, das nur aus dem flauschigen Wollmammut besteht. Da es anders sein knnte, ist fr sie gnzlich unvorstellbar.
Dann luft ihnen ein vermeintlicher "Trt" ber den Weg, der so vllig anders ist als all das, was aus ihrer bisherigen reinen Mastodon-Bubble kam. Mehr als 500 Zeichen. Textformatierung. Ein Zitat. Eine Drko oder Druko (also ein "Quote-Trt").
Das ist fr viele so verstrend wie ein H.R.-Giger-Xenomorph in einer Schafherde. Einige glauben erst an eine "bse", "gehackte" Mastodon-Instanz. Wenn sie dann erfahren, da das von etwas ist, das mit Mastodon verbunden ist, also mit ihnen auf Mastodon, das aber selbst nicht Mastodon ist, sind sie nicht selten noch mehr verstrt.
Und dann wollen sie das weghaben. Sie wollen ihr flauschiges reines Mastodon-Fediverse wiederhaben. So Sachen wie Calckey, das nutzt, oder Friendica oder das von mir genutzte Hubzilla nehmen sie als Eindringlinge wahr, die sich gerade erst unrechtmigerweise ins Mastodon-Fediverse reingehackt haben.
Wohlgemerkt, Hubzilla ist je nach Definition entweder zehn Monate oder knapp vier Jahre lter als Mastodon und Friendica fnfeinhalb Jahre. Und Mastodon ist mit beiden so lange verbunden, wie es selbst existiert.
Auch die Mastodon-Kultur, die viele Mastodon-Nutzer zur verpflichtenden Kultur fr das gesamte Fediverse machen wollen, ist so erschaffen worden von Mastodon-Nutzern, die zu dem Zeitpunkt nicht mal ahnten, da das Fediverse vielleicht mehr ist als nur Mastodon. Sie ist komplett und ausschlielich ausgelegt auf die Features von Mastodon 3.x und auch nur auf die.
Es gibt zwischen Mastodon-Nutzern und Nicht-Mastodon-Nutzern in dieser Hinsicht zwei groe Unterschiede.
Zum einen:
Mastodon-Nutzer haben entweder kein Problem, die Mastodon-Kultur zu leben, oder sie tun es lngst. Immerhin ist die Mastodon-Kultur zugeschnitten auf das, was sie eh nutzen.
Fr Nicht-Mastodon-Nutzer bedeutet die verpflichtende Mastodon-Kultur aber die Aufgabe der Kultur dessen, was sie selbst benutzen, und damit auch die Aufgabe von auch mal 90% der Features von dem, was sie selbst benutzen. Denn die Nutzung dieser Features strt die Mastodon-Kultur.
Zum anderen:
Nicht-Mastodon-Nutzer kennen es vielfach, dafr attackiert zu werden, da sie sich nicht ganz genau so verhalten, wie man es auf Mastodon erwartet.
Mastodon-Nutzer knnen sich dagegen vielfach nicht mal vorstellen, da das berhaupt passiert. Denn ihnen passiert das nicht.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon
3) make it easier to make alt available AFTER a picture has been posted, especially in a way that doesnt add more burden to the OP or requester if they cant 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:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta Alexander Goeres Die Alternative wre ein Mastodon, das sich wirklich wie Twitter anfhlt. Fully-featured App namens "Mastodon", die genau wie die Twitter-App aussieht, aufs Handy laden und lostrten. Vielleicht noch Nutzername und Pawort. Idealerweise bernimmt die App gleich den Nutzernamen und das Pawort aus einer anderen App, z. B. der -App.
Der Nutzer wird natrlich auf mastodon.social geparkt. Die App guckt in anderen installierten Apps, woran der Nutzer interessiert ist, und folgt sofort mindestens 200 bis 300 anderen Mastodon-Konten. (Wohlgemerkt, ausdrcklich nur Mastodon-Konten.) Folgeanfragen, die erst besttigt werden mssen, forciert die App dabei auf der Seite der Gefolgten.
Die App mu dann eine totale Black Box sein und das Konzept von Instanzen komplett verschleiern. Der Nutzer darf nicht mal wissen, was fr eine Website dahintersteckt.
Dann darf der Nutzer aber auch nicht mit Posts verwirrt werden, die irgendwie Rckschlsse auf die Technik oder das Fediverse zulassen. KI-gesttzte Schlsselworterkennung mu alles an Content vom Nutzer fernhalten, was
- das Fediverse auerhalb von Mastodon erwhnt
- nicht wie von Vanilla-Mastodon aussieht
- nicht von Vanilla-Mastodon kommt
- das Fediverse berhaupt erwhnt
- Instanzen erwhnt oder auch nur das Konzept
- irgendwie Fediverse-Technik erwhnt
Das heit, der Nutzer mu durchgngig verhtschelt werden bis zum Gehtnichtmehr, noch sehr viel mehr als sowieso schon. Wir wollen ihn doch nicht gleich wieder vergraulen, oder
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #UX Well, Mastodon's internal character limits, 500 characters for posts, 1,500 characters for alt-text, are both hard-coded in a file that is being synced by git. It can be changed, but only by modifying what's essentially the source code.
Mastodon's current culture was established in 2022 by people who came in from Twitter in the first migration wave which started in February when Elon Musk announced his intention to take over Twitter. In this migration wave already, so many people came to Mastodon, especially mastodon.social, that it didn't take long for them to only encounter their own likes and hardly come across anyone who had been Mastodon users before 2022. Thus, they created a culture that was completely independent from pre-2022 Mastodon.
Also, not a single one of them knew what the Fediverse really was. For absolutely all of them, the Fediverse was Mastodon and only Mastodon. Vanilla Mastodon with a hard 500-character limit which, in the light of only 280 characters on Twitter, already felt like a lot to them.
They did not know about Misskey with 3,000 hard-coded characters. Or Pleroma and Akkoma with 5,000 configurable characters. Or the various Misskey forks with configurable limits of several thousands of characters. Nor did they know about Friendica, over five years older than Mastodon, or Hubzilla, a Friendica fork that's still almost four years older than Mastodon at its core. These two don't have any arbitrary character limits at all. And especially, they didn't know that all of these were fully, bidirectionally connected to Mastodon and interacting with Mastodon all the time.
In fact, ever since, it has always taken Mastodon newbies quite a while to even learn about Mastodon instances with modified character limits, not to mention Mastodon forks with configurable character limits.
And so it was those recent Twitter-to-Mastodon newbies who defined a whole new culture, based on vanilla Mastodon 3.x, its features and its limitations, but for the entire Fediverse. This culture was set in stone in late October already when the second migration wave started, and Mastodon newcomers who really settled into Mastodon, rather than wanting another Twitter, have been living this culture ever since.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #CharacterLimit #CharacterLimits #AltText #AltTextMeta #CWAltTextMetaThis is going to be one busy day in OpenSim. I'll have to skip the Discovery Grid farewell party, but I've never had close ties to that grid anyway.
OpenSimulator Community Conference starts today Hypergrid Business
HG Safari: Something for the Weekend
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #DiscoveryGrid #OpenSimulatorCommunityConference #OSCC #OSCC2024 #OSCC24 There's no syntax for it on mastodon.social. You simply can't do it there.
Some users have already mentioned Markdown which is supported by a few Mastodon forks, Pleroma, Akkoma, Misskey and its several forks (including but not limited to Firefish, Iceshrimp, Sharkey and Catodon), Mitra, (streams), Forte and optionally also by Friendica, probably also by others.
For completion's sake, Friendica, Hubzilla, (streams) and Forte mainly use BBcode.
The syntax for quotes is either quoteHere goes the quote/quote or quote="Whoever is quoted"Here goes the quote/quote.
Both in-line code and code blocks are delimited with
Lastly, (streams) and Forte even support HTML.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Markdown #BBcode #HTML #TextFormatting Well, what I meant with "do what I do anyway" is not what everyone else does.
My Fediverse meme posts have fairly standard image descriptions. What may make them long and complex are the explanations. They matter in this context because everyone else would explain meme images in the alt-text, but explanations don't belong into alt-text. And meme posts about Fediverse things do need a lot of explanation if they go beyond Mastodon, and mine tend to go way beyond Mastodon.
(Content warning: eye contact) was made under the assumption that Mastodon users prefer explanations given to them on a silver platter, right in the post itself which also contains the image. I was told a while ago that external links are bad and inconvenient and probably not accessible, and it's better to explain everything myself.
I always have to explain the meme template, and especially in this case, I also had to explain the topic. So I ended up with nine explanations on four or five levels with some 25,000 characters altogether, more than half of which went into the two explanations for the topic.
I couldn't imagine that this was actually what people wanted, seeing as it was generally Mastodon users who seemed to want me to explain everything, but at the same time, it's Mastodon users who complain the most loudly about long posts. And so on how people actually wanted meme posts to be explained. At least of the few who voted, nobody wanted explanations in the post if they end up tens of thousands of characters long.
Ever since, I've delegated the meme template explanations to KnowYourMeme which I link to.
As for the topic, (content warning: eye contact, guns) . Sometimes (content warning: eye contact, food) . Sometimes (content warning: eye contact) .
But in cases like (content warning: eye contact, swearing) or (content warning: eye contact, anger, crying, Japanese swearing) , I have to write extensive explanations, even if I can link to a whole lot of external information sources.
For my original images, renderings from very obscure 3-D virtual worlds, I do much more. I always write two image descriptions for each image.
One goes into the alt-text, and it's as long as I can make it within the 1500-character limit imposed by Mastodon, Misskey and their forks. And that's the short description that's mostly only there to satisfy the "every image must have alt-text, no matter what" fundamentalists.
There's also a long description in the post itself which is much, much more detailed. It also contains all necessary explanations which I have to write myself because I can't really rely on external links. And if there's any text anywhere within the borders of the image, legible or not, verbatim transcripts of all these bits of text go into the long description.
My most recent example, already on my new image-posting channel, but from four months ago, is (content warning: eye contact) . I've taken care to have as little scenery or surrounding or anything else in the pictures as possible, and still, I ended up with over 20,000 characters of image description. I explain why portraits are easier to describe.
A few examples with scenery, in chronological order, and much longer descriptions, and I consider them all outdated regardless: (content warning: eye contact, food) , (content warning: eye contact) and (content warning: eye contact) .
The first two links also demonstrate how I used to describe pictures within a picture, even on three levels in the case of the second link. But if I had carried on doing this the same way for the image behind the third link, I would have had to describe over a hundred images in various locations on at least four levels. Besides, I would have described details that not only aren't visible in the image, but that aren't visible either in the place shown in the image. Also, this might have revealed eye contact or another trigger of sorts.
So I decided against describing things that cannot be seen in the shown place. This was the first time that I actually imposed a limitation on myself.
I could post many, many, many more scenery pictures, maybe even with actual scenery and with many more details. But it would always take me days to describe one of them. The last two image posts I've linked to required two days to write descriptions.
For example, a month ago. It would have made for a gorgeous picture report. But it would have taken me at least a week and a half to only describe the four images that Mastodon would let through. In fact, Mastodon would have rejected the post anyway because, with the massive image descriptions, it would have exceeded 100,000 characters by far.
If you're wondering why my descriptions of virtual world images have to be so long and so detailed, .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
Dolphins In Depth: Did Nick Saban issue a warning about Dolphins
I've spent two full days describing one image.I feel bad when I can't describe something in an image the way I'd like to see myself describe it.
I keep coming across scenes that I think might make for nice pictures. But then I start trying to describe them in my head. And when I discover something that I can't properly describe, I don't even take the picture. I couldn't post it anyway without a description that's up to my standards.
I refuse to post images with realistic-looking buildings in them due to how complex they are to describe. After all, I'd have to first research architectural terminology and then explain it to my readers in the long image description.
A bit over a year ago, while working on an image description which, the next day (!), would , I realised that I had to describe three pictures of stellar nebulae. I didn't even really know how. I was about to abandon the whole image-posting project due to this. What I've eventually written still feels like a sub-par kludge, not to mention outdated a few times over.
I've read about people going back and alt-texting their entire backlog of image posts. I've wondered a few times if it is or should be recommended to go back and edit and improve your old image descriptions after you've learned something new in terms of describing images.
What do you think, is this genuine or not
And seriously, I don't even know whom exactly I'm doing all this for because I almost never get any feedback in any form. I do it for whoever comes across one of my image posts. Since my new channel for original images (which I do these monstrous descriptions for) has only got nine followers, and my channel for Fediverse memes (which at least tend to come with extensive explanations) has only seven, it has to be a very rare occurrence that someone who really needs an image description finds one of my image posts.
But I guess the ultimate solution is to forget about "" and do what I think is right until too many people come complaining. Which will probably amount to indefinitely.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility I think that's part of the issue, even if it's unavoidable: There's no one way to please everyone. And the more niche and special your content is, the harder it becomes to please as many disabled people as possible.
There's a saying: "." Don't assume what disabled people may need. Ask them. Talk to them. Listen to them.
But I guess the attitude in the Fediverse is that everything is said, everything is defined, everything is set in stone, and it'll work in 100% of all cases. No need to talk about it. You're expected to know it. Just do it.
I mean, I could just carry on assuming, based on what I've read here and there, even if that's technically the wrong thing. I know that there are at least some people who enjoy what I do, for whom it may be helpful.
I could just go on doing that and improving that, for any definition of improving. I could go on until enough people complain to me that I'm doing it completely wrong, and that staggering level of detail is bad for magnitudes more people than it helps. But this is unlikely to happen, seeing as how little feedback I receive.
I mean, at the end of the day, I can't really know whom I describe my images for. Do blind or visually impaired users even come across my image posts, seeing as they come from two different channels than this one now Do those come across my image posts who demand sanctions for everyone who doesn't describe their images sufficiently Are my extensive image descriptions and explanations useful for anyone
Still, I go on putting huge efforts into describing them for the random stranger who stumbles upon one of them on some federated timeline, regardless of whether they're visually-impaired, blessed with a terribly slow Internet connection or a fully sighted alt-text enforcer.
And I will most likely go on increasing my efforts where I can. I'm currently polishing my way of describing persons or rather avatars. After all, I can see the alt-text quality requirements in the Fediverse be constantly raised, too. I need to stay ahead of them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility Add your location to a Google Map Apparently, accessibility is not about trying as hard as you can. It has to be about trying exactly the right amount of hard without even knowing what the right amount is because the right amount is different for everyone.
For the record: I refuse to post any image without sufficient description. And "sufficient description" may mean two descriptions, a short (and still long) one in the alt-text, a massive one in the post. If I can't describe it properly, I don't post it. And I'm trying to up my game and add new tricks and new elements to my descriptions.
On the one hand, disabled people demand being involved in the topic of accessibility. Before you do something, consult with those whom you want to help. Don't just simply assume what they may need. Ask them. Discuss things with them.
On the other hand, apparently, asking too much will get you branded ableist, all the way to your home instance with over users being on the brink of a fediblock.
Here's a comment I've written on by . I've directed it to a blind user whom I may have asked once too much.
Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Here is his reply in which he claims I'm an ableist who actually doesn't want to describe images. This is far from the truth.
You really don't think I remember you do you You ask this question every single time in an attempt to badger users like me into getting away with *not* providing alt text because you wanna be ableist but try to pass it off as perfectionist. You will *never* please everybody, so to even try and to even is patronizing and ableist all by itself. I consider you to be nothing more than a troll. Look dude, if you don't wanna provide alt text then don't fucking provide it, but don't insult my intelligence with this obvious C lion tactic of I'm a perfectionist. I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.
Here is my reply.
I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.
If I didn't care for accessibility, if I didn't want to describe my images, why would I want to satisfy everyone, all the way to random strangers who stumble upon my posts in some federated timeline I shouldn't even want to satisfy anyone!
Why would I spend literal days, morning to evening, Twice per image
Why would I refuse to even take pictures, let alone post them, if they'll be too difficult to describe in a way that I consider sufficient
Why would I pick up any advice on how to describe certain things, like people or colours, and consider any of my image descriptions that don't have this incorporated hopelessly outdated
Why would I transcribe text that's too small for sighted people to read, just because all text in an image has to be described Why would I feel bad about text that I couldn't transcribe and then try to find a source for that piece of text And yes, I do.
Why would I be literally the only one in the entire Fediverse who tries to tell people that and why explanations don't go into the alt-text because people with certain disabilities can't access alt-text, and any information that's only available in alt-text is lost to them
And why would I warn sensitive people about eyes or food that's in the image on a microscopic sub-pixel level if I didn't care And yes, I actually did that. .
Just because I don't just simply shut up and describe my images exactly on point like you personally want them described, doesn't justify insulting me as an ableist.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism
In the meantime, he wrote and sent this post in which he called for a fediblock of either my channel or the entirety of hub.netzgemeinde.eu, the biggest Hubzilla instance.
Link at end. I'm unsure if is on his own instance, but for concerned trolling and ableist behavior by being patronizing to disabled people about alt text. I can't find others on his instance, but every, single time, the person posts the same question over and over and over and over and over and over and over and over and over and over and over again, and expects disabled people to tell this person because you can't describe every thing in an image you don't have to do alt text. Or maybe my temper is just short today, but here's the question. This isn't genuine curiocity because he asks the, same, question, over and over and over and over and over and over and over and over and over again. No answer is to his satisfaction. Nobdoy waste your time with this obnoxious troll. If it turns out I am lashing out of anger and have misjudged, will delete the post but
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteBoost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility #Ableist #Ableism #FediblockMeta
I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.
If I didn't care for accessibility, if I didn't want to describe my images, why would I want to satisfy everyone, all the way to random strangers who stumble upon my posts in some federated timeline I shouldn't even want to satisfy anyone!
Why would I spend literal days, morning to evening, Twice per image
Why would I refuse to even take pictures, let alone post them, if they'll be too difficult to describe in a way that I consider sufficient
Why would I pick up any advice on how to describe certain things, like people or colours, and consider any of my image descriptions that don't have this incorporated hopelessly outdated
Why would I transcribe text that's too small for sighted people to read, just because all text in an image has to be described Why would I feel bad about text that I couldn't transcribe and then try to find a source for that piece of text And yes, I do.
Why would I be literally the only one in the entire Fediverse who tries to tell people that and why explanations don't go into the alt-text because people with certain disabilities can't access alt-text, and any information that's only available in alt-text is lost to them
And why would I warn sensitive people about eyes or food that's in the image on a microscopic sub-pixel level if I didn't care And yes, I actually did that. .
Just because I don't just simply shut up and describe my images exactly on point like you personally want them described, doesn't justify insulting me as an ableist.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism
Sometimes its really difficult on Mastodon to follow a thread. Are you saying Hubzilla does that better
Yes, because by default, Hubzilla always displays entire threads at once. Start post on top,
The Mastodon piecemeal way of making each reply into its own post and showing them one by one as separate items is optionally available, but I've got my doubts that anyone has actually ever used that feature.
I'd show screenshots, but I don't have enough time to adequately describe them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla
Sometimes its really difficult on Mastodon to follow a thread. Are you saying Hubzilla does that better
Yes, because by default, Hubzilla always displays entire threads at once. Start post on top,
The Mastodon piecemeal way of making each reply into its own post and showing them one by one as separate items is optionally available, but I've got my doubts that anyone has actually ever used that feature.
I'd show screenshots, but I don't have enough time to adequately describe them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla On Mastodon, a thread is loosely tied together from posts and more posts. You, as a user, get them one by one. And you only get posts into your timeline
- from those whom you follow
- if you're mentioned
- if someone whom you follow boosts them
Here on Hubzilla, and actually in the whole family from Friendica to Forte, it's vastly different. Here, a conversation is an enclosed object. A thread, any thread, has exactly one post. That's the start post. Everything else is not a post, it's a comment.
This also means that Friendica, Hubzilla & Co. don't serve you single activities like Mastodon serves you single posts. Threads aren't piecemeal here. Threads come in one piece.
Instead, when you have a post (remember the distinction, "post" only means start post, as in something that isn't a reply to anything else) in your feed/timeline/stream, you also receive all comments on that post. Still under the same post and not as separate activities, not by default anyway.
It's like on Facebook or a blog or in a forum. After all, Friendica, the oldest member of the family, was created as an alternative to Facebook more than five years before Mastodon was made.
There's another big difference between Mastodon on the one side and Friendica, Hubzilla, (streams) and Forte on the other side: The latter four have an unread activities counter and an unread activities list. Mastodon doesn't have either. Mastodon doesn't even have a concept of unread.
On Mastodon, you go to your timeline, and you scroll down until you either hit something that you know you've already read, or you don't have any time anymore, or you don't want anymore. What you don't scroll down to, you will never know you've ever received it.
Here on Hubzilla, I have a counter of unread activities at the top of the the right-hand sidebar. It includes
- unread posts on my stream
- unread comments on something I have on my stream
- unread edits something I have on my stream
- unnoticed reposts/boosts/renotes/repeats of something I have on my stream
- unnoticed likes/dislikes for something I have on my stream (in theory I've turned this off)
If I open the counter, I get a list of all unread/unnoticed activities. I can apply a filter that only shows me new posts with one click. It's only a list, though it's not the actual activities like in a Mastodon timeline. It only lists up all these activities so I can load them manually.
So what I usually do first is apply the posts-only filter. Then I scroll down to the oldest item on the list. I click it. In the middle (we were in the right-hand sidebar until now), the post with that activity is shown, complete with all comments known to my stream, like a post on Facebook or a blog post with its comments neatly listed right below.
Now, let's suppose this post came with 68 comments and 11 repeats (that's "boosts" in Mastodonese). That's one unread post, 68 unread comments, 11 unnoticed repeats, all loaded and read/noticed in one fell swoop. The unread activites counter goes down by 1+68+11=80 items.
And then I go on with the next new post.
Once I'm through the new posts, I turn the filter off again, and the unread activities list shows me everything that isn't a new post.
I scroll down again. I click on the bottom-most item. Whatever it is, it loads an entire thread with a post and, if there are any, its comments. And whatever was in this thread that I hadn't paid attention to yet is flagged read and removed from the unread activities list, and the counter goes down by that number again.
Now, my situation as described in the post (again, posts vs comments from a Hubzilla point of view) is that the official Mastodon account or Eugen Rochko or some Mastodon devs (intentionally not mentioning either) tend to post stuff which is then boosted by , and which may receive well over 100 replies.
Now let's suppose Eugen Rochko posts something, and Fediverse Report boosts it, and it gets 280 replies. Let's also suppose I only follow Fediverse Report.
On Mastodon, I'd only receive Eugen's post in my timeline. That's it. Unless, of course, someone mentions me in one of the replies, or someone decides to boost one of the replies to me. Then I also receive that one reply. Separately.
Here on Hubzilla, I receive Eugen's post and all 280 replies in my stream. That's 281 unread activities, and that doesn't even include boosts and edits. That's at least 281 pieces of uninteresting clutter on my unread activities list. Granted, when I click one of them, the whole thread loads, and 281 pieces of uninteresting clutter are marked read and removed from the list, and the unread activities counter goes down by 281. And I no longer have to wade through all that clutter to find the actually interesting content.
But I don't necessarily want to see that gunk. I don't want to click it.
And so I've Superblocked the official Mastodon account and the official Mastodon Development account and Eugen Rochko and some devs. In fact, I've also Superblocked a few more Mastodon users who tend to attract replies like lamps attract moths, just in case someone whom I've given permission to send me their boosts (yes, I can disallow that for individual contacts) boosts something from one of them.
Now I don't receive the actual content anymore. But if someone boosts something from someone Superblocked to me, it still shows up on the unread activities counter. It and all replies to it. If Eugen Rochko (Superblocked) posts something, Fediverse Report (not Superblocked, allowed to send me boosts) boosts it, and it gets 280 replies, that's still 281 unread items on the list.
The catch: Since Eugen Rochko's post is blocked, so is the whole thread. I can't load his post, and I can't load any of the replies either because loading any reply would require loading the post. Remember that replies aren't piecemeal here on Hubzilla, unlike on Mastodon.
And if I can't load them, I can't have them marked read the natural way. Mind you, I do have a "Mark everything read" button. The only way to mark that stuff read. But if I used it, I'd also mark the interesting unread stuff read.
So I have to scroll through a list of hundreds of unread replies to Eugen Rochko's post and boosts of such replies and whatnot to find the halfway interesting stuff, pick it out, click it, load it, read it, interact with it etc. Then more scrolling until I find something interesting again. Wash, rinse, repeat.
Only when everything on the list of unread activities is from threads starting with blocked posts, I can click "Mark everything read".
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte That's good.
I've asked because I've got the feeling that alt-text/image description requirements are constantly being refined and raised in the Fediverse, and more and more existing descriptions won't pass anymore.
See, I usually spend hours on meme posts, both describing the image in the alt-text and explaining it in the post. As for my original images, it can take me days to describe them twice over, once in a "short" description in the alt-text that's actually already fairly long, once in a "long" description the size of an essay or even a short story in the post itself.
And I'm honestly waiting for the first to be so dissatisfied with that that they reply with their own alt-text and order me to both replace my alt-text with theirs and remove the long description from my post or else.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I may not be on Mastodon (seriously, I'm not, open my profile and look at it), but same here. My image posts are usually one every few weeks, sometimes with more than a month in-between.
I can't churn out image posts daily if it takes me hours to write a proper explanation for one meme post or several days to describe and explain one original image in a way I consider sufficient. In fact, it takes long enough to find motives that won't cause me to spend weeks describing and explaining the image.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaWondering whether I should un-Superblock the various official Mastodon accounts. I've blocked them to unclutter my stream and free it from content that I'm not interested in. Still, since their posts come to me as boosts, they end up on my list of unread activities. And so do all comments from after the posts were boosted to me. These posts often have well over 100 comments. And here on Hubzilla, when I receive a post, and that post is being commented on 150 times, this doesn't count as one unread activity. It counts as 151 unread activities. That's two features that Hubzilla has but Mastodon doesn't at once.
I mean, when something from these accounts is being boosted to me, I get a notification for the post and then 100+ notifications for comments either way, regardless of whether they're Superblocked or not. And when I scroll through those notifications of content that I can't access because it's Superblocked, I have to pick out the few notifications in-between about activities from connection that I haven't Superblocked.
I might just as well un-Superblock them. Okay, then I might be tempted to see that propaganda that at least implies Mastodon is either the best there is in the Fediverse or the Fediverse. Not to mention the masses of comments from 99.9% Mastodon users, most of whom think the Fediverse is only Mastodon, most of the rest of whom think there's nothing better in the Fediverse than Mastodon, and none of whom has read even one other comment in the thread because Mastodon has no concept of conversations.
And I might be tempted to comment on 40 comments which essentially say the same because nobody on Mastodon ever reads other people's comments (because nobody receives them in the first place), and which are based on the assumption of there not being much/anything else in the Fediverse except Mastodon.
I might end up being blocked by another few dozen Mastodon users for whom my comment was the very first activity they've received from outside vanilla Mastodon, the very first one with over 500 characters, maybe the first one with text formatting, not to mention the freakish-looking long-name mentions (no, I can't turn them off, they're hard-coded, and they've been since some four years before Mastodon was launched).
I might even end up in another dispute between "the usual suspects" from Calckey, Akkoma, Friendica etc. on the one side and fundamentalists who want the Fediverse to be only Mastodon on the other side.
But at least I can mark over 100 comments read in one fell swoop by actually loading them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonWondering whether I should un-Superblock the various official Mastodon accounts. I've blocked them to unclutter my stream and free it from content that I'm not interested in. Still, since their posts come to me as boosts, they end up on my list of unread activities. And so do all comments from after the posts were boosted to me. These posts often have well over 100 comments. And here on Hubzilla, when I receive a post, and that post is being commented on 150 times, this doesn't count as one unread activity. It counts as 151 unread activities. That's two features that Hubzilla has but Mastodon doesn't at once.
I mean, when something from these accounts is being boosted to me, I get a notification for the post and then 100+ notifications for comments either way, regardless of whether they're Superblocked or not. And when I scroll through those notifications of content that I can't access because it's Superblocked, I have to pick out the few notifications in-between about activities from connection that I haven't Superblocked.
I might just as well un-Superblock them. Okay, then I might be tempted to see that propaganda that at least implies Mastodon is either the best there is in the Fediverse or the Fediverse. Not to mention the masses of comments from 99.9% Mastodon users, most of whom think the Fediverse is only Mastodon, most of the rest of whom think there's nothing better in the Fediverse than Mastodon, and none of whom has read even one other comment in the thread because Mastodon has no concept of conversations.
And I might be tempted to comment on 40 comments which essentially say the same because nobody on Mastodon ever reads other people's comments (because nobody receives them in the first place), and which are based on the assumption of there not being much/anything else in the Fediverse except Mastodon.
I might end up being blocked by another few dozen Mastodon users for whom my comment was the very first activity they've received from outside vanilla Mastodon, the very first one with over 500 characters, maybe the first one with text formatting, not to mention the freakish-looking long-name mentions (no, I can't turn them off, they're hard-coded, and they've been since some four years before Mastodon was launched).
I might even end up in another dispute between "the usual suspects" from Calckey, Akkoma, Friendica etc. on the one side and fundamentalists who want the Fediverse to be only Mastodon on the other side.
But at least I can mark over 100 comments read in one fell swoop by actually loading them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon
Pimping the Long Box Dec 2025
Guess whos back Yes, Im back again! With a new editor on board, Im ready to dive back into this. I want to wish everyone a happy, safe, positive, and blessed holiday season. Lets hope that 2025 is better for all of us than some parts of 2024. Remember, we dont need sight to have a visionso go chase your dreams, keep your spirit strong, and testify!
A Few...
box adam
...brigens etwas, was Hubilla, (streams) und wohl Forte (wenn es mal einsetzbar ist) von Hause aus auch schon hat.
Wohlgemerkt:
- Das ist eine durchdachte und keine halbgare Lsung.
- Sie beweist seit Jahren im tglichen Produktivbetrieb, da sie funktioniert. (Ich verwende sie selbst.)
- Hubzilla hat sie schon seit 2012, also sogar noch lnger, als es berhaupt Mastodon gibt. Und (streams) gibt es zumindest lnger als Bluesky, nmlich seit 2021.
- Hubzilla, (streams) und Forte sind ziemlich unbestrittenermaen Teil des Fediverse und direkt mit Mastodon verbunden. Und Bluesky nicht.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Bluesky #Hubzilla #Streams #(streams) #Forte #NomadischeIdentitt Richtig, Mastodon fing eigentlich mal an als alternatives Frontend fr GNU social, genau wie Pleroma. Aber Mastodon wurde schneller zu etwas Eigenstndigem hochgejazzt, zumal es auch nicht alle Features von GNU social untersttzte.
Hubzilla und Mastodon (in der Reihenfolge) waren ja die ersten, die ActivityPub hatten, noch bevor es ein W3C-Standard war. Hubzilla hat es eingebaut, weil es damals eh noch mit sehr viel fderierte, auch wenn es dann zwei Monate die einzige Serveranwendung mit ActivityPub war.
Mastodon hat es vermutlich eingebaut, weil OStatus als Protokoll gelinde gesagt meh ist. Aus demselben Grunde hat vier Jahre vorher identi.ca von OStatus auf pump.io umgestellt, was StatusNet killte.
Nur leider war Mastodons Implementation von ActivityPub von vornherein mindestens so eigenwillig und lckenhaft wie seine Implementation von OStatus. So kam es zu Reibereien zwischen Eugen und Mike die sind brigens der Grund, warum Mastodon Article-Type Objects als Links darstellt und Hubzilla selbst die lngsten, ausgestaltetsten Posts als Note-Type Objects verschickt.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #ActivityPub Nach dieser Logik mte zumindest Hubzilla komplett wieder rausfliegen.
Warum Ganz einfach:
Hubzilla basiert nicht auf ActivityPub. Es hat sein eigenes Protokoll, eine ltere Version von Nomad, auch bekannt als Zot6. Das macht gewisse Features wie nomadische Identitt erst mglich (Stand jetzt). Hubzilla war das allererste Fediverse-Projekt mit ActivityPub, zwei Monate vor Mastodon, aber eine komplette Umstellung auf ActivityPub ist weder mglich noch wnschenswert.
Die ActivityPub-Konnektivitt ist nicht in den Kern eingebaut. Sie ist ein offizielles Add-on namens PubCrawl. Das wird zwar von den Hubzilla-Entwicklern mitgepflegt und mit jeder Hubzilla-Installation mitinstalliert. Aber das ndert nichts daran, da Hubzilla ActivityPub ber ein Add-on spricht.
Noch besser: Das Add-on ist sowohl auf Server- als auch auf Nutzerebene optional. Auf Serverebene ist es standardmig an, aber auf Nutzerebene ist es standardmig aus und mu erst hndisch aktiviert werden, damit ein Hubzilla-Kanal ber ActivityPub kommunizieren kann.
Gem deiner Logik, da nur zum Fediverse zhlt, was nativ und ohne Plug-in ActivityPub spricht, drfte Hubzilla nicht zum Fediverse zhlen, weil es fr ActivityPub ein Plug-in braucht. Das knnte auch Wasser auf die Mhlen derjenigen auf Mastodon sein, die alles an "Strfaktoren" aus dem Fediverse entfernt haben wollen, wenn sie denn wten, da Hubzilla nicht auf ActivityPub basiert.
(BTW: Ich bin hier jetzt gerade auf Hubzilla.)
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #ActivityPub
Und selbst fr Friendica, die ja nativ mit Bluesky sprechen und interagieren knnen, wre es im Schaubild eher etwas wie mit Diaspora
Zumal Friendica ja auch nicht mit Bluesky so fderiert ist wie mit diaspora* oder Mastodon. Man kann ja nicht sein Friendica-Konto direkt mit Bluesky verbinden. Man braucht statt dessen ein Bluesky-Konto, das in Friendica eingebunden wird.
Auf exakt dieselbe Art und Weise ist Friendica brigens auch schon ewig mit Tumblr und mit verbunden. Kein Witz. Und ab 2012 war es auf die Weise kurzzeitig mit Facebook verbunden. Auch kein Witz.
Sollte irgendjemand argumentieren, da nicht nur Bluesky in das Schaubild gehrt, sondern auch Threads, ja, dann mssen auch und Tumblr mit rein, weil Friendica sich mit denen genauso verbinden kann wie mit Bluesky und sie gleichzeitig so kommerziell und zentralistisch sind wie Threads.
Dann wre es noch eher gerechtfertigt, eine XMPP-Farbe mit einzubauen, einen XMPP-Kreis um Friendica zu ziehen und von da eine Linie zu einem Kreis mit jabberd2, ejabberd, Prosody, Tigase und Openfire drin. Und noch eine Farbe fr die WordPress XMLRPC API mit Kreisen fr WordPress, Friendica und Hubzilla und Linien von Friendica und Hubzilla zu WordPress, weil Friendica und Hubzilla direkt zu WordPress-Blogs crossposten knnen. Von OStatus (mit z. B. GNU social) und RSS und Atom (Friendica und Hubzilla knnen Feeds abonnieren) ganz zu schweigen.
Und ich hre jetzt schon einige sich mokieren, da "diaspora*, was auch immer das ist", in dem Schaubild nichts verloren hat, weil es nicht mit Mastodon fderiert ist.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #diaspora* #Friendica #Hubzilla #Bluesky #Threads #Tumblr #Twitter # #Facebook #XMPP #WordPress
Auweia. Aber gerade, wenn es da so viel gibt, wre doch eine ffentliche Liste gut, mit der sich diese ganzen Fediverse-Instanzen erkennen lassen, zumindest wenn ihre Kennung nicht verflscht wird (wofr IMHO kein legitimer Grund besteht).
Nur da so eine Liste innerhalb von Tagen wieder veraltet wre. Da kommt ein neuer Stand raus, und kurz darauf bringt wieder jemand eine neue Fediverse-Serveranwendung an den Start.
Und (streams) ist auch dann noch ein Problem. Bei (streams) wird die Kennung ja nicht verflscht. (streams) hat gar keine feste Kennung, denn (streams) hat ganz offiziell und mit voller Absicht keinen Namen und keine Markenidentitt. "Streams" ist der Name des Code-Repository. Die Anwendung ist namenlos. Und die Kennung kann auf der Adminoberflche verndert werden. Meines Wissens gibt es nicht mal einen Default wenn man gar nichts eintrgt, wird die Kennung vom Namen der Instanz abgeleitet.
So kommt es dann, da die einzige wirkliche ffentliche Instanz, die es noch gibt, als Kennung "Get Ready To Rumbly" hat. Die Instanz, die der Entwickler nutzt, und die, auf der die offizielle Supportgruppe sind, haben als Kennung "Y", weil Y nicht X ist. Es gibt auch noch so Kennungen wie "Diversi Spiritus", "Bunny of Doom" usw. Alles vollkommen normal und legitim.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams) Ich bin kein Entwickler, aber meines Wissens ist die einzige Chance, die du hast, eine Fediverse-Instanz zu erkennen, Nodeinfo. Selbst das ist nicht 100% zuverlssig, schon gar nicht, wenn du hndisch eine Liste von Fediverse-Projekten aufsetzt und die mit der Nodeinfo zugreifender Server abgleichen willst.
Es gibt nmlich auch , eine Facebook-Alternative aus derselben Familie wie auch Friendica und Hubzilla vom selben Entwickler. Es ist mit voller Absicht offiziell namenlos, es hat keine Markenidentitt, und mit derselben vollen Absicht ist Nodeinfo fast komplett entfernt worden. Damit gibt es auch keinen vereinheitlichten Identifikator wie "mastodon" oder "hubzilla". Jede Instanz kann nicht nur einen eigenen Namen haben, sondern auch einen eigenen individuellen Identifikator, wo jeder gesunde Mensch von allen Instanzen dasselbe vereinheitlichte "streams" erwarten wrde.
Zum einen mtest du also deine Liste immer nachpflegen, wenn wieder irgendjemand Misskey oder einen Misskey-Fork geforkt hat oder so. Zum anderen mtest du in deiner Liste auch den Identifikator von jeder einzelnen (streams)-Instanz eintragen, der sich brigens auch mal ndern kann.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams) #nodeinfo
Celebrate consciously with us in this months Holiday Edition of Kids Zone Magazine! With info on Covid and a Pacing Penguins matching activity, printables, recipes, art, comics, and a spotlight on educators, you wont want to miss this issue!
Check out Issue 5 at:
I think I can say I've got quite a lot of experience in describing images and upping my game from description to description, always trying to keep up with people's requirements or what requirements I extrapolate from what they write. I don't post images often, but that's due to the gigantic effort I tend to put into describing images. That's mostly because what I post about with images is always a rather obscure niche topic.This includes not only original renderings from 3-D virtual worlds with two image descriptions each, but also Fediverse memes. For the latter, I've actually launched . It is absolutely part of the Fediverse, it is federated with Mastodon both in theory and in practice, it can be followed from Mastodon, and therefore, it must adhere to the rules of the Fediverse as much as possible with something that isn't Mastodon.
Now, my meme posts aren't usually easy to understand, not even for Fediverse users, because I tend to dive deep into the Fediverse, far beyond Mastodon. Thus, the topics of my posts may require a lot of explanation. Also, I can't always expect everyone to a) be familiar with and b) understand the template(s) I use. So, these require a lot of explanation, too.
My experience of more than one year of improving my image descriptions is that many Fediverse users, especially Mastodon users, love having all kinds of information served to them on a silver platter without them even having to ask. And so I try to provide all information needed to understand my meme posts with next to no prior knowledge.
However, I don't do so in the alt-text. The visual description, complete with full, 100% verbatim transcripts of all texts added in the image macro, goes into the alt-text, yes. But the explanations don't.
First of all, and this is very important: Explanations do not belong into alt-text because not everyone can access alt-text. There can be many reasons why someone can't access alt-text, including a variety of physical disabilities which make it impossible for people to move and hold a mouse cursor over an image. But if they can't access alt-text, information exclusively available in the alt-text and neither in the post nor in the image is inaccessible and therefore lost to them.
In addition, my explanations are too long for alt-text. That is, they aren't too long for alt-text on (streams) which technically has no character limit. But Mastodon, Misskey and their respective forks would chop it off at the 1,500-character mark. And besides, even on (streams) itself, the maximum amount of alt-text that can be read is limited itself, depending on the user interface, because it can't be scrolled.
Finally, my explanations tend to grow too long for screen readers. Having a screen reader read out 1,500 characters of alt-text with no possibility to navigate that chunk of text, e.g. jump back to a certain sentence in the alt-text, is inconvenient. Now imagine using a screen reader to read several tens of thousands of characters.
And so I've decided to do the same with my meme explanations as I do with my long image descriptions for my original images: I put them into the post itself. I don't have any character limit there either, and nothing will truncate my extremely long posts.
This was particularly important for my first attempt at a new meme-posting format, . From what I've caught over the months, the Fediverse in general preferred having all explanations for an image in one place, the same place as the image itself, over links to external explanations. And so I tried to explain that image as in-depth as possible with as few external links as possible for as little prior knowledge as I could expect from Fediverse users.
Of course, I had to explain the image itself. But all by itself, that explanation wasn't exactly comprehensible because it would have required knowledge from two niches, namely about the template and about the topic.
And so I explained the template on a level not much lower than KnowYourMeme. But in order to make that explanation comprehensible, I also had to explain image macros, snowclones and advice animals. In order to make these comprehensible, I had to explain Something Awful, 4chan and imageboards in general in addition. The template explanations alone are over 10,000 characters long.
But would you know what FEP-ef61 is Would you know what nomadic identity is Would you know what (streams) is Probably not. Probably not even by Googling them.
And so I had to explain the topic as well. FEP-ef61. The concept of nomadic identity, what it is, what it does, how it works, what it's good for, why it was even created. The streams repository. Hubzilla. I've even rattled down the whole 14-year history from Mistpark/Friendica to the Red Matrix to Hubzilla to three different Osadas, Zap, another Mistpark and another Redmatrix to Roadhouse to the streams repository to what was the present time then, just so that people who only just recently thought the Fediverse equals Mastodon understand what (streams) is and where it comes from. Another 13,000 characters with a high information density.
Preamble included, the explanation of this one measly image that isn't even that complex clocked in at almost 25,000 characters. So I thought that couldn't possibly be what Mastodon users want. You know, the kind of people who are used to 1/50th of that in one post, not few of whom already go ballistic if you put 600 characters in one post.
So I ran on how people want meme posts to be explained. This time, I also mentioned what would be how long. Nobody really wanted such massive explanations. A few preferred externally linked explanations. Most didn't even want links, probably because they thought I'd put the links into the alt-text, because they couldn't imagine an image being described anyplace else than the alt-text.
Anyway, I still think I owe them explanations, also seeing as what I make memes about tends to be so obscure and/or recent that you really can't Google your explanation together.
So what I currently do is: As for meme templates, I link to the appropriate KnowYourMeme pages. As for the topic, if there's something I can link to, I link to it. Otherwise, if it needs to be explained, I explain it.
This can range from nothing more than mentioning the template and linking to KYM like for to several thousand characters of explanations because the topic is so obscure for or several thousand characters of explanations because I've combined seven meme template with a very complex and techy topic that involves seven Fediverse server applications (and one on the fringe) to make .
As you can see, it's tremendously difficult to make Fediverse meme posts understandable for total normies who think the Fediverse is only Mastodon and at the same time easy and convenient enough to consume for those who do not want to read thousands upon thousands of characters in a meme post.
By the way, if you think that 25,000 characters of explanation are absolutely, incredibly hypermassive: As I've said at the beginning, my original virtual world renderings get two image descriptions. A short one in the alt-text which recently always ends up at exactly 1,500 characters or only a few characters short. And a long one which may exceed (content warning for the link: eye contact, food) or, in one case, characters for one image, including visual descriptions, text transcripts and explanations, also because the explanations cannot be separated from the visual descriptions. And I've actually limited myself in the 60,000-character case.
It's only when I go to great lengths to reduce the details in images that I can make do with something like (content warning for the link: eye contact) . I need the explanations nonetheless. And I've actually decided against making certain images, much less posting them, because the scenery was too complex to sensibly describe and explain.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes
Dolphins In Depth: Dolphins reinforcements are on the way
Attention-Worthy Links for December 3rd, 2024
-duration -cost -assembling -ligand -income -Patman
New entry of AI-generated and added to our :
's
Last updated: 2024-12-10
All text and images © eLoc8.is-fabulous.com