New Comic Trailer: LONG HAUL Coming
On the one hand, I'd like to post an in-world picture from OpenSim again.
On the other hand, it's hard to find something that's interesting, but that doesn't mean too much of an effort to describe.
I always have in mind that whenever I mention that there is something in a picture, blind or visually-impaired users may want to know what it looks like. And I'm not too keen on spending hours educating myself on architectural features and design elements and then spending hours explaining them to laypeople in an image description, only because there's a building or a dozen somewhere in a picture. But I also hate writing image descriptions that lack information.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Blind #VisuallyImpaired #Accessibility #A11y #InclusionWitcraft (Hubzilla) Mastodon was built first on top of OStatus and then on top of ActivityPub because using an existing protocol was much easier than making your own protocol from scratch.
Diaspora* was built around a scratch-made protocol because it was invented by four Apple/Mac fanbois to whom the concept of using something that already exists and was made by someone else was totally alien. The typical Apple mindset is, "Let's not be compatible to those filthy peasants out there. We're better than them." Thus, Apple has created proprietary solutions for literally everything without caring for compatibility with anything else. Remember the first two iPod generations were only compatible to Macs.
Diaspora* was built against Macs as servers and against MongoDB and a version of Ruby on Rails available for Macs, but for no typical Linux server distro. In fact, the first Diaspora* alpha releases only ran on Mac servers. And even when they were made cross-platform because it turned out that data centres rarely have Mac servers, and only so many people can buy a Mac Pro and have a fast enough landline to host a large pod at home, they still required server admins to compile a specific Ruby on Rails version from sources.
Federation with Diaspora* wasn't established by Hubzilla. Hubzilla only took over that technology from Friendica for which it was invented. And when it was invented, Diaspora* had no API whatsoever. I think it still doesn't. So Mike and the rest of the Friendica team had to reverse-engineer Diaspora*'s inner workings from its source code and spend months cracking Diaspora*'s home-brew encryption.
Imagine you want to connect a periphery device to another, very special device. Imagine you take a diamond milling cutter, you mill a hole into the steel/ceramics/Kevlar/carbon fibre compound layer case of the latter, figuring out what layers there are in the first place, and then you use the board layouts in the maintenance manual to figure out where to solder your connector cable directly onto the various circuit boards inside that device.
That's basically how Friendica federated with Diaspora*.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Diaspora* #Friendica #HubzillaScott M. Stolz
Mastodon actually chose to use the summary field for content warnings because of its hard 500-character cap. You don't need a summary for 500 characters, full stop. So they could also use that field for something else. Hey, why not use it for content warnings
And they likely did so under the assumption that, even though Mastodon spoke a common language with GNU social, Friendica and Hubzilla, no Mastodon user would ever follow or be followed by any non-Mastodon user.
One part of the assumption was that Mastodon users wouldn't find out that there's a world outside Mastodon anyway. Mastodon wasn't targetted at geeks proficient enough in decentralised networking history to know GNU social. GNU social itself was probably deemed so small and so self-centred that nobody there would even think of following someone on Mastodon. Not if Mastodon isn't officialy being advertised as compatible with GNU social. Which it wasn't.
Now you might say that the federation-happy Friendica and Hubzilla users were just too eager to connect with Mastodon users to pin the "Federated with Mastodon" badge on them, right next to the badges for Diaspora*, GNU social and RSS.
But it's very likely that Gargron did not even know that Friendica and Hubzilla exist back then. Both were never advertised or promoted in any way that could have piqued public interest. They were largely made and maintained with an "If you build it, they'll come" mindset. And Hubzilla was brand-new when Mastodon was made, and its existence was only known to Mike's connections who paid close attention to his development posts.
And even if Gargron had known Friendica, he might not have known that Friendica speaks OStatus, much less that Friendica users tend to federate with everything that moved just because can.
Basically, Mastodon was designed to be federated within itself but effectively a walled garden towards the outside. And a walled garden doesn't have to take compatibility with anything that already exists into consideration.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonWitcraft (Hubzilla) We Hubzilla users let ourselves be thrown into the cold water with an out-right feature monster with a lacking UI and even more lacking documentation. Hubzilla is for die-hard geeks who can wrestle sich a monster. Most of us came either from Friendica which has never been that extremely better or from nowhere. Add to this that the most popular platform here is probably desktop Linux.
Mastodon users are vastly different, especially since the second wave of Twitter migration. Most of them are on phones, many are only on phones. Almost all came from Twitter. And what they sought was not something like Twitter, but more for geeks. What they sought was Twitter without Musk, but otherwise 100% Twitter. And Mastodon was promised to them to be just that.
Also, unlike us, Mastodon users were generally mollycoddled to no end from the very moment they got disgruntled with Twitter. They were always protected from the harsh reality of the Fediverse outside Mastodon and, in fact, from much of what makes Mastodon "harder" to use than Twitter.
We had to fire up a search engine to find a website that lists Hubzilla hubs, including whether sign-up is open or not. They weren't even told that Mastodon is decentralised. Instead, they were railroaded to mastodon.social or any other big instance, and decentralisation was kept away from them until they had settled in and made themselves comfortable.
They weren't told either that the Fediverse is more than just Mastodon. I think nobody even thought about what'd happen if they find that out because those who mollycoddled them and railroaded them onto Mastodon were and often still are barely aware of that themselves.
It usually took them months to even read about Pixelfed and PeerTube which are all over Mastodon. Okay, so there's an Instagram and a YouTube in the Fediverse, too. Neat. Okay, and WordPress connects to the Fediverse, too. Maybe neat. Okay, and there's actual Instagram by Facebook pushing into the Fediverse. Not so neat.
But even then, they did not know or even expect that there are other things in the Fediverse that do the same as Mastodon. And do it differently. It took them the odd month on top of that to learn about that.
Hubzilla users are kind of intrigued when someone from remote corners of the Fediverse connects to them. We're used to federating with anything and everything because that's a killer feature.
Mastodon users of about six months or less recoil from their phones or computers when they see a post with over 500 characters for the first time. This shouldn't even be possible! Mastodon can't do over 500 characters! Witchcraft! Black sorcery!!!
It gets worse if they see text formatting.
It gets even worse if they see someone being quoted or "quote-tweeted". It gets much worse if it's them who is being quoted or "quote-tweeted".
Again, their first reaction is that this shouldn't be possible, and that this has to be some black-hat hacker's work. This just has to be illegal.
If that offending post came from you, and they ask you what you've done, and you tell them you're on Hubzilla, their first understanding is that Hubzilla is the name of a Mastodon instance. You know, like Universeodon.
If you tell them it isn't, they'll assume that Hubzilla is a Mastodon fork.
Then you tell them it isn't that either. It's a wholly independent project that has nothing to do with Mastodon. And they'll wonder why someone would make something like Hubzilla if there's already Mastodon. Mind you, at this point, they still assume that Gargron has made Mastodon in 2022 as a reaction upon Musk's plans to take over Twitter, and everything else was made after that. Because "everybody knows" that Gargron invented a) Mastodon, b) ActivityPub and c) the Fediverse.
Because nobody has told them otherwise before they joined. Because that would have made things so overwhelmingly complicated that they would have noped away from Mastodon.
Well, and then you tell them that Hubzilla is, in fact, older than Mastodon. It literally existed before Mastodon was even made. And even with Mastodon being six years older than they think, Hubzilla is almost another whole year older than Mastodon. And Hubzilla is a fork of a fork of another Fediverse project, Friendica, that's almost six years older than Mastodon.
Tell you what: They might still refuse to accept that there has been something in the Fediverse before Mastodon. Okay, if Hubzilla is actually older than Mastodon, it must have been made to federate with Mastodon just recently. Hubzilla is a rude, reckless intruder in Mastodon's nice and cosy and fluffy Fediverse that refuses to adapt to Mastodon and its culture.
At this point, their assumption is still that the whole Fediverse was built around Mastodon.
And then you tell them that, no, Mastodon is the intruder. When Mastodon was launched, it immediately federated itself with Friendica and Hubzilla and GNU social because it spoke GNU social's language from the very beginning, and Friendica and Hubzilla spoke and still speak that language, too, only that all three did so already before Mastodon. Oh, and even when Mastodon adopted ActivityPub, Hubzilla had it first.
This will drive them further into defending Mastodon's alleged position as the supreme leader over the whole Fediverse to whom all others have to bow. Well, at least it's the best. Everything else has to be inferior. Or why else is Mastodon the biggest
Well, that's because 99% of all Mastodon newbies were railroaded into it. They weren't given a choice between Fediverse projects. Either because whoever showed them the Fediverse didn't want to make matters too complicated and spare them of having to choose, or because whoever showed them the Fediverse only knew Mastodon, too. And it usually takes them months to find out the disturbing truth that the Fediverse is, in fact, not only Mastodon.
And since there's no easy-peasy, nomadic-identity-level way of moving from instance to instance and from project to project outside of Hubzilla and (streams), and since they don't want to get used to yet another project, and since Mastodon has the vastly best support for mobile apps (remember, everyone's on phones), they're stuck on Mastodon, demanding that Mastodon and their home instance introduce features that are readily available just about everywhere else in the Fediverse.
And since they're tendentially tech-illiterate and used to being mollycoddled, they demand all new Mastodon features have their personal preferences as the default settings.
Not to mention that they'll neither understand nor accept that other projects may have a different culture and have had it since times long before Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon
Mastodon users don't necessarily only react like this upon posts in their personal timelines.
See, Hubzilla's pubstream is optional, and almost all hubs have it turned off. Mastodon's federated timeline is not optional, always on and quite popular. And I guess not few Mastodon users react upon posts in the federated timeline the same as upon posts from their own contacts.
Mastodon's Web interface does have this feature.
But the vast majority of Mastodon users is on phones, using dedicated apps. And some apps were built by people who at that point didn't know that the Fediverse is not only vanilla Mastodon. They made them under the assumption that there'll never be posts longer than 500 characters in the Fediverse. So they didn't add a post collapsing feature because they deemed it unnecessary for posts of 500 characters and shorter.
Either they still don't know that posts over 500 characters are possible, even on Mastodon. Or it's too late now adding post collapsing would require re-writing half the app.
That, or there are apps which let you turn collapsing completely off, and people actually do that.
Otherwise, there wouldn't be complaints by people for whom extremely long posts show up in their timelines at full length.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Alles, was Nicht-Mastodon-Projekte knnen, strt. Auch nur ein bichen ber 500 Zeichen, Textformatierung, Codeblcke, Listen, Zitate, Quote-Posts usw. Ich bin ja sogar schon angegangen worden, weil meine Mentions so komisch aussehen, und ich sollte das geflligst abstellen.
Ich warte wirklich schon darauf, da ganze Projekte gefediblockt werden sollen, weil deren Nutzer sich so unmastodonhaft benehmen.
Meinen Main hast du, wie's aussieht, auch schon geblockt, weil ich mich nicht wie auf Mastodon benehme. Daher verwende ich hier jetzt meinen Klon.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NichtNurMastodon Find the latitdue and longitude of any place
Ein paar Beispiele ohne Anspruch auf Vollstndigkeit:
Ansonsten kannst du es auf dem Webinterface auch selbst berprfen:
Alternativ kannst du auch das Profil des Nutzers aufrufen. Das siehst du auch auf dessen Heimatinstanz und nicht auf Mastodon, wenn es nicht auf Mastodon ist.
Es wrde jetzt allerdings den Rahmen sprengen, wenn ich erklren wrde, an welchen visuellen Merkmalen man welches Projekt erkennt. Einige Projekte sind ja im Aussehen extrem variabel, und bei einigen Projekten knnen sogar die Nutzer das Aussehen ihres Kontos oder Kanals verndern.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Fediversum Dann mten aber DFRN (fr Friendica), Zot (fr Hubzilla), Nomad (fr (streams)), BBcode (fr alle drei), Markdown (fr (streams)), HTML (fr (streams) und die Darstellung im Web generell), ActivityPub (fr das gesamte restliche Fediverse) und Rich Text (fr ActivityPub) erweitert werden um die Mglichkeit, Alt-Text an Links anzuhngen.
Auerdem mten ausnahmslos alle Fediverse-Projekte nachziehen, dieses Feature einbauen und obendrein eine separate Vorschau bieten, die mit 100%er Verllichkeit anzeigt, wie der Post letztlich auf Mastodon aussehen wird. Gleichzeitig mten sie ihrerseits die Bildbeschreibung fr Linkvorschaubilder ignorieren, weil es die so nur auf Mastodon gibt.
Nur, damit Alt-Text fr Linkvorschaubilder auf Mastodon perfekt funktionieren.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodon
Does Mastodon only support so short option names that the "- sighted" and "- not sighted" appendices are swallowed
Each option is there once for sighted users and once for blind or visually-impaired users. I want to be able to distinguish between their opinions.
That isn't an option, and I've explained in the start post why. Money self-quote:
First of all, there must never be any information exclusively available in alt-text. Not everyone can access alt-text. There are physical disabilities that make that impossible. If information is only available in alt-text, it's lost to certain disabled users.
Besides, Mastodon chops off long alt-text that comes in from outside at the 1,500-character mark. And I mean it permanently discards everything that goes beyond 1,500 characters.
This isn't nearly enough for even basic explanations plus visual descriptions in my case. My images are always about an extremely niche topic. Thus, for a casual audience to even be able to understand them, I have to explain a lot, and I have to explain the explanation itself.
1,500 characters aren't nearly enough for that.
includes an explanation that's 2,635 characters long. This is not a typo.
I have to explain what Padm is so sceptical about.
In order to make that understandable, I have to explain in altogether 501 characters what OSgrid is.
Then I have to explain in 572 characters what OpenSimulator is in order for people to understand what OSgrid is.
Then I have to explain in 545 characters what Second Life is in order for people to understand what OpenSimulator is.
Then I have to explain in over 200 characters that and why worlds in OpenSim are called "grids" in order for people to further understand what OSgrid is.
Then I have to explain in 487 characters what it is about OSgrid that has Padm worried.
Without these explanations, nobody but OpenSim veterans would even get the meme. And I didn't even explain the meme template if I were to do that as well, I'd go well beyond 6,000 characters only for explanations because I'd have to go as in-depth as .
Only for explanations. This does not include visual descriptions. And if you've ever actually read any of my over-500-characters-long posts, you should know that my visual descriptions of my own pictures give "excessive" a new meaning. And they come with increasingly extensive general explanations plus detail explanations themselves.
You tell me how to get thousands upon thousands of characters in alt-text into Mastodon in one piece, undamaged.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Auch hier wieder: Mit Friendica, Hubzilla und (streams) technisch nicht mglich.
Noch einmal: Da gibt's kein Alt-Text-Eingabefeld. Alt-Text wird in den Bildeinbettungscode im Post selbst reingeschrieben.
Das heit, wenn du z. B. Alt-Text an ein Bild in einem Post von Hubzilla einbauen willst,
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodon
Ich hoffe nur, da das nie zur Pflicht wird mit Defderation ganzer Instanzen als Sanktion bei Nichterfllung.
Das Fediverse ist nicht nur Mastodon, auch nicht nur Mastodon und Mastodon-Forks. Einige Projekte sind vllig anders aufgebaut und funktionieren vllig anders als Mastodon. Vor allem Friendica, Hubzilla - da bin ich - und (streams) handhaben Alt-Text vllig anders als Mastodon, nmlich nicht in einem separaten Textfeld. Da wre der Aufwand, Alt-Text fr Profilbilder zu erlauben, viel zu gro.
Und Alt-Text fr Linkvorschaubilder ist da berhaupt nicht umsetzbar. Die drei haben gegenber Mastodon zwar den Vorteil, da sie eine Vorschaufunktion haben. Aber die Vorschaufunktion zeigt nicht an, wie die Posts auf Mastodon aussehen werden. Und "zu Hause" sehen sie vllig anders aus als auf Mastodon eine Linkvorschau gibt's da nicht.
Zum einen wrde ein Post mit Link also noch lnger ohne Alt-Text frs Vorschaubild im Fediverse stehen. Unsereins mte nmlich eine Mastodon-Instanz aufrufen, mit der wir verbunden sind, und da dann nach dem Post suchen, und warten, bis er da angekommen ist. Erst dann wissen wir berhaupt, was fr ein Bild Mastodon da eigentlich als Vorschau eingesetzt hat. Und bis der Alt-Text geschrieben ist, der Post editiert ist und der Edit durchs ganze Fediverse durchgereicht ist, das dauert nochmal.
Zum anderen ist das eh irrelevant, weil so etwas auf Friendica, Hubzilla und (streams) technisch unmglich ist. Wie gesagt, keine Alt-Text-Eingabefelder. In Posts werden Bilder ja auch nicht als Dateien angehngt, sondern wie in Blogposts eingebettet. Der Alt-Text wird dann ins Markup fr die Bildeinbettung reingeschrieben. Aber ein Link ist nur ein Link. Kein Markup der Welt sieht Alt-Text fr Links vor.
Es wre einfacher, wenn Misskey, Firefish, Iceshrimp, Sharkey, Catodon, Friendica, Hubzilla, (streams) etc. etc. pp. einen Ein-Klick-Totalimport ganzer Mastodon-Accounts anbieten wrden, um das Umziehen zu erleichtern. Die konnten nmlich alle schon immer Quote-Posts.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodonI have a question regarding descriptions and explanations for images:
Let's suppose I post an image showing something extremely niche and extremely obscure, something that'd require a whole lot of explanation for most people to understand. This also includes memes.
Let's also suppose I don't have a 500-character limit, for I don't have any character limit.
Where would you prefer general explanations
All options are listed separately for sighted and non-sighted users.
Please boost for a larger sample size!
Note 1: "In the alt-text" is not an option, by the way. Explanations never go into the alt-text. Besides, without a 500-character limit, I don't have to shove stuff into the alt-text because there's no room in the post.
Note 2: "No description" is not an option either. You shouldn't just leave it to your readers to search the Web for whatever they don't get. Besides, no, you can't Google everything, and ChatGPT doesn't know everything either.
Note 3: Explanations for specific elements in an image that go along with describing what they look like will always go into the image description, i.e. into the post, especially if there is no external webpage explaining them.
#Poll #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #DescriptiveText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #Accessibility #A11y #Inclusion #Inclusivity #Blind #VisuallyImpaired Just FYI: At least Hubzilla has the built-in functionality to add a geographic location to each post, and you can optionally even enter a default location into your channel settings. There's an optional app named that can show the post location or any other place in OSM. There's also an optional app named that can be used to plan meetings using OSM as the map provider.
Both and have similar OpenStreetMap add-ons, but they don't have anything like Rendez-vous.
Granted, it all dates back to before Mastodon, so it isn't geared towards working with Mastodon. Also, it isn't built against ActivityPub primarily but against DFRN (Friendica), Zot6 (Mastodon) and Nomad ((streams)). But maybe it's worth checking out.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #OpenStreetMap (streams) has always been a fully-fledged Fediverse server application capable of working as a decentralised social network, only that it has been slimmed down in extra features in comparison to Hubzilla to be easier to maintain. Its federation is reduced to Nomad, Zot6 and ActivityPub, and apps like Calendar, Articles, Webpages and Wiki are gone, too, while it got to keep WebDAV, CardDAV and now-headless CalDAV. On the other hand, its ActivityPub connectivity has been improved.
Its original intention was not to be built into other projects, but other projects to be built around/on top of it by developing add-ons for it and giving it a name. (streams) itself doesn't have a name, doesn't have a brand, doesn't have a logo and isn't actually even a project, only a software repository. But if you take what's in that software repository and install it on a Web server, you still get something that blows Friendica out of the water in all but cross-protocol federation, calendar and maybe fancy UI elements.
Its main "issues", apart from not handling anything like Mastodon either, are that it has precious few public instances with open sign-up, and that its very concept (it doesn't have a unique identifier for its instances, and it's being kept away from all instance listing websites) makes its instances next to impossible to find unless you already know one.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
It still isn't nomadic identity style.
Imagine you move from foo.social to bar.social. Your whole account, just without the instance-specific login credentials, moves along with you. Including all your posts.
Now it comes: Your posts don't re-appear on everyone's timelines as new, unread posts as they normally would. They don't appear as read double posts either. Your whole backlog of existing posts on everyone's timelines all over the Fediverse are being automatically re-assigned from tokyo0foo.social to tokyo0bar.social as the author.
Also, nobody has to re-follow you. All your followers and all your followed are being automatically re-assigned from tokyo0foo.social to tokyo0bar.social, too, without having to do anything themselves.
Also, your account on foo.social is completely wiped and ceases to exist.
Afterwards, everything looks like you've always been on bar.social.
That would be nomadic identity style.
That's because the main gateway into the Fediverse is not or . It's rather or which nudges everyone to mastodon.social, too. Or for Japanese users, it's .
Justifiedly so. If you tell people who want to get away from Musk that they first have to choose one out of dozens of Fediverse projects and then one out of dozens or hundreds or thousands of instances without even knowing what either is, they'll nope out because that's way too complicated.
If you railroad them to mastodon.social and leave them to figure out everything themselves when they're ready for it, they'll bite because that's easy enough.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Yes, because moving is so inconvenient. And a full, nomadic-identity-style move from Mastodon to anywhere is technically impossible. But many won't do less than that.
Yes, because 99% of all Fediverse newbies are railroaded to Mastodon without being told what else there is in the Fediverse because that'd just confuse them. People usually take three to six months to even only discover that there are alternatives to Mastodon in the Fediverse, at which point they've fully settled into Mastodon.
The newbies don't hate Mastodon for not being as powerful as e.g. Sharkey. They love it for not being . And they've never even heard of Sharkey at that point, so they can't and won't compare Mastodon to Sharkey.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Three reasons.
One, you can't move from Mastodon to any other Fediverse project with all your content, all your posts, all your settings, all your connections just like so, just like you can move from Hubzilla to (streams).
Two, Mastodon is the only Fediverse project with full, extensive, guaranteed iOS app support. Most "Fediverse" apps are built against Mastodon first and foremost or against Mastodon only. And almost everyone on Mastodon is on phones, mostly iPhones.
Three, coming from Twitter and adapting to Mastodon was hard enough already, and some still haven't recovered from that. You can't expect them to move and learn something new again.
And thus, everyone stays on Mastodon, waiting for features that are perfectly standard pretty much everywhere else to be introduced to their home instance.
And I'm not even counting those who aren't aware what the rest of the Fediverse can do. Or those who simply don't know that there is such a rest of the Fediverse because they think the Fediverse is only Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Well, everyone and their dog believes that Zuckerberg's virtual worlds platform is officially named "The Metaverse". ("Metaverse" and "The Metaverse" are registered trademarks of Meta Platforms, Inc. All rights reserved.") And both mainstream media and tech media spew out the same non-sense. The only exceptions are tech media specialising in virtual worlds.
Also, as I've already written, Second Life started to officially refer to itself as a "metaverse" in 2022 as a "Hey, we're still here, too, and we're still relevant" publicity stunt. And Second Life has always been a commercial walled garden.
Its API is only public insofar as it was reverse-engineered from the source code of the official viewer after the latter was made open-source in 2006. And that's only a viewer API, a client API, that's used to develop third-party viewers. "Compatibility" with other virtual worlds Well, there's OpenSim which was then built against the other side of the same API and the already existing third-party Second Life viewers and launched in 2007. But while it uses largely the same API and the same formats and the same standards, and while it's decentralised and federated within itself, it can't connect to Second Life. Even the 2008 "Six Lindens manage to teleport from Second Life to OpenSim" publicity stunt was bogus and faked.
I think I might write an article about the latter.
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #Secondlife #Metaverse
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #SecondLife #OpenSimulator #Decentraland #Roblox #VRchat #ThirdRoom #Vircadia #Overte #TheMetaverse #Metaverse
...where "Fediverse" is synonymous for "Mastodon", I guess.
I can't boost. Hubzilla doesn't have that feature. Hubzilla "quote-tweets" instead. It has done so since before there was Mastodon. You don't want me to do that instead, do you
Okay, I can do that. But from your typical Mastodon and formerly Twitter user's point of view, I guess I use way too many because I also use them to trigger filters. So I use a whole lot of them.
Hubzilla can't follow hashtags either.
First of all, there isn't a single Guppe group that even remotely covers the primary topic of this channel. There is a Lemmy community for that topic, though, and I'm connected to it.
Besides, I'm connected to various Friendica, Hubzilla and (streams) forums/groups which blow gup.pe clean out of the water feature-wise.
Right, I don't read them. Because they're all so Mastodon-centric it hurts. Almost none of them can be sensibly carried over to here.
Not to mention the edge-cases I have to deal with that FediTips don't cover, for example when it comes to describing images. I don't have to put everything into the alt-text. I don't have a 500-character limit that prevents me from describing stuff in the post text body and forces me to use only the alt-text.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fedisplaining #CWFedisplaining #NotOnlyMastodon #MastodonIsNotTheFediverse #FediverseIsNotMastodon
I almost always put my image descriptions into the post text body for two reasons. One, they contain explanations and other information neither available in the actual post text nor for sighted people in the image itself. Two, they're way too long. They exceed 1,500 characters multiple times, sometimes multiple dozen times. I don't have local character limits to worry about, but at least Mastodon, Misskey and all their forks chop alt-text over 1,500 characters off at the 1,500-character mark.
In addition, I always mention in alt-text where exactly this image description can be found. Not only in the post text body, but I add stuff like "above the image and hidden behind a content warning if you're viewing this post on Mastodon and right below this image if you're viewing this post on Friendica, Hubzilla or (streams)".
More recently, however, I started adding a short description of the image to the alt-text. It actually doesn't even begin to describe the actual contents of the image. It's only there to satisfy the "alt-text must describe the image or else" crowd. I may have alt-texts well beyond the 850-characters mark nonetheless.
And still, I think the only reason why nobody complains about the lack of image description in my alt-texts is because too many Mastodon users or entire instances have muted or blocked me for not acting "Mastodon-like" enough.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Weil es zu fast allen Themen Leute gibt, die sich darber aufregen, da die nicht hinter einer CW versteckt werden. Ja, auch Katzenbilder (CW: cats).
Deswegen bin ich dafr, da Mastodon mal den umgekehrten Weg geht. Zur Abwechslung mal nicht dem ganzen Fediverse seine eigene Kultur aufzwingt, die geprgt ist durch technisch ungerechtfertigte Beschrnkungen, Neuerfinden von Rdern und Walled-Garden-Denken. Statt dessen mal was nicht nur technisch, sondern vor allem in seine Kultur bernimmt, was im Fediverse vor Mastodon der Standard war:
Content Warnings aus Filtern. Automatisch generiert fr jeden Leser individuell.
Das kann Mastodon auch, und zwar seit Version 4.0, also seit letztem Jahr. Nur nutzt das keiner, und zwar aus einer ganzen Reihe an Grnden:
Erschwerend kommt hinzu: Viele Projekte, die nach Mastodon als Alternativen zu Mastodon gestartet wurden, wurden nicht nur auf Mastodons Technik, sondern auch auf Mastodons Kultur zugeschnitten. Entweder haben die gar keine Filter, oder die haben bis heute keine Mglichkeit, per Filter CWs zu generieren.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta Okay, here's a bit more. And I'm trying to write this from a Mastodon point of view, but as someone who has got experience outside of Mastodon.
If you're on Mastodon which you probably are, get used to the lingo.
This may come as a surprise, but the Fediverse is not only Mastodon. There are many other projects in the Fediverse which are connected to Mastodon. Some of them have actually already been around before Mastodon. And they have features that Mastodon doesn't have. So don't freak out if you see a post with over 500 characters. Or with italics. Or with bold type. Or with a
Double your content warnings with hashtags. Some projects in the Fediverse outside of Mastodon use text filters to automatically generate individual content warnings for those who need them. And Mastodon can do that, too, so even some Mastodon users do it.
If a post with content that you may deem sensitive has only got these hashtags but no actual content warning, this is not necessarily due to ill intent or neglect. Some Fediverse projects outside of Mastodon can't do content warnings the Mastodon way. Hubzilla can only do them in first posts, but not in replies. On Friendica, they're generally very difficult to do. So don't immediately call for moderation.
Actually describe your images in alt-text. And do only that. No hashtags in alt-text. No links in alt-text. No SEO keyword spamming in alt-text.
If there's text in your picture, transcribe it in alt-text word by word.
Don't forget: Different instances have different rules. So don't report someone on another instance for not adding a content warning that's mandatory on your instance but not on theirs or the like. And don't forget either: Different projects have different capabilities and different cultures of using them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fedisplaining #CWFedisplaining #MastodonIsNotTheFediverse #NotOnlyMastodon #FediverseIsNotMastodon #Hashtag #Hashtags #AltText
Da gibt es leider keinen wie auch immer gearteten Konsens, auch wenn einige behaupten, den gbe es. Genau wie mit der Lnge und Ausfhrlichkeit von Bildbeschreibungen.
Die einen Blinden wollen Bildbeschreibungen gern kurz und prgnant. Die anderen wollen sie ausfhrlicher. Z. B. lassen sie sich nicht damit abspeisen, da du Elemente in einem Bild erwhnst, sondern sie wollen auch wissen, wie das alles jeweils aussieht.
Wenn du jegliche Bildbeschreibung in den Alt-Text packst, bringt das fr Blinde noch einen weiteren Nachteil mit sich: Screenreader knnen Alt-Text nicht navigieren. Das heit, die knnen nicht innerhalb des Alt-Text an eine bestimmte Stelle zurckspringen, sondern nur wieder ganz zum Anfang, um dann alles wieder von vorne durchzurattern.
Das ist einer von diversen Grnden, warum ich z. B. meine ausfhrlichen Bildbeschreibungen immer in den Post selbst packe. Ein anderer ist, weil sie meistens weit lnger als 1500 Zeichen werden, aber zumindest Mastodon, Misskey und die Forkeys schneiden Alt-Text an der 1500-Zeichen-Marke hart ab.
Allerdings poste ich im allgemeinen Bilder zu einem sehr obskuren Nischenthema. Die meisten Leute brauchen sehr, sehr viel Erklrung, um die Bilder zu verstehen. Und gerade meine eigenen Bilder sind manchmal ziemlich komplex, auch wenn ich versuche, das zu vermeiden.
Wie gut meine Beschreibungen ankommen, wei ich nicht. Ich habe bisher mehr Bilder beschrieben als Feedback dafr bekommen, und zwar inklusive Feedback von Leuten, denen ich ausdrcklich meine Bilderposts als Beispiele fr lange, detaillierte Bildbeschreibungen gezeigt habe. Ungefragtes Feedback hatte ich bisher nur einmal, auch wenn das positiv war.
Nicht jeder, der blind ist, wurde blind geboren. Wer irgendwann in seinem Leben erblindet ist, hat frher mal Farben gesehen, also auch einen Begriff von Farben.
Auerdem ntzen Bildbeschreibungen nicht nur Blinden, sondern auch Sehenden, die mieses Internet haben, wo die Bilder berhaupt nicht laden.
Ich wrde Farben immer erwhnen.
Die meisten, die es gibt, sind nur fr professionelle/kommerzielle statische Websites oder vielleicht noch professionelle/kommerzielle klassische HTML-Blogs. Die meisten, die Social Media behandeln, sind nur fr kommerzielle Social Media, also Facebook, Twitter, Instagram, LinkedIn usw. Und die paar, die tatschlich das Fediverse behandeln, sind nur fr ganz normales Vanilla-Mastodon und gehen felsenfest davon aus, da Posts nicht lnger sein knnen als 500 Zeichen.
Die Sonderflle "Zeichenlimit deutlich ber 500 Zeichen" und "Social-Media-Post mit Bild, das viel Beschreibung und/oder Erklrung braucht", sind noch nie in so einer Anleitung abgedeckt worden.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch "MIA" means "missing in action".
I don't know all the details, just so much: The last time Kainoa was seen contributing to the Firefish repository was in June or July. Around that time, I guess, was also the last time that Kainoa was seen taking care of firefish.social. Kainoa is still alive and well and has posted something not long ago. Could be busy, nobody knows.
Anyways, fast-forward to December, 2023/January, 2024. Due to literally no maintenance whatsoever because the only admin hasn't shown up in a while, firefish.social has become entirely unresponsive. Nothing works anymore.
Also, Firefish is badly lagging behind Misskey's development. Not only no new features, but also no bug fixes, no security fixes, no nothing.
So the Firefish community took matters into their own hands. Just to mention three new forks:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon
Web interfaces could get switches like these, too, and ideally, admins could add their own switches, depending on the target audience of an instance. Ideally, apps could recognise these custom, instance-specific switches and add them to their UI.
On the posters' side, it'd still require discipline because they'd have to add appropriate hashtags, and these hashtags would have to be standardised, otherwise each filter would have to cover each trigger with half a dozen different hashtags per language or so. Dedicated apps could assist in this by adding checkboxes to the post editor which have the app automatically add appropriate standard hashtags for certain topics to the "hashtag line" at the end.
This could actually start in apps without breaking standards, and it could nudge Mastodon itself into adding it to its Web UI. In fact, I can see at least some Forkeys being quicker at introducing it.
The best part: This would move the Fediverse away from something Mastodon-specific and towards something more standard.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta
Even if Mastodon won't introduce the creation of quote-posts, Misskey, the various Forkeys (Firefish, Iceshrimp, Sharkey, Catodon etc. etc.), Friendica, Hubzilla and (streams) can quote-post just about any Mastodon toot out there with no resistance whatsoever. They always could, even when Mastodon wasn't able to display quote-posts halfway appropriately.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta To be fair, this doesn't apply to all the Fediverse. Mastodon, yes, but not the entire Fediverse.
I dare say there are two projects which handle this marvellously: from 2015 and a fork of a fork... by Hubzilla's own creator, commonly referred to as while technically being nameless. While both can "talk ActivityPub", they are based on different protocols which give them a feature that Bluesky tries hard to make everyone believe that they're working on inventing: .
First of all, Hubzilla and (streams) don't put your Fediverse identity directly into your account. Your account only grants you access. Your identity, your connections, your posts, your settings, your content etc. etc., all that resides in a , a kind of container. You can have multiple channels on one account, so you can also have fully separate identites on the same instance without having to log out and back in.
Nomadic identity itself can do two things. One, it takes care of moving a channel to another instance. And I mean actually moving it, not creating a dumb copy and leaving a dead account behind.
Two, and this is the actual killer feature, it can clone your channel to another instance. Again, not create a dumb copy. The clone is always synchronised with the original and vice versa. If one goes down, you've got the other readily at hand, so you're even safe from spontaneous shutdowns. And you can have more than one clone for each one of your channels.
Basically, moving is cloning light. Moving creates a synchronised clone, declares the clone the new main and the old main a clone, then deletes the old-main-gone-clone, and if there aren't any other channels on your old account, deletes that account.
Nomadic identity was invented in 2011 by who also created Hubzilla, now maintains (streams) and, in 2010, had created which was named Friendika back in 2011. Public Friendika nodes closing down had become a serious issue already, regardless of whether the shutdown was announced or came out of the blue. Early on, whenever this happened, all users on the node lost everything and had to start over from scratch.
Friendika eventually introduced moving from node to node by exporting and importing your account, but real resilience would have been different. Thus, nomadic identity was conceived. The Zot protocol was written around it because it couldn't be introduced to Friendika's DFRN protocol. In 2012, Friendica was forked and its backend re-written against Zot, becoming the Red Matrix, direct precursor of 2015's Hubzilla.
In a perfect Fediverse, everything would feature nomadic identity. But as it stands now, everything that isn't these two projects doesn't even understand nomadic identity and is easily confused by nomadic moves or someone posting from their clone instead of their main.
Unfortunately, nothing will change about this anytime soon. Mike Macgirvin has already proposed extensions for ActivityPub that'd introduce nomadic identity, albeit not in exactly the same fashion as on Hubzilla and (streams), but probably somewhat compatible. However, they have all been rejected.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #NomadicIdentity This might be a case of Chinese whispers.
What really increases accessibility when it comes to hashtags is how they're written if they consist of multiple words.
Always write multiple-word hashtags in "camelCase" (every word after the first one starts with a capital letter) or, better yet, "PascalCase" (every word starts with a capital letter). Screen readers used by blind or visually impaired users can't tell with certainty otherwise where a word ends and the next one starts.
Also, stop using Mastodon like Twitter and put all hashtags at the end of the post instead of into the text.
#Long #LongPost #CWLong #CWLongPost #Hashtag #Hashtags #Accessibility #A11y #camelCase #PascalCase
What do you mean would cause an instant ban The use of quote-posts for harassment or the use of quote-posts in general
I don't know if you've read the whole thread. I've already posted in it. If not: Lots of Fediverse projects have quote-posts regularly implemented. Two of them, Friendica and Hubzilla, have had them before Mastodon even existed, and it was Mastodon which federated itself with them and not the other way around. They call them "shared posts" and use them for the same purpose as Mastodon uses boosts: to forward posts.
They also both had quotes like the one above since their respective inception.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
On the other hand, it's hard to find something that's interesting, but that doesn't mean too much of an effort to describe.
I always have in mind that whenever I mention that there is something in a picture, blind or visually-impaired users may want to know what it looks like. And I'm not too keen on spending hours educating myself on architectural features and design elements and then spending hours explaining them to laypeople in an image description, only because there's a building or a dozen somewhere in a picture. But I also hate writing image descriptions that lack information.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Blind #VisuallyImpaired #Accessibility #A11y #InclusionWitcraft (Hubzilla) Mastodon was built first on top of OStatus and then on top of ActivityPub because using an existing protocol was much easier than making your own protocol from scratch.
Diaspora* was built around a scratch-made protocol because it was invented by four Apple/Mac fanbois to whom the concept of using something that already exists and was made by someone else was totally alien. The typical Apple mindset is, "Let's not be compatible to those filthy peasants out there. We're better than them." Thus, Apple has created proprietary solutions for literally everything without caring for compatibility with anything else. Remember the first two iPod generations were only compatible to Macs.
Diaspora* was built against Macs as servers and against MongoDB and a version of Ruby on Rails available for Macs, but for no typical Linux server distro. In fact, the first Diaspora* alpha releases only ran on Mac servers. And even when they were made cross-platform because it turned out that data centres rarely have Mac servers, and only so many people can buy a Mac Pro and have a fast enough landline to host a large pod at home, they still required server admins to compile a specific Ruby on Rails version from sources.
Federation with Diaspora* wasn't established by Hubzilla. Hubzilla only took over that technology from Friendica for which it was invented. And when it was invented, Diaspora* had no API whatsoever. I think it still doesn't. So Mike and the rest of the Friendica team had to reverse-engineer Diaspora*'s inner workings from its source code and spend months cracking Diaspora*'s home-brew encryption.
Imagine you want to connect a periphery device to another, very special device. Imagine you take a diamond milling cutter, you mill a hole into the steel/ceramics/Kevlar/carbon fibre compound layer case of the latter, figuring out what layers there are in the first place, and then you use the board layouts in the maintenance manual to figure out where to solder your connector cable directly onto the various circuit boards inside that device.
That's basically how Friendica federated with Diaspora*.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Diaspora* #Friendica #HubzillaScott M. Stolz
In a way, I understand why they chose the summary field for content warnings. If someone writes a summary, there is usually enough information to let people know what the rest of the content is about. It's just that on Mastodon, they don't care about summaries, they care about content warnings, so they renamed the field.
Mastodon actually chose to use the summary field for content warnings because of its hard 500-character cap. You don't need a summary for 500 characters, full stop. So they could also use that field for something else. Hey, why not use it for content warnings
And they likely did so under the assumption that, even though Mastodon spoke a common language with GNU social, Friendica and Hubzilla, no Mastodon user would ever follow or be followed by any non-Mastodon user.
One part of the assumption was that Mastodon users wouldn't find out that there's a world outside Mastodon anyway. Mastodon wasn't targetted at geeks proficient enough in decentralised networking history to know GNU social. GNU social itself was probably deemed so small and so self-centred that nobody there would even think of following someone on Mastodon. Not if Mastodon isn't officialy being advertised as compatible with GNU social. Which it wasn't.
Now you might say that the federation-happy Friendica and Hubzilla users were just too eager to connect with Mastodon users to pin the "Federated with Mastodon" badge on them, right next to the badges for Diaspora*, GNU social and RSS.
But it's very likely that Gargron did not even know that Friendica and Hubzilla exist back then. Both were never advertised or promoted in any way that could have piqued public interest. They were largely made and maintained with an "If you build it, they'll come" mindset. And Hubzilla was brand-new when Mastodon was made, and its existence was only known to Mike's connections who paid close attention to his development posts.
And even if Gargron had known Friendica, he might not have known that Friendica speaks OStatus, much less that Friendica users tend to federate with everything that moved just because can.
Basically, Mastodon was designed to be federated within itself but effectively a walled garden towards the outside. And a walled garden doesn't have to take compatibility with anything that already exists into consideration.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonWitcraft (Hubzilla) We Hubzilla users let ourselves be thrown into the cold water with an out-right feature monster with a lacking UI and even more lacking documentation. Hubzilla is for die-hard geeks who can wrestle sich a monster. Most of us came either from Friendica which has never been that extremely better or from nowhere. Add to this that the most popular platform here is probably desktop Linux.
Mastodon users are vastly different, especially since the second wave of Twitter migration. Most of them are on phones, many are only on phones. Almost all came from Twitter. And what they sought was not something like Twitter, but more for geeks. What they sought was Twitter without Musk, but otherwise 100% Twitter. And Mastodon was promised to them to be just that.
Also, unlike us, Mastodon users were generally mollycoddled to no end from the very moment they got disgruntled with Twitter. They were always protected from the harsh reality of the Fediverse outside Mastodon and, in fact, from much of what makes Mastodon "harder" to use than Twitter.
We had to fire up a search engine to find a website that lists Hubzilla hubs, including whether sign-up is open or not. They weren't even told that Mastodon is decentralised. Instead, they were railroaded to mastodon.social or any other big instance, and decentralisation was kept away from them until they had settled in and made themselves comfortable.
They weren't told either that the Fediverse is more than just Mastodon. I think nobody even thought about what'd happen if they find that out because those who mollycoddled them and railroaded them onto Mastodon were and often still are barely aware of that themselves.
It usually took them months to even read about Pixelfed and PeerTube which are all over Mastodon. Okay, so there's an Instagram and a YouTube in the Fediverse, too. Neat. Okay, and WordPress connects to the Fediverse, too. Maybe neat. Okay, and there's actual Instagram by Facebook pushing into the Fediverse. Not so neat.
But even then, they did not know or even expect that there are other things in the Fediverse that do the same as Mastodon. And do it differently. It took them the odd month on top of that to learn about that.
Hubzilla users are kind of intrigued when someone from remote corners of the Fediverse connects to them. We're used to federating with anything and everything because that's a killer feature.
Mastodon users of about six months or less recoil from their phones or computers when they see a post with over 500 characters for the first time. This shouldn't even be possible! Mastodon can't do over 500 characters! Witchcraft! Black sorcery!!!
It gets worse if they see text formatting.
It gets even worse if they see someone being quoted or "quote-tweeted". It gets much worse if it's them who is being quoted or "quote-tweeted".
Again, their first reaction is that this shouldn't be possible, and that this has to be some black-hat hacker's work. This just has to be illegal.
If that offending post came from you, and they ask you what you've done, and you tell them you're on Hubzilla, their first understanding is that Hubzilla is the name of a Mastodon instance. You know, like Universeodon.
If you tell them it isn't, they'll assume that Hubzilla is a Mastodon fork.
Then you tell them it isn't that either. It's a wholly independent project that has nothing to do with Mastodon. And they'll wonder why someone would make something like Hubzilla if there's already Mastodon. Mind you, at this point, they still assume that Gargron has made Mastodon in 2022 as a reaction upon Musk's plans to take over Twitter, and everything else was made after that. Because "everybody knows" that Gargron invented a) Mastodon, b) ActivityPub and c) the Fediverse.
Because nobody has told them otherwise before they joined. Because that would have made things so overwhelmingly complicated that they would have noped away from Mastodon.
Well, and then you tell them that Hubzilla is, in fact, older than Mastodon. It literally existed before Mastodon was even made. And even with Mastodon being six years older than they think, Hubzilla is almost another whole year older than Mastodon. And Hubzilla is a fork of a fork of another Fediverse project, Friendica, that's almost six years older than Mastodon.
Tell you what: They might still refuse to accept that there has been something in the Fediverse before Mastodon. Okay, if Hubzilla is actually older than Mastodon, it must have been made to federate with Mastodon just recently. Hubzilla is a rude, reckless intruder in Mastodon's nice and cosy and fluffy Fediverse that refuses to adapt to Mastodon and its culture.
At this point, their assumption is still that the whole Fediverse was built around Mastodon.
And then you tell them that, no, Mastodon is the intruder. When Mastodon was launched, it immediately federated itself with Friendica and Hubzilla and GNU social because it spoke GNU social's language from the very beginning, and Friendica and Hubzilla spoke and still speak that language, too, only that all three did so already before Mastodon. Oh, and even when Mastodon adopted ActivityPub, Hubzilla had it first.
This will drive them further into defending Mastodon's alleged position as the supreme leader over the whole Fediverse to whom all others have to bow. Well, at least it's the best. Everything else has to be inferior. Or why else is Mastodon the biggest
Well, that's because 99% of all Mastodon newbies were railroaded into it. They weren't given a choice between Fediverse projects. Either because whoever showed them the Fediverse didn't want to make matters too complicated and spare them of having to choose, or because whoever showed them the Fediverse only knew Mastodon, too. And it usually takes them months to find out the disturbing truth that the Fediverse is, in fact, not only Mastodon.
And since there's no easy-peasy, nomadic-identity-level way of moving from instance to instance and from project to project outside of Hubzilla and (streams), and since they don't want to get used to yet another project, and since Mastodon has the vastly best support for mobile apps (remember, everyone's on phones), they're stuck on Mastodon, demanding that Mastodon and their home instance introduce features that are readily available just about everywhere else in the Fediverse.
And since they're tendentially tech-illiterate and used to being mollycoddled, they demand all new Mastodon features have their personal preferences as the default settings.
Not to mention that they'll neither understand nor accept that other projects may have a different culture and have had it since times long before Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon
New Comic Trailer: LONG HAUL Coming Feb. 21 from Storm King Comics
The Barren Highways of the American West Become a Place of Terror and Violence in a No-Holds-Barred Tale Not for the Squeamish
The sun-baked deserts and wide-open vistas of the American West may have inspired tales of romance and grand adventure, but LONG HAUL, the newest graphic novel...
haul king
Ontario expands program to train long-term care staff
Ontario is extending a program that helps long-term care homes provide clinical placements for nursing and personal support worker students.
-termCare -termcareministerStanCho -TermCareStaffing
Ontario expands program to train long-term care staff
Ontario is extending a program that helps long-term care homes provide clinical placements for nursing and personal support worker students.
-termCare -termcareministerStanCho -TermCareStaffing
In the end, people have a choice of who they follow and who they don't. And with the fediverse, they have a choice of platform. If someone does not want to see over 500 characters, then they should not follow people who post over 500 characters. And there is even a block function, if they don't want to see their comments either.
Mastodon users don't necessarily only react like this upon posts in their personal timelines.
See, Hubzilla's pubstream is optional, and almost all hubs have it turned off. Mastodon's federated timeline is not optional, always on and quite popular. And I guess not few Mastodon users react upon posts in the federated timeline the same as upon posts from their own contacts.
Ideally, instead of content warnings, Mastodon should just collapse long posts and add a "read more" option. I thought it already did that, but if it doesn't, that feature should be added.
Mastodon's Web interface does have this feature.
But the vast majority of Mastodon users is on phones, using dedicated apps. And some apps were built by people who at that point didn't know that the Fediverse is not only vanilla Mastodon. They made them under the assumption that there'll never be posts longer than 500 characters in the Fediverse. So they didn't add a post collapsing feature because they deemed it unnecessary for posts of 500 characters and shorter.
Either they still don't know that posts over 500 characters are possible, even on Mastodon. Or it's too late now adding post collapsing would require re-writing half the app.
That, or there are apps which let you turn collapsing completely off, and people actually do that.
Otherwise, there wouldn't be complaints by people for whom extremely long posts show up in their timelines at full length.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Ontario expands program to train long-term care staff
Ontario is extending a program that helps long-term care homes provide clinical placements for nursing and personal support worker students.
-termCare -termcareministerStanCho -TermCareStaffing
Mumbles Pier, Swansea South Wales
image destinations wales
Das Fediverse ist eben Mastodon. Und alles, was nicht Mastodon ist, hat auch geflligst Mastodon zu sein. Das sind die Eindringlinge, die die Ruhe in Mastodons Fediverse stren. Auch Friendica von 2010 und Hubzilla von 2015, die die Frechheit besaen, sich in dem Augenblick mit Mastodon zu fderieren, als Mastodon 2016 startete.Alles, was Nicht-Mastodon-Projekte knnen, strt. Auch nur ein bichen ber 500 Zeichen, Textformatierung, Codeblcke, Listen, Zitate, Quote-Posts usw. Ich bin ja sogar schon angegangen worden, weil meine Mentions so komisch aussehen, und ich sollte das geflligst abstellen.
Ich warte wirklich schon darauf, da ganze Projekte gefediblockt werden sollen, weil deren Nutzer sich so unmastodonhaft benehmen.
Meinen Main hast du, wie's aussieht, auch schon geblockt, weil ich mich nicht wie auf Mastodon benehme. Daher verwende ich hier jetzt meinen Klon.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NichtNurMastodon Find the latitdue and longitude of any place
Woran wrde ich sehen, wenn jemand nicht von Mastodon kommt
Ein paar Beispiele ohne Anspruch auf Vollstndigkeit:
- Posts mit ber 500 Zeichen mssen nicht von Mastodon-Instanzen mit gehacktem Zeichenlimit kommen. Die knnen durchaus auch von Mastodon-Forks oder ganz anderen Projekten kommen.
- Listen wie die hier. Fettschrift. Kursivschrift.
Codeblcke.Zitate (siehe oben). Quote-Posts.
Wenn du so etwas siehst, dann weit du: Der Post kommt nicht von Mastodon. Denn Mastodon kann all dies zwar anzeigen, aber nicht erzeugen. - Guck dir Hashtags an. Ist die Raute ein Teil des Hashtag-Link Wenn nein (also #
Hashtagstatt#Hashtag), kommt der Post von Friendica, Hubzilla oder (streams). - Guck dir Mentions an.
Wenn sie einfach nur den Kurznamen zeigen (Simone21oderjupiterrowland) und das ein Teil des Link ist, knnte der Post von Mastodon kommen.
Wenn sie den Kurznamen und die Domain anzeigen (Simone21mastodon.socialoderjupiterrowlandhub.netzgemeinde.eu) und das ein Teil des Link ist, kommt der Post von Misskey, Firefish, Iceshrimp, Sharkey, Catodon oder einem der anderen Forkeys.
Wenn sie den Langnamen mitsamt Leerzeichen anzeigen (Simone,Jupiter Rowland) und das kein Teil des Link ist, kommt der Post von Friendica, Hubzilla oder (streams). - Wenn die Bilder, die unterm Post hngen, ganz offensichtlich in umgekehrter Reihenfolge sind, kommt der Post nicht von Mastodon zumindest bei Posts von Friendica, Hubzilla oder (streams) tritt das Phnomen auf.
- Dito, wenn der Post mehr als vier Bilder erwhnt. Dann hat er im Original nmlich mehr als vier Bilder. Aber Mastodon kann nicht mehr als vier Dateianhnge.
- Wenn jemand auf einen eigenen Artikel/Blogpost oder gar auf ein eigenes Wiki oder sogar eine eigene Webpage verlinkt, und die liegt auf genau derselben Subdomain, von der auch der Post kommt, und enthlt den Kurznamen des Nutzers (z. B.
hub.hubzilla.de/channel/jupiterrowland), dann hast du es mit Hubzilla zu tun. - Leute, die gegen Mastodon stnkern und sagen, andere Projekte sind besser, sind nie auf Mastodon.
- Achte mal auf die Instanzdomain.
Einige enthalten von vornherein den Namen des Projekts. Wo "pleroma" oder "misskey" oder "sharkey" oder "lemmy" oder "streams" dran steht, das ist mit Sicherheit kein Mastodon.
Manchmal gibt's auch ein Krzel als Subdomain. "hub." ist meistens Hubzilla, "mk." ist gern Misskey o. .
Ansonsten kannst du es auf dem Webinterface auch selbst berprfen:
- Klick auf die drei Punkte unten rechts unter dem betreffenden Post.
- Klick auf "Open original page" oder wie auch immer das letztlich im nchsten Release auf Deutsch heien wird. Ein neuer Tab wird sich ffnen mit demselben Post an seiner ursprnglichen Quelle.
- Sieh dir diesen Tab an. Wenn es absolut nicht wie Mastodon aussieht und nirgendwo steht, da es Mastodon ist, dann ist es hchstwahrscheinlich nicht Mastodon. Einige Projekte zeigen auch direkt auf jeder Instanz an, was sie sind. Dabei ist es brigens hilfreich zu wissen, was es so an Projekten gibt, um deren Namen auf der jeweiligen Website auch als solche identifizieren zu knnen.
Alternativ kannst du auch das Profil des Nutzers aufrufen. Das siehst du auch auf dessen Heimatinstanz und nicht auf Mastodon, wenn es nicht auf Mastodon ist.
Es wrde jetzt allerdings den Rahmen sprengen, wenn ich erklren wrde, an welchen visuellen Merkmalen man welches Projekt erkennt. Einige Projekte sind ja im Aussehen extrem variabel, und bei einigen Projekten knnen sogar die Nutzer das Aussehen ihres Kontos oder Kanals verndern.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Fediversum Dann mten aber DFRN (fr Friendica), Zot (fr Hubzilla), Nomad (fr (streams)), BBcode (fr alle drei), Markdown (fr (streams)), HTML (fr (streams) und die Darstellung im Web generell), ActivityPub (fr das gesamte restliche Fediverse) und Rich Text (fr ActivityPub) erweitert werden um die Mglichkeit, Alt-Text an Links anzuhngen.
Auerdem mten ausnahmslos alle Fediverse-Projekte nachziehen, dieses Feature einbauen und obendrein eine separate Vorschau bieten, die mit 100%er Verllichkeit anzeigt, wie der Post letztlich auf Mastodon aussehen wird. Gleichzeitig mten sie ihrerseits die Bildbeschreibung fr Linkvorschaubilder ignorieren, weil es die so nur auf Mastodon gibt.
Nur, damit Alt-Text fr Linkvorschaubilder auf Mastodon perfekt funktionieren.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodon
Also your post sets out two options then the poll has four.
Does Mastodon only support so short option names that the "- sighted" and "- not sighted" appendices are swallowed
Each option is there once for sighted users and once for blind or visually-impaired users. I want to be able to distinguish between their opinions.
And people who want the description in the alt text have no way to vote for it.
That isn't an option, and I've explained in the start post why. Money self-quote:
Note 1: "In the alt-text" is not an option, by the way. Explanations never go into the alt-text. Besides, without a 500-character limit, I don't have to shove stuff into the alt-text because there's no room in the post.
First of all, there must never be any information exclusively available in alt-text. Not everyone can access alt-text. There are physical disabilities that make that impossible. If information is only available in alt-text, it's lost to certain disabled users.
Besides, Mastodon chops off long alt-text that comes in from outside at the 1,500-character mark. And I mean it permanently discards everything that goes beyond 1,500 characters.
This isn't nearly enough for even basic explanations plus visual descriptions in my case. My images are always about an extremely niche topic. Thus, for a casual audience to even be able to understand them, I have to explain a lot, and I have to explain the explanation itself.
1,500 characters aren't nearly enough for that.
includes an explanation that's 2,635 characters long. This is not a typo.
I have to explain what Padm is so sceptical about.
In order to make that understandable, I have to explain in altogether 501 characters what OSgrid is.
Then I have to explain in 572 characters what OpenSimulator is in order for people to understand what OSgrid is.
Then I have to explain in 545 characters what Second Life is in order for people to understand what OpenSimulator is.
Then I have to explain in over 200 characters that and why worlds in OpenSim are called "grids" in order for people to further understand what OSgrid is.
Then I have to explain in 487 characters what it is about OSgrid that has Padm worried.
Without these explanations, nobody but OpenSim veterans would even get the meme. And I didn't even explain the meme template if I were to do that as well, I'd go well beyond 6,000 characters only for explanations because I'd have to go as in-depth as .
Only for explanations. This does not include visual descriptions. And if you've ever actually read any of my over-500-characters-long posts, you should know that my visual descriptions of my own pictures give "excessive" a new meaning. And they come with increasingly extensive general explanations plus detail explanations themselves.
You tell me how to get thousands upon thousands of characters in alt-text into Mastodon in one piece, undamaged.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Auch hier wieder: Mit Friendica, Hubzilla und (streams) technisch nicht mglich.
Noch einmal: Da gibt's kein Alt-Text-Eingabefeld. Alt-Text wird in den Bildeinbettungscode im Post selbst reingeschrieben.
Das heit, wenn du z. B. Alt-Text an ein Bild in einem Post von Hubzilla einbauen willst,
- mtest du den Post selber editieren - wie wrde es dir gefallen, wenn ich absolut ungehindert in deinen Trts rumpfuschen knnte
- mte Hubzilla den originalen Quellcode des Post nach Mastodon durchreichen
- mte Mastodon den Post in seinem originalen Quellcode darstellen
- gbe es keine schicke WYSIWYG-Klickibunti-Darstellung des Post, sondern rohen BBcode, und zwar mit hubzillaspezifischen Erweiterungen, und den mtest du fehlerfrei editieren knnen
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodon
Auch wichtig:
Usern erlauben Alt-Texte erzeugen zu knnen auf ProfilPhoto, ProfilBanner und ALLEN Link-Vorschau-Boxen in Posts!
Ich hoffe nur, da das nie zur Pflicht wird mit Defderation ganzer Instanzen als Sanktion bei Nichterfllung.
Das Fediverse ist nicht nur Mastodon, auch nicht nur Mastodon und Mastodon-Forks. Einige Projekte sind vllig anders aufgebaut und funktionieren vllig anders als Mastodon. Vor allem Friendica, Hubzilla - da bin ich - und (streams) handhaben Alt-Text vllig anders als Mastodon, nmlich nicht in einem separaten Textfeld. Da wre der Aufwand, Alt-Text fr Profilbilder zu erlauben, viel zu gro.
Und Alt-Text fr Linkvorschaubilder ist da berhaupt nicht umsetzbar. Die drei haben gegenber Mastodon zwar den Vorteil, da sie eine Vorschaufunktion haben. Aber die Vorschaufunktion zeigt nicht an, wie die Posts auf Mastodon aussehen werden. Und "zu Hause" sehen sie vllig anders aus als auf Mastodon eine Linkvorschau gibt's da nicht.
Zum einen wrde ein Post mit Link also noch lnger ohne Alt-Text frs Vorschaubild im Fediverse stehen. Unsereins mte nmlich eine Mastodon-Instanz aufrufen, mit der wir verbunden sind, und da dann nach dem Post suchen, und warten, bis er da angekommen ist. Erst dann wissen wir berhaupt, was fr ein Bild Mastodon da eigentlich als Vorschau eingesetzt hat. Und bis der Alt-Text geschrieben ist, der Post editiert ist und der Edit durchs ganze Fediverse durchgereicht ist, das dauert nochmal.
Zum anderen ist das eh irrelevant, weil so etwas auf Friendica, Hubzilla und (streams) technisch unmglich ist. Wie gesagt, keine Alt-Text-Eingabefelder. In Posts werden Bilder ja auch nicht als Dateien angehngt, sondern wie in Blogposts eingebettet. Der Alt-Text wird dann ins Markup fr die Bildeinbettung reingeschrieben. Aber ein Link ist nur ein Link. Kein Markup der Welt sieht Alt-Text fr Links vor.
Und:
Ich will endlich QuoteShares auf Mastodon, so da Kommentare zu Posts anderer User, fehlende #BiBesch etc prominent in neuen Posts geteilt werden knnen.
Es wre einfacher, wenn Misskey, Firefish, Iceshrimp, Sharkey, Catodon, Friendica, Hubzilla, (streams) etc. etc. pp. einen Ein-Klick-Totalimport ganzer Mastodon-Accounts anbieten wrden, um das Umziehen zu erleichtern. Die konnten nmlich alle schon immer Quote-Posts.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #NichtNurMastodonI have a question regarding descriptions and explanations for images:
Let's suppose I post an image showing something extremely niche and extremely obscure, something that'd require a whole lot of explanation for most people to understand. This also includes memes.
Let's also suppose I don't have a 500-character limit, for I don't have any character limit.
Where would you prefer general explanations
- Behind an external link.
Advantage: Shorter description, albeit still long.
Downsides: The explanation is not where the image is. The many mobile users will need a separate app, namely a Web browser. And the linked webpage might not be accessible. - In the post itself.
Advantage: Everything in one place and guaranteed to be accessible.
Downside: Thousands of characters more in an already very long image description.
All options are listed separately for sighted and non-sighted users.
Please boost for a larger sample size!
Note 1: "In the alt-text" is not an option, by the way. Explanations never go into the alt-text. Besides, without a 500-character limit, I don't have to shove stuff into the alt-text because there's no room in the post.
Note 2: "No description" is not an option either. You shouldn't just leave it to your readers to search the Web for whatever they don't get. Besides, no, you can't Google everything, and ChatGPT doesn't know everything either.
Note 3: Explanations for specific elements in an image that go along with describing what they look like will always go into the image description, i.e. into the post, especially if there is no external webpage explaining them.
#Poll #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #DescriptiveText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #Accessibility #A11y #Inclusion #Inclusivity #Blind #VisuallyImpaired Just FYI: At least Hubzilla has the built-in functionality to add a geographic location to each post, and you can optionally even enter a default location into your channel settings. There's an optional app named that can show the post location or any other place in OSM. There's also an optional app named that can be used to plan meetings using OSM as the map provider.
Both and have similar OpenStreetMap add-ons, but they don't have anything like Rendez-vous.
Granted, it all dates back to before Mastodon, so it isn't geared towards working with Mastodon. Also, it isn't built against ActivityPub primarily but against DFRN (Friendica), Zot6 (Mastodon) and Nomad ((streams)). But maybe it's worth checking out.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #OpenStreetMap (streams) has always been a fully-fledged Fediverse server application capable of working as a decentralised social network, only that it has been slimmed down in extra features in comparison to Hubzilla to be easier to maintain. Its federation is reduced to Nomad, Zot6 and ActivityPub, and apps like Calendar, Articles, Webpages and Wiki are gone, too, while it got to keep WebDAV, CardDAV and now-headless CalDAV. On the other hand, its ActivityPub connectivity has been improved.
Its original intention was not to be built into other projects, but other projects to be built around/on top of it by developing add-ons for it and giving it a name. (streams) itself doesn't have a name, doesn't have a brand, doesn't have a logo and isn't actually even a project, only a software repository. But if you take what's in that software repository and install it on a Web server, you still get something that blows Friendica out of the water in all but cross-protocol federation, calendar and maybe fancy UI elements.
Its main "issues", apart from not handling anything like Mastodon either, are that it has precious few public instances with open sign-up, and that its very concept (it doesn't have a unique identifier for its instances, and it's being kept away from all instance listing websites) makes its instances next to impossible to find unless you already know one.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
"a full, nomadic-identity-style move from Mastodon to anywhere is technically impossible"
It really isn't. Moving your social graph is built in. The lack of content portability is a problem, but there's tool now that helps with that
It still isn't nomadic identity style.
Imagine you move from foo.social to bar.social. Your whole account, just without the instance-specific login credentials, moves along with you. Including all your posts.
Now it comes: Your posts don't re-appear on everyone's timelines as new, unread posts as they normally would. They don't appear as read double posts either. Your whole backlog of existing posts on everyone's timelines all over the Fediverse are being automatically re-assigned from tokyo0foo.social to tokyo0bar.social as the author.
Also, nobody has to re-follow you. All your followers and all your followed are being automatically re-assigned from tokyo0foo.social to tokyo0bar.social, too, without having to do anything themselves.
Also, your account on foo.social is completely wiped and ceases to exist.
Afterwards, everything looks like you've always been on bar.social.
That would be nomadic identity style.
"99% of all Fediverse newbies are railroaded to Mastodon without being told what else there is in the Fediverse"
That's not really what happens, though. No one is strong-arming people to join Mastodon. It's just the one that's caught attention.
That's because the main gateway into the Fediverse is not or . It's rather or which nudges everyone to mastodon.social, too. Or for Japanese users, it's .
Justifiedly so. If you tell people who want to get away from Musk that they first have to choose one out of dozens of Fediverse projects and then one out of dozens or hundreds or thousands of instances without even knowing what either is, they'll nope out because that's way too complicated.
If you railroad them to mastodon.social and leave them to figure out everything themselves when they're ready for it, they'll bite because that's easy enough.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
The rest of your argument is self-perpetuating people use Mastodon because they hear about it, and they don't want to move, so they just wait for it to change
Yes, because moving is so inconvenient. And a full, nomadic-identity-style move from Mastodon to anywhere is technically impossible. But many won't do less than that.
So more and more people use Mastodon even though they hate it
Yes, because 99% of all Fediverse newbies are railroaded to Mastodon without being told what else there is in the Fediverse because that'd just confuse them. People usually take three to six months to even only discover that there are alternatives to Mastodon in the Fediverse, at which point they've fully settled into Mastodon.
The newbies don't hate Mastodon for not being as powerful as e.g. Sharkey. They love it for not being . And they've never even heard of Sharkey at that point, so they can't and won't compare Mastodon to Sharkey.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Three reasons.
One, you can't move from Mastodon to any other Fediverse project with all your content, all your posts, all your settings, all your connections just like so, just like you can move from Hubzilla to (streams).
Two, Mastodon is the only Fediverse project with full, extensive, guaranteed iOS app support. Most "Fediverse" apps are built against Mastodon first and foremost or against Mastodon only. And almost everyone on Mastodon is on phones, mostly iPhones.
Three, coming from Twitter and adapting to Mastodon was hard enough already, and some still haven't recovered from that. You can't expect them to move and learn something new again.
And thus, everyone stays on Mastodon, waiting for features that are perfectly standard pretty much everywhere else to be introduced to their home instance.
And I'm not even counting those who aren't aware what the rest of the Fediverse can do. Or those who simply don't know that there is such a rest of the Fediverse because they think the Fediverse is only Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Hundreds of doctors to sue NHS because government PPE failings gave them Long Covid Vox Political
Health Service Protective Equipment #19 Sivier Political
"Walled garden metaverse" sounds like an oxymoron. If it runs entirely on the servers of one company and has no public API or any way to interact with users from outside a proprietary ecosystem, then what's really "metaverse" about it
Well, everyone and their dog believes that Zuckerberg's virtual worlds platform is officially named "The Metaverse". ("Metaverse" and "The Metaverse" are registered trademarks of Meta Platforms, Inc. All rights reserved.") And both mainstream media and tech media spew out the same non-sense. The only exceptions are tech media specialising in virtual worlds.
Also, as I've already written, Second Life started to officially refer to itself as a "metaverse" in 2022 as a "Hey, we're still here, too, and we're still relevant" publicity stunt. And Second Life has always been a commercial walled garden.
Its API is only public insofar as it was reverse-engineered from the source code of the official viewer after the latter was made open-source in 2006. And that's only a viewer API, a client API, that's used to develop third-party viewers. "Compatibility" with other virtual worlds Well, there's OpenSim which was then built against the other side of the same API and the already existing third-party Second Life viewers and launched in 2007. But while it uses largely the same API and the same formats and the same standards, and while it's decentralised and federated within itself, it can't connect to Second Life. Even the 2008 "Six Lindens manage to teleport from Second Life to OpenSim" publicity stunt was bogus and faked.
I think I might write an article about the latter.
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #Secondlife #Metaverse
- "The Metaverse". Actually named Horizons. Get that into your heads, dammit. And yes, I'm talking about Meta's worlds.
- Cryptobros' attempted get-rich-quick schemes that imply that "the Metaverse" inevitably requires a blockchain, a cryptocurrency (usually either Dogecoin or Etherium or something running on Etherium's blockchain) and expensive NFTs for everything including land. Not seldomly buggy as hell because in-world experience doesn't earn the world owners any money.
- More or less failed attempts by other huge gigacorporations to launch their own monolithic walled garden metaverses for as many use-cases as imaginable. Failed because they came too late.
- The industrial metaverse which is still only a vague idea and probably another buzzword like "the cloud" and "the blockchain".
- Second Life which has slapped the term "metaverse" onto itself in 2022, trying to stay relevant in spite of stagnating user numbers and showing the world it's still around. This actually had even less of an effect than the comparisons between Horizons' simplistic avatars and Second Life's near-photo-realistic avatars and its 20th birthday PR campaign last year.
- Roblox, VRchat, Minecraft etc. They don't even need to refer to themselves as "metaverses" because they're so popular with kids that not much more publicity is necessary.
- which is as decentralised as Decentraland implies to be but isn't. It has been using the term "metaverse" regularly since 2007, the year it was launched. But as it doesn't make a fuss about it, nobody outside its own community knows.
- ThirdRoom which was one of the first FLOSS virtual worlds to work in a standard Web browser rather than requiring a specialised client. Its future is unclear because all three devs are on an indefinite hiatus.
- Vircadia, a HighFidelity fork, and Overte, a Vircadia fork, both trying to build the decentralised next-generation open-source metaverses with some interesting ideas, but neither having a significant community, and both being every bit as obscure and unknown as OpenSim.
- The proposed decentralised, standardised, open metaverse for everyone. Which might not even come because the virtual worlds hype of 2020 is over for obvious reasons, and whoever else would be interested in it is probably busy in other virtual worlds already.
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Meta #MetaMeta #Horizons #SecondLife #OpenSimulator #Decentraland #Roblox #VRchat #ThirdRoom #Vircadia #Overte #TheMetaverse #Metaverse
this guy, Im telling you
How to destroy the essential tools of our decentralized setup and there for the #fediVerse:
...where "Fediverse" is synonymous for "Mastodon", I guess.
* don't boost
I can't boost. Hubzilla doesn't have that feature. Hubzilla "quote-tweets" instead. It has done so since before there was Mastodon. You don't want me to do that instead, do you
* don't use #hashTags
Okay, I can do that. But from your typical Mastodon and formerly Twitter user's point of view, I guess I use way too many because I also use them to trigger filters. So I use a whole lot of them.
* don't follow #hashTags
Hubzilla can't follow hashtags either.
* don't follow groups a.gup.pe
* don't post to groups a.gup.pe
First of all, there isn't a single Guppe group that even remotely covers the primary topic of this channel. There is a Lemmy community for that topic, though, and I'm connected to it.
Besides, I'm connected to various Friendica, Hubzilla and (streams) forums/groups which blow gup.pe clean out of the water feature-wise.
* don't read, understand or follow #fediTips
Right, I don't read them. Because they're all so Mastodon-centric it hurts. Almost none of them can be sensibly carried over to here.
Not to mention the edge-cases I have to deal with that FediTips don't cover, for example when it comes to describing images. I don't have to put everything into the alt-text. I don't have a 500-character limit that prevents me from describing stuff in the post text body and forces me to use only the alt-text.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fedisplaining #CWFedisplaining #NotOnlyMastodon #MastodonIsNotTheFediverse #FediverseIsNotMastodon
Rory McIlroy Vs Micah Morris (Long Drive Contest)
If people actually let you get away with it... I mean, I expect some fundamentalists on Mastodon to demand a full image description in alt-text, no matter how, no matter what, full stop.I almost always put my image descriptions into the post text body for two reasons. One, they contain explanations and other information neither available in the actual post text nor for sighted people in the image itself. Two, they're way too long. They exceed 1,500 characters multiple times, sometimes multiple dozen times. I don't have local character limits to worry about, but at least Mastodon, Misskey and all their forks chop alt-text over 1,500 characters off at the 1,500-character mark.
In addition, I always mention in alt-text where exactly this image description can be found. Not only in the post text body, but I add stuff like "above the image and hidden behind a content warning if you're viewing this post on Mastodon and right below this image if you're viewing this post on Friendica, Hubzilla or (streams)".
More recently, however, I started adding a short description of the image to the alt-text. It actually doesn't even begin to describe the actual contents of the image. It's only there to satisfy the "alt-text must describe the image or else" crowd. I may have alt-texts well beyond the 850-characters mark nonetheless.
And still, I think the only reason why nobody complains about the lack of image description in my alt-texts is because too many Mastodon users or entire instances have muted or blocked me for not acting "Mastodon-like" enough.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Weil es zu fast allen Themen Leute gibt, die sich darber aufregen, da die nicht hinter einer CW versteckt werden. Ja, auch Katzenbilder (CW: cats).
Deswegen bin ich dafr, da Mastodon mal den umgekehrten Weg geht. Zur Abwechslung mal nicht dem ganzen Fediverse seine eigene Kultur aufzwingt, die geprgt ist durch technisch ungerechtfertigte Beschrnkungen, Neuerfinden von Rdern und Walled-Garden-Denken. Statt dessen mal was nicht nur technisch, sondern vor allem in seine Kultur bernimmt, was im Fediverse vor Mastodon der Standard war:
Content Warnings aus Filtern. Automatisch generiert fr jeden Leser individuell.
Das kann Mastodon auch, und zwar seit Version 4.0, also seit letztem Jahr. Nur nutzt das keiner, und zwar aus einer ganzen Reihe an Grnden:
- Die Urgesteine und die Nutzer der ersten drei Migrationswellen (Februar 2022, November 2022, Mrz 2023) sind im Kopf immer noch auf anderen Mastodon-Versionen und haben von diesem Feature noch nichts gehrt.
- Newbies sind noch nicht so weit.
- Twitter hat sowas auch nicht, also kennt man das gar nicht. Vor allem nicht, wenn man Mastodon stur weiter wie Twitter benutzt.
- Fr technisch Unbedarfte sind die Filter viel zu kompliziert zu bedienen.
- Fr Mobilnutzer, also geschtzte 98% der heutigen Mastodon-Nutzer, sind sie unbedienbar. Ich glaube, keine einzige Smartphone-App hat Filtersteuerung eingebaut, also braucht es die Weboberflche. Und da gehen die meisten Mobilnutzer nie hin.
- Was ntzt es, Filter zu haben, wenn die Leute zu faul sind, Keywords oder Hashtags in ihre Posts einzubauen, die die Filter auslsen wrden
Erschwerend kommt hinzu: Viele Projekte, die nach Mastodon als Alternativen zu Mastodon gestartet wurden, wurden nicht nur auf Mastodons Technik, sondern auch auf Mastodons Kultur zugeschnitten. Entweder haben die gar keine Filter, oder die haben bis heute keine Mglichkeit, per Filter CWs zu generieren.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta Okay, here's a bit more. And I'm trying to write this from a Mastodon point of view, but as someone who has got experience outside of Mastodon.
If you're on Mastodon which you probably are, get used to the lingo.
- (Twitter) tweet = (Mastodon) toot or post
- (Twitter) retweet = (Mastodon) boost
- (Twitter) like = (Mastodon) fave
This may come as a surprise, but the Fediverse is not only Mastodon. There are many other projects in the Fediverse which are connected to Mastodon. Some of them have actually already been around before Mastodon. And they have features that Mastodon doesn't have. So don't freak out if you see a post with over 500 characters. Or with italics. Or with bold type. Or with a
code block. Or using the content warning for a summary. Or with a quote. Or with a "quote-tweet". Outside of Mastodon, all this is standard and perfectly normal. Get used to it.Use content warnings (CW) to make browsing the #Fediverse safer for all.
Double your content warnings with hashtags. Some projects in the Fediverse outside of Mastodon use text filters to automatically generate individual content warnings for those who need them. And Mastodon can do that, too, so even some Mastodon users do it.
If a post with content that you may deem sensitive has only got these hashtags but no actual content warning, this is not necessarily due to ill intent or neglect. Some Fediverse projects outside of Mastodon can't do content warnings the Mastodon way. Hubzilla can only do them in first posts, but not in replies. On Friendica, they're generally very difficult to do. So don't immediately call for moderation.
Use #AltText on *all* your pictures! Visually impaired people like memes too.
Actually describe your images in alt-text. And do only that. No hashtags in alt-text. No links in alt-text. No SEO keyword spamming in alt-text.
If there's text in your picture, transcribe it in alt-text word by word.
You can mute, block, and/or report people, depending on the severity of their actions. That said, most people here are pretty cool, so give 'em a chance unless they're being a willful ass-hat.
Don't forget: Different instances have different rules. So don't report someone on another instance for not adding a content warning that's mandatory on your instance but not on theirs or the like. And don't forget either: Different projects have different capabilities and different cultures of using them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fedisplaining #CWFedisplaining #MastodonIsNotTheFediverse #NotOnlyMastodon #FediverseIsNotMastodon #Hashtag #Hashtags #AltText
Anfangs schrieb ich lange Aufstze wie in der Schule. Dann meldete sich mal ein Blinder und meinte, allzu ausfhrliche Beschreibungen, seien gar nicht so erwnscht: Eigentlich klar: Whrend die Sehenden das mit einem Blick erfassen, mssen Blinde den ganzen Text sich vorlesen lassen. Am schwierigsten finde ich zu erkennen, was einem Blinden ntzt uns was nicht.
Da gibt es leider keinen wie auch immer gearteten Konsens, auch wenn einige behaupten, den gbe es. Genau wie mit der Lnge und Ausfhrlichkeit von Bildbeschreibungen.
Die einen Blinden wollen Bildbeschreibungen gern kurz und prgnant. Die anderen wollen sie ausfhrlicher. Z. B. lassen sie sich nicht damit abspeisen, da du Elemente in einem Bild erwhnst, sondern sie wollen auch wissen, wie das alles jeweils aussieht.
Wenn du jegliche Bildbeschreibung in den Alt-Text packst, bringt das fr Blinde noch einen weiteren Nachteil mit sich: Screenreader knnen Alt-Text nicht navigieren. Das heit, die knnen nicht innerhalb des Alt-Text an eine bestimmte Stelle zurckspringen, sondern nur wieder ganz zum Anfang, um dann alles wieder von vorne durchzurattern.
Das ist einer von diversen Grnden, warum ich z. B. meine ausfhrlichen Bildbeschreibungen immer in den Post selbst packe. Ein anderer ist, weil sie meistens weit lnger als 1500 Zeichen werden, aber zumindest Mastodon, Misskey und die Forkeys schneiden Alt-Text an der 1500-Zeichen-Marke hart ab.
Allerdings poste ich im allgemeinen Bilder zu einem sehr obskuren Nischenthema. Die meisten Leute brauchen sehr, sehr viel Erklrung, um die Bilder zu verstehen. Und gerade meine eigenen Bilder sind manchmal ziemlich komplex, auch wenn ich versuche, das zu vermeiden.
Wie gut meine Beschreibungen ankommen, wei ich nicht. Ich habe bisher mehr Bilder beschrieben als Feedback dafr bekommen, und zwar inklusive Feedback von Leuten, denen ich ausdrcklich meine Bilderposts als Beispiele fr lange, detaillierte Bildbeschreibungen gezeigt habe. Ungefragtes Feedback hatte ich bisher nur einmal, auch wenn das positiv war.
Wer noch nie "rot" gesehen hat fngt sich mit rotem Kleid wohl eher wenig an.
Nicht jeder, der blind ist, wurde blind geboren. Wer irgendwann in seinem Leben erblindet ist, hat frher mal Farben gesehen, also auch einen Begriff von Farben.
Auerdem ntzen Bildbeschreibungen nicht nur Blinden, sondern auch Sehenden, die mieses Internet haben, wo die Bilder berhaupt nicht laden.
Ich wrde Farben immer erwhnen.
Gibt es diesbezglich eine Anleitung/FAQ
Die meisten, die es gibt, sind nur fr professionelle/kommerzielle statische Websites oder vielleicht noch professionelle/kommerzielle klassische HTML-Blogs. Die meisten, die Social Media behandeln, sind nur fr kommerzielle Social Media, also Facebook, Twitter, Instagram, LinkedIn usw. Und die paar, die tatschlich das Fediverse behandeln, sind nur fr ganz normales Vanilla-Mastodon und gehen felsenfest davon aus, da Posts nicht lnger sein knnen als 500 Zeichen.
Die Sonderflle "Zeichenlimit deutlich ber 500 Zeichen" und "Social-Media-Post mit Bild, das viel Beschreibung und/oder Erklrung braucht", sind noch nie in so einer Anleitung abgedeckt worden.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch "MIA" means "missing in action".
I don't know all the details, just so much: The last time Kainoa was seen contributing to the Firefish repository was in June or July. Around that time, I guess, was also the last time that Kainoa was seen taking care of firefish.social. Kainoa is still alive and well and has posted something not long ago. Could be busy, nobody knows.
Anyways, fast-forward to December, 2023/January, 2024. Due to literally no maintenance whatsoever because the only admin hasn't shown up in a while, firefish.social has become entirely unresponsive. Nothing works anymore.
Also, Firefish is badly lagging behind Misskey's development. Not only no new features, but also no bug fixes, no security fixes, no nothing.
So the Firefish community took matters into their own hands. Just to mention three new forks:
- Iceshrimp was forked from Firefish, but pretty much immediately rebased to Misskey because Firefish was hopelessly outdated. It is currently being rewritten in C#.
- Sharkey was forked directly from Misskey, probably because Firefish's codebase would have needed too much maintenance. But some Firefish features shall be ported to Sharkey.
- Catodon was forked from Misskey as well, but with a different focus. Whereas Sharkey's goal is to become a Firefish replacement that has never been Firefish in the first place, having features that Misskey doesn't have while still keeping that typical Japanese style, Catodon is being tailored for Western tastes and simplified to Mastodon's level. Whether that only affects the UI or typical Misskey/Forkey features being cut, I don't know.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon
Todays playlist is long songs. Everybody likes sagas:
This could work, and it could be a first step away from the oft-criticised "content warning field" and towards reader-side text filters which, by the way, have been in the Fediverse for longer than Mastodon itself.Web interfaces could get switches like these, too, and ideally, admins could add their own switches, depending on the target audience of an instance. Ideally, apps could recognise these custom, instance-specific switches and add them to their UI.
On the posters' side, it'd still require discipline because they'd have to add appropriate hashtags, and these hashtags would have to be standardised, otherwise each filter would have to cover each trigger with half a dozen different hashtags per language or so. Dedicated apps could assist in this by adding checkboxes to the post editor which have the app automatically add appropriate standard hashtags for certain topics to the "hashtag line" at the end.
This could actually start in apps without breaking standards, and it could nudge Mastodon itself into adding it to its Web UI. In fact, I can see at least some Forkeys being quicker at introducing it.
The best part: This would move the Fediverse away from something Mastodon-specific and towards something more standard.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta
To be honest, I'm even feeling like maybe this shouldn't be a feature, just so the Twitter-refugees don't use it, because then they will think that that is somehow what's protecting them from harassment, and not the fact that this isn't Twitter.
Even if Mastodon won't introduce the creation of quote-posts, Misskey, the various Forkeys (Firefish, Iceshrimp, Sharkey, Catodon etc. etc.), Friendica, Hubzilla and (streams) can quote-post just about any Mastodon toot out there with no resistance whatsoever. They always could, even when Mastodon wasn't able to display quote-posts halfway appropriately.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta To be fair, this doesn't apply to all the Fediverse. Mastodon, yes, but not the entire Fediverse.
I dare say there are two projects which handle this marvellously: from 2015 and a fork of a fork... by Hubzilla's own creator, commonly referred to as while technically being nameless. While both can "talk ActivityPub", they are based on different protocols which give them a feature that Bluesky tries hard to make everyone believe that they're working on inventing: .
First of all, Hubzilla and (streams) don't put your Fediverse identity directly into your account. Your account only grants you access. Your identity, your connections, your posts, your settings, your content etc. etc., all that resides in a , a kind of container. You can have multiple channels on one account, so you can also have fully separate identites on the same instance without having to log out and back in.
Nomadic identity itself can do two things. One, it takes care of moving a channel to another instance. And I mean actually moving it, not creating a dumb copy and leaving a dead account behind.
Two, and this is the actual killer feature, it can clone your channel to another instance. Again, not create a dumb copy. The clone is always synchronised with the original and vice versa. If one goes down, you've got the other readily at hand, so you're even safe from spontaneous shutdowns. And you can have more than one clone for each one of your channels.
Basically, moving is cloning light. Moving creates a synchronised clone, declares the clone the new main and the old main a clone, then deletes the old-main-gone-clone, and if there aren't any other channels on your old account, deletes that account.
Nomadic identity was invented in 2011 by who also created Hubzilla, now maintains (streams) and, in 2010, had created which was named Friendika back in 2011. Public Friendika nodes closing down had become a serious issue already, regardless of whether the shutdown was announced or came out of the blue. Early on, whenever this happened, all users on the node lost everything and had to start over from scratch.
Friendika eventually introduced moving from node to node by exporting and importing your account, but real resilience would have been different. Thus, nomadic identity was conceived. The Zot protocol was written around it because it couldn't be introduced to Friendika's DFRN protocol. In 2012, Friendica was forked and its backend re-written against Zot, becoming the Red Matrix, direct precursor of 2015's Hubzilla.
In a perfect Fediverse, everything would feature nomadic identity. But as it stands now, everything that isn't these two projects doesn't even understand nomadic identity and is easily confused by nomadic moves or someone posting from their clone instead of their main.
Unfortunately, nothing will change about this anytime soon. Mike Macgirvin has already proposed extensions for ActivityPub that'd introduce nomadic identity, albeit not in exactly the same fashion as on Hubzilla and (streams), but probably somewhat compatible. However, they have all been rejected.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #NomadicIdentity This might be a case of Chinese whispers.
What really increases accessibility when it comes to hashtags is how they're written if they consist of multiple words.
Always write multiple-word hashtags in "camelCase" (every word after the first one starts with a capital letter) or, better yet, "PascalCase" (every word starts with a capital letter). Screen readers used by blind or visually impaired users can't tell with certainty otherwise where a word ends and the next one starts.
Also, stop using Mastodon like Twitter and put all hashtags at the end of the post instead of into the text.
#Long #LongPost #CWLong #CWLongPost #Hashtag #Hashtags #Accessibility #A11y #camelCase #PascalCase
I consider this a reasonable compromise to be making with the people who are concerned about Quote-Responses, most of which seems to just be Twitter users, who are used to in environment which actively encourages using the feature, which is common on many websites, as a method of harassment, which is encouraged on Twitter but would be grounds for an instant ban on mainstream Fedi.
What do you mean would cause an instant ban The use of quote-posts for harassment or the use of quote-posts in general
I don't know if you've read the whole thread. I've already posted in it. If not: Lots of Fediverse projects have quote-posts regularly implemented. Two of them, Friendica and Hubzilla, have had them before Mastodon even existed, and it was Mastodon which federated itself with them and not the other way around. They call them "shared posts" and use them for the same purpose as Mastodon uses boosts: to forward posts.
They also both had quotes like the one above since their respective inception.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Last updated: 2024-02-04
All text and images © eLoc8.is-fabulous.com