Hubzilla Workshop #02
I've been told that by a Mastodon user who really values accessibility. However, she told me that she cannot access alt-texts because both of her hands don't work well enough for her to access alt-text.
It was her who told me to never explain things in alt-text because she and people like her can't read these explanations, because they can't open the alt-text with these explanations inside.
Explaining stuff in alt-text and not in the post throws people like her in front of a bus, just like not describing images at all throws blind and visually-impaired people in front of a bus.
I have explained my image posts in the post text body ever since, regardless of Mastodon users whining that I exceed 500 characters.
Explanations go into the post/toot where everyone can access them.
I mean, sure, you're free to put them only in the alt-text because your character limit is so meagre. You're just as free to write super-short alt-texts that don't really describe anything. You're just as free to not describe your images at all.
But don't complain if someone criticises you for either.
CC:
# # # # # # # # # # # # # # # This is actually a mistake that many Fediverse user keep making because they don't know better, and because the majority of Mastodon users only have 500 characters available.
That's because I'm being absolutely serious here. In order to access alt-text, you need either a screen reader (which sighted people don't have) or at least one sufficiently working hand.
If you want to explain your image, please do so in the post text itself and not in the alt-text.
# # # # # # # # # # # When I want to post an original image, that "one extra minute" is more like several hours or even multiple entire days that it takes to research for and write the descriptions for one image. No, I'm not joking.
Even when I post a meme, I can't describe the visuals in the image itself in a few minutes. And then the explanations (which go into the post itself rather than into the alt-text) come on top.
Still, I always go all the way whenever I post an image. I'd rather not post an image than underdescribe and/or underexplain it. I refuse to do any less than that because I always have to expect someone somewhere out there needing it. That's why I've only posted one measly image in the last 12 months, and that was a meme.
# # # # # # # # # # # Die Dnnhutigkeit gibt's auf beiden Seiten.
Auf der einen Seite sind Mastodon-Nutzer, die "Mastodon" und "Fediverse" gleichsetzen und es dann als bergriffig empfinden, wenn man ihnen etwas ber das Fediverse erklrt, wonach sie nicht vorher explizit gefragt haben.
Auf der anderen Seite sind Fediverse-aber-nicht-Mastodon-Nutzer, denen es auf den Geist geht, da, was auch immer sie benutzen, von den Mastodon-und-Fediverse-Gleichsetzern immer wieder als nichtexistent behandelt wird. Einige von denen mssen das jetzt schon seit fast zehn Jahren ertragen, weil sie schon im Fediverse waren, bevor sie auf Mastodon waren.
# # # # # # # # # # # # # #
Advantages:
Disadvantages:
Advantage or disadvantage, decide for yourself:
How it compares to Forte:
How it compares to (streams):
# # # # # # # # # # # # Nur so zur Info:
ist auf Mastodon.
ist auf Calckey, einem Misskey-Fork (siehe Fediverse-Sprechstunde, 27.10., 19.30 Uhr). Misskey ist seit 2014 in Entwicklung, fast zwei Jahre lnger als Mastodon, und wird vllig unabhngig von Mastodon entwickelt.
Und ich habe das hier gerade von Hubzilla gesendet, das aus einem Fork eines Forks von Friendica entstanden ist (siehe Hubzilla-Workshop, 29.10., 20.30 Uhr). Friendica ist seit 2010 in Entwicklung, fast sechs Jahre lnger als Mastodon, und wird vllig unabhngig von Mastodon entwickelt.
Trotzdem ist das alles auf Mastodon zu sehen. Aber nur weil es auf Mastodon zu sehen ist, heit das noch lange nicht, da es auch von Mastodon kommt.
brigens, deutliche Hinweise, da das hier nicht von Mastodon kommen kann:
# # # # # # # # # # # # # # # # #
What Mastodon refers to as "quoting", and what calls "quote-tweets", has been available on Friendica (which is on, by the way) since its inception a bit over 15 years ago, only that Friendica calls it "quoted sharing".
What Friendica calls "quoting" is what I've done up there at the top of this comment (I'm on Hubzilla, created by Friendica's creator in 2015 from a fork of a fork of Friendica).
Both features have been available in the Fediverse since five and a half years before Mastodon was launched.
# # # # # # # # # # # # # # # # # # # # # # Identitten unabhngig von Servern und Konten gibt's im Fediverse schon seit 2012, fast vier Jahre lnger, als es Mastodon gibt. Und dazu sogar noch besser als in der ATmosphere. Das Konzept nennt sich "nomadische Identitt". Erstmals eingefhrt wurde es Mitte 2012 auf Red, das Ende 2012 in Red Matrix umbenannt und 2015 in Hubzilla umgebaut wurde.
Der Clou bei der nomadischen Identitt ist, da deine Fediverse-Identitt mit wirklich allem, was dazugehrt, gleichzeitig auf beliebig vielen unabhngigen Servern existieren kann, und zwar als bidirektionale Echtzeit-Backups. Und diese Backups, auch Klone genannt, sind jeweils fr sich vollwertige Instanzen deiner Identitt, in die du dich ebenso einloggen und sie benutzen kannst wie das "Original". Und zwar auch und gerade, wenn das "Original" offline ist. Wenn es wieder online kommt, wird alles, was du auf den Klonen gemacht hast, und alles, was sonst auf den Klonen passiert ist, automatisch zum "Original" zurcksynchronisiert.
In der ATmosphere funktioniert Unabhngigkeit auch von einzelnen Relay-AppView-Stacks nur, indem jeder Relay alle, aber auch wirklich ausnahmslos alle Daten aus der ATmosphere speichert. Mit nomadischer Identitt mssen nur deine Daten geklont werden.
Das ist auch weder ein theoretisches Konzept noch ein experimentelles Projekt, sondern es wird seit mehr als einem Jahrzehnt produktiv genutzt.
Ich schreibe hier gerade selbst von Hubzilla von einem Kanal, der einen Klon hat. Und auch ist auf Hubzilla und knnte seinen Kanal klonen, wenn er es nicht schon getan hat.
# # # # # # # # # # # # Sagen wir, es hat sich ausgednnt.
Misskey gibt es natrlich weiterhin. Das ist in Ostasien, vor allem in seinem Heimatland Japan, meines Wissens populrer als Mastodon, auch wenn man sich das als westlicher Mastodon-Nutzer nicht vorstellen kann.
Calckey ist eingestellt worden, dessen Fork Firefish auch, aber es gibt noch Server.
Iceshrimp-JS ist im Wartungsmodus, wird also nicht mehr weiterentwickelt. Iceshrimp.NET ist kein Fork von irgendwas, sondern in C# neu geschrieben worden, aber in Sachen Features ist es von Misskey und den Forkeys meilenweit entfernt.
Der Platzhirsch unter den Forkeys ist nach wie vor Sharkey, das sagenhaft viele Features hat. Im Grunde ist es inzwischen der einzige Forkey, der in der westlichen Welt berhaupt noch eine Rolle spielt. Es gibt zwar einiges an Kritik, aber keine realistischen Alternativen.
CherryPick, das wie Misskey aus Japan kommt ist auch sehr leistungsfhig, aber mein letzter Stand war, da smtliche Server bis auf einen in den Grorumen Tokyo und Seoul stehen. Das ganze Projekt ist also wohl noch weit mehr vom Westen entkoppelt als Misskey.
Wie es mit der Entwicklung von Catodon aussieht, wei ich nicht. Ich schtze, das Problem war einfach, da Catodon sich zu sehr an Iceshrimp geklammert hat. Nur ist Iceshrimp-JS, auf dem Catodon ja basiert, fast tot, und das neue Iceshrimp.NET ist etwas ganz anderes, so da man von vorne htte anfangen mssen, und featuremig nicht mal auf Misskey-Niveau. Auerdem ist wohl die Idee, etwas zu bauen, das so einfach zu bedienen sein sollte wie Mastodon, aber mit *key-Unterbau, nicht so gut angekommen. Jedenfalls wird nchsten Monat wohl der letzte noch existierende Catodon-Server schlieen.
Hajkey ist schon lnger weg vom Fenster. Das war nur fr einen einzigen Server aufgezogen worden, und der ist zwischenzeitlich auf Sharkey umgestellt worden, weil es kaum mehr realistisch war, Hajkey aufrechtzuerhalten.
Bezglich der vielen anderen Forkeys (Meisskey, Tanukey, Neko usw.) bin ich nicht im Bilde.
Ganz neue Forks hat es wohl lange nicht gegeben. Den Aufwand, Misskey zu forken und hinzubiegen, macht sich keiner mehr. Sharkey ist an sich jetzt ziemlich tauglich, und es gibt wohl keinen Grund, der Entwicklerin mit einem Fork ans Bein zu pinkeln. Und Iceshrimp.NET ist noch zu unfertig, um es zu forken, mal ganz davon abgesehen, da keiner Fediverse-Software in Microsoft C# entwickeln will (aber in Microsoft TypeScript kurioserweise sehr wohl).
# # # # # # # # # # # # # # # # # # # # # # # # # There are several, but unlike Guppe, they all require a local account. They can be connected/followed from Mastodon, but you cannot simply create a group there on the fly with nothing but your existing Mastodon account. Also, no matter what you choose, it will handle nothing like Mastodon or a *key.
One more thing that's critically important to know is that posting (as in starting a new thread) on either of these from Mastodon or a *key is not quite straight-forward.
That's because a title is recommended on Friendica, Hubzilla and (streams), and on Lemmy, Mbin and PieFed, a title is pretty much mandatory. But neither Mastodon nor the *keys have any active support for titles. (The CW field corresponds to the summary the title is something entirely different.)
So if you want to start a new thread from Mastodon or a *key, you have to adhere to a special post format:
Lastly: Don't use hashtags when posting or commenting to Lemmy, Mbin and PieFed. Reddit doesn't have hashtags either, and what Reddit doesn't have has no place on either of these three.
# # # # # # # # # # # # # # # # # # # You do know that neither Catodon nor Firefish are singular server instances, but their own decentralised server applications like Mastodon
Anyway, the closest thing to Catodon that can be recommended to people living outside of East Asia right now is Sharkey. Like Catodon and Firefish, it's part of the family of Forkeys, i.e. direct or indirect Misskey forks.
# # # # # # # # # # # By the way, Friendica, Hubzilla, (streams) and Forte have a similar feature that lets you add a location tag to your post. It can be an arbitrary string, but it can also be something that OpenStreetMap recognises. If you or someone else has the appropriate OpenStreetMap add-on installed, the location can be shown on a map.
You have two options to set a location. One is to define a default location for all your posts it can be overridden as well as cleared for specific posts. The other one is to define a location for a specific post. I think all four can actually automatically tag your posts by figuring out your current physical location if you want them to.
At least Hubzilla also has an add-on that randomly tags posts with planets from the Star Wars franchise, and (streams) and Forte have one that randomly tags posts with real-world cities.
# # # # # # # # # # # # # # Mit denen wrde ich auch nicht klarkommen knnen. Ich meine, diese Cryptobros versuchen allen klarzumachen, da das Metaversum, also virtuelle 3-D-Welten, technisch nicht realisierbar wren ohne Blockchain, ohne Kryptowhrung, ohne Land per NFTs zu verkaufen und ohne Objekte als NFTs anzubieten.
Haha.
Jetzt in diesem Augenblick bin ich eingeloggt in eine virtuelle Welt, die seit Anfang 2010 existiert. Auf Basis eines Virtuelle-Welten-Systems von Anfang 2007, das komplett ohne Blockchain, ohne Crypto und ohne NFTs auskommt, und wo auch schon seit 2007 das Wort "Metaverse" Teil des stndigen Sprachgebrauchs ist.
Dieser Kanal und meine Zusatzkanle auf (streams) sind alle nach meinem Hauptavatar benannt.
Ich habe sogar Avatare in einem Grid auf Basis derselben Software, das schon seit Mitte 2007 existiert.
Die Cryptobros fhren ja auch gern Decentraland als Leuchtturmprojekt auf, als "erstes dezentrales Metaversum berhaupt". Auch das ist Bldsinn. Dezentral ist an Decentraland nur, da es nicht auf der Bitcoin-Blockchain luft, sondern auf der von Etherium. Ansonsten ist Decentraland nur eine einzige Welt, ein zentralistischer Walled Garden.
Wo ich bin, das ist ein Netzwerk von ber 4000 individuellen Welten, von denen die allermeisten miteinander verbunden sind mittels einer Technologie, die es auch schon seit Mitte 2008 gibt.
Und ich bin verbunden mit einer halben Busladung Leute, die in Second Life sind, das auch schon seit 2002 existiert, auch ohne Blockchain, Crypto und NFTs.
Da knnen mir die Cryptobros also viel erzhlen.
# # # # # # # # # # # #How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view
Enough of a nuisance for the main developer of Hubzilla to speak up against it.
Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :facewithrollingeyes:
See If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.
Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.
# # # # # # # # # # # # # # # # #How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view
Enough of a nuisance for the main developer of Hubzilla to speak up against it.
Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :facewithrollingeyes:
See If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.
Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.
# # # # # # # # # # # # # # # # # Das ist eigentlich als Feature gedacht, damit man nicht immer alles ffentlich macht, nur das, was ffentlich sein soll. Ist aber doof, wenn man wirklich alles ffentlich haben will, weil man keinen rein persnlichen Privatkanal betreibt.
Jedenfalls postet Hubzilla standardmig nur in eine sogenannte Privacy-Gruppe namens "Freunde". Privacy-Gruppen sind im Prinzip wie Mastodon-Listen, nur sehr viel mchtiger und eigentlich ein optionales Feature, hnlich wie auch schon ActivityPub.
Wenn du Privacy-Gruppen nicht aktiviert hast, hast du nur genau diese eine und kannst sie auch nicht konfigurieren. Du mut also erstmal die App installieren und kannst dann in der Privacy-Gruppe "Freunde" abschalten, da standardmig in diese Privacy-Gruppe gepostet wird.
# # # # # # # # # # # Der Funktionsumfang ist ber gut 15 Jahre gewachsen von Mistpark/Friendica (2010) ber Red/die Red Matrix (2012), ber den Start von Hubzilla (2015), ber einen Entwicklerwechsel (2018) und ber Vernderungen im Fediverse, neue FEPs und Backports von Hubzillas eigenen Nachfahren bis heute.
Die meisten Features sind aber entweder geerbt von Friendica, das sie 2010 schon hatte, oder 2012 mit dem Start von Red dazugekommen oder 2015 bei der Umstellung von der Red Matrix nach Hubzilla.
brigens, falls du Bock und Zeit hast: Nchsten Mittwoch ist der zweite Hubzilla-Workshop. Die luft online auf BigBlueButton, du brauchst also nur einen Browser, was zum Hren, idealerweise ein Mikro und Zeit.
Datum: Mi., 29.10.2025
Uhrzeit: 20:30 Uhr
Ort:
Dieser Workshop richtet sich im Hauptthema an Einsteiger und Neugierige. Es geht darum, einen Account und einen Kanal bei Hubzilla zu erstellen, und um die unumgnglichen notwendigen ersten Schritte der Konfiguration.
Zu Beginn wird ein Video prsentiert, welches die einzelnen Punkte erlutert, die notwendig sind, um mit Hubzilla am Fediverse teilnehmen zu knnen.
Im Anschluss daran werden wir gemeinsam mit den Teilnehmern beispielhaft eine Einrichtung vornehmen. Es folgt eine Frage-und-Antwort Runde, zum Schwerpunkt, aber auch zu allgemeinen Themen rund um Hubzilla.
Also: Habt Ihr Interesse an Hubzilla, wrdet Ihr gerne mit Hubzilla das Fediverse bereisen Traut Ihr Euch nicht, weil es als schrecklich kompliziert verschrien ist Mchtet Ihr erfahren, was mit Hubzilla sonst noch alles mglich ist
Dann solltet Ihr an diesem Workshop unbedingt teilnehmen!
Administratoren und Hub-Betreiber sind selbstverstndlich auch herzlich eingeladen. Wir aber vor allem auch die Einsteiger brauchen Euch und Eure Expertise!
Ort: Online-Veranstaltung:
# # #
# # # # # # # # # # # # Es wre brigens lohnenswert, nicht nur auf Mastodon zu suchen.
Die Piraten-Partei hat als ursprnglichen bundesweit offiziellen Fediverse-Server nmlich keinen Mastodon-Server, sondern einen Friendica-Node und den schon weitaus lnger, als es Mastodon berhaupt gibt.
# # # # # # # # # # # # # Die offizielle Mastodon-App ist so ziemlich die schlechteste und unterausgestattetste Mastodon-App, die es berhaupt gibt.
Viele glauben, die sei die Referenz-App, weil es ja die offizielle App ist und offizielle Apps ja eigentlich immer fully-featured sind. Tatschlich ist sie aber eine Verlegenheitslsung, damit es im Apple App Store und im Google Play Store berhaupt eine offizielle App namens "Mastodon" gibt, weil 99% der Twitter-Umsteiger erstmal danach suchen werden.
Was die nicht kann
Beispiel: Beinahe jedes Fediverse-Frontend da drauen rollt lange Inhalte standardmig ein, und dann kann man sie hndisch wieder ausrollen. Auer superminimalistischen "Damit es berhaupt eine Weboberflche gibt"-Behelfs-Weboberflchen von superminimalistischen Serveranwendungen ist die offizielle Mastodon-App das einzige Frontend, das das nicht kann. Die ist gebaut worden in der Annahme, da es im Fediverse nur Inhalte mit maximal 500 Zeichen gibt.
Dieses Manko in der offiziellen Mastodon-App ist wahrscheinlich einer der Hauptgrnde, warum viele Mastodon-Nutzer sich ber "lange Posts" mit ber 500 Zeichen aufregen.
Ich frage mich gerade, ob sie in der Lage ist, Textformatierung anzuzeigen.
# # # # # # # # # # #
Noch arroganter zeigen, da das Fediverse nur besteht aus
Sonst httest du nmlich lngst gelesen, da ich gar nicht auf Friendica bin.
Und weil alle, die nicht auf Mastodon sind, sowieso irrelevant sind, hast du doch bestimmt auch nichts dagegen, wenn wir uns weiterhin an unsere Kulturen halten, statt sie fr Mastodons Kultur ber Bord zu werfen.
CC:
# # # # # # # # # # # Deine vielleicht.
Ich wei dagegen, da ich gengend reine Folgeverbindungen habe, die definitiv mein Profil nicht gesehen haben. Also, gar nicht, nicht mal im Mastodon-Webinterface oder in irgendeiner Mastodon-App.
Wer ein Mastodon-Konto hat, das erst ein paar Stunden alt ist, aber schon mehr als 1000 Akteuren folgt, hat sich definitiv nicht die Mhe gemacht, sich von jedem davon jeweils das Profil anzugucken. Und mir passiert es nur einmal alle tausend kalten Winter, da mir jemand wegen des Primrthemas meines Kanals folgt.
Ich wage auch zu behaupten, annhernd niemand zumindest von meinen Mastodon-Kontakten hat sich die Mhe gemacht, sich mein Profil im Original anzusehen, also im Webbrowser und dann auf Hubzilla selbst (). Da steht nmlich noch einiges mehr, was Mastodon nicht zeigen kann, weil Mastodon die allermeisten von Hubzillas Profilfelders berhaupt nicht untersttzt.
Im Grunde wei ja schon annhernd niemand, da das hier ein Hubzilla-Kanal ist, der auf zwei Themengebiete spezialisiert ist und seine Identitt von einem Virtuelle-Welten-Avatar bernommen hat, und nicht das eine private Allzweck-Mastodon-Konto einer realen Person. Oder wutest du das
# # # # # # # # # # Die Darstellung als Markdown im Klartext ist ein eindeutiger Bug in Iceshrimp. Ganz offensichtlich kennt Iceshrimp keine Hashtags, wie sie Friendica schon seit mehr als 15 Jahren produziert, also, wo die Raute nicht Zeichen des Link ist. Also wandelt Iceshrimp die Hashtags in Markdown um, rendert sie dann hinterher aber nicht entsprechend.
Hubzilla selbst verwendet berhaupt kein Markdown. Hubzilla wandelt Hashtags intern in BBcode um. Beim Versenden wird der BBcode in den RTF-Standard umgewandelt. Iceshrimp wiederum wandelt RTF in Misskey-Flavored Markdown um. Aber wie es aussieht, kommt Iceshrimp nicht mit der Konstellation klar, wenn vor einem Link ein Rautenzeichen steht. Daran kann Hubzilla nichts machen.
Viele der Hashtags, die ich verwende, dienen dazu, Filter auszulsen, weil ich immer davon ausgehen mu, da das, was ich hier so gerade bers Fediverse schreibe, so einige Leute strt. "Oh mein Gott, jetzt schreibt der Rowland wieder irgend so einen Mist ber das Fediverse/Quote-Posts/CWs/Alt-Texte/Bildbeschreibungen/..." So knnen sie diese Inhalte gezielt rausfiltern. Oder sie knnen sie hinter individuellen, nur fr sie automatisch leserseitig generierten CWs verstecken lassen (geht auf Mastodon seit 2022 und auf Mikes Schpfungen schon immer) deswegen die vielen Hashtags mit "CW" am Anfang.
Beispiele:
# und # heien: "Der Rowland labert schon wieder bers Fediverse."
# und # heien: "CW: Der Rowland labert schon wieder bers Fediverse."
Hashtags sind es deshalb, weil die sich noch am unaufflligsten als Schlsselwrter in jeden Post, jeden Kommentar und jede Antwort einbauen lassen.
Und es sind deswegen soviele, weil ich ja nicht wissen kann, ob jetzt jemand "QuotePost" oder "QuoteTweet" oder "QuoteToot" oder "QuoteTrt" oder "QuoteBoost" oder den jeweiligen Plural filtert. Die meisten drften davon genau eins filtern, aber ich wei eben nicht welches.
Wenn ich damit jetzt aufhren wrde, weil das einige Leute strt, wrde ich andere Leute stren, die genau diese Hashtags filtern.
Warum nicht "einfach" CWs wie auf Mastodon
Weil Mastodons CW-Feld hier ein Zusammenfassungsfeld ist. Und zwar auf Hubzilla seit Frhjahr 2015, auf Red bzw. der Red Matrix (quasi Proto-Hubzilla) seit 2012 und auf Friendica seit 2010. Lnger, als es Mastodon berhaupt gibt.
Zwei Dinge sind bombenfest in den Kulturen von Friendica und Hubzilla einzementiert.
Zum einen: Das Zusammenfassungsfeld ist fr Zusammenfassungen.
Zum anderen: CWs lt sich jeder automatisch und nur fr sich individuell mittels eines Filters namens "NSFW" generieren. Und das ist tausendmal besser, als dieselben CWs allen Leuten ber das Zusammenfassungsfeld aufzuzwingen, ob sie diese CWs brauchen oder nicht.
# # # # # # # # # # # # # # # #
Das macht er deshalb, weil die Leute
Je eher sie erfahren, da a) das Fediverse mehr ist als nur Mastodon, b) das vllig normal und Teil des Konzepts des Fediverse ist und c) das Fediverse zu keinem Zeitpunkt nur Mastodon war, desto besser.
# # # # # # # # # # # # # # # #
...dann tun wir das, weil diese Menschen "Auto" mit "Mexiko-Kfer" gleichsetzen. Weil sie sich vielfach Features in Autos wnschen, die praktisch nur der Kfer nicht hat. Weil so Technologien wie ein 12-Volt-Bordnetz fr sie unvorstellbar sind. Und weil wir ihnen dazu raten wollen, sich mal statt dessen einen Toyota oder so zuzulegen. Dann htten sie auch mal eine anstndige Heizung und mehr Platz im Auto. Aber nein, einmal Kfer, immer Kfer, und der Kfer ist das beste Auto berhaupt.
Und dazu kriegen wir stndig auf die Schnauze von Leuten, die sagen, die Straen sind nur fr Kfer gebaut worden, und Autos mit wassergekhltem Motor oder mit mehr als 34 PS haben auf der Strae nichts zu suchen. Jedem, der auch nur einmal schneller fhrt als 115 km/h, gehrt der Fhrerschein entzogen. Und wenn ein Auto den Kofferraum hinten hat, dann ist das eine eindeutige Fehlentwicklung.
Nur da es in diesem Fall die Mercedes V-Klasse schon vor dem Mexiko-Kfer gab.
CC:
# # # # # # # # # # # # # # #
I always describe my fully original images twice, only that the description in the alt-text is the short one. The one that goes into the post text is much, much, much longer. It contains verbatim transcripts of all text within the borders of the image, and it contains all explanations needed for random laypeople to understand the image and the long image description.
CC:
# # # # # # # # # # #When I describe my images, I do so under a few assumptions.
One: My audience is not limited to my following contacts. It's absolutely everyone who comes across any of my posts.
It isn't sufficient to make my posts accessible to those who have chosen to follow me. I must make them just as accessible to a random stranger who receives them after they've been boosted a dozen times over. I must make them just as accessible to a random stranger who stumbles upon them on the public timeline of whatever server they're on.
Two: If an element in an image is mentioned, it must also be described visually.
Blind or visually-impaired people always need to know what something in my images looks like. This goes doubly for my typical original images I mean, how are they supposed to know what something looks like in a specific 3-D virtual world
So if there's a building in one of my images, and I mention that this building is there, I also have to give a visual description of it. A full, detailed description.
If there's an image in one of my images, e.g. a preview image on a teleporter that shows the place where the teleporter would take me, I have to fully describe that image. An image in my image that doesn't even take up 200 pixels in my image. (Something that I've refused to do in my longest image description so far because that would have led me to going at least four levels deep: describing loads of infinitely small images in several dozen infinitely small images in an image in my image.)
In fact, this isn't an assumption. I have written confirmation for it. I can't find it right now, otherwise I'd share it here, but I have it somewhere.
Three: Image descriptions must always deliver all information that someone may need right away.
Not everyone wants to ask for a description of a certain detail in an image. Not everyone wants to ask for an explanation of what they don't understand or what they're unfamiliar with. Having to look things up yourself isn't much better. Some may go as far as likening not having an image description that contains everything they need to know to not having any image description.
By the way: It's a fact that some Mastodon users consider linking to external information ableist because linked websites aren't necessarily sufficiently accessible themselves. Instead of linking to information, the information must go into the post itself. (And I can't even use any character limit as an excuse not to do that because my "limit" is over 16.7 million.)
In other words, the only way for me not to be ableist is to give any and all information that anyone out there may require in my image post immediately.
Of course, this will clash with the demand by other Mastodon users (or maybe even some of the same) to never post more than 500 characters at once. But I can't do both. And I've never read anywhere that posting more than 500 characters is allegedly ableist.
Four: Someone somewhere out there may be interested in even small details in my image. And they may not be sighted.
Maybe you aren't. But someone somewhere out there may be. And they matter every bit as much as you or everyone else.
If they need a full description of all details, regardless of why, I have to deliver it. Immediately. See above.
Five: Any and all text within the borders of the image must be transcribed verbatim, no exception.
Most importantly, this even extends to text that's unreadable in the image if I can read and/or source it.
The assumptions further up apply here as well: If I mention it (the text in this case, and be it as part of the visual description of something else like a teleporter), then I must describe (as in transcribe) it. And someone somewhere out there may be interested in it.
If this means that I have to transcribe not one or two, but 20, 30, 40 bits of text in one image, then so be it, so are the rules.
Just because nobody on Mastodon does it, doesn't mean they're doing it right, and I'm doing it wrong. Maybe they don't know what that unreadable text says. Maybe they don't know that someone wants to know what's written there.
Six: All images must have an accurate and sufficiently detailed proper alt-text.
I can spend two days, morning to evening, working on an image description of 60,000 characters. 10,000 words. Three hours worth of reading. I can put the whole thing into the same post as the image. As in the post text body. As opposed to the alt-text for which this description is way too long.
But if the image in the post doesn't have an actual alt-text (and, again, it doesn't because the image description is in the post text itself), Mastodon's alt-text police is likely and fully justified to sanction me regardless.
So no matter how long and detailed and well-researched the long image description in the post is, I still have to distill an additional, shorter image description for the alt-text from it. And I have to do so without cutting too much information. Ideally, without cutting any information. If any of my images need a long description in the post, they need two descriptions, the long one in the post, the shorter one in the alt-text.
Leaving the several dozen individual text transcripts out of the description for the alt-text is risky already because text transcripts belong into the alt-text.
# # # # # # # # # # # # # # # # # # # # # # # # # #When I describe my images, I do so under a few assumptions.
One: My audience is not limited to my following contacts. It's absolutely everyone who comes across any of my posts.
It isn't sufficient to make my posts accessible to those who have chosen to follow me. I must make them just as accessible to a random stranger who receives them after they've been boosted a dozen times over. I must make them just as accessible to a random stranger who stumbles upon them on the public timeline of whatever server they're on.
Two: If an element in an image is mentioned, it must also be described visually.
Blind or visually-impaired people always need to know what something in my images looks like. This goes doubly for my typical original images I mean, how are they supposed to know what something looks like in a specific 3-D virtual world
So if there's a building in one of my images, and I mention that this building is there, I also have to give a visual description of it. A full, detailed description.
If there's an image in one of my images, e.g. a preview image on a teleporter that shows the place where the teleporter would take me, I have to fully describe that image. An image in my image that doesn't even take up 200 pixels in my image. (Something that I've refused to do in my longest image description so far because that would have led me to going at least four levels deep: describing loads of infinitely small images in several dozen infinitely small images in an image in my image.)
In fact, this isn't an assumption. I have written confirmation for it. I can't find it right now, otherwise I'd share it here, but I have it somewhere.
Three: Image descriptions must always deliver all information that someone may need right away.
Not everyone wants to ask for a description of a certain detail in an image. Not everyone wants to ask for an explanation of what they don't understand or what they're unfamiliar with. Having to look things up yourself isn't much better. Some may go as far as likening not having an image description that contains everything they need to know to not having any image description.
By the way: It's a fact that some Mastodon users consider linking to external information ableist because linked websites aren't necessarily sufficiently accessible themselves. Instead of linking to information, the information must go into the post itself. (And I can't even use any character limit as an excuse not to do that because my "limit" is over 16.7 million.)
In other words, the only way for me not to be ableist is to give any and all information that anyone out there may require in my image post immediately.
Of course, this will clash with the demand by other Mastodon users (or maybe even some of the same) to never post more than 500 characters at once. But I can't do both. And I've never read anywhere that posting more than 500 characters is allegedly ableist.
Four: Someone somewhere out there may be interested in even small details in my image. And they may not be sighted.
Maybe you aren't. But someone somewhere out there may be. And they matter every bit as much as you or everyone else.
If they need a full description of all details, regardless of why, I have to deliver it. Immediately. See above.
Five: Any and all text within the borders of the image must be transcribed verbatim, no exception.
Most importantly, this even extends to text that's unreadable in the image if I can read and/or source it.
The assumptions further up apply here as well: If I mention it (the text in this case, and be it as part of the visual description of something else like a teleporter), then I must describe (as in transcribe) it. And someone somewhere out there may be interested in it.
If this means that I have to transcribe not one or two, but 20, 30, 40 bits of text in one image, then so be it, so are the rules.
Just because nobody on Mastodon does it, doesn't mean they're doing it right, and I'm doing it wrong. Maybe they don't know what that unreadable text says. Maybe they don't know that someone wants to know what's written there.
Six: All images must have an accurate and sufficiently detailed proper alt-text.
I can spend two days, morning to evening, working on an image description of 60,000 characters. 10,000 words. Three hours worth of reading. I can put the whole thing into the same post as the image. As in the post text body. As opposed to the alt-text for which this description is way too long.
But if the image in the post doesn't have an actual alt-text (and, again, it doesn't because the image description is in the post text itself), Mastodon's alt-text police is likely and fully justified to sanction me regardless.
So no matter how long and detailed and well-researched the long image description in the post is, I still have to distill an additional, shorter image description for the alt-text from it. And I have to do so without cutting too much information. Ideally, without cutting any information. If any of my images need a long description in the post, they need two descriptions, the long one in the post, the shorter one in the alt-text.
Leaving the several dozen individual text transcripts out of the description for the alt-text is risky already because text transcripts belong into the alt-text.
# # # # # # # # # # # # # # # # # # # # # # # # # #So OpenSimFest 2025 has started. But there hasn't been any announcement whatsoever, at least not recently. Even the official OpenSimFest website is dead as OpenSimFest is ongoing. OpenSimFest will span 16 days, but you only learn that in-world, too.
The grid is down to one normal expo sim the other "expo" sim is the home of the fenced-in zombie zone now. It's a far cry from 2022 and 2023 with their many expo sims, also because several very prolific exhibitors haven't been at OpenSimFest since 2023.
Also, the grid seems to have become painfully slow. It isn't laggy, there's no rubber-banding. But things rez rather slowly. Anything below the lowest mesh LOD only shows when I'm close and even then sometimes only after one or two minutes. Some objects take that long to appear in the first place. I've got my doubts that the recent Firestorm beta is to blame.
At least there are more exhibits on that one expo sim. Last year, OpenSim World's Fair in the Wolf Territories hogged so many resources that about half of the few remaining expo parcels at OSFest remained vacant and had to be used as impromptu Arcadia Asylum showcases upon short notice so that there was at least something on the land. Now we have things like a tiny Venice exhibit built by Cooper Swizzle, complete with a keyframed gondola ride.
Speaking of Kitely, Kimm Starr has brought back the fairground freak show that had to be removed when Coopersville was shrunk prior to being passed to its new owner. (By the way, Coopersville is not named after Cooper Swizzle. That's coincidence.)
Surprisingly little is still a work in progress on the first day. Then again, the sole expo sim is entirely in use.
After last year's break, Remmy Ravenhurst is back with her products, including an assortment of freebies. She even brought something new, namely free boxes with textures from which PBR materials can be made and free boxes with untextured mesh models. Since they are full-perm, it's possible to export the roughness texture and convert it into a specular texture for Blinn-Phong.
In general, the usage of the two Stores sims has improved, and that isn't only because the northern one of the two Stores sims is down to only two big stores. Still, as usual, there isn't a single freebie store all stores offer payware either mostly or only.
What still makes me wonder are the clothes that are being sold, often for prices that appear to be converted from Linden dollars to Gloebits 1:1, regardless of the Gloebit being more expensive than the Linden dollar.
There are boxes with classic layer and prim clothes that must be well over a decade old, and yet, in real-life currency, they cost more than a comparable fitted mesh outfit with PBR materials and Blinn-Phong fallback textures costs in Second Life. Then there are boxes with mesh clothes that are rigged for mesh bodies of which not a single one is officially being sold in OpenSim. So in order to be able to wear these legally bought clothes, you need a pirated mesh body.
Interestingly, the grid was not reset since last year. I'm still a member of the OSFest Participant group.
# # # # # # # # # # # #So OpenSimFest 2025 has started. But there hasn't been any announcement whatsoever, at least not recently. Even the official OpenSimFest website is dead as OpenSimFest is ongoing. OpenSimFest will span 16 days, but you only learn that in-world, too.
The grid is down to one normal expo sim the other "expo" sim is the home of the fenced-in zombie zone now. It's a far cry from 2022 and 2023 with their many expo sims, also because several very prolific exhibitors haven't been at OpenSimFest since 2023.
Also, the grid seems to have become painfully slow. It isn't laggy, there's no rubber-banding. But things rez rather slowly. Anything below the lowest mesh LOD only shows when I'm close and even then sometimes only after one or two minutes. Some objects take that long to appear in the first place. I've got my doubts that the recent Firestorm beta is to blame.
At least there are more exhibits on that one expo sim. Last year, OpenSim World's Fair in the Wolf Territories hogged so many resources that about half of the few remaining expo parcels at OSFest remained vacant and had to be used as impromptu Arcadia Asylum showcases upon short notice so that there was at least something on the land. Now we have things like a tiny Venice exhibit built by Cooper Swizzle, complete with a keyframed gondola ride.
Speaking of Kitely, Kimm Starr has brought back the fairground freak show that had to be removed when Coopersville was shrunk prior to being passed to its new owner. (By the way, Coopersville is not named after Cooper Swizzle. That's coincidence.)
Surprisingly little is still a work in progress on the first day. Then again, the sole expo sim is entirely in use.
After last year's break, Remmy Ravenhurst is back with her products, including an assortment of freebies. She even brought something new, namely free boxes with textures from which PBR materials can be made and free boxes with untextured mesh models. Since they are full-perm, it's possible to export the roughness texture and convert it into a specular texture for Blinn-Phong.
In general, the usage of the two Stores sims has improved, and that isn't only because the northern one of the two Stores sims is down to only two big stores. Still, as usual, there isn't a single freebie store all stores offer payware either mostly or only.
What still makes me wonder are the clothes that are being sold, often for prices that appear to be converted from Linden dollars to Gloebits 1:1, regardless of the Gloebit being more expensive than the Linden dollar.
There are boxes with classic layer and prim clothes that must be well over a decade old, and yet, in real-life currency, they cost more than a comparable fitted mesh outfit with PBR materials and Blinn-Phong fallback textures costs in Second Life. Then there are boxes with mesh clothes that are rigged for mesh bodies of which not a single one is officially being sold in OpenSim. So in order to be able to wear these legally bought clothes, you need a pirated mesh body.
Interestingly, the grid was not reset since last year. I'm still a member of the OSFest Participant group.
# # # # # # # # # # # # That's probably because "followers only" is not a Fediverse-wide standard backed by the ActivityPub spec or a FEP, nor does it tie in with any actual permissions systems available in the Fediverse.
As an example for the latter, Hubzilla, (streams) and Forte do not translate Mastodon's "followers only" into "these Fediverse actors are granted permission to view, like/dislike and reply to this message indefinitely, and everyone else isn't".
On top of that, all three assume that the permissions of all elements in a conversation are always the same because that's how they work. So if I post in public, and one of my Mastodon followers comments "followers only", then Hubzilla will treat it as public regardless because if my post is public, and it is, then all comments and replies are public, too.
At least Hubzilla shows a red padlock symbol on each message whose "permissions" don't align with what Hubzilla understands or expects.
CC:
# # # # # # # # # # # # # # #
I'm occasionally working on . It's still a very early WIP, also because it's highly ambitious. It might have its readers write very long and detailed image descriptions once it's "done". And it will not include step-by-step how-tos for alt-texts on certain frontends (e.g. I will not walk you through adding an alt-text to an image on Mastodon's Web interface or on Mona or IceCubes or Tusky). But what I have right now is a start.
CC:
# # # # # # # # # # # # # # # Add your location to a Google Map
Das Fediverse war Facebook, bevor es von Millionen von ahnungslosen Mastodon-Newbies zu Twitter gemacht wurde.
Mehr als die Hlfte der Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Der weit berwiegende Teil derer, die eines Besseren belehrt wurden, glauben immer noch, das Fediverse sei
Um das mal zurechtzurcken:
Im Januar 2016 ging Mastodon an den Start.
Im Juli 2010, fnfeinhalb Jahre vor Mastodon, startete Friendica (, ) als Facebook-Alternative.
Jetzt regen sich Mastodon-Nutzer darber auf, da Friendica auf so infame und rcksichtslose Art und Weise ins Mastodon-Fediverse eingedrungen ist und seine Nutzer
Fakt ist aber: Friendica gab es nicht nur schon fnfeinhalb Jahre, als Mastodon startete, sondern es war auch schon fnfeinhalb Jahre im Fediverse, als Mastodon startete. Und es hatte auch schon gut fnf Jahre lang seine eigene Kultur, als Mastodon startete.
In dem Augenblick, wo Mastodon startete, verband es sich sofort mit StatusNet (von 2008, wofr Mastodon ursprnglich nur eine Alternativoberflche war heute GNU social, , ), Friendica und Hubzilla (von 2015, basiert auf einem Fork eines Forks von Friendica von 2012 , ). Und nicht umgekehrt.
Wir waren zuerst hier. Findet euch damit ab.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # The danger in this, however, is that another Fediverse feature that's way older than Mastodon and at the same time absent from Mastodon would be reappropriated as something else, making Mastodon even more incompatible with the rest of the Fediverse.
In 2017, Mastodon introduced its content warning field. Ever since, almost everyone on Mastodon has been fully convinced that Eugen Rochko had invented that field from scratch. (Be honest, how about you)
However, Mastodon's content warning field is actually a summary field that has been used by StatusNet, Friendica and Hubzilla as such since 2008, 2010 and 2012 respectively. Mastodon hadn't had any support for that summary field at first, for you don't need a summary for 500 characters. And I guess that coder from the demo scene who submitted the merge request that reappropriated the summary field as a content warning field was blissfully unaware that Mastodon was actually connected to something that did use the summary field as such.
And now you have Mastodon users scolding Friendica users because the latter allegedly misuse the CW field for "like a subject or smth idk", unaware that the self-same field has been the abstract field on Friendica for five and a half years longer than Mastodon has even existed and some seven years longer than Mastodon had its CW field.
Today, in 2025, next to nobody on Mastodon knows that the Fediverse already has group actors, and probably neither do many on the *keys. Neither Mastodon nor Misskey nor their respective forks have or support groups in any way.
If they go and reappropriate group actors as starter packs, this will break compatibility with Friendica groups, Hubzilla forums, (streams) groups, Forte groups, Lemmy communities, /kbin magazines, Mbin magazines, PieFed communities, NodeBB forums etc., all of which can be and often already are being followed by Mastodon and *key users right now. And again, they've all had group actors since their respective inception.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Both have their use.
On the one hand, unless you're on a Mastodon server with a very low character limit, the post gives you much more room for a detailed description. A description in the post text is easier to navigate with a screen reader: It can jump back a few words or a sentence or so whereas, when reading out an alt-text, it can only jump back to the beginning of the alt-text. And if you have to explain the image or its description, something that keeps happening to me again and again, .
On the other hand, if you want to be safe from the wrath of Mastodon's alt-text police, you must add an accurate and sufficiently detailed alt-text to every last one of your images, regardless of image descriptions in the post itself.
Whenever I post an original image, I always describe it twice, both in the alt-text and in the post text. The description in the alt-text never contains any explanations, and it often doesn't contain any text transcripts either if there is too much text to transcribe. The description in the post always contains both (transcripts only if there's any text within the borders of the image).
When I post a meme, I only describe the visuals and transcribe the text bits in the alt-text. The post still contains all explanations, partially as external links if possible.
# # # # # # # # # # # # # # #
Diejenigen, die verneinen, da das Fediverse durch Mastodon zum Minenfeld geworden sind, sind allesamt selbst auf Mastodon und haben zum Brechen der Hlfte der Regeln berhaupt nicht die technischen Mittel. Deswegen bekommen sie von all dem auch nichts mit.
Der Rest des Fediverse mu sehr, sehr vorsichtig handeln, um nicht massiv an Reichweite zu verlieren. Ich bin wahrscheinlich trotzdem schon massenhaft geblockt worden und vielleicht auch der Grund, warum eine Mastodon-Instanz die Netzgemeinde komplett blockiert hat.
Ich frage mich, wie man auf Mastodon wohl reagieren wrde, wenn man wte, da Hubzilla ein, Forte zwei und (streams) drei verschiedene Mittel hat, um Mastodon komplett auszusperren, also alle existierenden und alle zuknftigen Server. Aber schon Hubzilla kennt da ja keine Sau, und (streams) und Forte sind, wenn berhaupt, ihrerseits sonst beinahe nur Hubzilla-Nutzern bekannt.
# # # # # # # # # # # # # # # # # # # # Thanks, that's the confirmation I needed that it isn't sufficient to mention what's in an image, but that I always have to give a sufficiently detailed description of what it looks like.
As I usually post images from virtual worlds, the threshold for "sufficiently detailed" is extremely high, though, because nobody has even only got a rough idea what anything in my images looks like.
One more reason for me to avoid having buildings in my images like the plague.
Also, this renders all of my existing image descriptions even more obsolete. I recall plants like mountain pines, a potted Jacaranda tree, a potted Bougainvillea, a maple tree, a potted banana tree etc. that hardly got more than their names dropped.
Lastly, several blind people have told me after I've asked that I don't have to give an exact visual description of a full brogue shoe or a herringbone fabric pattern. But reading this, I may question their advice again because I can't assume that everyone is familiar with these things.
# # # # # # # #
I tend to explain things at such a level of detail that nobody in the Fediverse will have to go look anything up themselves or ask me anything. From outside, especially Mastodon looks to me like that's what I'm expected to do.
So , I used well over 3,000 characters alone to explain Hubzilla (which, by the way, I'm normally daily-driving, so I know it very well). And the post wasn't even about Hubzilla I just needed to explain Hubzilla to be able to explain the streams repository and the concept of nomadic identity in order to be able to explain the post itself.
The last time I've described a UI .
# # # # # # # # # # # #
It was her who told me to never explain things in alt-text because she and people like her can't read these explanations, because they can't open the alt-text with these explanations inside.
Explaining stuff in alt-text and not in the post throws people like her in front of a bus, just like not describing images at all throws blind and visually-impaired people in front of a bus.
I have explained my image posts in the post text body ever since, regardless of Mastodon users whining that I exceed 500 characters.
Explanations go into the post/toot where everyone can access them.
I mean, sure, you're free to put them only in the alt-text because your character limit is so meagre. You're just as free to write super-short alt-texts that don't really describe anything. You're just as free to not describe your images at all.
But don't complain if someone criticises you for either.
CC:
# # # # # # # # # # # # # # # This is actually a mistake that many Fediverse user keep making because they don't know better, and because the majority of Mastodon users only have 500 characters available.
That's because I'm being absolutely serious here. In order to access alt-text, you need either a screen reader (which sighted people don't have) or at least one sufficiently working hand.
If you want to explain your image, please do so in the post text itself and not in the alt-text.
# # # # # # # # # # # When I want to post an original image, that "one extra minute" is more like several hours or even multiple entire days that it takes to research for and write the descriptions for one image. No, I'm not joking.
Even when I post a meme, I can't describe the visuals in the image itself in a few minutes. And then the explanations (which go into the post itself rather than into the alt-text) come on top.
Still, I always go all the way whenever I post an image. I'd rather not post an image than underdescribe and/or underexplain it. I refuse to do any less than that because I always have to expect someone somewhere out there needing it. That's why I've only posted one measly image in the last 12 months, and that was a meme.
# # # # # # # # # # # Die Dnnhutigkeit gibt's auf beiden Seiten.
Auf der einen Seite sind Mastodon-Nutzer, die "Mastodon" und "Fediverse" gleichsetzen und es dann als bergriffig empfinden, wenn man ihnen etwas ber das Fediverse erklrt, wonach sie nicht vorher explizit gefragt haben.
Auf der anderen Seite sind Fediverse-aber-nicht-Mastodon-Nutzer, denen es auf den Geist geht, da, was auch immer sie benutzen, von den Mastodon-und-Fediverse-Gleichsetzern immer wieder als nichtexistent behandelt wird. Einige von denen mssen das jetzt schon seit fast zehn Jahren ertragen, weil sie schon im Fediverse waren, bevor sie auf Mastodon waren.
# # # # # # # # # # # # # #
Advantages:
- written in PHP, runs on a LAMP stack
- uses much fewer system resources than Mastodon while being magnitudes more powerful
- comes with a git-based update script
- result of over 15 years of development (traces back to Friendica from 2010)
- developed by a retired professional developer with almost half a century of experience who has made more Fediverse server apps than anyone else and even more decentralised protocols than anyone else
- does not cache everyone's images and media
- Facebook-like not a microblogging system
- highly configurable Web UI
- your login/account is not your identity you can have as many fully independent channels/identities (each corresponding to one full-blown Mastodon account) on the same login/account and switch between them without logging out
- if you run another server (or you find a public server, and Forte doesn't have any), you can clone your channel between multiple servers and make it resilient against server outage
- over 24 million characters
- full set of text formatting, using BBcode, Markdown and HTML
- supports both titles and summaries (Mastodon understands summaries as CWs)
- embed as many images as you want within the post (as in text, image, more text, another image, even more text etc., like a blog post)
- can double as a long-form blog
- can optionally send multiple-paragraph posts as Article-type objects
- the most advanced permissions system in the whole Fediverse
- full support for threaded conversations see entire conversations by default instead of single-message piecemeal like on Mastodon supports
- supports groups built-in group functionality including moderated groups and private groups as well as hiding groups (and other channels) from directories
- has at least one support group on (streams)
- built-in cloud file storage which is also used for embedded images ties into the permissions system WebDAV connectivity
- built-in federating event calendar
- built-in headless CalDAV calendar server
- built-in headless CardDAV addressbook server
- highly modular, comes with lots of add-ons called "apps"
Disadvantages:
- steep learning curve, especially if all you're used to are Twitter and Mastodon (this looks, feels and handles absolutely nothing like Mastodon, so you'll have to relearn everything from the ground up and learn tons of stuff on top)
- does not cosy up to Mastodon at all, makes few to no concessions for more compatibility with Mastodon
- will need configuration before you can really get started
- doesn't post in public by default configuration needed if you want to always post in public
- poor documentation
- doesn't work with any phone app out there progressive Web app with the Web interface is the best you can do on a phone
Advantage or disadvantage, decide for yourself:
- implements ActivityPub by the book (whereas other Fediverse server applications "implement Mastodon" rather than implementing ActivityPub)
How it compares to Forte:
- direct precursor of Forte which is forked from it
- from the same developer
- officially and intentionally nameless and brandless ("streams" is the name of the code repository)
- has at least two public, open-registration servers, but they're hard to find
- uses the same support group
- based on its own protocol, Nomad, which has even better support for nomadic identity ActivityPub is optional and on by default on new channels
- cannot clone from or to Forte
How it compares to (streams):
- older than Mastodon (forked from a Friendica fork in 2011, development started in 2012, became Hubzilla in 2015, still 10 months before Mastodon)
- created by the same developer, now maintained by two other devs
- server lists readily available on FediDB and Fediverse Observer (in case you want to try it first or clone to a public server)
- even steeper learning curve
- ActivityPub is off by default for new channels, must be activated in order for Hubzilla to federate with most of the rest of the Fediverse
- can optionally federate with diaspora* as well
- can subscribe to RSS and Atom feeds
- requires another bit more of configuration before you can get started
- way better documentation written by a user
- one public and multiple private profiles per channel, can be assigned to certain contacts
- over 16.7 million characters
- text formatting only with BBcode
- cannot send Article-type objects, always sends Note-type objects
- the second-most advanced permissions system in the Fediverse (a bit more complicated and less adapted to today's Fediverse also, not quite as detailed reply control)
- even more configurable UI
- CalDAV calendar can use the event calender UI
- optional non-federating long-form articles
- optional non-federating wikis (as in multiple wikis per channel with multiple pages per wiki)
- optional non-federating "planning cards"
- optional non-federating webpages
# # # # # # # # # # # # Nur so zur Info:
ist auf Mastodon.
ist auf Calckey, einem Misskey-Fork (siehe Fediverse-Sprechstunde, 27.10., 19.30 Uhr). Misskey ist seit 2014 in Entwicklung, fast zwei Jahre lnger als Mastodon, und wird vllig unabhngig von Mastodon entwickelt.
Und ich habe das hier gerade von Hubzilla gesendet, das aus einem Fork eines Forks von Friendica entstanden ist (siehe Hubzilla-Workshop, 29.10., 20.30 Uhr). Friendica ist seit 2010 in Entwicklung, fast sechs Jahre lnger als Mastodon, und wird vllig unabhngig von Mastodon entwickelt.
Trotzdem ist das alles auf Mastodon zu sehen. Aber nur weil es auf Mastodon zu sehen ist, heit das noch lange nicht, da es auch von Mastodon kommt.
brigens, deutliche Hinweise, da das hier nicht von Mastodon kommen kann:
- Es ist lnger als 500 Zeichen.
- Guck dir die Erwhnungen an. Langnamen Mastodon erwhnt nicht mit Langnamen. Hubzilla schon. Auerdem ist bei Mastodon das Teil des Link. Hier auf Hubzilla nicht.
- Guck dir die Hashtags an. Bei Mastodon ist das # Teil des Link. Hier Hubzilla nicht.
# # # # # # # # # # # # # # # # #
(but not quote it since quoting is a Mastodon "neologism")
What Mastodon refers to as "quoting", and what calls "quote-tweets", has been available on Friendica (which is on, by the way) since its inception a bit over 15 years ago, only that Friendica calls it "quoted sharing".
What Friendica calls "quoting" is what I've done up there at the top of this comment (I'm on Hubzilla, created by Friendica's creator in 2015 from a fork of a fork of Friendica).
Both features have been available in the Fediverse since five and a half years before Mastodon was launched.
# # # # # # # # # # # # # # # # # # # # # # Identitten unabhngig von Servern und Konten gibt's im Fediverse schon seit 2012, fast vier Jahre lnger, als es Mastodon gibt. Und dazu sogar noch besser als in der ATmosphere. Das Konzept nennt sich "nomadische Identitt". Erstmals eingefhrt wurde es Mitte 2012 auf Red, das Ende 2012 in Red Matrix umbenannt und 2015 in Hubzilla umgebaut wurde.
Der Clou bei der nomadischen Identitt ist, da deine Fediverse-Identitt mit wirklich allem, was dazugehrt, gleichzeitig auf beliebig vielen unabhngigen Servern existieren kann, und zwar als bidirektionale Echtzeit-Backups. Und diese Backups, auch Klone genannt, sind jeweils fr sich vollwertige Instanzen deiner Identitt, in die du dich ebenso einloggen und sie benutzen kannst wie das "Original". Und zwar auch und gerade, wenn das "Original" offline ist. Wenn es wieder online kommt, wird alles, was du auf den Klonen gemacht hast, und alles, was sonst auf den Klonen passiert ist, automatisch zum "Original" zurcksynchronisiert.
In der ATmosphere funktioniert Unabhngigkeit auch von einzelnen Relay-AppView-Stacks nur, indem jeder Relay alle, aber auch wirklich ausnahmslos alle Daten aus der ATmosphere speichert. Mit nomadischer Identitt mssen nur deine Daten geklont werden.
Das ist auch weder ein theoretisches Konzept noch ein experimentelles Projekt, sondern es wird seit mehr als einem Jahrzehnt produktiv genutzt.
Ich schreibe hier gerade selbst von Hubzilla von einem Kanal, der einen Klon hat. Und auch ist auf Hubzilla und knnte seinen Kanal klonen, wenn er es nicht schon getan hat.
# # # # # # # # # # # # Sagen wir, es hat sich ausgednnt.
Misskey gibt es natrlich weiterhin. Das ist in Ostasien, vor allem in seinem Heimatland Japan, meines Wissens populrer als Mastodon, auch wenn man sich das als westlicher Mastodon-Nutzer nicht vorstellen kann.
Calckey ist eingestellt worden, dessen Fork Firefish auch, aber es gibt noch Server.
Iceshrimp-JS ist im Wartungsmodus, wird also nicht mehr weiterentwickelt. Iceshrimp.NET ist kein Fork von irgendwas, sondern in C# neu geschrieben worden, aber in Sachen Features ist es von Misskey und den Forkeys meilenweit entfernt.
Der Platzhirsch unter den Forkeys ist nach wie vor Sharkey, das sagenhaft viele Features hat. Im Grunde ist es inzwischen der einzige Forkey, der in der westlichen Welt berhaupt noch eine Rolle spielt. Es gibt zwar einiges an Kritik, aber keine realistischen Alternativen.
CherryPick, das wie Misskey aus Japan kommt ist auch sehr leistungsfhig, aber mein letzter Stand war, da smtliche Server bis auf einen in den Grorumen Tokyo und Seoul stehen. Das ganze Projekt ist also wohl noch weit mehr vom Westen entkoppelt als Misskey.
Wie es mit der Entwicklung von Catodon aussieht, wei ich nicht. Ich schtze, das Problem war einfach, da Catodon sich zu sehr an Iceshrimp geklammert hat. Nur ist Iceshrimp-JS, auf dem Catodon ja basiert, fast tot, und das neue Iceshrimp.NET ist etwas ganz anderes, so da man von vorne htte anfangen mssen, und featuremig nicht mal auf Misskey-Niveau. Auerdem ist wohl die Idee, etwas zu bauen, das so einfach zu bedienen sein sollte wie Mastodon, aber mit *key-Unterbau, nicht so gut angekommen. Jedenfalls wird nchsten Monat wohl der letzte noch existierende Catodon-Server schlieen.
Hajkey ist schon lnger weg vom Fenster. Das war nur fr einen einzigen Server aufgezogen worden, und der ist zwischenzeitlich auf Sharkey umgestellt worden, weil es kaum mehr realistisch war, Hajkey aufrechtzuerhalten.
Bezglich der vielen anderen Forkeys (Meisskey, Tanukey, Neko usw.) bin ich nicht im Bilde.
Ganz neue Forks hat es wohl lange nicht gegeben. Den Aufwand, Misskey zu forken und hinzubiegen, macht sich keiner mehr. Sharkey ist an sich jetzt ziemlich tauglich, und es gibt wohl keinen Grund, der Entwicklerin mit einem Fork ans Bein zu pinkeln. Und Iceshrimp.NET ist noch zu unfertig, um es zu forken, mal ganz davon abgesehen, da keiner Fediverse-Software in Microsoft C# entwickeln will (aber in Microsoft TypeScript kurioserweise sehr wohl).
# # # # # # # # # # # # # # # # # # # # # # # # # There are several, but unlike Guppe, they all require a local account. They can be connected/followed from Mastodon, but you cannot simply create a group there on the fly with nothing but your existing Mastodon account. Also, no matter what you choose, it will handle nothing like Mastodon or a *key.
- Friendica
Alternative to/works like: Facebook, long-form blogging platforms
Official website:
Wikipedia:
Join the Fediverse Wiki:
List of existing groups:
Official server list:
FediDB:
Fediverse Observer:
FediIndex: - (streams)
Alternative to/works like: Facebook, long-form blogging platforms, various cloud services
Officially nameless and brandless colloquially "named" after its code repository
No official website
Code repository (instead of website):
Join the Fediverse Wiki:
No official server list
No FediDB, Fediverse Observer and FediIndex entries
Public server in North America (USA):
Public server in Europe (Hungary German admin also speaking English):
list - Hubzilla
Alternative to/works like: Facebook, long-form blogging platforms, various cloud services, GeoCities etc.
Official website:
Wikipedia:
Join the Fediverse Wiki:
Notice: Software versions with an odd number after the first dot (e.g. 10.5.x) are experimental. Software versions with an even number after the first dot (e.g. 10.4.x) are stable.
Official server list:
FediDB:
Fediverse Observer:
FediIndex: - PieFed
Alternative to/works like: Reddit, Hacker News
Official website:
Official server list:
FediDB:
Fediverse Observer:
FediIndex: - Mbin
Alternative to/works like: Reddit, Hacker News
Official website:
Official server list:
FediDB:
Fediverse Observer:
FediIndex: - Lemmy
Alternative to/works like: Reddit, Hacker News
Official website:
Official server list:
Unofficial server list:
Unofficial list of existing communities:
FediDB:
Fediverse Observer:
FediIndex:
One more thing that's critically important to know is that posting (as in starting a new thread) on either of these from Mastodon or a *key is not quite straight-forward.
That's because a title is recommended on Friendica, Hubzilla and (streams), and on Lemmy, Mbin and PieFed, a title is pretty much mandatory. But neither Mastodon nor the *keys have any active support for titles. (The CW field corresponds to the summary the title is something entirely different.)
So if you want to start a new thread from Mastodon or a *key, you have to adhere to a special post format:
- First line: the title.
- Second line: mentions the group with .
- Then: the actual post text.
Lastly: Don't use hashtags when posting or commenting to Lemmy, Mbin and PieFed. Reddit doesn't have hashtags either, and what Reddit doesn't have has no place on either of these three.
# # # # # # # # # # # # # # # # # # # You do know that neither Catodon nor Firefish are singular server instances, but their own decentralised server applications like Mastodon
Anyway, the closest thing to Catodon that can be recommended to people living outside of East Asia right now is Sharkey. Like Catodon and Firefish, it's part of the family of Forkeys, i.e. direct or indirect Misskey forks.
- Official website:
- FediDB server list:
- Fediverse Observer serverlist:
- Sharkey at FediIndex:
# # # # # # # # # # # By the way, Friendica, Hubzilla, (streams) and Forte have a similar feature that lets you add a location tag to your post. It can be an arbitrary string, but it can also be something that OpenStreetMap recognises. If you or someone else has the appropriate OpenStreetMap add-on installed, the location can be shown on a map.
You have two options to set a location. One is to define a default location for all your posts it can be overridden as well as cleared for specific posts. The other one is to define a location for a specific post. I think all four can actually automatically tag your posts by figuring out your current physical location if you want them to.
At least Hubzilla also has an add-on that randomly tags posts with planets from the Star Wars franchise, and (streams) and Forte have one that randomly tags posts with real-world cities.
# # # # # # # # # # # # # # Mit denen wrde ich auch nicht klarkommen knnen. Ich meine, diese Cryptobros versuchen allen klarzumachen, da das Metaversum, also virtuelle 3-D-Welten, technisch nicht realisierbar wren ohne Blockchain, ohne Kryptowhrung, ohne Land per NFTs zu verkaufen und ohne Objekte als NFTs anzubieten.
Haha.
Jetzt in diesem Augenblick bin ich eingeloggt in eine virtuelle Welt, die seit Anfang 2010 existiert. Auf Basis eines Virtuelle-Welten-Systems von Anfang 2007, das komplett ohne Blockchain, ohne Crypto und ohne NFTs auskommt, und wo auch schon seit 2007 das Wort "Metaverse" Teil des stndigen Sprachgebrauchs ist.
Dieser Kanal und meine Zusatzkanle auf (streams) sind alle nach meinem Hauptavatar benannt.
Ich habe sogar Avatare in einem Grid auf Basis derselben Software, das schon seit Mitte 2007 existiert.
Die Cryptobros fhren ja auch gern Decentraland als Leuchtturmprojekt auf, als "erstes dezentrales Metaversum berhaupt". Auch das ist Bldsinn. Dezentral ist an Decentraland nur, da es nicht auf der Bitcoin-Blockchain luft, sondern auf der von Etherium. Ansonsten ist Decentraland nur eine einzige Welt, ein zentralistischer Walled Garden.
Wo ich bin, das ist ein Netzwerk von ber 4000 individuellen Welten, von denen die allermeisten miteinander verbunden sind mittels einer Technologie, die es auch schon seit Mitte 2008 gibt.
Und ich bin verbunden mit einer halben Busladung Leute, die in Second Life sind, das auch schon seit 2002 existiert, auch ohne Blockchain, Crypto und NFTs.
Da knnen mir die Cryptobros also viel erzhlen.
# # # # # # # # # # # #How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view
Enough of a nuisance for the main developer of Hubzilla to speak up against it.
Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :facewithrollingeyes:
See If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.
Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.
# # # # # # # # # # # # # # # # #How much of a nuisance have Mastodon users working around Mastodon's hard-coded 500-character limit become, at least from a non-Mastodon point of view
Enough of a nuisance for the main developer of Hubzilla to speak up against it.
Dear people of the Fediverse,
Please STOP tearing your carefully crafted essays to pieces. This is no longer necessary. If your preferred instance does not allow this, consider asking your instance admin to increase the limit or switch to a different instance. Besides, it is so last decade :facewithrollingeyes:
See If Mastodon users can complain about "long posts" from outside Mastodon, namely anything that exceeds 500 characters, then those of us who did not come into the Fediverse via Mastodon can complain about Mastodon users chopping long posts up into lots of little pieces.
Little nitpick: It has never been necessary. Friendica and Hubzilla have had a nearly unlimited character count since before Mastodon came with 500 characters.
# # # # # # # # # # # # # # # # # Das ist eigentlich als Feature gedacht, damit man nicht immer alles ffentlich macht, nur das, was ffentlich sein soll. Ist aber doof, wenn man wirklich alles ffentlich haben will, weil man keinen rein persnlichen Privatkanal betreibt.
Jedenfalls postet Hubzilla standardmig nur in eine sogenannte Privacy-Gruppe namens "Freunde". Privacy-Gruppen sind im Prinzip wie Mastodon-Listen, nur sehr viel mchtiger und eigentlich ein optionales Feature, hnlich wie auch schon ActivityPub.
Wenn du Privacy-Gruppen nicht aktiviert hast, hast du nur genau diese eine und kannst sie auch nicht konfigurieren. Du mut also erstmal die App installieren und kannst dann in der Privacy-Gruppe "Freunde" abschalten, da standardmig in diese Privacy-Gruppe gepostet wird.
# # # # # # # # # # # Der Funktionsumfang ist ber gut 15 Jahre gewachsen von Mistpark/Friendica (2010) ber Red/die Red Matrix (2012), ber den Start von Hubzilla (2015), ber einen Entwicklerwechsel (2018) und ber Vernderungen im Fediverse, neue FEPs und Backports von Hubzillas eigenen Nachfahren bis heute.
Die meisten Features sind aber entweder geerbt von Friendica, das sie 2010 schon hatte, oder 2012 mit dem Start von Red dazugekommen oder 2015 bei der Umstellung von der Red Matrix nach Hubzilla.
brigens, falls du Bock und Zeit hast: Nchsten Mittwoch ist der zweite Hubzilla-Workshop. Die luft online auf BigBlueButton, du brauchst also nur einen Browser, was zum Hren, idealerweise ein Mikro und Zeit.
Hubzilla Workshop #02
Datum: Mi., 29.10.2025
Uhrzeit: 20:30 Uhr
Ort:
Dieser Workshop richtet sich im Hauptthema an Einsteiger und Neugierige. Es geht darum, einen Account und einen Kanal bei Hubzilla zu erstellen, und um die unumgnglichen notwendigen ersten Schritte der Konfiguration.
Zu Beginn wird ein Video prsentiert, welches die einzelnen Punkte erlutert, die notwendig sind, um mit Hubzilla am Fediverse teilnehmen zu knnen.
Im Anschluss daran werden wir gemeinsam mit den Teilnehmern beispielhaft eine Einrichtung vornehmen. Es folgt eine Frage-und-Antwort Runde, zum Schwerpunkt, aber auch zu allgemeinen Themen rund um Hubzilla.
Also: Habt Ihr Interesse an Hubzilla, wrdet Ihr gerne mit Hubzilla das Fediverse bereisen Traut Ihr Euch nicht, weil es als schrecklich kompliziert verschrien ist Mchtet Ihr erfahren, was mit Hubzilla sonst noch alles mglich ist
Dann solltet Ihr an diesem Workshop unbedingt teilnehmen!
Administratoren und Hub-Betreiber sind selbstverstndlich auch herzlich eingeladen. Wir aber vor allem auch die Einsteiger brauchen Euch und Eure Expertise!
Ort: Online-Veranstaltung:
# # #
# # # # # # # # # # # # Es wre brigens lohnenswert, nicht nur auf Mastodon zu suchen.
Die Piraten-Partei hat als ursprnglichen bundesweit offiziellen Fediverse-Server nmlich keinen Mastodon-Server, sondern einen Friendica-Node und den schon weitaus lnger, als es Mastodon berhaupt gibt.
# # # # # # # # # # # # # Die offizielle Mastodon-App ist so ziemlich die schlechteste und unterausgestattetste Mastodon-App, die es berhaupt gibt.
Viele glauben, die sei die Referenz-App, weil es ja die offizielle App ist und offizielle Apps ja eigentlich immer fully-featured sind. Tatschlich ist sie aber eine Verlegenheitslsung, damit es im Apple App Store und im Google Play Store berhaupt eine offizielle App namens "Mastodon" gibt, weil 99% der Twitter-Umsteiger erstmal danach suchen werden.
Was die nicht kann
Beispiel: Beinahe jedes Fediverse-Frontend da drauen rollt lange Inhalte standardmig ein, und dann kann man sie hndisch wieder ausrollen. Auer superminimalistischen "Damit es berhaupt eine Weboberflche gibt"-Behelfs-Weboberflchen von superminimalistischen Serveranwendungen ist die offizielle Mastodon-App das einzige Frontend, das das nicht kann. Die ist gebaut worden in der Annahme, da es im Fediverse nur Inhalte mit maximal 500 Zeichen gibt.
Dieses Manko in der offiziellen Mastodon-App ist wahrscheinlich einer der Hauptgrnde, warum viele Mastodon-Nutzer sich ber "lange Posts" mit ber 500 Zeichen aufregen.
Ich frage mich gerade, ob sie in der Lage ist, Textformatierung anzuzeigen.
# # # # # # # # # # #
All Black Jordie Barrett proposes to his long time girlfriend
Barrett popped the question days before the All Blacks embark on their Grand Slam tour which kicks off
Ihr paar Friendica-Heinzeln seid wirklich komplett irrelevant.
Noch arroganter zeigen, da das Fediverse nur besteht aus
- Mastodon
- Spinnern, die besser jetzt als gleich allesamt aus dem Mastodon-Fediverse rausgeschmissen gehren
Sonst httest du nmlich lngst gelesen, da ich gar nicht auf Friendica bin.
Und weil alle, die nicht auf Mastodon sind, sowieso irrelevant sind, hast du doch bestimmt auch nichts dagegen, wenn wir uns weiterhin an unsere Kulturen halten, statt sie fr Mastodons Kultur ber Bord zu werfen.
CC:
# # # # # # # # # # # Deine vielleicht.
Ich wei dagegen, da ich gengend reine Folgeverbindungen habe, die definitiv mein Profil nicht gesehen haben. Also, gar nicht, nicht mal im Mastodon-Webinterface oder in irgendeiner Mastodon-App.
Wer ein Mastodon-Konto hat, das erst ein paar Stunden alt ist, aber schon mehr als 1000 Akteuren folgt, hat sich definitiv nicht die Mhe gemacht, sich von jedem davon jeweils das Profil anzugucken. Und mir passiert es nur einmal alle tausend kalten Winter, da mir jemand wegen des Primrthemas meines Kanals folgt.
Ich wage auch zu behaupten, annhernd niemand zumindest von meinen Mastodon-Kontakten hat sich die Mhe gemacht, sich mein Profil im Original anzusehen, also im Webbrowser und dann auf Hubzilla selbst (). Da steht nmlich noch einiges mehr, was Mastodon nicht zeigen kann, weil Mastodon die allermeisten von Hubzillas Profilfelders berhaupt nicht untersttzt.
Im Grunde wei ja schon annhernd niemand, da das hier ein Hubzilla-Kanal ist, der auf zwei Themengebiete spezialisiert ist und seine Identitt von einem Virtuelle-Welten-Avatar bernommen hat, und nicht das eine private Allzweck-Mastodon-Konto einer realen Person. Oder wutest du das
# # # # # # # # # # Die Darstellung als Markdown im Klartext ist ein eindeutiger Bug in Iceshrimp. Ganz offensichtlich kennt Iceshrimp keine Hashtags, wie sie Friendica schon seit mehr als 15 Jahren produziert, also, wo die Raute nicht Zeichen des Link ist. Also wandelt Iceshrimp die Hashtags in Markdown um, rendert sie dann hinterher aber nicht entsprechend.
Hubzilla selbst verwendet berhaupt kein Markdown. Hubzilla wandelt Hashtags intern in BBcode um. Beim Versenden wird der BBcode in den RTF-Standard umgewandelt. Iceshrimp wiederum wandelt RTF in Misskey-Flavored Markdown um. Aber wie es aussieht, kommt Iceshrimp nicht mit der Konstellation klar, wenn vor einem Link ein Rautenzeichen steht. Daran kann Hubzilla nichts machen.
Viele der Hashtags, die ich verwende, dienen dazu, Filter auszulsen, weil ich immer davon ausgehen mu, da das, was ich hier so gerade bers Fediverse schreibe, so einige Leute strt. "Oh mein Gott, jetzt schreibt der Rowland wieder irgend so einen Mist ber das Fediverse/Quote-Posts/CWs/Alt-Texte/Bildbeschreibungen/..." So knnen sie diese Inhalte gezielt rausfiltern. Oder sie knnen sie hinter individuellen, nur fr sie automatisch leserseitig generierten CWs verstecken lassen (geht auf Mastodon seit 2022 und auf Mikes Schpfungen schon immer) deswegen die vielen Hashtags mit "CW" am Anfang.
Beispiele:
# und # heien: "Der Rowland labert schon wieder bers Fediverse."
# und # heien: "CW: Der Rowland labert schon wieder bers Fediverse."
Hashtags sind es deshalb, weil die sich noch am unaufflligsten als Schlsselwrter in jeden Post, jeden Kommentar und jede Antwort einbauen lassen.
Und es sind deswegen soviele, weil ich ja nicht wissen kann, ob jetzt jemand "QuotePost" oder "QuoteTweet" oder "QuoteToot" oder "QuoteTrt" oder "QuoteBoost" oder den jeweiligen Plural filtert. Die meisten drften davon genau eins filtern, aber ich wei eben nicht welches.
Wenn ich damit jetzt aufhren wrde, weil das einige Leute strt, wrde ich andere Leute stren, die genau diese Hashtags filtern.
Warum nicht "einfach" CWs wie auf Mastodon
Weil Mastodons CW-Feld hier ein Zusammenfassungsfeld ist. Und zwar auf Hubzilla seit Frhjahr 2015, auf Red bzw. der Red Matrix (quasi Proto-Hubzilla) seit 2012 und auf Friendica seit 2010. Lnger, als es Mastodon berhaupt gibt.
Zwei Dinge sind bombenfest in den Kulturen von Friendica und Hubzilla einzementiert.
Zum einen: Das Zusammenfassungsfeld ist fr Zusammenfassungen.
Zum anderen: CWs lt sich jeder automatisch und nur fr sich individuell mittels eines Filters namens "NSFW" generieren. Und das ist tausendmal besser, als dieselben CWs allen Leuten ber das Zusammenfassungsfeld aufzuzwingen, ob sie diese CWs brauchen oder nicht.
# # # # # # # # # # # # # # # #
Mario weist neue User:innen bei jeder sich bietenden Gelegenheit darauf hin )
Das macht er deshalb, weil die Leute
- ins Fediverse kommen und vorher nur von Mastodon erfahren
- Monate oder ganze Jahre auf Mastodon verbringen mit dem unumstlichen "Wissen", das Fediverse sei nur Mastodon
- wann immer sie ber das Fediverse schreiben, es mit Mastodon gleichsetzen, und damit alle Nicht-Mastodon-Nutzer diskriminieren
- der felsenfesten berzeugung sind, wenn Mastodon ein Feature nicht hat, dann hat es das ganze Fediverse nicht, z. B. Quote-Posts
- Software oder Websites fr "das Fediverse" mit "Fedi" im Namen bauen, aber alles nur fr Mastodon und entweder ohne Untersttzung fr oder gnzlich inkompatibel zum Rest des Fediverse
- bei ihrem Erstkontakt mit Inhalt, der so unmglich von Mastodon kommen kann, schlagartig in Xenophobie umschlagen (sich aber trotzdem selbst als die tolerantesten Menschen berhaupt sehen)
- seither das Fediverse "wieder" zu nur Mastodon machen wollen
- mit aller Vehemenz versuchen, berall im Fediverse die Mastodon-Kultur durchzudrcken, auch auf Calckey und Iceshrimp und Friendica und Hubzilla usw., wo es eine ganz eigene Kultur gibt und die Mastodon-Kultur schon technisch so kaum bis gar nicht funktionieren kann
Je eher sie erfahren, da a) das Fediverse mehr ist als nur Mastodon, b) das vllig normal und Teil des Konzepts des Fediverse ist und c) das Fediverse zu keinem Zeitpunkt nur Mastodon war, desto besser.
# # # # # # # # # # # # # # # #
Wenn ihr hier darauf hinweist, dass Menschen doch von Mastodon weg, hin zu sharkey, friendica, iceshrimp, oder zu welcher "FediVerse-Zugangssoftware" auch immer ... migrieren sollen, ...
...dann tun wir das, weil diese Menschen "Auto" mit "Mexiko-Kfer" gleichsetzen. Weil sie sich vielfach Features in Autos wnschen, die praktisch nur der Kfer nicht hat. Weil so Technologien wie ein 12-Volt-Bordnetz fr sie unvorstellbar sind. Und weil wir ihnen dazu raten wollen, sich mal statt dessen einen Toyota oder so zuzulegen. Dann htten sie auch mal eine anstndige Heizung und mehr Platz im Auto. Aber nein, einmal Kfer, immer Kfer, und der Kfer ist das beste Auto berhaupt.
Und dazu kriegen wir stndig auf die Schnauze von Leuten, die sagen, die Straen sind nur fr Kfer gebaut worden, und Autos mit wassergekhltem Motor oder mit mehr als 34 PS haben auf der Strae nichts zu suchen. Jedem, der auch nur einmal schneller fhrt als 115 km/h, gehrt der Fhrerschein entzogen. Und wenn ein Auto den Kofferraum hinten hat, dann ist das eine eindeutige Fehlentwicklung.
Nur da es in diesem Fall die Mercedes V-Klasse schon vor dem Mexiko-Kfer gab.
CC:
# # # # # # # # # # # # # # #
- most importantly, you can have both, like if you have a short description of a scene that you intended to be read, and then a drawing of that scene, the alt text could say something like "a drawing depicting the scene"
I always describe my fully original images twice, only that the description in the alt-text is the short one. The one that goes into the post text is much, much, much longer. It contains verbatim transcripts of all text within the borders of the image, and it contains all explanations needed for random laypeople to understand the image and the long image description.
CC:
# # # # # # # # # # #When I describe my images, I do so under a few assumptions.
One: My audience is not limited to my following contacts. It's absolutely everyone who comes across any of my posts.
It isn't sufficient to make my posts accessible to those who have chosen to follow me. I must make them just as accessible to a random stranger who receives them after they've been boosted a dozen times over. I must make them just as accessible to a random stranger who stumbles upon them on the public timeline of whatever server they're on.
Two: If an element in an image is mentioned, it must also be described visually.
Blind or visually-impaired people always need to know what something in my images looks like. This goes doubly for my typical original images I mean, how are they supposed to know what something looks like in a specific 3-D virtual world
So if there's a building in one of my images, and I mention that this building is there, I also have to give a visual description of it. A full, detailed description.
If there's an image in one of my images, e.g. a preview image on a teleporter that shows the place where the teleporter would take me, I have to fully describe that image. An image in my image that doesn't even take up 200 pixels in my image. (Something that I've refused to do in my longest image description so far because that would have led me to going at least four levels deep: describing loads of infinitely small images in several dozen infinitely small images in an image in my image.)
In fact, this isn't an assumption. I have written confirmation for it. I can't find it right now, otherwise I'd share it here, but I have it somewhere.
Three: Image descriptions must always deliver all information that someone may need right away.
Not everyone wants to ask for a description of a certain detail in an image. Not everyone wants to ask for an explanation of what they don't understand or what they're unfamiliar with. Having to look things up yourself isn't much better. Some may go as far as likening not having an image description that contains everything they need to know to not having any image description.
By the way: It's a fact that some Mastodon users consider linking to external information ableist because linked websites aren't necessarily sufficiently accessible themselves. Instead of linking to information, the information must go into the post itself. (And I can't even use any character limit as an excuse not to do that because my "limit" is over 16.7 million.)
In other words, the only way for me not to be ableist is to give any and all information that anyone out there may require in my image post immediately.
Of course, this will clash with the demand by other Mastodon users (or maybe even some of the same) to never post more than 500 characters at once. But I can't do both. And I've never read anywhere that posting more than 500 characters is allegedly ableist.
Four: Someone somewhere out there may be interested in even small details in my image. And they may not be sighted.
Maybe you aren't. But someone somewhere out there may be. And they matter every bit as much as you or everyone else.
If they need a full description of all details, regardless of why, I have to deliver it. Immediately. See above.
Five: Any and all text within the borders of the image must be transcribed verbatim, no exception.
Most importantly, this even extends to text that's unreadable in the image if I can read and/or source it.
The assumptions further up apply here as well: If I mention it (the text in this case, and be it as part of the visual description of something else like a teleporter), then I must describe (as in transcribe) it. And someone somewhere out there may be interested in it.
If this means that I have to transcribe not one or two, but 20, 30, 40 bits of text in one image, then so be it, so are the rules.
Just because nobody on Mastodon does it, doesn't mean they're doing it right, and I'm doing it wrong. Maybe they don't know what that unreadable text says. Maybe they don't know that someone wants to know what's written there.
Six: All images must have an accurate and sufficiently detailed proper alt-text.
I can spend two days, morning to evening, working on an image description of 60,000 characters. 10,000 words. Three hours worth of reading. I can put the whole thing into the same post as the image. As in the post text body. As opposed to the alt-text for which this description is way too long.
But if the image in the post doesn't have an actual alt-text (and, again, it doesn't because the image description is in the post text itself), Mastodon's alt-text police is likely and fully justified to sanction me regardless.
So no matter how long and detailed and well-researched the long image description in the post is, I still have to distill an additional, shorter image description for the alt-text from it. And I have to do so without cutting too much information. Ideally, without cutting any information. If any of my images need a long description in the post, they need two descriptions, the long one in the post, the shorter one in the alt-text.
Leaving the several dozen individual text transcripts out of the description for the alt-text is risky already because text transcripts belong into the alt-text.
# # # # # # # # # # # # # # # # # # # # # # # # # #When I describe my images, I do so under a few assumptions.
One: My audience is not limited to my following contacts. It's absolutely everyone who comes across any of my posts.
It isn't sufficient to make my posts accessible to those who have chosen to follow me. I must make them just as accessible to a random stranger who receives them after they've been boosted a dozen times over. I must make them just as accessible to a random stranger who stumbles upon them on the public timeline of whatever server they're on.
Two: If an element in an image is mentioned, it must also be described visually.
Blind or visually-impaired people always need to know what something in my images looks like. This goes doubly for my typical original images I mean, how are they supposed to know what something looks like in a specific 3-D virtual world
So if there's a building in one of my images, and I mention that this building is there, I also have to give a visual description of it. A full, detailed description.
If there's an image in one of my images, e.g. a preview image on a teleporter that shows the place where the teleporter would take me, I have to fully describe that image. An image in my image that doesn't even take up 200 pixels in my image. (Something that I've refused to do in my longest image description so far because that would have led me to going at least four levels deep: describing loads of infinitely small images in several dozen infinitely small images in an image in my image.)
In fact, this isn't an assumption. I have written confirmation for it. I can't find it right now, otherwise I'd share it here, but I have it somewhere.
Three: Image descriptions must always deliver all information that someone may need right away.
Not everyone wants to ask for a description of a certain detail in an image. Not everyone wants to ask for an explanation of what they don't understand or what they're unfamiliar with. Having to look things up yourself isn't much better. Some may go as far as likening not having an image description that contains everything they need to know to not having any image description.
By the way: It's a fact that some Mastodon users consider linking to external information ableist because linked websites aren't necessarily sufficiently accessible themselves. Instead of linking to information, the information must go into the post itself. (And I can't even use any character limit as an excuse not to do that because my "limit" is over 16.7 million.)
In other words, the only way for me not to be ableist is to give any and all information that anyone out there may require in my image post immediately.
Of course, this will clash with the demand by other Mastodon users (or maybe even some of the same) to never post more than 500 characters at once. But I can't do both. And I've never read anywhere that posting more than 500 characters is allegedly ableist.
Four: Someone somewhere out there may be interested in even small details in my image. And they may not be sighted.
Maybe you aren't. But someone somewhere out there may be. And they matter every bit as much as you or everyone else.
If they need a full description of all details, regardless of why, I have to deliver it. Immediately. See above.
Five: Any and all text within the borders of the image must be transcribed verbatim, no exception.
Most importantly, this even extends to text that's unreadable in the image if I can read and/or source it.
The assumptions further up apply here as well: If I mention it (the text in this case, and be it as part of the visual description of something else like a teleporter), then I must describe (as in transcribe) it. And someone somewhere out there may be interested in it.
If this means that I have to transcribe not one or two, but 20, 30, 40 bits of text in one image, then so be it, so are the rules.
Just because nobody on Mastodon does it, doesn't mean they're doing it right, and I'm doing it wrong. Maybe they don't know what that unreadable text says. Maybe they don't know that someone wants to know what's written there.
Six: All images must have an accurate and sufficiently detailed proper alt-text.
I can spend two days, morning to evening, working on an image description of 60,000 characters. 10,000 words. Three hours worth of reading. I can put the whole thing into the same post as the image. As in the post text body. As opposed to the alt-text for which this description is way too long.
But if the image in the post doesn't have an actual alt-text (and, again, it doesn't because the image description is in the post text itself), Mastodon's alt-text police is likely and fully justified to sanction me regardless.
So no matter how long and detailed and well-researched the long image description in the post is, I still have to distill an additional, shorter image description for the alt-text from it. And I have to do so without cutting too much information. Ideally, without cutting any information. If any of my images need a long description in the post, they need two descriptions, the long one in the post, the shorter one in the alt-text.
Leaving the several dozen individual text transcripts out of the description for the alt-text is risky already because text transcripts belong into the alt-text.
# # # # # # # # # # # # # # # # # # # # # # # # # #So OpenSimFest 2025 has started. But there hasn't been any announcement whatsoever, at least not recently. Even the official OpenSimFest website is dead as OpenSimFest is ongoing. OpenSimFest will span 16 days, but you only learn that in-world, too.
The grid is down to one normal expo sim the other "expo" sim is the home of the fenced-in zombie zone now. It's a far cry from 2022 and 2023 with their many expo sims, also because several very prolific exhibitors haven't been at OpenSimFest since 2023.
Also, the grid seems to have become painfully slow. It isn't laggy, there's no rubber-banding. But things rez rather slowly. Anything below the lowest mesh LOD only shows when I'm close and even then sometimes only after one or two minutes. Some objects take that long to appear in the first place. I've got my doubts that the recent Firestorm beta is to blame.
At least there are more exhibits on that one expo sim. Last year, OpenSim World's Fair in the Wolf Territories hogged so many resources that about half of the few remaining expo parcels at OSFest remained vacant and had to be used as impromptu Arcadia Asylum showcases upon short notice so that there was at least something on the land. Now we have things like a tiny Venice exhibit built by Cooper Swizzle, complete with a keyframed gondola ride.
Speaking of Kitely, Kimm Starr has brought back the fairground freak show that had to be removed when Coopersville was shrunk prior to being passed to its new owner. (By the way, Coopersville is not named after Cooper Swizzle. That's coincidence.)
Surprisingly little is still a work in progress on the first day. Then again, the sole expo sim is entirely in use.
After last year's break, Remmy Ravenhurst is back with her products, including an assortment of freebies. She even brought something new, namely free boxes with textures from which PBR materials can be made and free boxes with untextured mesh models. Since they are full-perm, it's possible to export the roughness texture and convert it into a specular texture for Blinn-Phong.
In general, the usage of the two Stores sims has improved, and that isn't only because the northern one of the two Stores sims is down to only two big stores. Still, as usual, there isn't a single freebie store all stores offer payware either mostly or only.
What still makes me wonder are the clothes that are being sold, often for prices that appear to be converted from Linden dollars to Gloebits 1:1, regardless of the Gloebit being more expensive than the Linden dollar.
There are boxes with classic layer and prim clothes that must be well over a decade old, and yet, in real-life currency, they cost more than a comparable fitted mesh outfit with PBR materials and Blinn-Phong fallback textures costs in Second Life. Then there are boxes with mesh clothes that are rigged for mesh bodies of which not a single one is officially being sold in OpenSim. So in order to be able to wear these legally bought clothes, you need a pirated mesh body.
Interestingly, the grid was not reset since last year. I'm still a member of the OSFest Participant group.
# # # # # # # # # # # #So OpenSimFest 2025 has started. But there hasn't been any announcement whatsoever, at least not recently. Even the official OpenSimFest website is dead as OpenSimFest is ongoing. OpenSimFest will span 16 days, but you only learn that in-world, too.
The grid is down to one normal expo sim the other "expo" sim is the home of the fenced-in zombie zone now. It's a far cry from 2022 and 2023 with their many expo sims, also because several very prolific exhibitors haven't been at OpenSimFest since 2023.
Also, the grid seems to have become painfully slow. It isn't laggy, there's no rubber-banding. But things rez rather slowly. Anything below the lowest mesh LOD only shows when I'm close and even then sometimes only after one or two minutes. Some objects take that long to appear in the first place. I've got my doubts that the recent Firestorm beta is to blame.
At least there are more exhibits on that one expo sim. Last year, OpenSim World's Fair in the Wolf Territories hogged so many resources that about half of the few remaining expo parcels at OSFest remained vacant and had to be used as impromptu Arcadia Asylum showcases upon short notice so that there was at least something on the land. Now we have things like a tiny Venice exhibit built by Cooper Swizzle, complete with a keyframed gondola ride.
Speaking of Kitely, Kimm Starr has brought back the fairground freak show that had to be removed when Coopersville was shrunk prior to being passed to its new owner. (By the way, Coopersville is not named after Cooper Swizzle. That's coincidence.)
Surprisingly little is still a work in progress on the first day. Then again, the sole expo sim is entirely in use.
After last year's break, Remmy Ravenhurst is back with her products, including an assortment of freebies. She even brought something new, namely free boxes with textures from which PBR materials can be made and free boxes with untextured mesh models. Since they are full-perm, it's possible to export the roughness texture and convert it into a specular texture for Blinn-Phong.
In general, the usage of the two Stores sims has improved, and that isn't only because the northern one of the two Stores sims is down to only two big stores. Still, as usual, there isn't a single freebie store all stores offer payware either mostly or only.
What still makes me wonder are the clothes that are being sold, often for prices that appear to be converted from Linden dollars to Gloebits 1:1, regardless of the Gloebit being more expensive than the Linden dollar.
There are boxes with classic layer and prim clothes that must be well over a decade old, and yet, in real-life currency, they cost more than a comparable fitted mesh outfit with PBR materials and Blinn-Phong fallback textures costs in Second Life. Then there are boxes with mesh clothes that are rigged for mesh bodies of which not a single one is officially being sold in OpenSim. So in order to be able to wear these legally bought clothes, you need a pirated mesh body.
Interestingly, the grid was not reset since last year. I'm still a member of the OSFest Participant group.
# # # # # # # # # # # # That's probably because "followers only" is not a Fediverse-wide standard backed by the ActivityPub spec or a FEP, nor does it tie in with any actual permissions systems available in the Fediverse.
As an example for the latter, Hubzilla, (streams) and Forte do not translate Mastodon's "followers only" into "these Fediverse actors are granted permission to view, like/dislike and reply to this message indefinitely, and everyone else isn't".
On top of that, all three assume that the permissions of all elements in a conversation are always the same because that's how they work. So if I post in public, and one of my Mastodon followers comments "followers only", then Hubzilla will treat it as public regardless because if my post is public, and it is, then all comments and replies are public, too.
At least Hubzilla shows a red padlock symbol on each message whose "permissions" don't align with what Hubzilla understands or expects.
CC:
# # # # # # # # # # # # # # #
Also learning how to write effective alt text. It does take skill, time, and intention.
I'm occasionally working on . It's still a very early WIP, also because it's highly ambitious. It might have its readers write very long and detailed image descriptions once it's "done". And it will not include step-by-step how-tos for alt-texts on certain frontends (e.g. I will not walk you through adding an alt-text to an image on Mastodon's Web interface or on Mona or IceCubes or Tusky). But what I have right now is a start.
CC:
# # # # # # # # # # # # # # # Add your location to a Google Map
Das Fediverse wird immer mehr zu Facebook und ich hab da wenig Lust drauf.
Das Fediverse war Facebook, bevor es von Millionen von ahnungslosen Mastodon-Newbies zu Twitter gemacht wurde.
Mehr als die Hlfte der Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Der weit berwiegende Teil derer, die eines Besseren belehrt wurden, glauben immer noch, das Fediverse sei
- (frhestens) 2016
- von Eugen Rochko
- als reine Microblogging-Plattform und Twitter-Klon
- mit einem Zeichenlimit von 500 Zeichen
Um das mal zurechtzurcken:
Im Januar 2016 ging Mastodon an den Start.
Im Juli 2010, fnfeinhalb Jahre vor Mastodon, startete Friendica (, ) als Facebook-Alternative.
- Ohne Zeichenbegrenzung (tatschlich 16.777.215 Zeichen).
- Mit allem, was eine gute Bloggingplattform an Textformatierung hergibt.
- Mit Inhaltswarnungen, die jeder fr sich selbst automatisch generieren lassen kann mittels einer Liste von Schlsselwrtern.
- Mit Titeln und Zusammenfassungen, und die Zusammenfassungen waren schon immer in dem Datenfeld, das Mastodon seit 2017 fr CWs verwendet.
- Mit der Fhigkeit, andere Posts als Komplettzitate zu teilen. Und nicht ein einziges Mal ist das mibruchlich verwendet worden.
Jetzt regen sich Mastodon-Nutzer darber auf, da Friendica auf so infame und rcksichtslose Art und Weise ins Mastodon-Fediverse eingedrungen ist und seine Nutzer
- sich nicht ans 500-Zeichen-Limit halten
- alle mit ihren Textformatierungen nerven
- keine CWs schreiben
- dafr das CW-Feld mibrauchen mit "Titeln oder was wei ich, was das ist"
Fakt ist aber: Friendica gab es nicht nur schon fnfeinhalb Jahre, als Mastodon startete, sondern es war auch schon fnfeinhalb Jahre im Fediverse, als Mastodon startete. Und es hatte auch schon gut fnf Jahre lang seine eigene Kultur, als Mastodon startete.
In dem Augenblick, wo Mastodon startete, verband es sich sofort mit StatusNet (von 2008, wofr Mastodon ursprnglich nur eine Alternativoberflche war heute GNU social, , ), Friendica und Hubzilla (von 2015, basiert auf einem Fork eines Forks von Friendica von 2012 , ). Und nicht umgekehrt.
Wir waren zuerst hier. Findet euch damit ab.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # The danger in this, however, is that another Fediverse feature that's way older than Mastodon and at the same time absent from Mastodon would be reappropriated as something else, making Mastodon even more incompatible with the rest of the Fediverse.
In 2017, Mastodon introduced its content warning field. Ever since, almost everyone on Mastodon has been fully convinced that Eugen Rochko had invented that field from scratch. (Be honest, how about you)
However, Mastodon's content warning field is actually a summary field that has been used by StatusNet, Friendica and Hubzilla as such since 2008, 2010 and 2012 respectively. Mastodon hadn't had any support for that summary field at first, for you don't need a summary for 500 characters. And I guess that coder from the demo scene who submitted the merge request that reappropriated the summary field as a content warning field was blissfully unaware that Mastodon was actually connected to something that did use the summary field as such.
And now you have Mastodon users scolding Friendica users because the latter allegedly misuse the CW field for "like a subject or smth idk", unaware that the self-same field has been the abstract field on Friendica for five and a half years longer than Mastodon has even existed and some seven years longer than Mastodon had its CW field.
Today, in 2025, next to nobody on Mastodon knows that the Fediverse already has group actors, and probably neither do many on the *keys. Neither Mastodon nor Misskey nor their respective forks have or support groups in any way.
If they go and reappropriate group actors as starter packs, this will break compatibility with Friendica groups, Hubzilla forums, (streams) groups, Forte groups, Lemmy communities, /kbin magazines, Mbin magazines, PieFed communities, NodeBB forums etc., all of which can be and often already are being followed by Mastodon and *key users right now. And again, they've all had group actors since their respective inception.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Both have their use.
On the one hand, unless you're on a Mastodon server with a very low character limit, the post gives you much more room for a detailed description. A description in the post text is easier to navigate with a screen reader: It can jump back a few words or a sentence or so whereas, when reading out an alt-text, it can only jump back to the beginning of the alt-text. And if you have to explain the image or its description, something that keeps happening to me again and again, .
On the other hand, if you want to be safe from the wrath of Mastodon's alt-text police, you must add an accurate and sufficiently detailed alt-text to every last one of your images, regardless of image descriptions in the post itself.
Whenever I post an original image, I always describe it twice, both in the alt-text and in the post text. The description in the alt-text never contains any explanations, and it often doesn't contain any text transcripts either if there is too much text to transcribe. The description in the post always contains both (transcripts only if there's any text within the borders of the image).
When I post a meme, I only describe the visuals and transcribe the text bits in the alt-text. The post still contains all explanations, partially as external links if possible.
# # # # # # # # # # # # # # #
Police dog falls into geothermal water: Teo recovering after receiving burns in search
Johannsen, who suffered minor burns in pulling Teo out, has stayed by her side at the hospital. Police
Diejenigen, die verneinen, da das Fediverse durch Mastodon zum Minenfeld geworden sind, sind allesamt selbst auf Mastodon und haben zum Brechen der Hlfte der Regeln berhaupt nicht die technischen Mittel. Deswegen bekommen sie von all dem auch nichts mit.
Der Rest des Fediverse mu sehr, sehr vorsichtig handeln, um nicht massiv an Reichweite zu verlieren. Ich bin wahrscheinlich trotzdem schon massenhaft geblockt worden und vielleicht auch der Grund, warum eine Mastodon-Instanz die Netzgemeinde komplett blockiert hat.
Ich frage mich, wie man auf Mastodon wohl reagieren wrde, wenn man wte, da Hubzilla ein, Forte zwei und (streams) drei verschiedene Mittel hat, um Mastodon komplett auszusperren, also alle existierenden und alle zuknftigen Server. Aber schon Hubzilla kennt da ja keine Sau, und (streams) und Forte sind, wenn berhaupt, ihrerseits sonst beinahe nur Hubzilla-Nutzern bekannt.
# # # # # # # # # # # # # # # # # # # # Thanks, that's the confirmation I needed that it isn't sufficient to mention what's in an image, but that I always have to give a sufficiently detailed description of what it looks like.
As I usually post images from virtual worlds, the threshold for "sufficiently detailed" is extremely high, though, because nobody has even only got a rough idea what anything in my images looks like.
One more reason for me to avoid having buildings in my images like the plague.
Also, this renders all of my existing image descriptions even more obsolete. I recall plants like mountain pines, a potted Jacaranda tree, a potted Bougainvillea, a maple tree, a potted banana tree etc. that hardly got more than their names dropped.
Lastly, several blind people have told me after I've asked that I don't have to give an exact visual description of a full brogue shoe or a herringbone fabric pattern. But reading this, I may question their advice again because I can't assume that everyone is familiar with these things.
# # # # # # # #
das Trgerische ist doch, dass -19 sehr mild verlaufen kann. Und deshalb wird es als harmlos abgetan. Aber -Covid hat inzwischen kaum noch jemand auf dem Schirm.
I myself don't actually need screenshots I can quote-post just about anything. It's purely theoretical.I tend to explain things at such a level of detail that nobody in the Fediverse will have to go look anything up themselves or ask me anything. From outside, especially Mastodon looks to me like that's what I'm expected to do.
So , I used well over 3,000 characters alone to explain Hubzilla (which, by the way, I'm normally daily-driving, so I know it very well). And the post wasn't even about Hubzilla I just needed to explain Hubzilla to be able to explain the streams repository and the concept of nomadic identity in order to be able to explain the post itself.
The last time I've described a UI .
# # # # # # # # # # # #
Last updated: 2025-10-28
All text and images © eLoc8.is-fabulous.com