Pipeline release! nf-core/mag v3.0.0 - mag
You won't get Mario Vavti and Mike Macgirvin to build Hubzilla and the streams repository respectively against the Mastodon API any more than necessary. Read, ideally at all.
Neither have anything to do with Mastodon. The streams repository is the latest in a series of developments that started yesterday 14 years ago with Mistpark. That was six years before Mastodon when Eugen Rochko was still a school kid. And Hubzilla is one of the stopovers on this path and ten months older than Mastodon itself, created by Mike as well.
Not to mention that both have absolutely nothing in common with Mastodon, technologically-wise, except for supporting ActivityPub. And both Mike and Mario hate Mastodon and its home-brew, non-standard, proprietary wanna-be "standards" while rejecting actual standards with a flaming passion because it hinders innovation in the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaYou think decentralised social networking was invented with Mastodon Think twice.
It was almost exactly 14 years ago, on May 13th, 2010, that Mike Macgirvin conceived Mistpark. All by itself revolutionary and with features which no-one else has ever built into a decentralised project until today, it was only the first step of a long journey which led to , , , all three still before Mastodon, and eventually .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mistpark #Friendika #Friendica #Hubzilla #Streams #(streams)
And I mean the effort of describing the image.
Since the sims of 3rd Rock Grid are being rescued and largely already have been, there's no point in showing one of them anymore. So I'm looking for a motive elsewhere.
It's hard to find something that's interesting to look at while still not impossible for me to describe adequately before the end of the day.
I'm currently looking around NyAlfheim in OSgrid. I've found a scene that's absolutely gorgeous. But it'd also absolutely be hell to describe, what with all the different buildings and what's inside the buildings and the furniture in front of the buildings and the boats and all the other decoration.
Also, there are static human figures plus one human animesh figure in the scene which means eye contact which, in turn, means I'd have to link to the image instead of embedding it because that's the only way I have to hide the image from sensitive Mastodon users.
On the other hand, I don't want to show something that's so simple that it's lacklustre and not a bit interesting.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Long
The big event that Alia wanted never had a chance to materialise. All they managed to do was a farewell party in 3RG yesterday. Today there's nothing. And the welcome party in ZetaWorlds will be at some point in the next weeks.
They didn't even manage to advertise or communicate anything. I guess they had no Hypergridders yesterday, only residents.
Oh well, good thing there are more events around the Hypergrid this evening.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #3rdRockGrid Bei ActivityPub-basierten Microbloggingprojekten haben im allgemeinen alle Instanzen desselben Projekts denselben Funktionsumfang. Vielleicht unterscheiden sie sich mal in der Auswahl der Emojis oder der maximalen Postlnge.
Aber Riesenunterschiede von Instanz zu Instanz in den Features wie bei den modular aufgebauten Friendica, Hubzilla und (streams) hast du da nicht.
Und die Unterschiede zwischen Mastodon einerseits und z. B. Misskey oder Pleroma andererseits haben nichts mit Instanzen zu tun. Das sind vllig unterschiedliche, voneinander unabhngige Projekte, also noch nicht mal Hardforks voneinander.
Bei vielen Apps ist der Grund, warum sie keine Funktionen ber Mastodon 3.x hinaus untersttzen, ganz einfach: Als der Entwickler anfing, kannte er nur Mastodon. Als der erste stabile Punktrelease raus war, kannte der Entwickler immer noch nur Mastodon. Als der Entwickler erfuhr, da es im Fediverse auch noch was anderes als Mastodon gibt mit ganz anderen Fhigkeiten, war es zu spt, die zu implementieren.
Es gibt aber nicht nur Entwickler, die nur gegen Mastodon bauen, weil sie nur Mastodon kennen. Es gibt auch Entwickler, die sagen: "Das ist 'ne iPhone-App, iPhone-Nutzer haben's gern total simpel, also bau ich nur das Allerntigste ein, um die App schn einfach zu halten. Listen und Filter und Einstellungen braucht man eh nicht tglich, die machen alles nur komplizierter, also bau ich die nicht mit ein."
Und es gibt Apps, die "opinionated" sind: Die ganze App ist nur auf den Geschmack des Entwicklers abgestimmt. Was der Entwickler doof findet, kommt nicht rein. Z. B. wenn der Entwickler das bichen Textformatierung, das Mastodon 4.0 eingefhrt hat, schon doof findet, kann die App nur Plaintext anzeigen, egal, was reinkommt. Und was der Entwickler geil findet, wird unabschaltbar hartgecodet. Wenn der Entwickler z. B. total auf diesen "Hackerlook" mit roter Monospace-Konsolen-Schrift auf schwarzem Grund steht, sieht die App auch immer so aus.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #NichtNurMastodon #MastodonAppsBill Statler What I meant is, for example:
On Hubzilla, I can deny the permission to send me posts in my channel role. Then I can grant that permission to certain connections per contact role.
However, if I grant that permission in my channel role, I cannot configure a contact role so that it denies that permission.
Permissions granted by the channel role are always inherited by contact roles and cannot be overridden. A contact role can't deny a permission which the channel role grants.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Mastodon refuses to implement full HTML rendering for content, including a larger set of text formatting and embedded images because that wouldn't be purist, old-school, Twitter-like microblogging. So if Mastodon actually tried to render fully formated blog posts, it'd mangle them. Linking to the original is a compromise.
As for blogging solutions, there's also Plume, but while it has more features than WriteFreely, it's so sparsely developed that its own devs recommend WriteFreely.
Or you could use Friendica, Hubzilla or the streams repository for blogging. Friendica even lets you "switch" between blog-like Article-type objects (with a title) and microblog-like Note-type objects (without a title). And all three can cover microblogging as well.
However, all three handle dramatically differently from Mastodon. Only Friendica has partial support for the Mastodon API, but Friendica doesn't support polls, neither locally nor in-bound, and Friendica handles Mastodon-style content warnings with BBcode tags. All three require getting your hands dirty on markup code for alt-text. But if you're a blogger, that shouldn't be such a big issue, and at least (streams) also supports Markdown in posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Blog #Blogging #Friendica #Hubzilla #Streams #(streams) #Plume #WriteFreely My current issue with Wayland, at least under Plasma on Debian testing, is that keyboard levels beyond Shift stopped working in Firefox installed natively, as in the Mozilla way, not through apt.
The slight performance improvements in the Firestorm Viewer on Wayland as opposed to X, and even Firestorm has an issue with Wayland which I've had to fix myself, don't justify permanently putting up with this inconvenience.
Installing Firefox through apt is out of question. Anything Debian delivers is painfully outdated, and again, I'm on testing and not on stable. And the Ubuntu PPA is not only not recommended, but it has actually given me headaches in the past.
Also, since I've got Plasma on a 14" laptop, and since Wayland zooms the whole desktop environment by a percentage rather than matching text with a dpi setting, I only get two panes in Hubzilla in Firefox on Wayland on the internal screen.
#Long #LongPost #CWLong #CWLongPost #Linux #Debian #KDEPlasma #Firefox #Firestorm #FirestormViewer #Wayland
Its basic functionality is to keep at least one clone of your identity on another server.
On most Fediverse projects, e.g. Mastodon, your identity is in your account and thus bound to one specific server.
Hubzilla and (streams) put "identity containers" into your account, so-called channels. Your identity is not directly put into your account, but into one of these channels. The channel separates your identity, your connections, your posts, your settings, your files etc. etc. from your login credentials.
This makes two things possible. One, you can have multiple, completely separate identities (channels) on one and the same account, accessible through one and the same login.
Two, and here does nomadic identity come into play: A channel can be cloned to another server.
Such a clone is not a dumb copy like when you move from one Mastodon server to another Mastodon server. It's a real-time, bidirectional, live, hot backup. And it's fully identical to the main instance of your channel, down to the identity, at least as perceived by server applications that know nomadic identity. Anything that happens on the main instance is mirrored to all clones, and anything that happens on a clone is mirrored to the main instance and the other clones.
For example: The main instance of my channel is on hub.netzgemeinde.eu. Thus, my identity is jupiterrowlandhub.netzgemeinde.eu.
I've got one clone on hub.hubzilla.de. Hubzilla and (streams) understand nomadic identity. They know that this clone is the same jupiterrowlandhub.netzgemeinde.eu. Even if I should send something from my clone which I've actually done once when Netzgemeinde was acting up, Hubzilla and (streams) connections still perceive it as coming from jupiterrowlandhub.netzgemeinde.eu.
The big advantage of this is resilience against server shutdowns. This is actually the very reason why Mike invented nomadic identity in the first place: He saw Mistpark/Friendica nodes disappearing into thin air upon short notice or spontaneously. He saw users lose everything from one day or hour or minute to the next and always have to start over from zero. And he knew that the only solution for this problem would be if a user's identity resided on multiple servers simultaneously.
Nomadic identity makes channels even resilient against the shutdown of the server that contains the main instance. You can always declare any clone the main instance. If you still have a main instance, it's demoted to clone. All of your connections on Hubzilla and (streams) are automatically changed accordingly. The only difference in practice between the main instance and a clone is that the main instance is the one that defines the identity.
A byproduct of nomadic identity is that it provides the best way to move an identity from one server to another. It first creates a clone. Then it declares the clone the new main instance, turning the old instance into a clone. Then it deletes the old instance. If the account on the old server doesn't hold any more channels, the whole account is deleted.
So not only can you move with actually absolutely everything, a Mastodon user's wet dream that will probably never come true, but you can do so with relative ease and quite safely, and most of all, you don't leave a dead identity/account behind.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #RedMatrix #Hubzilla #Nomad #Streams #(streams) #NomadicIdentity Either the Bluesky devs genuinely have never heard of Mike Macgirvin , nomadic identity, the Zot protocol, Red/the Red Matrix or Hubzilla, much less of the Nomad protocol or the streams repository. This is actually rather believable because next to nobody outside the bubble around Mike's creations knows about them.
Or, worse yet, they have caught wind of them. But nonetheless, they want to pose as the inventors of a revolutionary, ground-breaking innovation in social networking that has never been done before. You know, like Microsoft invented gloss and transparency effects in operating systems. Never would they admit that a competitor had done it before. And that whoever has done it before is even competition.
And since mass media, tech media, tech bloggers etc. have never heard of Mike's works, just like they've never heard of Compiz and often not even of Linux back in the 2000s, they will all just believe and regurgitate it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #RedMatrix #Hubzilla #Nomad #Streams #(streams) #NomadicIdentity
This has happened to me as well. I remember having to describe for pictures of nebulae in a set of three images I wanted to post. I felt like I couldn't do it up to my own standards, but I had to do it. Had I been able to go all the way, I guess the description of the first image would still be my longest one by far.
Most recently, i.e. three months ago, I skipped a lot of details and actually even some transcripts. An actually unrecognisable drawing on a poster in that picture proved way too hard to describe in my usual detail. Also, I wanted to get it done after some eight hours. So when I described the motel on the advertising poster, I did not transcribe anything, not even the license plate above the office door, and I didn't describe what's inside the rooms with open blinds at all although I should have.
Another classic is when I raise my own standards right after having described and posted one or multiple images, and that brand-new image post is obsolete and outdated right away.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaThen again, the whole effort would probably be halfway futile. I'd barely reach anyone in the Fediverse, even with hundreds of Mastodon contacts. I guess many of them have muted me without unfollowing me because I post stuff they don't want to read, and they don't know how to filter. Some may have blocked me without unfollowing me for the same reason. Others may actually have unfollowed me, but as they keep their followers lists secret, I don't know.
Besides, hardly anyone follows any of the hashtags I'd use on that post, also because only a tiny minority of Mastodon users even know that you can follow hashtags on Mastodon because they couldn't do that on Twitter. And I guess those who do follow one of these hashtags have long since muted or blocked me.
So my reach within the ActivityPub-based Fediverse, especially on Mastodon, is limited to federated timelines. And hardly anyone uses them.
What few are left who might actually see the post I'm planning will most likely ignore it because it will be over 500 characters long. And I can't do that in 500 characters or fewer for obvious reasons: The full image description will have to go somewhere, and that somewhere can only be the post text body itself because it'll be too long and too informative for alt-text.
At least I can't find any traces of entire Mastodon instances having banned me or my home hub. But that could also be that Mastodon doesn't reject posts from banned users or instances and instead receives and deletes them which Hubzilla's delivery reports can't detect.
#Long #LongPost #CWLong #CWLongPost #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Accessibility #A11y #Inclusion #FediverseWorldSightDay #GlobalAccessibilityAwarenessDay I don't have mixed feelings. From my personal experience, and for my own purposes, it just plain sucks. But that's to be expected. It would require extensive pop culture knowledge plus absolutely extreme niche omniscience in my special field. Like, if I've built something in-world, an AI would have to immediately know everything about it.
Yes, it was an in-world rendering.
In comparison with my own 25,271 characters (no, I'm not kidding, go check the link), LLaVA's 558-character description was vague, it was painfully lacking and incomplete, it didn't explain anything because it had no idea what it was really dealing with, and it was even glaringly wrong in some points. It would not helped anyone understand the image.
I've got my doubts that ChatGPT can do much better than LLaVA. And I've got huge doubts that ChatGPT can produce something more detailed, more informative, more explanatory and more accurate than me from any in-world image I'd post. After all, ChatGPT would only have the picture while I could look around in the virtual world itself and see things that ChatGPT can't see.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AI #LLaVA #ChatGPTI'm thinking about posting an in-world picture on May 16th which is Fediverse World Sight Day as well as Global Accessibility Awareness Day. That'd be my first image post in three months. This means the image description should ideally be done until May 15th.
I just don't know what to show yet. It must not contain faces, food or other sensitive elements, otherwise I'd have to link to it rather than embedding it directly into a post. In general, it must not contain any avatars or other depictions of persons because they're too tedious to describe. It should ideally not contain too detailed buildings or more elaborately-crafted plants because they're too hard to describe.
Also, the motive must not be so detail-rich that the post with the image description in it exceeds 50,000 characters due to the long image description. Pleroma and Akkoma reject posts over 50,000 characters, and I have a growing suspicion that at least some Mastodon instances do that, too.
Maybe I can find something in which is after some 16 years of operation. However, only one picture wouldn't do the third-oldest grid in the Hypergrid justice, one chosen mostly with simplicity of the scenery in mind even less. Also, I don't think I want to prepare multiple posts with one image each, seeing as it'd take me about one day to describe each image. And multiple images in one post would inflate the post to sizes that will be rejected by entire Fediverse projects.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #3rdRockGrid #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Accessibility #A11y #Inclusion #FediverseWorldSightDay #GlobalAccessibilityAwarenessDay
Eine Umfrage hat mal ergeben, da einer von vier Mastodon-Nutzern noch nie auch nur von der Existenz von Hubzilla gehrt hat. Und das, obwohl Hubzilla lter ist als Mastodon und schon immer mit Mastodon fderiert war.
Und (streams) ist folgerichtigermaen noch obskurer. Das kennen eigentlich sonst praktisch nur Hubzilla-Nutzer.
Das liegt auch daran, da geschtzt jeder zweite Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Und der Groteil vom Rest hat hchstens mal von Pixelfed, PeerTube oder Threads gehrt.
Mastodon stellt 64% der monatlich aktiven Fediverse-Nutzer. Aber ich schtze, mindestens 95% aller Kommunikation auf Mastodon kommt von Mastodon selbst.
Die meisten Mastodon-Nutzer haben nur andere Mastodon-Nutzer als Kontakte. Bei nicht wenigen haben auch die wieder alle nur Mastodon-Nutzer als Kontakte. Sie leben in Blasen, in denen nur Mastodon existiert.
Die Ausbreitung des Wissens ber das Fediverse ber Mastodon hinaus wird also dadurch erschwert, da es praktisch ausschlielich durch Reply Guys hauptschlich auf Friendica geschieht. Und auf Mastodon gelten Reply Guys als Problem, das bekmpft gehrt.
Auerdem wei auch auf Friendica kaum jemand, da (streams) existiert, und einige noch nicht mal, da Hubzilla existiert. Und die *oma- und *key-Bubbles reden sowieso nicht ber irgendwas, was weder auf ActivityPub aufgebaut wurde (auer Pleroma und Misskey selbst) noch primr Microblogging ist.
Dazu kommt aber noch etwas: (streams) verweigert sich nicht nur eines Namens und einer Markenidentitt, sondern es hat auch keinen eindeutigen Identifikator fr Instanzen als zusammenhngendes Projekt. Mastodon-Instanzen identifizieren sich immer als "mastodon", Hubzilla-Hubs als "hubzilla", aber (streams)-Instanzen knnen sich als alles Mgliche und Unmgliche identifizieren. Es sendet auch keine Nodeinfo-Statistiken. Mike hat den entsprechenden Code mit voller Absicht entfernt.
Somit fehlt es auch ebenso mit voller Absicht auf allen Websites, die Fediverse-Projekte und deren Instanzen listen. The Federation fhrt (streams) nicht. Fediverse Party fhrt (streams) nicht. Fediverse Observer fhrt (streams) nicht. Fediverse.info fhrt (streams) nicht.
Es wre auch sinnlos, (streams) zu fhren. Nicht nur, weil (streams)-Instanzen keine Statistiken senden, sondern auch, weil es unmglich ist, nach (streams)-Instanzen zu crawlen. Mastodon-Instanzen knnen ja gecrawlt werden, indem man alle nimmt, die sich als "mastodon" identifizieren. Aber (streams)-Instanzen identifizieren sich als z. B. "Y" (Begrndung: Y ist nicht X) oder "Get Ready To Rumbly" oder "Tales of My Life" oder das erste Wort des Instanznamen, wenn kein Instanztyp eingetragen ist. Und standardmig ist kein Instanztyp eingetragen. So sind sie fr Crawler nicht eindeutig identifizierbar und somit auch nicht auffindbar.
Im Grunde wird (streams) nur durch sein Code-Repository reprsentiert. Das macht es also schwierig zu finden.
Das totale Fehlen jeglicher Dokumentation drfte eine Extrahrde sein. Ich habe schon gehrt von jemandem, der (streams) komplett aufgegeben hat, weil es keine Dokumentation darber gibt, wie man berhaupt einen Server aufsetzt. Alles luft nur durch Hrensagen, wenn man zufllig auf die richtige Blase stt. Selbst von ffentlichen Instanzen erfhrt man meistens hchstens zufllig, wenn man nicht wei, wo man danach suchen soll.
Zu guter Letzt hat Mike selbst erst vor ein paar Monaten angefangen, verstrkt Werbung zu machen fr das, was er macht. Ich sehe auch, da er jede Menge Daumen hoch bekommt und seine Posts auch oft repeatet werden. Aber leider nicht von reichweitenstrkeren Accounts wie Fediverse Report.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams)I keep seeing pictures from or related to Second Life and OpenSimulator, 3-D virtual worlds that hardly anyone in the Fediverse is familiar with. And they never have alt-text. No visual description, no text transcripts, nothing. Ever. Except my own ones, but they don't count.
Strangely, I've also never seen anyone complain. Or ask the original poster to add alt-text. Or supply their own alt-text for the original poster to add. Not even once.
Does nobody care about the accessibility of posts about virtual worlds Do those who receive such posts have no intersection with those who demand all media in the Fediverse be described, preferably in sufficient detail Do they never come across virtual world posts
Are all Second Life and/or OpenSim users in the Fediverse so out of touch with Mastodon's culture But at the same time, are those who are familiar with Mastodon's culture and eager to enforce it upon all of Mastodon as well as everything that reaches Mastodon so detached from the Second Life and OpenSim communities
Sure, Second Life and/or OpenSim users tend to exist in their own tiny bubbles with no followers from outside. But while almost all OpenSim users in the Fediverse are on one and the same dedicated Mastodon instance with me being their only connection outside it, Second Life users are all over their place, so their posts do show up in the local timelines of general-purpose instances.
Could it be that Mastodon users only care for the accessibility of posts in their personal timeline, but neither in the local nor in the federated timeline
This doesn't mean I'll stop describing my images, even though I could churn out many many more images if I did. But it might mean that I describe them in vain because nobody cares, and that the many hours invested into the descriptions of what few images I've actually posted were ultimately wasted.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonCulture #Inclusion #A11y #Accessibility Hubzilla doesn't have a culture of accessibility at all. It isn't even known which pages or "apps" are accessible in the first place. Besides, the huge majority of my readers are on Mastodon.
What I do is:
I write a fairly short, purely visual description for the alt-text. I do so to satisfy those who absolutely demand there be an image description in the alt-text, no matter if there's already one elsewhere.
Still in the alt-text, this short visual description is followed by a note that says that the actual, fully detailed image description with explanations, text transcripts etc. can be found in the post text. And if you're on Mastodon or a similar Twitter-mimicking microblogging project, the description is in the post text, hidden behind a long post content warning, whereas if you're on Friendica, Hubzilla or (streams), the image description will follow right below the image itself. Or sometimes, when I post multiple images, below the block of embedded images so as not to have a wall of text separate the images.
The alt-text practically always exceeds 800 characters regardless which, I guess, is still much too much for many Mastodon users, also seeing as Hubzilla does not support line feeds in alt-text.
And yes, the actual image description goes into the post itself where hardly any Mastodon user would expect it and where Mastodon's culture sees no place for image descriptions. The post itself is always hidden behing a summary/content warning that reads, "CW: long post (<four or five-digit number> characters" in order to protect those on the official Mastodon mobile app and everyone else on Mastodon who doesn't want to see posts with over 500 characters.
For example, which was three months ago. Fair warning: When I say I write image descriptions that are tens of thousands of characters long, I mean it.
At a bit over 25,000 characters, the description is nowhere near my longest, and while it's the most up-to-date, I found it lacking after posting it already, and I already consider it outdated. If this link opens as a Web page in a browser instead of as a toot in your Mastodon app, then sorry, I can't show you how your Mastodon app renders this post. I could tell you a hashtag under which to find that post, but troet.cafe doesn't know any of my image posts.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Another interesting question is: What if the image description is in English, but it has to transcribe bits of text in the image that are not in English
Last year, I was in a situation in which I had to transcribe a whole lot of signs in an image. Some were in English. Some were in two or three of these languages: English, Germany, rather broken German, French. Others were in Latin.
When a sign was in English, broken German and French, I started with a 100% verbatim transcript of the English part. Then I wrote a 100% verbatim transcript of the German part, spelling mistakes, grammar errors and all. Then I added an English translation below that's as close to literal as possible. Then I wrote a 100% verbatim transcript of the French part. Then, again, I added an English translation below that's as close to literal as possible.
Of course, screen readers won't necessarily be able to switch languages in the middle of a description. But if 100% verbatim transcripts of everything are required, I give them, no matter what. And if people don't understand them, I give a near-literal translation in addition.
Sorry for not linking to the example, but the image description is hopelessly outdated and a bad example, and it'd probably be at least three times as long today.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts I always describe and explain my images on a level of detail that I deem appropriate, considering how niche and obscure what the images show is, and considering that almost nobody in the Fediverse is familiar with anything in them and with what they're about.
This means I have a whole lot to explain for those who wouldn't understand the images otherwise and to describe for blind or visually-impaired users who simply have no idea what the stuff in my images looks like because they've never come across it ever before. My image descriptions practically always exceed Mastodon's alt-text limit of 1,500 characters many times over.
I need almost 1,500 characters alone to explain where I've taken the image, and that doesn't include any visual description yet.
However, I don't know how useful they actually are. If I get feedback at all, it's because I link to my image posts in discussions about image descriptions, and even that's rare. Right after posting these pictures for the first time, I get next to no feedback whatsoever.
It could be that nobody says a word because people only give feedback if they have to complain about something. But they neither complain about the excessive length, nor do they complain that they still don't understand something because I haven't explained it sufficiently, or that they still don't know what something looks like because I haven't described it.
But it could just as well be that nobody even opens the long post content warning, much less reads through the image description in the post text. At best, people completely ignore my image post because it's too long. At worst, they block me for posting over 500 characters in one post which goes against the Mastodon culture (I'm not even on Mastodon myself) and disturbs them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaThings seem to be about to escalate now, but hopefully outside OSW.
That British madcap has attacked another British user in IMs, and he's lying about it in The Box, demanding proof for these attacks, accusing him of being a hacker and threatening to alert the authorities about him.
Upon this, the other Brit has requested the server logs from Satyr Aeon, and it looks like he is actually going to alert the authorities and drag the madcap to court.
The madcap's reaction was the announcement per IM that if this happened, he'd walk into the court room with a gun, kill the other Brit and then shoot himself because he says he has got nothing to lose.
I hope Satyr will provide the logs for this as well. And I halfway expect that madcap to be insane enough to resist arrest and duke it out with the MO19 over this.
Whatever the outcome, I guess nothing will change on OSW itself because the users have take care of stuff themselves.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #OpenSimWorld #Violence #CWViolenceSo how fscked-up is OpenSimWorld with its complete lack of user rules and moderation Yes.
There's a guy with a thousand sock puppet accounts who keeps creating new ones just to attack others and claims to have governmental authorities take care of everything that's going wrong on OSW and in OpenSim in general. Now he has revealed himself to allegedly be British, and he's still implying to have something like the MI6 go against hatespeech on OSW as well as pirated Second Life content in-world.
He's currently duking it out with an good ol', red-blooded, flag-wavin', gun-tote'n all-Amurkin 'Murkin MAGA "patriot" from 'Murkuh who, on a scale from 0 = the most radical Antifa groups to 100 = literally Hitler in 1944, is a solid 500 and insults everyone from 499 downward as a "libtard", who "knows" he can beat anyone in a swearing contest just like 'Murkuh can beat anyone in anything, and who has told me once that he thinks Germans are wimps for not having enough balls to have an ultra-extremist right-wing government.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #OpenSimWorld #USpol #CWUSpol #Libtard #Libtards #MAGA
That's what I mean when I say I write about an extremely obscure niche topic, and I always have a lot to explain for people to get my images.
Unfortunately, the whole topic is probably so special-interest that I have to shove too much down people's throats to give them even only the basics. They might not understand the images either way.
It isn't so much the technology. It doesn't make much of a difference whether Mastodon cuts my 40,000-character image description off at the 1,500-character mark, or whether Hubzilla lets me read only the first 3,500 characters because there's only so much vertical space in my browser window.
The full description goes into the post text either way because it contains explanations that are necessary for people to understand the image, and people e.g. with a severe tremor who can't move a mouse steadily or with a head pointer that they poke around on a keyboard with can't read it when it's in the alt-text because they can't access alt-text.
And when it's in the post text, Mastodon won't cut it off at the 500-character mark and throw the excess 39,500 characters away. If anything, it rejects posts with over 100,000 characters altogether AFAIK.
I know that Pleroma and Akkoma reject posts over 50,000 characters, and I suspect Misskey and the Forkeys to reject even shorter posts. But nobody in my primary audience is on either of these.
The problem is rather the culture. It's a culture that's cultivated on Mastodon and on Mastodon only, that disregards the rest of the Fediverse and how it's different because nobody knows, but that is being forced upon that self-same rest of the Fediverse regardless. If your home instance is connected to Mastodon, you play by Mastodon's unofficial rules or else.
Sad, but true: The rules of one Mastodon instance don't apply to all connected Mastodon instances all the same. They apply to the local timeline, but not to the federated timeline. Other instances may have contradicting rules, and no instance admin is going to enforce rules that apply to other instances, but not their own one.
At the same time, however, Mastodon's overarching unwritten cultural rules do apply to the federated timeline because they apply to all Mastodon instances. And they're forced upon everything that isn't Mastodon all the same.
That's partly because Mastodon users don't even notice when something doesn't come from Mastodon, partly because some of those who do know that the Fediverse is more than Mastodon still believe that everything that isn't Mastodon is either an alternative UI for Mastodon with a couple extra features (Akkoma or Iceshrimp or Friendica is for the Web what Mona or Tusky is for the phone) or bolted onto Mastodon as an add-on otherwise, and it's partly because whoever is the biggest is the boss, and because Mastodon users tend to think Mastodon was there first.
Mastodon's culture includes not only a sufficient description for each image you post, but you're expected to put the full description into the alt-text and only into the alt-text. This comes from adequately describing images in the post text being technically impossible on vanilla Mastodon with only 500 characters minus the actual post text, minus hashtags, minus mentions, minus even content warning.
So for one, Mastodon users expect an image description in the alt-text. That's why I describe each image twice, once with a few hundred characters in the alt-text, once with thousands upon thousands of characters in the post text.
Besides, I expect Mastodon users to be highly irritated when they discover that I've put a detailed image description into the post text rather than into the alt-text where they expect it. Yes, there's an image description in the alt-text. But why is there a longer one in the post text Why isn't the long one in the alt-text where it belongs by Mastodon's standards Why do I refuse to do things like they're done on Mastodon
Okay, so my full image description is too long for alt-text. But why don't I make it shorter then Nobody on Mastodon writes image descriptions that are several thousand characters long. Why don't I write image descriptions like Mastodon users
Also: While Mastodon is fully capable of importing and displaying posts that are tens of thousands of characters long, many many Mastodon users are very opposed to posts longer than 500 characters. They're technically possible, but they're culturally disliked and frowned upon. This mostly applies to those who use the official Mastodon app that can't fold long posts in and expand them if you want to read them, but it isn't limited to those users.
It's another cultural thing: Mastodon cannot post over 500 characters, so Mastodon users aren't used to over 500 characters, so nobody anywhere in the Fediverse must post over 500 characters. Mastodon users actually keep tooting that they want filters which remove everything over 500 characters from their timelines.
And not exactly rarely, they take matters into their own hands. If they spot a post with over 500 characters in their personal timeline, they block the poster upon first strike, but not necessarily without complaining to the user first. Some go as far as doing that when they see a post with over 500 characters in the federated timeline.
In fact, I expect entire Mastodon instances to have blocked non-Mastodon users instance-wide because some local user felt disturbed about their over-500-characters posts and asked the moderation to step in. There may even be instances, not even exactly small ones, that go as far as blocking the entire offending instance.
For these reasons, for me, posting images while having connections all over Mastodon is like treading on raw eggs. I spend 13 hours describing an image in 40,000 characters just to give a casual bystander audience a chance to understand them. I post that thing. A few people may find it helpful. To many, it makes no difference in practice because they don't read my image description. And then there's the unknown number of Mastodon users who take countermeasures or have countermeasures taken by admins/mods because my gargantuan image post disturbs them and/or goes against Mastodon's culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Fediverse #Mastodon #MastodonCulture #500Characters #CharacterLimit #CharacterLimits I'm not even sure if Laconi.ca/StatusNet could quote, much less quote-post. It wanted to be microblogging, and it supported the Twitter API from some point on, but it didn't aim to be a Twitter clone.
As for Friendica or rather Mistpark, I'm convinced it had quote-posts already when it was first released in July, 2010. It didn't try to mimic Twitter either, though, because it was positioned as an alternative to Facebook.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Laconica #Laconi.ca #StatusNet #Mistpark #Friendika #Friendica On the one hand, there's describing images the Mastodon way. It may range from one-liners to descriptions that almost reach 1,500 characters which are seen as absolutely massive and incredibly detailed. But they always go into the alt-text, explanations included. "Image description" and "alt-text" are mutually synonymous on Mastodon. Nobody ever questions that. After all, posts can contain no more than 500 characters.
However, this is mostly geared towards fairly simple real-life photographs which contain lots of elements that don't have to be described because they're uninteresting, and that don't have to be explained because everyone's fairly familiar with them.
And then there's the attitude that any alt-text is better than no alt-text and the idea that AI can describe any and all pictures well enough or even perfectly already now. The latter, of course, comes from people only using AI on simple real-life photographs or social media screenshots.
Those who are on Mastodon not only see these things as given, but they can't imagine them possibly being any different.
On the other hand, I break all these rules.
For one, here on Hubzilla, I don't have a limit for post text, nor do I have a limit for alt-text which has to be grafted into the post text anyway. That is, alt-text is kind of limited because even Hubzilla can only show so much, and it can't scroll through alt-text. Besides, Mastodon, Misskey and all their mutual forks cut off alt-texts from outside at the 1,500-character mark and permanently discard anything that goes beyond. So alt-text remains limited to 1,500 characters.
But posts remain unlimited. If I put an image description into the post text, I can make it as long as I want to or as I have to. And in fact, explanations don't belong into alt-text. Not everyone can access alt-text, and any information only available in alt-text is inaccessible and therefore lost to those who can't.
That's important because my image descriptions have to go with a whole lot of explanation.
That, in turn, is because the pictures I post are nothing like what you'd normally find on Mastodon.
They aren't real-life photographs. They're renderings from inside 3-D virtual worlds. Extremely obscure 3-D virtual worlds even I'm not talking about VRchat or Roblox. The whole system is known to probably not more than one in 200,000 Fediverse users, and particular places may be known to not even one in a million Fediverse users. Chances are I'm the only one in over ten million Fediverse users who knows that particular place where an image is from.
This means two things.
One, almost nobody who comes across my image posts knows anything about anything in these pictures. They don't get the pictures at all. And blind or visually-impaired users wouldn't even know what what's in the pictures looks like if I told them what's in the pictures.
Two, on the other hand, people could pretty well be interested in them. After all, I'm talking about something that has been referring to itself as a "metaverse" regularly since early 2007. "The Metaverse" is real, it's living, breathing, much to everyone's surprise. It's got nothing to do with Meta Platforms. And there has to be cool stuff in it if it's worth showing in-world pictures.
So people might become so curious about this discovery that they want to know as much as they can. But they know nothing, so they don't get the images in the first place if these images don't come with extensive explanations and descriptions.
This is the main reason why my image descriptions grow so massively long.
And with "massively long", I mean tens of thousands of characters. My most recent example is , and although it's the most up-to-date, I'm not even satisfied with it. Two posts with multiple images each and even longer descriptions for the respectively first one, albeit a bit more out-dated, are and .
As you may be able to see, what I do is: I write a fairly short, purely visual description to have at least some description in the alt-text so nobody can complain that the alt-text doesn't actually describe the image. Also, the alt-text mentions that the actual, more detailed and explanatory image description is in the post text, including where and how to find it. That's because I'd never post something of that length with a summary/content warning, so for users on ActivityPub-based microblogging projects, the full image description is hidden.
Not only has nobody ever done anything like this on Mastodon, but it's completely unimaginable because it isn't even possible on the vast majority of instances. My longest picture post is way longer than 150 Mastodon toots.
This gives me experiences with image descriptions that nobody else has ever made, especially not on Mastodon. Those many Mastodon users who "know" it's set in stone that the Mastodon way is the only way sometimes deserve to read about someone else's completely different point of view.
In fact, this becomes a necessity whenever Mastodon users want to establish image-describing standards that a) only apply to Mastodon with its limitations and b) only apply to the kind of image content that's usually posted on Mastodon, but that'd be completely and utterly incompatible with my images and my way of describing them to the point of rendering my image descriptions invalid.
But there may also be other cases in which I differ from the general Mastodon way of thinking.
Memes, for example. Memes in posts should always be described accordingly and explained if necessary. From this, I deduce that template-based memes require explanations of the templates used. At the same time, I know that the majority of Fediverse users prefers having all information in the same place as the image itself over having to get extra information from another website which, for mobile users, means from a different app.
In summary, this means that template-based memes require explanations that go even beyond KnowYourMeme because KnowYourMeme relies on linking to other pages on the same site, e.g. to explain things like 4chan, SomethingAwful, Wojak, snowclones or advice animals. But since the Fediverse prefers to have it all in one place, all these extra explanations have to be woven into the meme description and explanation specific to this particular meme. Nobody on Mastodon has ever thought of this.
Another example is the recurring talk about describing the automatically-selected image in a Mastodon link preview. It's important to know here that it's next to impossible to tell which image from which link will be picked as the preview image, if any. Also, while Hubzilla has a preview feature for posts in the making, it does not have link previews.
Not only does this mean that the link preview image on Mastodon will have to be identified and described after sending the post, but Hubzilla users will have to go to a Mastodon instance and wait until their images have federated there before they can edit the post and describe the image. This, of course, is a greater effort and takes longer than for Mastodon users who can see the link preview in their own timelines immediately or shortly after posting. In the meantime, the post will spend even more time spreading around Mastodon with no image description, and many many more people will see it without an image description, and they might react accordingly, not expecting an image description to be added rather soon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
You can stay within the Fediverse, connected to Mastodon, and still have quote-posts. Because the Fediverse is not only Mastodon.
Check out Pleroma or Akkoma or any of the other Pleroma forks. Or Misskey or Firefish or Iceshrimp or Sharkey or any of the other Forkeys. Or Friendica or Hubzilla or (streams). They've all got quote-posts already now, and they can quote-post each other as well as Mastodon. And Mastodon won't be able to stop them.
In fact, both Friendica and Hubzilla have had both quotes and quote-posts long before Mastodon was even made. And they've been federated with Mastodon ever since the moment Mastodon was launched.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ReplyGuy #CWReplyGuy #Mansplaining #CWMansplaining #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Pleroma #Akkoma #Misskey #Firefish #Iceshrimp #Sharkey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedSharesI think I should add some the filter-triggering hashtags #ReplyGuy, #CWReplyGuy, #Mansplaining and #CWMansplaining to my standard repertoire, in case my other filter-triggering hashtags aren't sufficient.
They'd make it 51 characters more likely that I'll also have to add #Long, #LongPost, #CWLong and #CWLongPost because what I've written surpasses the 500-character mark, much to many Mastodon users' chagrin.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta Denen ist von dem Augenblick an, wo sie auf Twitter abgeworben wurden, praktisch durchgngig der Arsch gepudert worden. Die sind immer verhtschelt worden, sonst wren sie ja gar nicht erst hier.
Und was sie verlangen, verlangen sie nicht fr Mastodon allgemeinen, sondern ganz speziell fr die Instanz, auf der sie sind. Selbst wenn das mastodon.social ist, wo ihre Interessen denen von hunderttausenden anderen Nutzern kollidieren, die auch nicht umziehen wollen.
Die ganzen Friendica- und Hubzilla-Urgesteine haben allen Grund, darber zu kotzen. Die sind nicht mit lauter Htscheleien von Microblogging fr Doofe per Handy-App auf anderes Micro-Blogging fr Doofe per Handy-App gefhrt worden. Die kamen entweder von Facebook, wo ihnen der Kampf mit den Privacy-Einstellungen zu doof wurde, oder von gar nix.
Die haben sich damals alles selbst draufgeschafft. Am PC. Ohne App, weil's meistens gar keine gab. Ohne Drittwebsites, die ihnen alles erklrt haben. Mit noch nicht mal besonders benutzerfreundlicher Dokumentation, wenn berhaupt. Und mit einem Minimum an fremder Hilfe, wenn berhaupt. Und nicht wenige haben's sogar geschafft bis zum Headless-Miniserver auf Linux-Basis in ihren eigenen vier Wnden.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
You wouldn't have needed at least some of them.
If you aren't afraid of going onto people's nerves by posting Fediverse content, you don't need #CWFediMeta and #CWFediverseMeta.
And if, without these two and without #Long #LongPost #CWLong #CWLongPost, your reply had been under 500 characters, you wouldn't have needed these four either.
Neither have anything to do with Mastodon. The streams repository is the latest in a series of developments that started yesterday 14 years ago with Mistpark. That was six years before Mastodon when Eugen Rochko was still a school kid. And Hubzilla is one of the stopovers on this path and ten months older than Mastodon itself, created by Mike as well.
Not to mention that both have absolutely nothing in common with Mastodon, technologically-wise, except for supporting ActivityPub. And both Mike and Mario hate Mastodon and its home-brew, non-standard, proprietary wanna-be "standards" while rejecting actual standards with a flaming passion because it hinders innovation in the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaYou think decentralised social networking was invented with Mastodon Think twice.
It was almost exactly 14 years ago, on May 13th, 2010, that Mike Macgirvin conceived Mistpark. All by itself revolutionary and with features which no-one else has ever built into a decentralised project until today, it was only the first step of a long journey which led to , , , all three still before Mastodon, and eventually .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mistpark #Friendika #Friendica #Hubzilla #Streams #(streams)
Pipeline release! nf-core/mag v3.0.0 - mag 3.0.0 - Magenta Magpie!
Please see the changelog:
-read-sequencing -sequencing
I've launched my next image post project. Yes, what'd take you seconds will take me at least one day. And what you may do every couple of minutes, I haven't done in over three months due to the effort.And I mean the effort of describing the image.
Since the sims of 3rd Rock Grid are being rescued and largely already have been, there's no point in showing one of them anymore. So I'm looking for a motive elsewhere.
It's hard to find something that's interesting to look at while still not impossible for me to describe adequately before the end of the day.
I'm currently looking around NyAlfheim in OSgrid. I've found a scene that's absolutely gorgeous. But it'd also absolutely be hell to describe, what with all the different buildings and what's inside the buildings and the furniture in front of the buildings and the boats and all the other decoration.
Also, there are static human figures plus one human animesh figure in the scene which means eye contact which, in turn, means I'd have to link to the image instead of embedding it because that's the only way I have to hide the image from sensitive Mastodon users.
On the other hand, I don't want to show something that's so simple that it's lacklustre and not a bit interesting.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Long
Weekly Sketch #205 - 17th of May. A Classic Chinese Dragon, drawn in my style (I used the photo of a Chinese Dragon statue from a temple in Hongkong for reference).
Okay, the mystery is solved. I've managed to catch someone from 3RG.The big event that Alia wanted never had a chance to materialise. All they managed to do was a farewell party in 3RG yesterday. Today there's nothing. And the welcome party in ZetaWorlds will be at some point in the next weeks.
They didn't even manage to advertise or communicate anything. I guess they had no Hypergridders yesterday, only residents.
Oh well, good thing there are more events around the Hypergrid this evening.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #3rdRockGrid Bei ActivityPub-basierten Microbloggingprojekten haben im allgemeinen alle Instanzen desselben Projekts denselben Funktionsumfang. Vielleicht unterscheiden sie sich mal in der Auswahl der Emojis oder der maximalen Postlnge.
Aber Riesenunterschiede von Instanz zu Instanz in den Features wie bei den modular aufgebauten Friendica, Hubzilla und (streams) hast du da nicht.
Und die Unterschiede zwischen Mastodon einerseits und z. B. Misskey oder Pleroma andererseits haben nichts mit Instanzen zu tun. Das sind vllig unterschiedliche, voneinander unabhngige Projekte, also noch nicht mal Hardforks voneinander.
Bei vielen Apps ist der Grund, warum sie keine Funktionen ber Mastodon 3.x hinaus untersttzen, ganz einfach: Als der Entwickler anfing, kannte er nur Mastodon. Als der erste stabile Punktrelease raus war, kannte der Entwickler immer noch nur Mastodon. Als der Entwickler erfuhr, da es im Fediverse auch noch was anderes als Mastodon gibt mit ganz anderen Fhigkeiten, war es zu spt, die zu implementieren.
Es gibt aber nicht nur Entwickler, die nur gegen Mastodon bauen, weil sie nur Mastodon kennen. Es gibt auch Entwickler, die sagen: "Das ist 'ne iPhone-App, iPhone-Nutzer haben's gern total simpel, also bau ich nur das Allerntigste ein, um die App schn einfach zu halten. Listen und Filter und Einstellungen braucht man eh nicht tglich, die machen alles nur komplizierter, also bau ich die nicht mit ein."
Und es gibt Apps, die "opinionated" sind: Die ganze App ist nur auf den Geschmack des Entwicklers abgestimmt. Was der Entwickler doof findet, kommt nicht rein. Z. B. wenn der Entwickler das bichen Textformatierung, das Mastodon 4.0 eingefhrt hat, schon doof findet, kann die App nur Plaintext anzeigen, egal, was reinkommt. Und was der Entwickler geil findet, wird unabschaltbar hartgecodet. Wenn der Entwickler z. B. total auf diesen "Hackerlook" mit roter Monospace-Konsolen-Schrift auf schwarzem Grund steht, sieht die App auch immer so aus.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #NichtNurMastodon #MastodonAppsBill Statler What I meant is, for example:
On Hubzilla, I can deny the permission to send me posts in my channel role. Then I can grant that permission to certain connections per contact role.
However, if I grant that permission in my channel role, I cannot configure a contact role so that it denies that permission.
Permissions granted by the channel role are always inherited by contact roles and cannot be overridden. A contact role can't deny a permission which the channel role grants.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
nagano, japan. what we did for our anniversary! (its alpacas) (in japan!) weve been married for 13 years so we went and had some fun. hel
Admissions suspension at Peterborough long-term care part of systemic challenges, advocates argue
Advocacy groups Concerned Friends and the Ontario Association of Residents Councils weigh in on the admissions suspension issue May 2 for St. Joseph's at Fleming in Peterborough.
-termCare -TermCare
Mastodon refuses to implement full HTML rendering for content, including a larger set of text formatting and embedded images because that wouldn't be purist, old-school, Twitter-like microblogging. So if Mastodon actually tried to render fully formated blog posts, it'd mangle them. Linking to the original is a compromise.
As for blogging solutions, there's also Plume, but while it has more features than WriteFreely, it's so sparsely developed that its own devs recommend WriteFreely.
Or you could use Friendica, Hubzilla or the streams repository for blogging. Friendica even lets you "switch" between blog-like Article-type objects (with a title) and microblog-like Note-type objects (without a title). And all three can cover microblogging as well.
However, all three handle dramatically differently from Mastodon. Only Friendica has partial support for the Mastodon API, but Friendica doesn't support polls, neither locally nor in-bound, and Friendica handles Mastodon-style content warnings with BBcode tags. All three require getting your hands dirty on markup code for alt-text. But if you're a blogger, that shouldn't be such a big issue, and at least (streams) also supports Markdown in posts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Blog #Blogging #Friendica #Hubzilla #Streams #(streams) #Plume #WriteFreely My current issue with Wayland, at least under Plasma on Debian testing, is that keyboard levels beyond Shift stopped working in Firefox installed natively, as in the Mozilla way, not through apt.
The slight performance improvements in the Firestorm Viewer on Wayland as opposed to X, and even Firestorm has an issue with Wayland which I've had to fix myself, don't justify permanently putting up with this inconvenience.
Installing Firefox through apt is out of question. Anything Debian delivers is painfully outdated, and again, I'm on testing and not on stable. And the Ubuntu PPA is not only not recommended, but it has actually given me headaches in the past.
Also, since I've got Plasma on a 14" laptop, and since Wayland zooms the whole desktop environment by a percentage rather than matching text with a dpi setting, I only get two panes in Hubzilla in Firefox on Wayland on the internal screen.
#Long #LongPost #CWLong #CWLongPost #Linux #Debian #KDEPlasma #Firefox #Firestorm #FirestormViewer #Wayland
MySQL 8.4.0
LTS Percona distribution
MySQL 8.0 EoL 2026/04/30
8.4What Is New in MySQL 8.4 since MySQL 8.0 8.0
InnoDB
MySQL Replication: tagged GTIDs re
#84
Deprived of interruptions, away from podcasts or audio books I try to use the sudden opportunity and think about something meaningful, but the silence doesn't work as expected making me formulate sentences like: 'German shepherds have beauty spots. Very much like Eva Mendes''.
Its basic functionality is to keep at least one clone of your identity on another server.
On most Fediverse projects, e.g. Mastodon, your identity is in your account and thus bound to one specific server.
Hubzilla and (streams) put "identity containers" into your account, so-called channels. Your identity is not directly put into your account, but into one of these channels. The channel separates your identity, your connections, your posts, your settings, your files etc. etc. from your login credentials.
This makes two things possible. One, you can have multiple, completely separate identities (channels) on one and the same account, accessible through one and the same login.
Two, and here does nomadic identity come into play: A channel can be cloned to another server.
Such a clone is not a dumb copy like when you move from one Mastodon server to another Mastodon server. It's a real-time, bidirectional, live, hot backup. And it's fully identical to the main instance of your channel, down to the identity, at least as perceived by server applications that know nomadic identity. Anything that happens on the main instance is mirrored to all clones, and anything that happens on a clone is mirrored to the main instance and the other clones.
For example: The main instance of my channel is on hub.netzgemeinde.eu. Thus, my identity is jupiterrowlandhub.netzgemeinde.eu.
I've got one clone on hub.hubzilla.de. Hubzilla and (streams) understand nomadic identity. They know that this clone is the same jupiterrowlandhub.netzgemeinde.eu. Even if I should send something from my clone which I've actually done once when Netzgemeinde was acting up, Hubzilla and (streams) connections still perceive it as coming from jupiterrowlandhub.netzgemeinde.eu.
The big advantage of this is resilience against server shutdowns. This is actually the very reason why Mike invented nomadic identity in the first place: He saw Mistpark/Friendica nodes disappearing into thin air upon short notice or spontaneously. He saw users lose everything from one day or hour or minute to the next and always have to start over from zero. And he knew that the only solution for this problem would be if a user's identity resided on multiple servers simultaneously.
Nomadic identity makes channels even resilient against the shutdown of the server that contains the main instance. You can always declare any clone the main instance. If you still have a main instance, it's demoted to clone. All of your connections on Hubzilla and (streams) are automatically changed accordingly. The only difference in practice between the main instance and a clone is that the main instance is the one that defines the identity.
A byproduct of nomadic identity is that it provides the best way to move an identity from one server to another. It first creates a clone. Then it declares the clone the new main instance, turning the old instance into a clone. Then it deletes the old instance. If the account on the old server doesn't hold any more channels, the whole account is deleted.
So not only can you move with actually absolutely everything, a Mastodon user's wet dream that will probably never come true, but you can do so with relative ease and quite safely, and most of all, you don't leave a dead identity/account behind.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #RedMatrix #Hubzilla #Nomad #Streams #(streams) #NomadicIdentity Either the Bluesky devs genuinely have never heard of Mike Macgirvin , nomadic identity, the Zot protocol, Red/the Red Matrix or Hubzilla, much less of the Nomad protocol or the streams repository. This is actually rather believable because next to nobody outside the bubble around Mike's creations knows about them.
Or, worse yet, they have caught wind of them. But nonetheless, they want to pose as the inventors of a revolutionary, ground-breaking innovation in social networking that has never been done before. You know, like Microsoft invented gloss and transparency effects in operating systems. Never would they admit that a competitor had done it before. And that whoever has done it before is even competition.
And since mass media, tech media, tech bloggers etc. have never heard of Mike's works, just like they've never heard of Compiz and often not even of Linux back in the 2000s, they will all just believe and regurgitate it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #RedMatrix #Hubzilla #Nomad #Streams #(streams) #NomadicIdentity
sometimes I have provided what I would consider less than adequate descriptions because it has been really difficult to come up with a good one.
This has happened to me as well. I remember having to describe for pictures of nebulae in a set of three images I wanted to post. I felt like I couldn't do it up to my own standards, but I had to do it. Had I been able to go all the way, I guess the description of the first image would still be my longest one by far.
Most recently, i.e. three months ago, I skipped a lot of details and actually even some transcripts. An actually unrecognisable drawing on a poster in that picture proved way too hard to describe in my usual detail. Also, I wanted to get it done after some eight hours. So when I described the motel on the advertising poster, I did not transcribe anything, not even the license plate above the office door, and I didn't describe what's inside the rooms with open blinds at all although I should have.
Another classic is when I raise my own standards right after having described and posted one or multiple images, and that brand-new image post is obsolete and outdated right away.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaThen again, the whole effort would probably be halfway futile. I'd barely reach anyone in the Fediverse, even with hundreds of Mastodon contacts. I guess many of them have muted me without unfollowing me because I post stuff they don't want to read, and they don't know how to filter. Some may have blocked me without unfollowing me for the same reason. Others may actually have unfollowed me, but as they keep their followers lists secret, I don't know.
Besides, hardly anyone follows any of the hashtags I'd use on that post, also because only a tiny minority of Mastodon users even know that you can follow hashtags on Mastodon because they couldn't do that on Twitter. And I guess those who do follow one of these hashtags have long since muted or blocked me.
So my reach within the ActivityPub-based Fediverse, especially on Mastodon, is limited to federated timelines. And hardly anyone uses them.
What few are left who might actually see the post I'm planning will most likely ignore it because it will be over 500 characters long. And I can't do that in 500 characters or fewer for obvious reasons: The full image description will have to go somewhere, and that somewhere can only be the post text body itself because it'll be too long and too informative for alt-text.
At least I can't find any traces of entire Mastodon instances having banned me or my home hub. But that could also be that Mastodon doesn't reject posts from banned users or instances and instead receives and deletes them which Hubzilla's delivery reports can't detect.
#Long #LongPost #CWLong #CWLongPost #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Accessibility #A11y #Inclusion #FediverseWorldSightDay #GlobalAccessibilityAwarenessDay I don't have mixed feelings. From my personal experience, and for my own purposes, it just plain sucks. But that's to be expected. It would require extensive pop culture knowledge plus absolutely extreme niche omniscience in my special field. Like, if I've built something in-world, an AI would have to immediately know everything about it.
Yes, it was an in-world rendering.
In comparison with my own 25,271 characters (no, I'm not kidding, go check the link), LLaVA's 558-character description was vague, it was painfully lacking and incomplete, it didn't explain anything because it had no idea what it was really dealing with, and it was even glaringly wrong in some points. It would not helped anyone understand the image.
I've got my doubts that ChatGPT can do much better than LLaVA. And I've got huge doubts that ChatGPT can produce something more detailed, more informative, more explanatory and more accurate than me from any in-world image I'd post. After all, ChatGPT would only have the picture while I could look around in the virtual world itself and see things that ChatGPT can't see.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AI #LLaVA #ChatGPTI'm thinking about posting an in-world picture on May 16th which is Fediverse World Sight Day as well as Global Accessibility Awareness Day. That'd be my first image post in three months. This means the image description should ideally be done until May 15th.
I just don't know what to show yet. It must not contain faces, food or other sensitive elements, otherwise I'd have to link to it rather than embedding it directly into a post. In general, it must not contain any avatars or other depictions of persons because they're too tedious to describe. It should ideally not contain too detailed buildings or more elaborately-crafted plants because they're too hard to describe.
Also, the motive must not be so detail-rich that the post with the image description in it exceeds 50,000 characters due to the long image description. Pleroma and Akkoma reject posts over 50,000 characters, and I have a growing suspicion that at least some Mastodon instances do that, too.
Maybe I can find something in which is after some 16 years of operation. However, only one picture wouldn't do the third-oldest grid in the Hypergrid justice, one chosen mostly with simplicity of the scenery in mind even less. Also, I don't think I want to prepare multiple posts with one image each, seeing as it'd take me about one day to describe each image. And multiple images in one post would inflate the post to sizes that will be rejected by entire Fediverse projects.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #3rdRockGrid #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Accessibility #A11y #Inclusion #FediverseWorldSightDay #GlobalAccessibilityAwarenessDay
Risk of harm: Ontario suspends admissions to Peterborough long-term care facility
Inspections conducted in February and March found a number of issues including patient neglect, improper care and injuries.
-termCareAct -termCare
Risk of harm Ontario suspends admissions to Peterborough long-term care facility
Inspections conducted in February and March found a number of issues including patient neglect, improper care and injuries.
-termCareAct -termCare
Risk of harm Ontario suspends admissions to Peterborough long-term care facility
Inspections conducted in February and March found a number of issues including patient neglect, improper care and injuries.
-termCareAct -termCare
Ontario suspends admissions to Peterborough long-term care facility
A long-term care inspections branch director says the order comes under Sec. 56 of the Fixing Long-term Care Act.
-termCareAct -termCare
Ontario suspends admissions to Peterborough long-term care facility
A long-term care inspections branch director says the order comes under Sec. 56 of the Fixing Long-term Care Act.
-termCareAct -termCare
Eine Umfrage hat mal ergeben, da einer von vier Mastodon-Nutzern noch nie auch nur von der Existenz von Hubzilla gehrt hat. Und das, obwohl Hubzilla lter ist als Mastodon und schon immer mit Mastodon fderiert war.
Und (streams) ist folgerichtigermaen noch obskurer. Das kennen eigentlich sonst praktisch nur Hubzilla-Nutzer.
Das liegt auch daran, da geschtzt jeder zweite Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Und der Groteil vom Rest hat hchstens mal von Pixelfed, PeerTube oder Threads gehrt.
Mastodon stellt 64% der monatlich aktiven Fediverse-Nutzer. Aber ich schtze, mindestens 95% aller Kommunikation auf Mastodon kommt von Mastodon selbst.
Die meisten Mastodon-Nutzer haben nur andere Mastodon-Nutzer als Kontakte. Bei nicht wenigen haben auch die wieder alle nur Mastodon-Nutzer als Kontakte. Sie leben in Blasen, in denen nur Mastodon existiert.
Die Ausbreitung des Wissens ber das Fediverse ber Mastodon hinaus wird also dadurch erschwert, da es praktisch ausschlielich durch Reply Guys hauptschlich auf Friendica geschieht. Und auf Mastodon gelten Reply Guys als Problem, das bekmpft gehrt.
Auerdem wei auch auf Friendica kaum jemand, da (streams) existiert, und einige noch nicht mal, da Hubzilla existiert. Und die *oma- und *key-Bubbles reden sowieso nicht ber irgendwas, was weder auf ActivityPub aufgebaut wurde (auer Pleroma und Misskey selbst) noch primr Microblogging ist.
Dazu kommt aber noch etwas: (streams) verweigert sich nicht nur eines Namens und einer Markenidentitt, sondern es hat auch keinen eindeutigen Identifikator fr Instanzen als zusammenhngendes Projekt. Mastodon-Instanzen identifizieren sich immer als "mastodon", Hubzilla-Hubs als "hubzilla", aber (streams)-Instanzen knnen sich als alles Mgliche und Unmgliche identifizieren. Es sendet auch keine Nodeinfo-Statistiken. Mike hat den entsprechenden Code mit voller Absicht entfernt.
Somit fehlt es auch ebenso mit voller Absicht auf allen Websites, die Fediverse-Projekte und deren Instanzen listen. The Federation fhrt (streams) nicht. Fediverse Party fhrt (streams) nicht. Fediverse Observer fhrt (streams) nicht. Fediverse.info fhrt (streams) nicht.
Es wre auch sinnlos, (streams) zu fhren. Nicht nur, weil (streams)-Instanzen keine Statistiken senden, sondern auch, weil es unmglich ist, nach (streams)-Instanzen zu crawlen. Mastodon-Instanzen knnen ja gecrawlt werden, indem man alle nimmt, die sich als "mastodon" identifizieren. Aber (streams)-Instanzen identifizieren sich als z. B. "Y" (Begrndung: Y ist nicht X) oder "Get Ready To Rumbly" oder "Tales of My Life" oder das erste Wort des Instanznamen, wenn kein Instanztyp eingetragen ist. Und standardmig ist kein Instanztyp eingetragen. So sind sie fr Crawler nicht eindeutig identifizierbar und somit auch nicht auffindbar.
Im Grunde wird (streams) nur durch sein Code-Repository reprsentiert. Das macht es also schwierig zu finden.
Das totale Fehlen jeglicher Dokumentation drfte eine Extrahrde sein. Ich habe schon gehrt von jemandem, der (streams) komplett aufgegeben hat, weil es keine Dokumentation darber gibt, wie man berhaupt einen Server aufsetzt. Alles luft nur durch Hrensagen, wenn man zufllig auf die richtige Blase stt. Selbst von ffentlichen Instanzen erfhrt man meistens hchstens zufllig, wenn man nicht wei, wo man danach suchen soll.
Zu guter Letzt hat Mike selbst erst vor ein paar Monaten angefangen, verstrkt Werbung zu machen fr das, was er macht. Ich sehe auch, da er jede Menge Daumen hoch bekommt und seine Posts auch oft repeatet werden. Aber leider nicht von reichweitenstrkeren Accounts wie Fediverse Report.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Streams #(streams)I keep seeing pictures from or related to Second Life and OpenSimulator, 3-D virtual worlds that hardly anyone in the Fediverse is familiar with. And they never have alt-text. No visual description, no text transcripts, nothing. Ever. Except my own ones, but they don't count.
Strangely, I've also never seen anyone complain. Or ask the original poster to add alt-text. Or supply their own alt-text for the original poster to add. Not even once.
Does nobody care about the accessibility of posts about virtual worlds Do those who receive such posts have no intersection with those who demand all media in the Fediverse be described, preferably in sufficient detail Do they never come across virtual world posts
Are all Second Life and/or OpenSim users in the Fediverse so out of touch with Mastodon's culture But at the same time, are those who are familiar with Mastodon's culture and eager to enforce it upon all of Mastodon as well as everything that reaches Mastodon so detached from the Second Life and OpenSim communities
Sure, Second Life and/or OpenSim users tend to exist in their own tiny bubbles with no followers from outside. But while almost all OpenSim users in the Fediverse are on one and the same dedicated Mastodon instance with me being their only connection outside it, Second Life users are all over their place, so their posts do show up in the local timelines of general-purpose instances.
Could it be that Mastodon users only care for the accessibility of posts in their personal timeline, but neither in the local nor in the federated timeline
This doesn't mean I'll stop describing my images, even though I could churn out many many more images if I did. But it might mean that I describe them in vain because nobody cares, and that the many hours invested into the descriptions of what few images I've actually posted were ultimately wasted.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonCulture #Inclusion #A11y #Accessibility Hubzilla doesn't have a culture of accessibility at all. It isn't even known which pages or "apps" are accessible in the first place. Besides, the huge majority of my readers are on Mastodon.
What I do is:
I write a fairly short, purely visual description for the alt-text. I do so to satisfy those who absolutely demand there be an image description in the alt-text, no matter if there's already one elsewhere.
Still in the alt-text, this short visual description is followed by a note that says that the actual, fully detailed image description with explanations, text transcripts etc. can be found in the post text. And if you're on Mastodon or a similar Twitter-mimicking microblogging project, the description is in the post text, hidden behind a long post content warning, whereas if you're on Friendica, Hubzilla or (streams), the image description will follow right below the image itself. Or sometimes, when I post multiple images, below the block of embedded images so as not to have a wall of text separate the images.
The alt-text practically always exceeds 800 characters regardless which, I guess, is still much too much for many Mastodon users, also seeing as Hubzilla does not support line feeds in alt-text.
And yes, the actual image description goes into the post itself where hardly any Mastodon user would expect it and where Mastodon's culture sees no place for image descriptions. The post itself is always hidden behing a summary/content warning that reads, "CW: long post (<four or five-digit number> characters" in order to protect those on the official Mastodon mobile app and everyone else on Mastodon who doesn't want to see posts with over 500 characters.
For example, which was three months ago. Fair warning: When I say I write image descriptions that are tens of thousands of characters long, I mean it.
At a bit over 25,000 characters, the description is nowhere near my longest, and while it's the most up-to-date, I found it lacking after posting it already, and I already consider it outdated. If this link opens as a Web page in a browser instead of as a toot in your Mastodon app, then sorry, I can't show you how your Mastodon app renders this post. I could tell you a hashtag under which to find that post, but troet.cafe doesn't know any of my image posts.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Another interesting question is: What if the image description is in English, but it has to transcribe bits of text in the image that are not in English
Last year, I was in a situation in which I had to transcribe a whole lot of signs in an image. Some were in English. Some were in two or three of these languages: English, Germany, rather broken German, French. Others were in Latin.
When a sign was in English, broken German and French, I started with a 100% verbatim transcript of the English part. Then I wrote a 100% verbatim transcript of the German part, spelling mistakes, grammar errors and all. Then I added an English translation below that's as close to literal as possible. Then I wrote a 100% verbatim transcript of the French part. Then, again, I added an English translation below that's as close to literal as possible.
Of course, screen readers won't necessarily be able to switch languages in the middle of a description. But if 100% verbatim transcripts of everything are required, I give them, no matter what. And if people don't understand them, I give a near-literal translation in addition.
Sorry for not linking to the example, but the image description is hopelessly outdated and a bad example, and it'd probably be at least three times as long today.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts I always describe and explain my images on a level of detail that I deem appropriate, considering how niche and obscure what the images show is, and considering that almost nobody in the Fediverse is familiar with anything in them and with what they're about.
This means I have a whole lot to explain for those who wouldn't understand the images otherwise and to describe for blind or visually-impaired users who simply have no idea what the stuff in my images looks like because they've never come across it ever before. My image descriptions practically always exceed Mastodon's alt-text limit of 1,500 characters many times over.
I need almost 1,500 characters alone to explain where I've taken the image, and that doesn't include any visual description yet.
However, I don't know how useful they actually are. If I get feedback at all, it's because I link to my image posts in discussions about image descriptions, and even that's rare. Right after posting these pictures for the first time, I get next to no feedback whatsoever.
It could be that nobody says a word because people only give feedback if they have to complain about something. But they neither complain about the excessive length, nor do they complain that they still don't understand something because I haven't explained it sufficiently, or that they still don't know what something looks like because I haven't described it.
But it could just as well be that nobody even opens the long post content warning, much less reads through the image description in the post text. At best, people completely ignore my image post because it's too long. At worst, they block me for posting over 500 characters in one post which goes against the Mastodon culture (I'm not even on Mastodon myself) and disturbs them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaThings seem to be about to escalate now, but hopefully outside OSW.
That British madcap has attacked another British user in IMs, and he's lying about it in The Box, demanding proof for these attacks, accusing him of being a hacker and threatening to alert the authorities about him.
Upon this, the other Brit has requested the server logs from Satyr Aeon, and it looks like he is actually going to alert the authorities and drag the madcap to court.
The madcap's reaction was the announcement per IM that if this happened, he'd walk into the court room with a gun, kill the other Brit and then shoot himself because he says he has got nothing to lose.
I hope Satyr will provide the logs for this as well. And I halfway expect that madcap to be insane enough to resist arrest and duke it out with the MO19 over this.
Whatever the outcome, I guess nothing will change on OSW itself because the users have take care of stuff themselves.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #OpenSimWorld #Violence #CWViolenceSo how fscked-up is OpenSimWorld with its complete lack of user rules and moderation Yes.
There's a guy with a thousand sock puppet accounts who keeps creating new ones just to attack others and claims to have governmental authorities take care of everything that's going wrong on OSW and in OpenSim in general. Now he has revealed himself to allegedly be British, and he's still implying to have something like the MI6 go against hatespeech on OSW as well as pirated Second Life content in-world.
He's currently duking it out with an good ol', red-blooded, flag-wavin', gun-tote'n all-Amurkin 'Murkin MAGA "patriot" from 'Murkuh who, on a scale from 0 = the most radical Antifa groups to 100 = literally Hitler in 1944, is a solid 500 and insults everyone from 499 downward as a "libtard", who "knows" he can beat anyone in a swearing contest just like 'Murkuh can beat anyone in anything, and who has told me once that he thinks Germans are wimps for not having enough balls to have an ultra-extremist right-wing government.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #OpenSimWorld #USpol #CWUSpol #Libtard #Libtards #MAGA
but honestly a lot of it just goes over my head past a certain point.
That's what I mean when I say I write about an extremely obscure niche topic, and I always have a lot to explain for people to get my images.
Unfortunately, the whole topic is probably so special-interest that I have to shove too much down people's throats to give them even only the basics. They might not understand the images either way.
But I do see your frustrations on things like post limits and alt text character limits and such.
It isn't so much the technology. It doesn't make much of a difference whether Mastodon cuts my 40,000-character image description off at the 1,500-character mark, or whether Hubzilla lets me read only the first 3,500 characters because there's only so much vertical space in my browser window.
The full description goes into the post text either way because it contains explanations that are necessary for people to understand the image, and people e.g. with a severe tremor who can't move a mouse steadily or with a head pointer that they poke around on a keyboard with can't read it when it's in the alt-text because they can't access alt-text.
And when it's in the post text, Mastodon won't cut it off at the 500-character mark and throw the excess 39,500 characters away. If anything, it rejects posts with over 100,000 characters altogether AFAIK.
I know that Pleroma and Akkoma reject posts over 50,000 characters, and I suspect Misskey and the Forkeys to reject even shorter posts. But nobody in my primary audience is on either of these.
The problem is rather the culture. It's a culture that's cultivated on Mastodon and on Mastodon only, that disregards the rest of the Fediverse and how it's different because nobody knows, but that is being forced upon that self-same rest of the Fediverse regardless. If your home instance is connected to Mastodon, you play by Mastodon's unofficial rules or else.
Sad, but true: The rules of one Mastodon instance don't apply to all connected Mastodon instances all the same. They apply to the local timeline, but not to the federated timeline. Other instances may have contradicting rules, and no instance admin is going to enforce rules that apply to other instances, but not their own one.
At the same time, however, Mastodon's overarching unwritten cultural rules do apply to the federated timeline because they apply to all Mastodon instances. And they're forced upon everything that isn't Mastodon all the same.
That's partly because Mastodon users don't even notice when something doesn't come from Mastodon, partly because some of those who do know that the Fediverse is more than Mastodon still believe that everything that isn't Mastodon is either an alternative UI for Mastodon with a couple extra features (Akkoma or Iceshrimp or Friendica is for the Web what Mona or Tusky is for the phone) or bolted onto Mastodon as an add-on otherwise, and it's partly because whoever is the biggest is the boss, and because Mastodon users tend to think Mastodon was there first.
Mastodon's culture includes not only a sufficient description for each image you post, but you're expected to put the full description into the alt-text and only into the alt-text. This comes from adequately describing images in the post text being technically impossible on vanilla Mastodon with only 500 characters minus the actual post text, minus hashtags, minus mentions, minus even content warning.
So for one, Mastodon users expect an image description in the alt-text. That's why I describe each image twice, once with a few hundred characters in the alt-text, once with thousands upon thousands of characters in the post text.
Besides, I expect Mastodon users to be highly irritated when they discover that I've put a detailed image description into the post text rather than into the alt-text where they expect it. Yes, there's an image description in the alt-text. But why is there a longer one in the post text Why isn't the long one in the alt-text where it belongs by Mastodon's standards Why do I refuse to do things like they're done on Mastodon
Okay, so my full image description is too long for alt-text. But why don't I make it shorter then Nobody on Mastodon writes image descriptions that are several thousand characters long. Why don't I write image descriptions like Mastodon users
Also: While Mastodon is fully capable of importing and displaying posts that are tens of thousands of characters long, many many Mastodon users are very opposed to posts longer than 500 characters. They're technically possible, but they're culturally disliked and frowned upon. This mostly applies to those who use the official Mastodon app that can't fold long posts in and expand them if you want to read them, but it isn't limited to those users.
It's another cultural thing: Mastodon cannot post over 500 characters, so Mastodon users aren't used to over 500 characters, so nobody anywhere in the Fediverse must post over 500 characters. Mastodon users actually keep tooting that they want filters which remove everything over 500 characters from their timelines.
And not exactly rarely, they take matters into their own hands. If they spot a post with over 500 characters in their personal timeline, they block the poster upon first strike, but not necessarily without complaining to the user first. Some go as far as doing that when they see a post with over 500 characters in the federated timeline.
In fact, I expect entire Mastodon instances to have blocked non-Mastodon users instance-wide because some local user felt disturbed about their over-500-characters posts and asked the moderation to step in. There may even be instances, not even exactly small ones, that go as far as blocking the entire offending instance.
For these reasons, for me, posting images while having connections all over Mastodon is like treading on raw eggs. I spend 13 hours describing an image in 40,000 characters just to give a casual bystander audience a chance to understand them. I post that thing. A few people may find it helpful. To many, it makes no difference in practice because they don't read my image description. And then there's the unknown number of Mastodon users who take countermeasures or have countermeasures taken by admins/mods because my gargantuan image post disturbs them and/or goes against Mastodon's culture.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Fediverse #Mastodon #MastodonCulture #500Characters #CharacterLimit #CharacterLimits I'm not even sure if Laconi.ca/StatusNet could quote, much less quote-post. It wanted to be microblogging, and it supported the Twitter API from some point on, but it didn't aim to be a Twitter clone.
As for Friendica or rather Mistpark, I'm convinced it had quote-posts already when it was first released in July, 2010. It didn't try to mimic Twitter either, though, because it was positioned as an alternative to Facebook.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Laconica #Laconi.ca #StatusNet #Mistpark #Friendika #Friendica On the one hand, there's describing images the Mastodon way. It may range from one-liners to descriptions that almost reach 1,500 characters which are seen as absolutely massive and incredibly detailed. But they always go into the alt-text, explanations included. "Image description" and "alt-text" are mutually synonymous on Mastodon. Nobody ever questions that. After all, posts can contain no more than 500 characters.
However, this is mostly geared towards fairly simple real-life photographs which contain lots of elements that don't have to be described because they're uninteresting, and that don't have to be explained because everyone's fairly familiar with them.
And then there's the attitude that any alt-text is better than no alt-text and the idea that AI can describe any and all pictures well enough or even perfectly already now. The latter, of course, comes from people only using AI on simple real-life photographs or social media screenshots.
Those who are on Mastodon not only see these things as given, but they can't imagine them possibly being any different.
On the other hand, I break all these rules.
For one, here on Hubzilla, I don't have a limit for post text, nor do I have a limit for alt-text which has to be grafted into the post text anyway. That is, alt-text is kind of limited because even Hubzilla can only show so much, and it can't scroll through alt-text. Besides, Mastodon, Misskey and all their mutual forks cut off alt-texts from outside at the 1,500-character mark and permanently discard anything that goes beyond. So alt-text remains limited to 1,500 characters.
But posts remain unlimited. If I put an image description into the post text, I can make it as long as I want to or as I have to. And in fact, explanations don't belong into alt-text. Not everyone can access alt-text, and any information only available in alt-text is inaccessible and therefore lost to those who can't.
That's important because my image descriptions have to go with a whole lot of explanation.
That, in turn, is because the pictures I post are nothing like what you'd normally find on Mastodon.
They aren't real-life photographs. They're renderings from inside 3-D virtual worlds. Extremely obscure 3-D virtual worlds even I'm not talking about VRchat or Roblox. The whole system is known to probably not more than one in 200,000 Fediverse users, and particular places may be known to not even one in a million Fediverse users. Chances are I'm the only one in over ten million Fediverse users who knows that particular place where an image is from.
This means two things.
One, almost nobody who comes across my image posts knows anything about anything in these pictures. They don't get the pictures at all. And blind or visually-impaired users wouldn't even know what what's in the pictures looks like if I told them what's in the pictures.
Two, on the other hand, people could pretty well be interested in them. After all, I'm talking about something that has been referring to itself as a "metaverse" regularly since early 2007. "The Metaverse" is real, it's living, breathing, much to everyone's surprise. It's got nothing to do with Meta Platforms. And there has to be cool stuff in it if it's worth showing in-world pictures.
So people might become so curious about this discovery that they want to know as much as they can. But they know nothing, so they don't get the images in the first place if these images don't come with extensive explanations and descriptions.
This is the main reason why my image descriptions grow so massively long.
And with "massively long", I mean tens of thousands of characters. My most recent example is , and although it's the most up-to-date, I'm not even satisfied with it. Two posts with multiple images each and even longer descriptions for the respectively first one, albeit a bit more out-dated, are and .
As you may be able to see, what I do is: I write a fairly short, purely visual description to have at least some description in the alt-text so nobody can complain that the alt-text doesn't actually describe the image. Also, the alt-text mentions that the actual, more detailed and explanatory image description is in the post text, including where and how to find it. That's because I'd never post something of that length with a summary/content warning, so for users on ActivityPub-based microblogging projects, the full image description is hidden.
Not only has nobody ever done anything like this on Mastodon, but it's completely unimaginable because it isn't even possible on the vast majority of instances. My longest picture post is way longer than 150 Mastodon toots.
This gives me experiences with image descriptions that nobody else has ever made, especially not on Mastodon. Those many Mastodon users who "know" it's set in stone that the Mastodon way is the only way sometimes deserve to read about someone else's completely different point of view.
In fact, this becomes a necessity whenever Mastodon users want to establish image-describing standards that a) only apply to Mastodon with its limitations and b) only apply to the kind of image content that's usually posted on Mastodon, but that'd be completely and utterly incompatible with my images and my way of describing them to the point of rendering my image descriptions invalid.
But there may also be other cases in which I differ from the general Mastodon way of thinking.
Memes, for example. Memes in posts should always be described accordingly and explained if necessary. From this, I deduce that template-based memes require explanations of the templates used. At the same time, I know that the majority of Fediverse users prefers having all information in the same place as the image itself over having to get extra information from another website which, for mobile users, means from a different app.
In summary, this means that template-based memes require explanations that go even beyond KnowYourMeme because KnowYourMeme relies on linking to other pages on the same site, e.g. to explain things like 4chan, SomethingAwful, Wojak, snowclones or advice animals. But since the Fediverse prefers to have it all in one place, all these extra explanations have to be woven into the meme description and explanation specific to this particular meme. Nobody on Mastodon has ever thought of this.
Another example is the recurring talk about describing the automatically-selected image in a Mastodon link preview. It's important to know here that it's next to impossible to tell which image from which link will be picked as the preview image, if any. Also, while Hubzilla has a preview feature for posts in the making, it does not have link previews.
Not only does this mean that the link preview image on Mastodon will have to be identified and described after sending the post, but Hubzilla users will have to go to a Mastodon instance and wait until their images have federated there before they can edit the post and describe the image. This, of course, is a greater effort and takes longer than for Mastodon users who can see the link preview in their own timelines immediately or shortly after posting. In the meantime, the post will spend even more time spreading around Mastodon with no image description, and many many more people will see it without an image description, and they might react accordingly, not expecting an image description to be added rather soon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
My old, trusted, vw finally gave up and now I'm facing 800 km motorbike ride which scares and excites me at the same time
You can stay within the Fediverse, connected to Mastodon, and still have quote-posts. Because the Fediverse is not only Mastodon.
Check out Pleroma or Akkoma or any of the other Pleroma forks. Or Misskey or Firefish or Iceshrimp or Sharkey or any of the other Forkeys. Or Friendica or Hubzilla or (streams). They've all got quote-posts already now, and they can quote-post each other as well as Mastodon. And Mastodon won't be able to stop them.
In fact, both Friendica and Hubzilla have had both quotes and quote-posts long before Mastodon was even made. And they've been federated with Mastodon ever since the moment Mastodon was launched.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ReplyGuy #CWReplyGuy #Mansplaining #CWMansplaining #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Pleroma #Akkoma #Misskey #Firefish #Iceshrimp #Sharkey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedSharesI think I should add some the filter-triggering hashtags #ReplyGuy, #CWReplyGuy, #Mansplaining and #CWMansplaining to my standard repertoire, in case my other filter-triggering hashtags aren't sufficient.
They'd make it 51 characters more likely that I'll also have to add #Long, #LongPost, #CWLong and #CWLongPost because what I've written surpasses the 500-character mark, much to many Mastodon users' chagrin.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta Denen ist von dem Augenblick an, wo sie auf Twitter abgeworben wurden, praktisch durchgngig der Arsch gepudert worden. Die sind immer verhtschelt worden, sonst wren sie ja gar nicht erst hier.
Und was sie verlangen, verlangen sie nicht fr Mastodon allgemeinen, sondern ganz speziell fr die Instanz, auf der sie sind. Selbst wenn das mastodon.social ist, wo ihre Interessen denen von hunderttausenden anderen Nutzern kollidieren, die auch nicht umziehen wollen.
Die ganzen Friendica- und Hubzilla-Urgesteine haben allen Grund, darber zu kotzen. Die sind nicht mit lauter Htscheleien von Microblogging fr Doofe per Handy-App auf anderes Micro-Blogging fr Doofe per Handy-App gefhrt worden. Die kamen entweder von Facebook, wo ihnen der Kampf mit den Privacy-Einstellungen zu doof wurde, oder von gar nix.
Die haben sich damals alles selbst draufgeschafft. Am PC. Ohne App, weil's meistens gar keine gab. Ohne Drittwebsites, die ihnen alles erklrt haben. Mit noch nicht mal besonders benutzerfreundlicher Dokumentation, wenn berhaupt. Und mit einem Minimum an fremder Hilfe, wenn berhaupt. Und nicht wenige haben's sogar geschafft bis zum Headless-Miniserver auf Linux-Basis in ihren eigenen vier Wnden.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
I'mma just copypasta your hashtag line below )
You wouldn't have needed at least some of them.
If you aren't afraid of going onto people's nerves by posting Fediverse content, you don't need #CWFediMeta and #CWFediverseMeta.
And if, without these two and without #Long #LongPost #CWLong #CWLongPost, your reply had been under 500 characters, you wouldn't have needed these four either.
Last updated: 2024-05-14
All text and images © eLoc8.is-fabulous.com