This is the lens I shot
Again, I'm NOT talking about the technological side. I'm NOT talking about how certain platforms are rendering alt-texts.
I'm talking about describing an image for one person whom I know vs describing an image for billions of people whom I don't know. That's a huge difference.
Let's suppose I've rendered a picture in a 3-D virtual world. A very obscure one. (Because that's what I normally do.) Chances are people won't get that image without explanations, simply because they don't know anything about these worlds.
If I want to describe that image to my friend Joe over a landline phone, I can ask Joe what he knows about virtual worlds, and whether he needs some explanations first.
If Joe says yes, he'd like some explanations, I can take a deep breath and explain away. If the explanations go too much in-depth, or if they become too big an info dump for him to handle, Joe can stop me while I'm explaining.
After explaining, I can ask Joe what I shall describe to him. Only what's important Everything because Joe is super-curious about these virtual worlds, and he wants to know all the details so he can imagine what that virtual world looks like
And Joe can answer. If Joe answers that he does not want a super-detailed description of everything, I don't have to give him a super-detailed description of everything. And if my description becomes too detailed, Joe can rein me in and tell me to stop.
If I want to describe that image when I post it in the Fediverse, it's very different.
The result: I have to deliver the maximum right away. I have to start with a whole lot of explanations because someone somewhere out there probably won't understand my image without these explanations. And then I have to continue with an extremely detailed visual description because someone somewhere out there may want or even require one. Regardless of what everyone else wants.
It's like describing an image to Joe over a landline phone, but I don't know Joe, I don't know what Joe wants or needs, I don't even know that it's Joe on the other end, there may be other people around Joe's phone who want to hear the description, too, and someone has cut off the microphone in Joe's phone first, only to re-activate it after I'm done describing the image three hours later.
# # # # # # # # # # # # # # #
Hashtags kann man meines Wissens "folgen", aber nicht wie auf Mastodon als eine Art Akteur und durch Klicken, sondern mit einem Feld in den Einstellungen, wo man Hashtags eintragen kann.
Alt-Text kann man weiterhin in den Bildeinbettungscode reinschreiben. Aber zum einen kann das jetzt neben BBcode auch Markdown/HTML sein, wenn einem das vertrauter ist. Zum anderen mu man das nicht mehr. Statt dessen kann man schon beim Hochladen eines Bildes in den Filespace einen Alt-Text eintragen oder auch hinterher in der Bilder-App. Und dann kann man dasselbe Bild mit demselben Alt-Text immer und immer wieder einbauen, ohne den Alt-Text mehr als einmal schreiben zu mssen. Das wiederum geht auf Mastodon nicht.
berhaupt ist da einiges eleganter gelst als auf Hubzilla. ActivityPub mu nicht mehr aktiviert werden. Die Rechteverwaltung ist jetzt auch deutlich einfacher zu handhaben, weil sie jetzt gebaut ist fr das reale Fediverse der 2020er und nicht mehr fr eine Vision eines Fediverse, das es Mitte der 2010er geben sollte, das so aber nie kam.
diaspora* knnen beide nicht mehr. Der Aufwand, noch ein weiteres nichtnomadisches Protokoll mitzuschleppen und Zot ab Version 6 darauf auszulegen, hat sich wahrscheinlich nicht mehr gelohnt. (streams) basiert weiterhin auf Nomad, wie Zot jetzt heit, aber ActivityPub ist so gut integriert, da es Teil des Kerns geworden ist und standardmig aktiviert. Und Forte erschlgt alles mit ActivityPub und kennt gar kein anderes Protokoll mehr.
# # # # # # # # # # # # # # If you really want some criticism:
Alt-text really should not contain line breaks, nor should it contain the quotations marks on your keyboard. Neither are standard alt-text elements. And just because Mastodon renders them with no problems, doesn't mean everything does. Not even in the Fediverse.
As for line breaks: Some screen readers will take each new line for a whole new alt-text and therefore a whole new image. And they will read multi-line alt-texts as alt-texts of multiple images, e.g. starting each line with, "Graphic."
As for quotation marks: For one, just like line breaks, they're actually completely useless for the actual target audience of alt-text, namely blind or visually-impaired people. Screen readers don't read out quotation marks. I mean, how should they
But if a frontend doesn't render quotation marks properly, screen readers will read out gobbledygook where there's a quotation mark because they will see gobbledygook in the place of that quotation mark, because the frontend renders quotation marks as gobbledygook.
For example, there's Hubzilla which is what I'm posting from right now, so it's very much part of the Fediverse. Hubzilla renders quotation marks in alt-text as their HTML entities, namely
And then there are two descendants of Hubzilla made by Hubzilla's own creator, (streams) and Forte. The same quotation marks that you have on whatever keyboard you use, they use as alt-text delimiters. When the first quotation mark comes, they think it's the end of the alt-text, and they stop parsing and rendering the alt-text. For them, your alt-text ends right after, "Panel 1:"
# # # # # # # # # # # # # # # I'm not talking about the technical side.
That is, you may not have noticed, but I'm not posting from Mastodon. I'm on Hubzilla where things are quite a bit different. Images aren't file attachments they're embedded into posts in-line using BBcode markup like in classic bulletin board forums. Alt-text has no dedicated text entry box instead, it's manually woven into the image embedding code.
No, what I mean is that here in the Fediverse, you can't describe an image like describing it to a friend over the phone. Open the link in my post. (If it looks like it may be a link, it actually is one, even if it isn't a URL in plain sight. I can do embedded links on Hubzilla, too.)
Anyway, if you describe an image to a friend over a landline phone with no image transfer, your friend can talk back. Your friend can even talk back before you start describing. You can ask your friend what they need to know, what they want to know. You can do that beforehand. And then you can describe the image in exactly the way that your friend needs.
In the Fediverse, you describe your images for potentially millions of Fediverse users and billions of Internet users. You can't first go around and ask them all, every last one of them, what they need to know and what they want to know. You have to perfectly cater to everyone's needs without even knowing anyone's actual needs because you can't know everyone's needs.
Describing for one person over the phone is one-size-fits-one. It's tailor-made for one person. Describing in the Fediverse has to be one-size-fits-all at first try, right off the bat.
This may not matter if you post a simple real-life cat photo. But I post renderings from super-obscure 3-D virtual worlds. Nobody knows what anything in my images look like until they can either see the images themselves, or I describe everything in these images to them. So this matters a whole lot in my case.
# # # # # # # # # # # # # # # Only that "my best" has actually led to unimaginable extremes.
They say an image is worth a thousand words. I've once in over 10,000 words. Over 60,000 characters. The post is so long that, I think, Misskey and its various forks have rejected it, as have Pleroma and Akkoma. It took me two full days, morning to evening, to describe that one image, in-world research included.
And I actually had to limit myself. For once, I did not give in-depth descriptions of the images within that image, especially not beyond what's actually visible in these images. That's because I've discovered that if I were to do that, I'd have to describe dozens of images in one particular image (in my image) and potentially over a hundred images in these, even though they're so small that they're technically invisible. It would have taken me months to write all that. And it would have been futile anyway. My character limit is over 16 million, but Mastodon rejects posts over 100,000 characters, and in the few places that do accept posts with millions of characters, next to nobody cares about image descriptions.
I haven't posted a new in-world image in over half a year. I've been working on-and-off on the descriptions for a series of rather simple avatar portraits since last autumn.
# # # # # # # # # # # # # # # Of course, this means that the more obscure the content of your image is, the more in-depth you will have to go. At worst, there's nothing in your image of which non-sighted people know what it looks like unless you describe it. Simply mentioning that it's there is not sufficient.
My own original images aren't even photographs, nor are they pieces of art that represent real life. They're renderings from 3-D virtual worlds, very obscure 3-D virtual worlds even. Nobody knows what anything in these world looks like unless they can see it in my images. At the same time, however, chances are that they become so curious about these virtual worlds that they also become curious about everything in the image, not just what matters within the context of the post. That is, sometimes the image itself as a whole is the context. Either way, this means I can't just focus on certain elements in the image in my descriptions. I have to describe everything.
So I've gotten to a point at which even filling the alt-text character limit forced by Mastodon, Misskey and their respective forks (they cut longer alt-texts off at the 1,500-character mark) doesn't cut it. All my original images have two descriptions now. In addition to the one in the alt-text that's very limited, there is another one in the post that's more or less fully detailed, that contains transcripts of all text within the borders of the image, and that also comes with all explanations that I deem necessary. Since I don't have a character limit to worry about (the limit is defined by the database field rather than a hard-coded or configurable number), this description is likely to grow well over a hundred times longer than typical alt-text.
# # # # # # # # # # # # # # #
The alt-text is fine How about the long descriptions in the post itself
Again: I've described all these images twice. One description is in the alt-text. It's the short one with no text transcripts and no explanations (because explanations don't belong into alt-texts).
The other one is in the post itself, not in the alt-text. If you look at the post at the source, open the summary/content warning, and then scroll beyond the image(s). Right below, there are the long image descriptions.
Again: Would you say it's okay to describe one image in over 60,000 characters and over 10,000 words Would you say it's okay to spend two full days, morning to evening, describing one image and researching for the description Would you say it's okay for an image description to be so long that it has two levels of headlines Would you say it's okay to start a long image description with well over 5,000 characters of explanations before any visuals are described because these explanations are necessary to understand the image and the description Would you say it's okay to use over 3,000 characters to describe one single object in an image which even sighted people would have a hard time spotting without the description, and to transcribe the 14 individual bits of text on that object, even though they're so tiny in the image that they're basically invisible
After all, I myself think I've made lots of mistakes in that description.
# # # # # # # # # # # If you don't mind the learning curve (because it handles nothing like Twitter or Mastodon), maybe is something for you. It's the youngest member of a family of Fediverse server applications that started 15 years ago with a Facebook alternative that's now known as Friendica, and that also gave us Hubzilla and the streams repository.
It's written in PHP with a little side of JavaScript for post formatting, so no fumbling around with exotic dependencies. Administration is fairly easy, especially upgrading the whole thing for which there's a dedicated script. At the same time, it's both very powerful and very secure.
And it's probably the most technologically advanced Fediverse server software out there. After all, it's the first one to implement nomadic identity with nothing but ActivityPub.
# # # # # # # # #
I think we aren't thinking in the same dimensions.
How about
How about
In case you're on a phone: If the above looks like links, that's because it is links. The links lead to two of my image posts which, while not originally on Mastodon, are still in the Fediverse, and copies of both can actually be found on mastodon.social. The first one can be found under the hashtag # it's the third one (or fourth, counting this one) from the top. The second one can be found under the hashtag # it's the one at the bottom.
Oh, there's plenty of documentation on alt-text and image descriptions. For example:
Beware, though: They may contradict each other.
# # # # # # # # # # # # # # # So the more detailed it is, the better Would you say it's possible to describe an image in too many details, regardless of circumstances (e.g. what the expected audience may be curious about)
Also, what about the rule that any and all text within the borders of an image must be transcribed 100% verbatim There is text on the T-shirt, that's why I'm asking. I myself am someone who always transcribes every last bit of text within my original images. That said, the transcripts usually only go into the long description in the post itself (the character limit here is so high, it's fully negligible but my original images always get two descriptions each). Most of the time, there simply isn't enough room for them in the alt-text (or what of it Mastodon, Misskey and their respective forks let through at full length).
I'm also asking because I plan to write my own wiki on alt-texts and image descriptions specifically for the Fediverse. It will be a wiki because it will be too detailed for only one article or page.
# # # # # # # # # # # # # # #
Friendica was created by an American living in Australia, but it's maintained by two Germans. Hubzilla was created (actually forked) by the same guy, and now it's maintained by a German and a Norwegian.
Both are part of the Fediverse. Friendica connects to Mastodon and everything else in the Fediverse, and Hubzilla can optionally do that, too.
None of them is an all-out, 1:1 clone of Facebook, though. Instead, both are better than Facebook.
# # # # # # # # # # # #Author(s): riktoi
Title: Sandpaper
You wake up in a strange room...
Ist problemlos schon lange auch im Fediverse mglich, nur eben nicht auf Mastodon.
Friendica, Hubzilla, (streams) und Forte haben nicht nur Gruppen mit allen Schikanen, sondern auch private Gruppen. Das heit: Wer nicht in der Gruppe ist, kann die Threads in der Gruppe nicht sehen, kann das Profil der Gruppe nicht sehen, kann nicht sehen, wer alles in der Gruppe ist. Auf Hubzilla kann das sogar jeweils einzeln und unabhngig voneinander geschaltet werden.
Private Gruppen auf Hubzilla, (streams) und Forte untersttzen auch OpenWebAuth Magic Single Sign-On: Wenn du auf Friendica, Hubzilla, (streams) oder Forte bist, egal, auf welcher Instanz du bist, und du besuchst die Gruppe, wird dein Login automatisch erkannt. Wenn du Gruppenmitglied bist, kannst du das Profil, die Gruppenmitglieder und den Gruppen-Stream mit allen Threads sehen.
Zustzlich, also unabhngig davon, knnen solche Gruppen auch wahlweise in Verzeichnissen nicht angezeigt werden, damit sie nicht jeder findet.
Friendica-Gruppen knnen zustzliche Moderatoren auf demselben Friendica-Node haben. Hubzilla-Foren, (streams)-Gruppen und Forte-Gruppen knnen zustzliche Moderatoren irgendwo auf Hubzilla, (streams) oder Forte haben.
Gleichzeitig kannst du dein Friendica-Konto oder deinen Hubzilla-, (streams)- oder Forte-Kanal nutzen, um dich damit auch mit dem ganzen Rest des Fediverse zu verbinden, Mastodon, Misskey, Pixelfed, PeerTube, Castopod, Funkwhale, Lemmy, Mbin, PieFed usw. usf.
Aber: Wenn du einer privaten Friendica-Gruppe beitreten willst, brauchst du ein Friendica-Konto oder einen Hubzilla-, (streams)- oder Forte-Kanal. Wenn du einem privaten Hubzilla-Forum oder einer privaten (streams)- oder Forte-Gruppe beitreten willst brauchst du einen Hubzilla-, (streams)- oder Forte-Kanal. Mastodon kommt da jeweils nicht rein, weil es kein Konzept von Berechtigungen hat.
# # # # # # # # # # # # # # # # # # # #
This starts with Mastodon's timeline which still is a 1:1 clone of Twitter's feed. It only supports one mode: message-by-message piecemeal doomscrolling. It does not support listing entire threads instead of single messages. And while it does have notifications, it doesn't have an unread messages counter like Friendica, Hubzilla, (streams) and Forte which also allows you to directly jump to a thread with unread messages in it.
Result: Comments on threads drown in the deluge that's a Mastodon timeline, never to be seen, unless they mention you. And on Fediverse server applications with full-blown, native group support from the very beginning, they usually don't mention you.
Add to this the hundreds or thousands of Fediverse actors that typical Mastodon users follow, often also to catch as many messages about certain topics as possible because they don't know that Mastodon can follow hashtags, because Twitter never could. This alone leads to timelines that may consist of 5% interesting stuff and 95% cruft, but they still have to scroll through the cruft because lists are so inconvenient, having more than four lists more so (it's tempting to think that Mastodon was actually designed by a Watership Down rabbit that can't count beyond four).
Most Mastodon users never get to read nearly everything that comes rushing through their timelines. Maybe 20%, maybe 10%, maybe less. They simply don't have the time to scroll all the way down until they see messages that they already know, especially not if they've only got time to check Mastodon once a day or even only once every couple of days.
They won't even scroll far enough down to catch all comments on a thread. Well, and even if they do, there's nothing signalling to them which "toots" are part of the same thread, not even which "toots" are comments on which "toot".
A huge improvement would be if Mastodon a) implemented full support for one-post-many-comments threaded conversations, b) implemented threaded modes for the timeline (sorted by newest post, sorted by newest comment) which would then list entire threads instead of message-by-message piecemeal and c) made it the default for everyone because the vast majority of Mastodon users run their accounts on 100% default settings. Also, at least all the important mobile apps for Mastodon would have to do the same, all the way to making the sorted-by-newest-comment threaded timeline the default for everyone, because next to nobody ever users Mastodon via the Web interface.
Then we can talk about improving interaction with link aggregators or anything else that supports groups, e.g. titles being unavailable and largely unknown on Mastodon, but a hard requirement for new threads on Lemmy, /kbin, Mbin and PieFed, or Mastodon and the Threadiverse having mutually incompatible ways of handling images.
# # # # # # # # # # # # # # # # # # # # # # # # #
Ich rechne stndig damit, da Leute von der Mastodon HOA, Abteilung Alt-Text-Polizei, auch dann fehlenden Alt-Text sanktionieren, wenn das Bild im Post beschrieben ist, weil sie eisern die Regel durchsetzen wollen, da jedes Bild im Fediverse einen hinreichend detaillierten und akkuraten Alt-Text haben mu.
Ich selbst mu meine eigenen Bilder . Dazu kommen dann noch genug Erklrungen, damit wirklich jeder meine Bilderposts sofort versteht, egal, wie obskur das Thema auch sein mag. Und dazu kommen Transkripte von allem an Text im Bild. Ich brauche auch mal Stunden oder Tage, um ein einziges Bild zu beschreiben. Das Ergebnis ist eine Bildbeschreibung, die alle "normalen" Zeichenlimits im Fediverse um Grenordnungen bertrifft und auch deshalb direkt in den Post geht statt in den Alt-Text. (kein Problem hier, mein Zeichenlimit ist nicht 500, sondern ber 16 Millionen). Das ist anstrengend genug, da ich nicht alle paar Tage Bilder posten kann.
Da will ich nicht noch dafr angeschnauzt werden oder anderweitig auf den Deckel bekommen, da das Bild keinen Alt-Text hat.
Also schreibe ich immer zustzlich eine Bildbeschreibung fr den Alt-Text, wobei meine Alt-Texte auch regelmig bei exakt 1500 Zeichen oder einigen wenigen darunter liegen. Vorsicht ist die Mutter der Porzellankiste.
Das heit, Leute, die noch auf alten Mastodon-Versionen sind, wo Inhaltswarnungen die Bilder noch nicht verstecken, sehen eh erstmal nur das Bild, aber nicht den Post-Text, den ich wegen seiner berlnge (= ber 500 Zeichen) hinter einer Zusammenfassung und Inhaltswarnung verstecke. Das heit, die sehen die lange Bildbeschreibung gar nicht, also wissen sie nicht, da sie existiert.
Deswegen gibt's von mir im Alt-Text nicht nur eine Bildbeschreibung, die hoffentlich detailliert genug ist (auch wenn ich unmglich die ganzen Text-Transkripte mit darin unterbringen kann), sondern auch einen Hinweis auf die lange Bildbeschreibung, und wo sie zu finden ist.
# # # # # # # # # # # # # # # # # # #
Well, for me personally, whimsy in image descriptions falls under "no can do".
One single image regularly takes me multiple days, morning to evening, to research for the description and explanation, to describe and explain. I end up with a long image description that measures several tens of thousands of characters, and that goes directly into the post. At that point, I don't have the time and energy to edit whimsy into that monster description. Besides, whimsy clashes with the extensive explanations that are necessary for everyone to understand my image posts.
Furthermore, I also distill a shorter image description for the alt-text to satisfy the Mastodon Home Owners' Association that demands there be a sufficiently detailed and descriptive alt-text for each image even if there are well over 100 Mastodon toots worth of image description in the post itself. Nonetheless, my alt-texts end up either exactly 1,500 characters long or only a very few characters short of that. I simply don't have room for whimsy in my alt-texts. I could technically make them longer, but then Mastodon, Misskey and their respective forks would chop them off at the 1,500-character mark.
Not to mention that my original images never mean to convey emotions. Ever.
Oh, and I can't describe my images like to a friend over a landline phone either. That'd mean I'd describe my image to one person. In a situation that allows for dialogue. I could ask my friend beforehand what they want to know about the image and what they need to know about the topics touched by the image to understand the image. I'd have to ask that because my images always show extremely obscure niche content that the vast majority of Fediverse users knows exactly nothing about. After asking and receiving the answers I need, I could give a description tailor-made for that one friend. Also, that friend could always ask me about details while I'm describing.
In the Fediverse, I describe my images to potentially millions of Fediverse users and billions of Internet users. That's a situation that does not allow for dialogue. I can't possibly ask any of them what they want or what they need, much less every last one of them. I can't tailor my descriptions to their needs. Before I start describing, I know nothing about who wants and needs what. But when I'm done, everybody must know everything about the image and the topic of the image that they want or need to know. This means everyone must get the same massive info-dump because someone somewhere out there may want or need it.
I can't describe an image over the phone the same way. I can't start describing an image over the phone by first giving lengthy explanations between several minutes and about an hour before I start describing the visuals. But my long descriptions require just that if I want to cover everyone's needs and requirements all the same.
A pity I can't give any direct feedback. But then again, the author most likely knows nothing about Fediverse culture and how alt-text and image descriptions are even more deeply engrained there. And the author probably can't imagine either that it's possible to post in excess of 50,000 characters at once in social media.
# # # # # # # # # # # # # # # # #
Well I don't think I'm the ActivityPub inventress, though I certainly played a big role in its standardization and etc. The history of the name "ActivityPub" is one of those things that could be lost to time tho, so here's what happened, per my memory: - developed Pump.io's API experimenting towards a new, simpler, better design to replace OStatus called the "Pump.io API"
- sets up "ActivityPump" doc, converting Evan's api docs into more formal protocol format/language, using ActivityStreams2
- In the SocialWG, MicroPub was also being standardized there was hope the two specs would converge, and suggested we rename to ActivityPub, a big name upgrade anyway Ultimately the merge between MicroPub and ActivityPub didn't happen, but they did learn from each other, and ActivityPub did keep its improved name. The "Pump" language was awkward Pump.io had an infamously awkward (but I don't think intentional) tagline along the lines of "Pump.io pumps your life through your family and friends" or something else that made me think yes, actually dropping the name "pump" might be a good idea, and ActivityPub seemed good I'm not much of the ActivityPub inventress I did shape it a lot, and guided it through the process. Ultimately, ActivityPub's core design ideas came from , though really I think they really derive from the kind of design that comes out of actor model systems (even though AP deviates in various places from the actor model, it's best when it follows it)
# # # # # # # # # # # # # #
OpenCloud kommt dagegen direkt als ausfhrbare Binaries, die selbst keine groen Spezialabhngigkeiten brauchen.
Zum anderen: Nextcloud haut immer neue fest eingebaute Features raus, die vor allem Privatanwender gar nicht haben wollen. Vor allem KI wird jetzt allen aufgezwungen. Zumindest wird KI wohl mit neuen Versionen ausgerollt und dann auch auf bestehenden Servern standardmig aktiviert, wenn sie denn berhaupt abschaltbar ist. Bei den ganzen neuen Features bleiben aber dringend ntige Bugfixes auf der Strecke.
Ich glaube, wenn "das Metaversum" (nicht das, was wir zwei schon lange als Metaverse kennen) nicht offiziell fr tot erklrt worden wre, htte Nextcloud wahrscheinlich eine VR-Umgebung als alternative Bedienoberflche eingebaut und zwangsausgerollt, um auch wieder auf irgendeinen Hype aufzuspringen. Und wieder htten sie nicht statt dessen mehrere Jahre alte Bugs gefixt.
OpenCloud setzt eher auf Stabilitt und fixt Bugs, statt allen mglichen Klimbim einzubauen, der gerade der heie Schei ist, den aber keiner haben will.
CC:
# # # # # # # # # # Zivilklagen bringen gegen Konzerne schon lange nichts mehr. Strafanzeigen bringen auch nichts mehr.
Das einzig wirksame Mittel sind inzwischen internationale Haftbefehle gegen Vorstnde, die dann auch durchgesetzt werden. Und Przedenzflle, wo Vorstandsmitglieder oder gar Vorstandsvorsitzende anderer Konzerne in vergleichbaren Fllen tatschlich verhaftet und zu langen Haftstrafen verurteilt worden sind. Die Aussage mu sein: "Wir kriegen euch und bringen euch hinter Gitter. Wir haben schon ganz andere gekriegt, die glaubten, wir kriegen sie nicht, und euch kriegen wir auch noch."
Siehe Martin Winterkorn. Als gegen VW geklagt wurde: "Haha, damit kommen wir doch sowieso durch." Als Strafanzeige erstattet wurde: "Haha, damit komme ich doch sowieso durch." Dann aber hat die US-Justiz (der deutsche Michel ist da immer noch zu zahnlos) gegen ihn einen internationalen Haftbefehl erwirkt und das FBI auf ihn angesetzt. Das darf ihn zwar nicht auf deutschem Boden verhaften, aber sollte Winterkorn einen Fu auf US-Boden sitzen: Handschellen und effektiv lebenslnglich.
Andere Geschichte: Vor vielen Jahren haben drei Anwltinnen eine gemeinsame Kanzlei gegrndet und dafr einen DSL-Anschlu bestellt. Der wurde aber nicht termingerecht geschaltet. Auch auf Anfrage passierte nichts. Da haben die drei an die Telekom geschrieben, wenn nicht binnen ein paar Tagen der Anschlu geschaltet ist, werden sie gegen den damaligen Telekom-Vorstandsvorsitzenden Strafanzeige (wahrscheinlich wegen gewerbs- und bandenmigen Betrugs) erstatten und einen Haftbefehl gegen ihn erwirken. Noch einmal: Anwltinnen. Wahrscheinlich sogar in mindestens einem Fall mit Spezialgebiet Strafrecht. Nach zwei Tagen hatten sie ihren Anschlu.
Die DSGVO kann man in Deutschland nur so durchsetzen:
Das einzige Problem bei Unterlassungsaufforderungen ist, da vor allem in Deutschland die digitale Infrastruktur von der persnlichen Kommunikation (ich sage nur WhatsApp) ber Startups, ber Kleinunternehmen, ber den Mittelstand, ber Grokonzerne bis hin zur ffentlichen Verwaltung fast komplett abhngig ist von US-Gigakonzernen wie Microsoft, Alphabet, Amazon und Oracle. Traurig, aber wahr: Es sind praktisch nur sie, die die Technologie des 21. Jahrhunderts bereitstellen in einem Land, das selbst technologisch in den ersten zwei Legislaturperioden Helmut Kohls steckengeblieben ist.
# # # # # #
In the meantime, at least three quarters of the Fediverse's user base have never even heard of Hubzilla (there has been a poll, yes). But most Mastodon users only know of one Twitter alternative in the Fediverse as well, namely Mastodon, regardless of even only the uncountable Forkeys.
Reason #2: Hubzilla has the Eiger North Face of learning curves. I'm a Hubzilla veteran. Still, I think that even (streams) is user-friendlier, and (streams) is still harder to get into than Friendica which, in turn, is much harder to get into than Mastodon or some *key, especially when you've got "Twitter on the brain".
Even though I daily-drive Hubzilla, I normally only recommend it to those who really need its extra features. To those who want fail-safe Friendica or Friendica with even better permissions, I'd rather recommend Forte or, if they like the idea of being able to turn ActivityPub of as a last line of defence against the Mastodon HOA, (streams).
I think the new community-written help has yet to be officially adopted by Hubzilla, too. Hubzilla is one of the few Fediverse server applications with a built-in help system, but as of now, that help is not only hard to understand, but also hopelessly outdated, often simply factually wrong and very incomplete.
Reason #3: Friendica's UI has actually evolved over the years. In the meantime, Hubzilla's only official theme hasn't changed much since 2012. The name "Redbasic" says it all: It was the basic theme in the early days when Hubzilla was still named Red. And back in the day, Friendica's standard theme which it was derived from wasn't exactly pretty either.
The development of third-party Hubzilla themes hasn't really picked up speed until not even a year ago. I mean, we have some now, but especially the big hubs only offer you Redbasic. (Still I wish (streams) and Forte upgraded Redbasic to version 2.2 and maybe also Bootstrap icons.)
Speaking of third-party themes: BookFace. A theme to make Facebook refugees feel at home. Exclusive to Friendica.
Reason #4: Friendica has at least got native third-party Android apps plus a third-party iOS app in very incomplete development. All that Hubzilla has is Nomad, a glorified specialised Web browser that's about 10% native and 90% Web interface, that's only available on F-Droid and not in the Google Play Store, that has last been maintained in December, 2019, and that can't even be installed on newer devices. (Fun fact: Nomad has also become the name of Hubzilla's underlying protocol in the meantime.) Hubzilla's Web UI adapts to small screens gracefully, but people expect and demand a native iOS or Android UI.
Reason #5: Newbies who approached Hubzilla like they had approached Mastodon, who wanted to get going right away with 100% default settings, and who threw in the towel because they couldn't connect to Mastodon accounts. Hubzilla really lacks a big fat honkin' red label that warns you that you first have to "install" the ActivityPub "app" because ActivityPub not only isn't Hubzilla's basic protocol, but it's optional and, on top of even that, off by default for new channels.
Maybe reason #6: GPL fanatics for whom all licenses that aren't any kind of GNU GPL are non-free and must therefore be abolished. Friendica was re-licensed under the AGPLv3 in late 2011 whereas Hubzilla remains under the MIT license.
# # # # # # # # # # # # #
I'm talking about describing an image for one person whom I know vs describing an image for billions of people whom I don't know. That's a huge difference.
Let's suppose I've rendered a picture in a 3-D virtual world. A very obscure one. (Because that's what I normally do.) Chances are people won't get that image without explanations, simply because they don't know anything about these worlds.
If I want to describe that image to my friend Joe over a landline phone, I can ask Joe what he knows about virtual worlds, and whether he needs some explanations first.
If Joe says yes, he'd like some explanations, I can take a deep breath and explain away. If the explanations go too much in-depth, or if they become too big an info dump for him to handle, Joe can stop me while I'm explaining.
After explaining, I can ask Joe what I shall describe to him. Only what's important Everything because Joe is super-curious about these virtual worlds, and he wants to know all the details so he can imagine what that virtual world looks like
And Joe can answer. If Joe answers that he does not want a super-detailed description of everything, I don't have to give him a super-detailed description of everything. And if my description becomes too detailed, Joe can rein me in and tell me to stop.
If I want to describe that image when I post it in the Fediverse, it's very different.
- I post it to not one person, but to many persons. Potentially billions of them, namely everyone with an Internet access.
- I cannot ask them all what they need explained before I start describing. Especially, I cannot ask everyone of them individually what they need explained.
- In fact, I can't even know beforehand who will receive my image post.
- Still, I have to cater to everyone's needs all the same. I have to do so immediately without being explicitly asked to do so. And people's needs are different.
- Lastly, they cannot talk back while I'm describing/explaining. If my explanations go too much into detail, they cannot stop me in the middle of my explanations. Besides, someone somewhere out there might actually need my explanations in their entirety.
- The same goes for the visual descriptions. Some may want or need every last detail in the image described in-depth because they're so curious about the topic. Others may only be interested in what they think or what I think is important in the image. But they can't stop my super-detailed describing of absolutely everything in the image for those who want or need it. Even if they could, it'd be unfair towards those who do need a full, detailed description.
The result: I have to deliver the maximum right away. I have to start with a whole lot of explanations because someone somewhere out there probably won't understand my image without these explanations. And then I have to continue with an extremely detailed visual description because someone somewhere out there may want or even require one. Regardless of what everyone else wants.
It's like describing an image to Joe over a landline phone, but I don't know Joe, I don't know what Joe wants or needs, I don't even know that it's Joe on the other end, there may be other people around Joe's phone who want to hear the description, too, and someone has cut off the microphone in Joe's phone first, only to re-activate it after I'm done describing the image three hours later.
# # # # # # # # # # # # # # #
This is the lens I shot a roll (of 120) on, a Carl Jena DDR f2.8 80mm lens. Till now I been shooting, like, Dianas & , or my plastic TLR (waist viewfinder I struggle), a folding viewfinder one
This is a proper & I also got a viewfinder, hope it works!
of
The long lens arrived! My first roll with my Pentacon Six is in the mail to the developer, well see how the 80mm Zeiss looks. It shoots only twelve 6 x 6 cm exposures per 120 film roll. This lens is 180mm focal length, auto or manual aperture (so you can focus wide open) setting. Now to find lens caps front and rear.
of
Hashtags kann man meines Wissens "folgen", aber nicht wie auf Mastodon als eine Art Akteur und durch Klicken, sondern mit einem Feld in den Einstellungen, wo man Hashtags eintragen kann.
Alt-Text kann man weiterhin in den Bildeinbettungscode reinschreiben. Aber zum einen kann das jetzt neben BBcode auch Markdown/HTML sein, wenn einem das vertrauter ist. Zum anderen mu man das nicht mehr. Statt dessen kann man schon beim Hochladen eines Bildes in den Filespace einen Alt-Text eintragen oder auch hinterher in der Bilder-App. Und dann kann man dasselbe Bild mit demselben Alt-Text immer und immer wieder einbauen, ohne den Alt-Text mehr als einmal schreiben zu mssen. Das wiederum geht auf Mastodon nicht.
berhaupt ist da einiges eleganter gelst als auf Hubzilla. ActivityPub mu nicht mehr aktiviert werden. Die Rechteverwaltung ist jetzt auch deutlich einfacher zu handhaben, weil sie jetzt gebaut ist fr das reale Fediverse der 2020er und nicht mehr fr eine Vision eines Fediverse, das es Mitte der 2010er geben sollte, das so aber nie kam.
diaspora* knnen beide nicht mehr. Der Aufwand, noch ein weiteres nichtnomadisches Protokoll mitzuschleppen und Zot ab Version 6 darauf auszulegen, hat sich wahrscheinlich nicht mehr gelohnt. (streams) basiert weiterhin auf Nomad, wie Zot jetzt heit, aber ActivityPub ist so gut integriert, da es Teil des Kerns geworden ist und standardmig aktiviert. Und Forte erschlgt alles mit ActivityPub und kennt gar kein anderes Protokoll mehr.
# # # # # # # # # # # # # # If you really want some criticism:
Alt-text really should not contain line breaks, nor should it contain the quotations marks on your keyboard. Neither are standard alt-text elements. And just because Mastodon renders them with no problems, doesn't mean everything does. Not even in the Fediverse.
As for line breaks: Some screen readers will take each new line for a whole new alt-text and therefore a whole new image. And they will read multi-line alt-texts as alt-texts of multiple images, e.g. starting each line with, "Graphic."
As for quotation marks: For one, just like line breaks, they're actually completely useless for the actual target audience of alt-text, namely blind or visually-impaired people. Screen readers don't read out quotation marks. I mean, how should they
But if a frontend doesn't render quotation marks properly, screen readers will read out gobbledygook where there's a quotation mark because they will see gobbledygook in the place of that quotation mark, because the frontend renders quotation marks as gobbledygook.
For example, there's Hubzilla which is what I'm posting from right now, so it's very much part of the Fediverse. Hubzilla renders quotation marks in alt-text as their HTML entities, namely
". A screen reader will read out every single quotation mark as, "And quot."And then there are two descendants of Hubzilla made by Hubzilla's own creator, (streams) and Forte. The same quotation marks that you have on whatever keyboard you use, they use as alt-text delimiters. When the first quotation mark comes, they think it's the end of the alt-text, and they stop parsing and rendering the alt-text. For them, your alt-text ends right after, "Panel 1:"
# # # # # # # # # # # # # # # I'm not talking about the technical side.
That is, you may not have noticed, but I'm not posting from Mastodon. I'm on Hubzilla where things are quite a bit different. Images aren't file attachments they're embedded into posts in-line using BBcode markup like in classic bulletin board forums. Alt-text has no dedicated text entry box instead, it's manually woven into the image embedding code.
No, what I mean is that here in the Fediverse, you can't describe an image like describing it to a friend over the phone. Open the link in my post. (If it looks like it may be a link, it actually is one, even if it isn't a URL in plain sight. I can do embedded links on Hubzilla, too.)
Anyway, if you describe an image to a friend over a landline phone with no image transfer, your friend can talk back. Your friend can even talk back before you start describing. You can ask your friend what they need to know, what they want to know. You can do that beforehand. And then you can describe the image in exactly the way that your friend needs.
In the Fediverse, you describe your images for potentially millions of Fediverse users and billions of Internet users. You can't first go around and ask them all, every last one of them, what they need to know and what they want to know. You have to perfectly cater to everyone's needs without even knowing anyone's actual needs because you can't know everyone's needs.
Describing for one person over the phone is one-size-fits-one. It's tailor-made for one person. Describing in the Fediverse has to be one-size-fits-all at first try, right off the bat.
This may not matter if you post a simple real-life cat photo. But I post renderings from super-obscure 3-D virtual worlds. Nobody knows what anything in my images look like until they can either see the images themselves, or I describe everything in these images to them. So this matters a whole lot in my case.
# # # # # # # # # # # # # # # Only that "my best" has actually led to unimaginable extremes.
They say an image is worth a thousand words. I've once in over 10,000 words. Over 60,000 characters. The post is so long that, I think, Misskey and its various forks have rejected it, as have Pleroma and Akkoma. It took me two full days, morning to evening, to describe that one image, in-world research included.
And I actually had to limit myself. For once, I did not give in-depth descriptions of the images within that image, especially not beyond what's actually visible in these images. That's because I've discovered that if I were to do that, I'd have to describe dozens of images in one particular image (in my image) and potentially over a hundred images in these, even though they're so small that they're technically invisible. It would have taken me months to write all that. And it would have been futile anyway. My character limit is over 16 million, but Mastodon rejects posts over 100,000 characters, and in the few places that do accept posts with millions of characters, next to nobody cares about image descriptions.
I haven't posted a new in-world image in over half a year. I've been working on-and-off on the descriptions for a series of rather simple avatar portraits since last autumn.
# # # # # # # # # # # # # # # Of course, this means that the more obscure the content of your image is, the more in-depth you will have to go. At worst, there's nothing in your image of which non-sighted people know what it looks like unless you describe it. Simply mentioning that it's there is not sufficient.
My own original images aren't even photographs, nor are they pieces of art that represent real life. They're renderings from 3-D virtual worlds, very obscure 3-D virtual worlds even. Nobody knows what anything in these world looks like unless they can see it in my images. At the same time, however, chances are that they become so curious about these virtual worlds that they also become curious about everything in the image, not just what matters within the context of the post. That is, sometimes the image itself as a whole is the context. Either way, this means I can't just focus on certain elements in the image in my descriptions. I have to describe everything.
So I've gotten to a point at which even filling the alt-text character limit forced by Mastodon, Misskey and their respective forks (they cut longer alt-texts off at the 1,500-character mark) doesn't cut it. All my original images have two descriptions now. In addition to the one in the alt-text that's very limited, there is another one in the post that's more or less fully detailed, that contains transcripts of all text within the borders of the image, and that also comes with all explanations that I deem necessary. Since I don't have a character limit to worry about (the limit is defined by the database field rather than a hard-coded or configurable number), this description is likely to grow well over a hundred times longer than typical alt-text.
# # # # # # # # # # # # # # #
Thn Ti h phm xung dn gian ri vng th lng ngi dn v ci kt P1/2.
Thn Ti h phm xung dn gian ri vng th lng ngi dn v ci kt P 1/2. Your browser does not support HTML video. Thn Ti h phm xung dn gian ri vng th lng ngi dn v ci kt P 1/2. xin cho
Report: Devin Bookers role in coaching interviews signals long-term commitment from Suns
but yes, I think the alt text in those posts you linked is fine and not too much
The alt-text is fine How about the long descriptions in the post itself
Again: I've described all these images twice. One description is in the alt-text. It's the short one with no text transcripts and no explanations (because explanations don't belong into alt-texts).
The other one is in the post itself, not in the alt-text. If you look at the post at the source, open the summary/content warning, and then scroll beyond the image(s). Right below, there are the long image descriptions.
Again: Would you say it's okay to describe one image in over 60,000 characters and over 10,000 words Would you say it's okay to spend two full days, morning to evening, describing one image and researching for the description Would you say it's okay for an image description to be so long that it has two levels of headlines Would you say it's okay to start a long image description with well over 5,000 characters of explanations before any visuals are described because these explanations are necessary to understand the image and the description Would you say it's okay to use over 3,000 characters to describe one single object in an image which even sighted people would have a hard time spotting without the description, and to transcribe the 14 individual bits of text on that object, even though they're so tiny in the image that they're basically invisible
After all, I myself think I've made lots of mistakes in that description.
# # # # # # # # # # # If you don't mind the learning curve (because it handles nothing like Twitter or Mastodon), maybe is something for you. It's the youngest member of a family of Fediverse server applications that started 15 years ago with a Facebook alternative that's now known as Friendica, and that also gave us Hubzilla and the streams repository.
It's written in PHP with a little side of JavaScript for post formatting, so no fumbling around with exotic dependencies. Administration is fairly easy, especially upgrading the whole thing for which there's a dedicated script. At the same time, it's both very powerful and very secure.
And it's probably the most technologically advanced Fediverse server software out there. After all, it's the first one to implement nomadic identity with nothing but ActivityPub.
# # # # # # # # #
but more detail cant hurt.
I think we aren't thinking in the same dimensions.
How about
How about
In case you're on a phone: If the above looks like links, that's because it is links. The links lead to two of my image posts which, while not originally on Mastodon, are still in the Fediverse, and copies of both can actually be found on mastodon.social. The first one can be found under the hashtag # it's the third one (or fourth, counting this one) from the top. The second one can be found under the hashtag # it's the one at the bottom.
I just wrote this page because there was no documentation on it really,
Oh, there's plenty of documentation on alt-text and image descriptions. For example:
- (this has loads of pages about alt-text and image descriptions, and the author is visually impaired herself)
Beware, though: They may contradict each other.
# # # # # # # # # # # # # # # So the more detailed it is, the better Would you say it's possible to describe an image in too many details, regardless of circumstances (e.g. what the expected audience may be curious about)
Also, what about the rule that any and all text within the borders of an image must be transcribed 100% verbatim There is text on the T-shirt, that's why I'm asking. I myself am someone who always transcribes every last bit of text within my original images. That said, the transcripts usually only go into the long description in the post itself (the character limit here is so high, it's fully negligible but my original images always get two descriptions each). Most of the time, there simply isn't enough room for them in the alt-text (or what of it Mastodon, Misskey and their respective forks let through at full length).
I'm also asking because I plan to write my own wiki on alt-texts and image descriptions specifically for the Fediverse. It will be a wiki because it will be too detailed for only one article or page.
# # # # # # # # # # # # # # #
Cub Tracks long fly trap
Mets Series Preview: Mets wrap up long homestand with woeful Rockies
Add your location to a Google Map To be fair, "European Facebook" already exists. And it has been around for longer than Mastodon.Friendica was created by an American living in Australia, but it's maintained by two Germans. Hubzilla was created (actually forked) by the same guy, and now it's maintained by a German and a Norwegian.
Both are part of the Fediverse. Friendica connects to Mastodon and everything else in the Fediverse, and Hubzilla can optionally do that, too.
None of them is an all-out, 1:1 clone of Facebook, though. Instead, both are better than Facebook.
# # # # # # # # # # # #Author(s): riktoi
Title: Sandpaper
You wake up in a strange room...
Ist problemlos schon lange auch im Fediverse mglich, nur eben nicht auf Mastodon.
Friendica, Hubzilla, (streams) und Forte haben nicht nur Gruppen mit allen Schikanen, sondern auch private Gruppen. Das heit: Wer nicht in der Gruppe ist, kann die Threads in der Gruppe nicht sehen, kann das Profil der Gruppe nicht sehen, kann nicht sehen, wer alles in der Gruppe ist. Auf Hubzilla kann das sogar jeweils einzeln und unabhngig voneinander geschaltet werden.
Private Gruppen auf Hubzilla, (streams) und Forte untersttzen auch OpenWebAuth Magic Single Sign-On: Wenn du auf Friendica, Hubzilla, (streams) oder Forte bist, egal, auf welcher Instanz du bist, und du besuchst die Gruppe, wird dein Login automatisch erkannt. Wenn du Gruppenmitglied bist, kannst du das Profil, die Gruppenmitglieder und den Gruppen-Stream mit allen Threads sehen.
Zustzlich, also unabhngig davon, knnen solche Gruppen auch wahlweise in Verzeichnissen nicht angezeigt werden, damit sie nicht jeder findet.
Friendica-Gruppen knnen zustzliche Moderatoren auf demselben Friendica-Node haben. Hubzilla-Foren, (streams)-Gruppen und Forte-Gruppen knnen zustzliche Moderatoren irgendwo auf Hubzilla, (streams) oder Forte haben.
Gleichzeitig kannst du dein Friendica-Konto oder deinen Hubzilla-, (streams)- oder Forte-Kanal nutzen, um dich damit auch mit dem ganzen Rest des Fediverse zu verbinden, Mastodon, Misskey, Pixelfed, PeerTube, Castopod, Funkwhale, Lemmy, Mbin, PieFed usw. usf.
Aber: Wenn du einer privaten Friendica-Gruppe beitreten willst, brauchst du ein Friendica-Konto oder einen Hubzilla-, (streams)- oder Forte-Kanal. Wenn du einem privaten Hubzilla-Forum oder einer privaten (streams)- oder Forte-Gruppe beitreten willst brauchst du einen Hubzilla-, (streams)- oder Forte-Kanal. Mastodon kommt da jeweils nicht rein, weil es kein Konzept von Berechtigungen hat.
# # # # # # # # # # # # # # # # # # # #
: continued through a considerable tine, or to a great length
- French: long
- German: lang
- Italian: lungo
- Portuguese: longo
- Spanish: largo
------------
Join our new Discord Server for language learners
Scientist who studied centenarians for 20 years reveals four habits she follows for a , healthy
1. Eat five colours of fruits and vegetables every day
2. Exercise daily and vary the routine
3. Prioritise high-quality sleep
4. Learn a new skill
This starts with Mastodon's timeline which still is a 1:1 clone of Twitter's feed. It only supports one mode: message-by-message piecemeal doomscrolling. It does not support listing entire threads instead of single messages. And while it does have notifications, it doesn't have an unread messages counter like Friendica, Hubzilla, (streams) and Forte which also allows you to directly jump to a thread with unread messages in it.
Result: Comments on threads drown in the deluge that's a Mastodon timeline, never to be seen, unless they mention you. And on Fediverse server applications with full-blown, native group support from the very beginning, they usually don't mention you.
Add to this the hundreds or thousands of Fediverse actors that typical Mastodon users follow, often also to catch as many messages about certain topics as possible because they don't know that Mastodon can follow hashtags, because Twitter never could. This alone leads to timelines that may consist of 5% interesting stuff and 95% cruft, but they still have to scroll through the cruft because lists are so inconvenient, having more than four lists more so (it's tempting to think that Mastodon was actually designed by a Watership Down rabbit that can't count beyond four).
Most Mastodon users never get to read nearly everything that comes rushing through their timelines. Maybe 20%, maybe 10%, maybe less. They simply don't have the time to scroll all the way down until they see messages that they already know, especially not if they've only got time to check Mastodon once a day or even only once every couple of days.
They won't even scroll far enough down to catch all comments on a thread. Well, and even if they do, there's nothing signalling to them which "toots" are part of the same thread, not even which "toots" are comments on which "toot".
A huge improvement would be if Mastodon a) implemented full support for one-post-many-comments threaded conversations, b) implemented threaded modes for the timeline (sorted by newest post, sorted by newest comment) which would then list entire threads instead of message-by-message piecemeal and c) made it the default for everyone because the vast majority of Mastodon users run their accounts on 100% default settings. Also, at least all the important mobile apps for Mastodon would have to do the same, all the way to making the sorted-by-newest-comment threaded timeline the default for everyone, because next to nobody ever users Mastodon via the Web interface.
Then we can talk about improving interaction with link aggregators or anything else that supports groups, e.g. titles being unavailable and largely unknown on Mastodon, but a hard requirement for new threads on Lemmy, /kbin, Mbin and PieFed, or Mastodon and the Threadiverse having mutually incompatible ways of handling images.
# # # # # # # # # # # # # # # # # # # # # # # # #
FanPost Friday: Long weekends, ugly hats, and a first place baseball team (the Seattle Mariners)
...
The
they should build a 180 hole golf course somewhere in and just let spend all his time wandering aimlessly round the course...
...
Da bin ich lieber vorsichtig.Ich rechne stndig damit, da Leute von der Mastodon HOA, Abteilung Alt-Text-Polizei, auch dann fehlenden Alt-Text sanktionieren, wenn das Bild im Post beschrieben ist, weil sie eisern die Regel durchsetzen wollen, da jedes Bild im Fediverse einen hinreichend detaillierten und akkuraten Alt-Text haben mu.
Ich selbst mu meine eigenen Bilder . Dazu kommen dann noch genug Erklrungen, damit wirklich jeder meine Bilderposts sofort versteht, egal, wie obskur das Thema auch sein mag. Und dazu kommen Transkripte von allem an Text im Bild. Ich brauche auch mal Stunden oder Tage, um ein einziges Bild zu beschreiben. Das Ergebnis ist eine Bildbeschreibung, die alle "normalen" Zeichenlimits im Fediverse um Grenordnungen bertrifft und auch deshalb direkt in den Post geht statt in den Alt-Text. (kein Problem hier, mein Zeichenlimit ist nicht 500, sondern ber 16 Millionen). Das ist anstrengend genug, da ich nicht alle paar Tage Bilder posten kann.
Da will ich nicht noch dafr angeschnauzt werden oder anderweitig auf den Deckel bekommen, da das Bild keinen Alt-Text hat.
Also schreibe ich immer zustzlich eine Bildbeschreibung fr den Alt-Text, wobei meine Alt-Texte auch regelmig bei exakt 1500 Zeichen oder einigen wenigen darunter liegen. Vorsicht ist die Mutter der Porzellankiste.
Das heit, Leute, die noch auf alten Mastodon-Versionen sind, wo Inhaltswarnungen die Bilder noch nicht verstecken, sehen eh erstmal nur das Bild, aber nicht den Post-Text, den ich wegen seiner berlnge (= ber 500 Zeichen) hinter einer Zusammenfassung und Inhaltswarnung verstecke. Das heit, die sehen die lange Bildbeschreibung gar nicht, also wissen sie nicht, da sie existiert.
Deswegen gibt's von mir im Alt-Text nicht nur eine Bildbeschreibung, die hoffentlich detailliert genug ist (auch wenn ich unmglich die ganzen Text-Transkripte mit darin unterbringen kann), sondern auch einen Hinweis auf die lange Bildbeschreibung, und wo sie zu finden ist.
# # # # # # # # # # # # # # # # # # #
Kansas City Royals Podcast: Giants Recap, Longs Road, Twins Preview
he's a long boi
I just stumbled upon the fairly recent blog post by Bryn Newell who, unfortunately, is nowhere to be found on anything that Hubzilla can directly federate with. It talks about fun and poetry and whimsy in alt-text.Well, for me personally, whimsy in image descriptions falls under "no can do".
One single image regularly takes me multiple days, morning to evening, to research for the description and explanation, to describe and explain. I end up with a long image description that measures several tens of thousands of characters, and that goes directly into the post. At that point, I don't have the time and energy to edit whimsy into that monster description. Besides, whimsy clashes with the extensive explanations that are necessary for everyone to understand my image posts.
Furthermore, I also distill a shorter image description for the alt-text to satisfy the Mastodon Home Owners' Association that demands there be a sufficiently detailed and descriptive alt-text for each image even if there are well over 100 Mastodon toots worth of image description in the post itself. Nonetheless, my alt-texts end up either exactly 1,500 characters long or only a very few characters short of that. I simply don't have room for whimsy in my alt-texts. I could technically make them longer, but then Mastodon, Misskey and their respective forks would chop them off at the 1,500-character mark.
Not to mention that my original images never mean to convey emotions. Ever.
Oh, and I can't describe my images like to a friend over a landline phone either. That'd mean I'd describe my image to one person. In a situation that allows for dialogue. I could ask my friend beforehand what they want to know about the image and what they need to know about the topics touched by the image to understand the image. I'd have to ask that because my images always show extremely obscure niche content that the vast majority of Fediverse users knows exactly nothing about. After asking and receiving the answers I need, I could give a description tailor-made for that one friend. Also, that friend could always ask me about details while I'm describing.
In the Fediverse, I describe my images to potentially millions of Fediverse users and billions of Internet users. That's a situation that does not allow for dialogue. I can't possibly ask any of them what they want or what they need, much less every last one of them. I can't tailor my descriptions to their needs. Before I start describing, I know nothing about who wants and needs what. But when I'm done, everybody must know everything about the image and the topic of the image that they want or need to know. This means everyone must get the same massive info-dump because someone somewhere out there may want or need it.
I can't describe an image over the phone the same way. I can't start describing an image over the phone by first giving lengthy explanations between several minutes and about an hour before I start describing the visuals. But my long descriptions require just that if I want to cover everyone's needs and requirements all the same.
A pity I can't give any direct feedback. But then again, the author most likely knows nothing about Fediverse culture and how alt-text and image descriptions are even more deeply engrained there. And the author probably can't imagine either that it's possible to post in excess of 50,000 characters at once in social media.
# # # # # # # # # # # # # # # # #
Baylors V.J. Edgecombe offers immediate impact, long-term upside at No. 3 for Sixers
Since you weren't mentioned in these replies, you probably weren't notified about them either. So, fresh from your thread:Well I don't think I'm the ActivityPub inventress, though I certainly played a big role in its standardization and etc. The history of the name "ActivityPub" is one of those things that could be lost to time tho, so here's what happened, per my memory: - developed Pump.io's API experimenting towards a new, simpler, better design to replace OStatus called the "Pump.io API"
- sets up "ActivityPump" doc, converting Evan's api docs into more formal protocol format/language, using ActivityStreams2
- In the SocialWG, MicroPub was also being standardized there was hope the two specs would converge, and suggested we rename to ActivityPub, a big name upgrade anyway Ultimately the merge between MicroPub and ActivityPub didn't happen, but they did learn from each other, and ActivityPub did keep its improved name. The "Pump" language was awkward Pump.io had an infamously awkward (but I don't think intentional) tagline along the lines of "Pump.io pumps your life through your family and friends" or something else that made me think yes, actually dropping the name "pump" might be a good idea, and ActivityPub seemed good I'm not much of the ActivityPub inventress I did shape it a lot, and guided it through the process. Ultimately, ActivityPub's core design ideas came from , though really I think they really derive from the kind of design that comes out of actor model systems (even though AP deviates in various places from the actor model, it's best when it follows it)
# # # # # # # # # # # # # #
<>
: Can legally tell the to change someone's status
BILLY LONG: I'm not able to answer
WARREN: You can't read these words and tell me what those words say!
: I can read the statute and I did
WARREN: Then tell me what they mean!
A Simple Server to Match Long/Lat to a TimeZone
/Lat
Echoes of Language
"A Long Way Home"
Culture, space economy,investments Puglia at Expo 2025 Osaka General News 
 
 The week dedicated to Puglia has
 concluded at the Italy Pavilion at Expo 2025 Osaka.
 
 
 The event highlighted the Regions great role in supporting the
 Country System.
 
 
 From hospitali
Zum einen: Nextcloud ist in PHP gebaut. Viele haben ja aus guten Grnden ein Problem mit PHP, nicht nur, aber auch, weil es da bel aussieht mit Abwrtskompatibilitt.OpenCloud kommt dagegen direkt als ausfhrbare Binaries, die selbst keine groen Spezialabhngigkeiten brauchen.
Zum anderen: Nextcloud haut immer neue fest eingebaute Features raus, die vor allem Privatanwender gar nicht haben wollen. Vor allem KI wird jetzt allen aufgezwungen. Zumindest wird KI wohl mit neuen Versionen ausgerollt und dann auch auf bestehenden Servern standardmig aktiviert, wenn sie denn berhaupt abschaltbar ist. Bei den ganzen neuen Features bleiben aber dringend ntige Bugfixes auf der Strecke.
Ich glaube, wenn "das Metaversum" (nicht das, was wir zwei schon lange als Metaverse kennen) nicht offiziell fr tot erklrt worden wre, htte Nextcloud wahrscheinlich eine VR-Umgebung als alternative Bedienoberflche eingebaut und zwangsausgerollt, um auch wieder auf irgendeinen Hype aufzuspringen. Und wieder htten sie nicht statt dessen mehrere Jahre alte Bugs gefixt.
OpenCloud setzt eher auf Stabilitt und fixt Bugs, statt allen mglichen Klimbim einzubauen, der gerade der heie Schei ist, den aber keiner haben will.
CC:
# # # # # # # # # # Zivilklagen bringen gegen Konzerne schon lange nichts mehr. Strafanzeigen bringen auch nichts mehr.
Das einzig wirksame Mittel sind inzwischen internationale Haftbefehle gegen Vorstnde, die dann auch durchgesetzt werden. Und Przedenzflle, wo Vorstandsmitglieder oder gar Vorstandsvorsitzende anderer Konzerne in vergleichbaren Fllen tatschlich verhaftet und zu langen Haftstrafen verurteilt worden sind. Die Aussage mu sein: "Wir kriegen euch und bringen euch hinter Gitter. Wir haben schon ganz andere gekriegt, die glaubten, wir kriegen sie nicht, und euch kriegen wir auch noch."
Siehe Martin Winterkorn. Als gegen VW geklagt wurde: "Haha, damit kommen wir doch sowieso durch." Als Strafanzeige erstattet wurde: "Haha, damit komme ich doch sowieso durch." Dann aber hat die US-Justiz (der deutsche Michel ist da immer noch zu zahnlos) gegen ihn einen internationalen Haftbefehl erwirkt und das FBI auf ihn angesetzt. Das darf ihn zwar nicht auf deutschem Boden verhaften, aber sollte Winterkorn einen Fu auf US-Boden sitzen: Handschellen und effektiv lebenslnglich.
Andere Geschichte: Vor vielen Jahren haben drei Anwltinnen eine gemeinsame Kanzlei gegrndet und dafr einen DSL-Anschlu bestellt. Der wurde aber nicht termingerecht geschaltet. Auch auf Anfrage passierte nichts. Da haben die drei an die Telekom geschrieben, wenn nicht binnen ein paar Tagen der Anschlu geschaltet ist, werden sie gegen den damaligen Telekom-Vorstandsvorsitzenden Strafanzeige (wahrscheinlich wegen gewerbs- und bandenmigen Betrugs) erstatten und einen Haftbefehl gegen ihn erwirken. Noch einmal: Anwltinnen. Wahrscheinlich sogar in mindestens einem Fall mit Spezialgebiet Strafrecht. Nach zwei Tagen hatten sie ihren Anschlu.
Die DSGVO kann man in Deutschland nur so durchsetzen:
- Strafanzeigen gegen die verantwortlichen Entwickler wegen unerlaubten Eindringens in die Privatsphre in Millionen Fllen
- juristischer Schutz fr Entwickler, die sich weigern, so etwas auf Befehl zu implementieren, und Whistleblower, die so etwas offenlegen
- Strafanzeigen gegen die gesamte Befehlskette wegen Beihilfe
- Strafanzeigen gegen den Vorstand wegen gewerbs- und bandenmiger Datenhehlerei oder zumindest Beihilfe dazu
- internationale Haftbefehle mindestens gegen den Vorstand
- tatschliche Inhaftierungen bis hin zu Vorstandsvorsitzenden als Signal: "Nein, damit kommt ihr nicht davon!"
- nachrckende Vorstandsmitglieder mssen binnen 7 Tagen wirksame Gegenmanahmen einleiten, oder ihnen blht dasselbe
- auerdem sehr viel hhere Strafzahlungen fr die Konzerne, die wirklich weh tun und auch tatschlich vollumfnglich eingefordert werden (ja, auch in Irland, das noch nie soviel Geld auf einen Haufen gesehen hat und gar nicht wei, was es damit anstellen soll)
- letztlich richterliche Unterlassungsaufforderungen, die ggf. von der Staatsmacht durchgesetzt werden (Inhaftierungen, zwangsweise Abschaltung und Beschlagnahmung technischer Einrichtungen, Netzsperren etc.)
- idealerweise sollten auch millionenschwere Lobbyisten, die versuchen, das alles zu verhindern, strafrechtlich wegen versuchter oder tatschlicher Beihilfe und Bestechung belangt werden, wieder bis hin zu Haftbefehlen
Das einzige Problem bei Unterlassungsaufforderungen ist, da vor allem in Deutschland die digitale Infrastruktur von der persnlichen Kommunikation (ich sage nur WhatsApp) ber Startups, ber Kleinunternehmen, ber den Mittelstand, ber Grokonzerne bis hin zur ffentlichen Verwaltung fast komplett abhngig ist von US-Gigakonzernen wie Microsoft, Alphabet, Amazon und Oracle. Traurig, aber wahr: Es sind praktisch nur sie, die die Technologie des 21. Jahrhunderts bereitstellen in einem Land, das selbst technologisch in den ersten zwei Legislaturperioden Helmut Kohls steckengeblieben ist.
# # # # # #
Mariners play long ball, small ball, snatch series from Padres
Reason #1: Friendica is more known than Hubzilla. Friendica is somewhat well-known as "the Fediverse's Facebook alternative", regardless of there technically being four from the same original creator (not counting those in-between that were discontinued). Early this year, when Facebook was further enshittified, half the Fediverse was completely crazy about Friendica.In the meantime, at least three quarters of the Fediverse's user base have never even heard of Hubzilla (there has been a poll, yes). But most Mastodon users only know of one Twitter alternative in the Fediverse as well, namely Mastodon, regardless of even only the uncountable Forkeys.
Reason #2: Hubzilla has the Eiger North Face of learning curves. I'm a Hubzilla veteran. Still, I think that even (streams) is user-friendlier, and (streams) is still harder to get into than Friendica which, in turn, is much harder to get into than Mastodon or some *key, especially when you've got "Twitter on the brain".
Even though I daily-drive Hubzilla, I normally only recommend it to those who really need its extra features. To those who want fail-safe Friendica or Friendica with even better permissions, I'd rather recommend Forte or, if they like the idea of being able to turn ActivityPub of as a last line of defence against the Mastodon HOA, (streams).
I think the new community-written help has yet to be officially adopted by Hubzilla, too. Hubzilla is one of the few Fediverse server applications with a built-in help system, but as of now, that help is not only hard to understand, but also hopelessly outdated, often simply factually wrong and very incomplete.
Reason #3: Friendica's UI has actually evolved over the years. In the meantime, Hubzilla's only official theme hasn't changed much since 2012. The name "Redbasic" says it all: It was the basic theme in the early days when Hubzilla was still named Red. And back in the day, Friendica's standard theme which it was derived from wasn't exactly pretty either.
The development of third-party Hubzilla themes hasn't really picked up speed until not even a year ago. I mean, we have some now, but especially the big hubs only offer you Redbasic. (Still I wish (streams) and Forte upgraded Redbasic to version 2.2 and maybe also Bootstrap icons.)
Speaking of third-party themes: BookFace. A theme to make Facebook refugees feel at home. Exclusive to Friendica.
Reason #4: Friendica has at least got native third-party Android apps plus a third-party iOS app in very incomplete development. All that Hubzilla has is Nomad, a glorified specialised Web browser that's about 10% native and 90% Web interface, that's only available on F-Droid and not in the Google Play Store, that has last been maintained in December, 2019, and that can't even be installed on newer devices. (Fun fact: Nomad has also become the name of Hubzilla's underlying protocol in the meantime.) Hubzilla's Web UI adapts to small screens gracefully, but people expect and demand a native iOS or Android UI.
Reason #5: Newbies who approached Hubzilla like they had approached Mastodon, who wanted to get going right away with 100% default settings, and who threw in the towel because they couldn't connect to Mastodon accounts. Hubzilla really lacks a big fat honkin' red label that warns you that you first have to "install" the ActivityPub "app" because ActivityPub not only isn't Hubzilla's basic protocol, but it's optional and, on top of even that, off by default for new channels.
Maybe reason #6: GPL fanatics for whom all licenses that aren't any kind of GNU GPL are non-free and must therefore be abolished. Friendica was re-licensed under the AGPLv3 in late 2011 whereas Hubzilla remains under the MIT license.
# # # # # # # # # # # # #
Making code last a long time
Last updated: 2025-06-02
All text and images © eLoc8.is-fabulous.com