Find the latitude of any place.  

Police dog falls into geothermal water:

Ihr paar Friendica-Heinzeln seid wirklich komplett irrelevant.

Noch arroganter zeigen, da das Fediverse nur besteht aus
besteht, kannst du gar nicht mehr, als vorstzlich zu miachten, was ich schreibe.
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
Alles schon erlebt.
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:
# # # # # # # # # # # # # # #
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
erfunden worden. Und alles, was davon abweicht und nicht "offensichtlich (wie PeerTube & Co.) als Extra an Mastodon drangeklebt" worden ist, wird aufgefat als lstige Eindringlinge im Mastodon-Fediverse, die sich nicht an die Regeln des Mastodon-Fediverse halten und sich auch nicht an die Kultur des Mastodon-Fediverse anpassen.
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
Da Friendica schon seit ber 15 Jahren quote-posten kann, wei zum Glck beinahe niemand auf Mastodon.
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.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Long 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

Es reicht doch schon vllig, sich nicht exakt an die Mastodon-Kultur und die Mastodon-Regeln zu halten.
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 .
# # # # # # # # # # # # Theoretical but honest question: Let's suppose a screenshot is from the Web interface of a more obscure Fediverse server application, one that isn't Mastodon.
Is it sufficient to mention its name
Is a link to the official website (or, if there is none, the code repository) the minimum requirement If so, can it be an embedded link (""), or must it be a link with the URL in plain sight ("Hubzilla ()")
Or are links bad per se, but an explanation is still necessary, so a full explanation what kind of place is shown in the screenshot must go into the post itself
I'm asking because I always try to supply explanations for the non-Mastodon parts of the Fediverse whenever I post Fediverse-related memes. That way, even those who don't know anything in the Fediverse other than Mastodon still have a chance to understand them without having to ask.
Also, if it isn't Mastodon and thus unfamiliar enough, is a visual description of the UI necessary
# # # # # # # # # # # #

Evening Calm at Jokulsarlon by Vagelis Pikoulas

#24105 #2025

Kampagnen auch nicht-kommerzielle sind im Fediverse schwierig.

Sagen wir mal so: Sie sind auf Mastodon schwierig. Woanders, wo es a) ein vernnftiges Konversationsmodell und b) Gruppen gibt, wren sie einfacher.
Nur macht Mastodon immer noch um die 60% des Fediverse aus und geschtzt 80-90% des deutschsprachigen Fediverse. Der Postverkehr auf Mastodon selbst wirkt sogar wie zu 95-99% von Mastodon. Und der berwiegende Teil der Mastodon-Nutzer wei fast oder tatschlich gar nichts vom Fediverse jenseits von Mastodon.
# # # # # # # # # # # # # # Sascha Lobo ist ein Sonderfall.
Er hatte einfach eine zu groe Zielgruppenberschneidung mit dem Fediverse. Als Musk Twitter bernommen hat, ist seine effektive Followerzahl schlagartig eingebrochen.
Ein kluger Mensch htte dann Twitter und das Fediverse bespielt und so a) die abgewanderten Follower wiedergewonnen und b) noch mehr Follower gewonnen, die bis dahin gar nicht auf Twitter waren.
Sascha Lobo hat statt dessen ber das Fediverse gemotzt, um seine von Twitter nach Mastodon abgewanderten Follower alle dazu zu bringen, wieder in Vollzeit nach Twitter zurckzukehren und wieder schn seine speichelleckenden Claqueure zu werden.
# # # # # # # # # # This is actually correct.
Alt-text must never include explanations, author credits, license information or other additional information that is not available in the post text or the image!
Why
Because not everyone can access alt-text. Sighted people need a mouse/trackball/touchpad/trackpoint to access alt-text or a touch screen if the UI allows for that.
And in order to operate that, they need at least one working hand. But not everyone has working hands. Just like not everyone has working eyes, which is why you describe your images in the first place, right
For those who can't access alt-text, any information only available in alt-text and neither in the post text nor in the image itself is inaccessible and permanently lost. They can't open it, they can't read it. Ever.
This means: Explanations and additional information must always go into the post itself where everyone can access them!
Here are three relevant pages in my (very early WIP) wiki about image descriptions and alt-text:

# # # # # # # # # #

Nobel Prize Hails Firm-Level Innovation As Key To Economic Growth

(LtoR) Chairman of the comittee for the Nobel Economics Prize Per Stromberg, Secretary General Royal Swedish Academy Goran
-termprofits -termprofits

Alt-Text your images for:

- clarity and explication

Alt-text must never include explanations or other additional information that is not available in the post text or the image!
Why
Because not everyone can access alt-text. Sighted people need a mouse/trackball/touchpad/trackpoint to access alt-text or a touch screen if the UI allows for that.
And in order to operate that, they need at least one working hand. But not everyone has working hands. Just like not everyone has working eyes, which is why you describe your images in the first place, right
For those who can't access alt-text, any information only available in alt-text and neither in the post text nor in the image itself is inaccessible and permanently lost. They can't open it, they can't read it. Ever.
This means: Explanations and additional information must always go into the post itself where everyone can access them!
Here are three relevant pages in my (very early WIP) wiki about image descriptions and alt-text:

# # # # # # # # # # I guess nobody on Mastodon except you will ever read this due to how Mastodon handles conversations (namely not at all), but:
Alt-text must never include explanations or other additional information that is not available in the post text or the image!
Why
Because not everyone can access alt-text. Sighted people need a mouse/trackball/touchpad/trackpoint to access alt-text or a touch screen if the UI allows for that.
And in order to operate that, they need at least one working hand. But not everyone has working hands. Just like not everyone has working eyes, which is why you describe your images in the first place, right
For those who can't access alt-text, any information only available in alt-text and neither in the post text nor in the image itself is inaccessible and permanently lost. They can't open it, they can't read it. Ever.
This means: Explanations and additional information must always go into the post itself where everyone can access them!
Here are three relevant pages in my (very early WIP) wiki about image descriptions and alt-text:

# # # # # # # # # # # # # #

Fukushimas Fabulous Unique Pagoda! Fukushimas Fabulous Unique Pagoda! Here comes Katie. I love just yoloing things and then finding like this. In this episode, we find a mys

Added to my image description wiki right now for people like you:
Money quote in case you can't be bothered to open the link (or in case you don't even know it's a link because it isn't a URL in plain sight):
That's the same as refusing to add a wheelchair ramp to stairs as a store owner and instead demanding all wheelchair manufacturers build all their wheelchairs in such a way that they can roll up and down stairs. Where I come from, this is not only called "selfish", but also "ableist". This is every bit as bad as not describing your images at all and demanding all Fediverse software include some AI that automatically describes images.

CC:
# # # # # # # # # # # # # # #
I would also be in favor of Fediblock for instances where this behavior is rampant.

Alt-text on images is only a thing on Mastodon and amongst Pixelfed users who are also on Mastodon.
Fediblocking entire servers for a too low quota of sufficiently accurate, sufficiently detailed, rule-conforming alt-text would end up defederating Mastodon from most of the rest of the Fediverse. It would end up in the Fediblocking of entire Fediverse server application types. Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, CherryPick, Sharkey, Catodon, Smithereen, snac, GoToSocial, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte, Lemmy, /kbin, Mbin, PieFed, nodeBB, WordPress, Ghost, Flipboard, Plume and a whole lot of others would end up being defederated from Mastodon in their entirety because they don't have alt-text (and everyone upping their game in alt-text style, accuracy and level of detail) as an integral part of their culture.
Basically, from Mastodon's point of view, the Fediverse would end up actually being only Mastodon because Mastodon would have defederated with everything else, server by server.
I think I'm the only one on Hubzilla who actually describes their images. I'm definitely the only one amongst the few dozen (streams) users who does. But even if I put more time and effort into describing images than just about anyone else in the Fediverse, I think that wouldn't be enough to save either server application from being defederated from Mastodon in their entirety as long as not everyone else adds sufficiently accurate, sufficiently detailed, rule-conforming alt-texts to every last one of their images, as cumbersome as that may be on Hubzilla.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #

:
Oh my gosh: THEY BOUGHT IT BACK!

My favorite bought back the latex I asked them about...

This really is a stunning piece, as there are rarely made out of latex on the market.

And yes it does have (abeit flat) steel bones...

The end of Windows 10 is near. What should you do

At the time of posting this article, Theres less than a week left for the official Windows 10 support, and we have to explore options to keep using our computers that wont be able to upgrade to the relatively new version of the operating system, or options to use it with the least issues possible, as long as Windows updates keep working correctly.

...

Ich glaube, viel verpat man da nicht.
hat sich Bonfire mal angeguckt. Die Posts und Konversationen dazu sind interessant:

Um es vorsichtig auszudrcken: Begeistert war er vorher schon nicht und hinterher noch weniger.
Nun mu man allerdings sagen: Wenn jemand von Mastodon kommt und im Fediverse kaum etwas anderes als Mastodon kennt, dann erscheint Bonfire als die absolute, ultimative eierlegende Wollmilchsau, als das Schweizer Taschenmesser des Fediverse, als der unbertreffliche Allesknner. Zumindest gem der offiziellen Hochglanz-Website. Da lt man sich dann leicht blenden, weil man noch nichts auch nur ansatzweise Vergleichbares jemals gesehen hat.
Ganz anders sieht das aber aus, wenn man als Daily Driver verwendet, und zwar schon sehr viel lnger daily-drivet, als 95% der Mastodon-Nutzer auf Mastodon sind.
Pepe daily-drivet Hubzilla schon ungefhr so lange, wie es Mastodon berhaupt gibt, also noch lnger als ich und im Gegensatz zu mir durchgngig. Er hat zwei eigene ffentliche Hubs, und den (und nebenher Europas einzigen ffentlichen -Server, ). Er reizt Hubzilla fast bis zum Gehtnichtmehr aus. und betreibt zustzlich die . Und er ist Teil der Speerspitze der deutschsprachigen Hubzilla-Szene und kmmert sich mit um den monatlichen Hubzilla-Workshop. Er wei also, wovon er schreibt.
Noch sehr viel anders sieht es aus, wenn man mit diesem Hintergrund Bonfire auch tatschlich ausprobiert. Das hat Pepe auch getan. Fazit siehe Links.
Um mich mal selbst zu quote-posten:
Ich sag's ja: Bonfire ist Hubzilla bei Wish bestellt. Und Solid auch.
# # # # # # # # #
Der Witz ist: Bonfire hat eine ganze Menge Publicity, wirbt mit Wahnsinnsfeatures und zieht dabei besonders bei Mastodon-Nutzern. Tatschlich funktioniert es in der Praxis kaum richtig. Und so ziemlich alles, was Bonfire angeblich knnen soll, kann Hubzilla tatschlich, und zwar meistens schon seit etwa zehn Jahren, also lnger, als es auch nur Mastodon gibt. Und noch mehr oben drauf.
Wer sich auf Bonfire einlt, verplempert nur seine Zeit. Zeit, die meines Erachtens besser darin investiert ist, sich mit etwas anzufreunden, das auch wirklich funktioniert.
# # # # # # # # # # # #

Why Japans mom-and-pop investors are stepping back into the market

Efforts to encourage investing in Japan, where many have long kept a big chunk of their wealth in deposit accounts, have been slow to take root. But a revamped government program has l
-termassets

Nuclear Energy Agency (NEA) Operating experience in focus during CODAP meeting

Technical visit to the Energy Transformation Research Laboratory of the Central Research Institute of Electric Power Industry (CRIEPI)
-termoperation

Exactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.

Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
# # # # # # # # # # # # # If technology was a solution against racism in the Fediverse, we'd now have a huge Black community on or , empowered to defend itself against racism, harassment and dogpiling with technological countermeasures that are light years away from Mastodon and unimaginable from a Mastodon point of view.
Alas, there is none. Not because nobody knows what Hubzilla can do, nobody knows that (streams) exists, and/or there is no native mobile app for either. But because the BIPoC in the Fediverse want racism in the Fediverse to disappear entirely.
They don't want new weapons to fight racism. They don't want strongholds to protect themselves against racism. Neither do they want to retreat into an existing stronghold, nor do they want a stronghold to be built around them. They want racism to simply no longer be there. The only feasible solution. Unrealistic, unfortunately, but without any good alternative.
CC:
# # # # # # # # # # # # # # #
Do you mean ActivityPub That seems culturally opposed to search.

The general ActivityPub community isn't.
Large parts of the Mastodon community are. But a whole lot of things in the Fediverse that aren't Mastodon have had full-text search since their respective inception, some even since before Mastodon was made. And their users are okay with that or even happy about it.
The Fediverse is much more than Mastodon and stuff bolted onto Mastodon as an extra feature.
CC:
# # # # # # # # # # # I hope this won't end up in a culture clash due to how big Misskey and other Forkeys are in East Asia (CherryPick almost only exists in Japan and South Korea) while Westerners tend to talk about the Fediverse and Mastodon as if they're one and the same.
Language has a chance of being an obstacle, too. If you want to get e.g. Japanese Forkey devs on board as well, chances are they don't speak English.
# # # # # # # # # # # # # #

L'glise, Long, Somme, c.1910 - Bigand CPA


Last updated: 2025-10-21