...berschriften...
Come to think of it...
Imagine someone made an automatically generated instance filter list for Mastodon that tries to contain all instances of everything that isn't vanilla Mastodon. No matter if it's Glitch or Pixelfed or Lemmy or Sharkey or Hubzilla or Threads or whatever.
Imagine whatever created that filter list even scraped the Communities pages of (streams) instances and then started scraping the Communities pages of new (streams) instances it found there. That'd be the only way to discover (streams) instances. Imagine that scraper even went for the last remaining Osada, Zap, Misty, Redmatrix and Roadhouse instances.
What do you think, how many Mastodon instances would actually include that filter list How many Mastodon users would demand that list be used on whichever instances they're on if they find out that the list exists
#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #NotMastodon #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Dann hier nochmal der Block, der sich an dich richtet:
Ach ja, nur zur Information, : Friendica und Hubzilla sind keine Eindringlinge. Die waren zuerst hier.
Mastodon ist von 2016. Hubzilla ist von 2015 und umbenannt aus der Red Matrix von 2012. Und Friendica ist von 2010 und somit das lteste Fediverse-Projekt, das ActivityPub untersttzt.
Als Mastodon 2016 startete, sprach es sofort eine Sprache, die Friendica und Hubzilla zu dem Zeitpunkt auch schon sprachen: OStatus. Das heit, Friendica und Hubzilla haben sich nicht mit Mastodon verbunden, sondern Mastodon hat sich mit Friendica und Hubzilla verbunden.
Und als 2018 ActivityPub kam, hatte zumindest Hubzilla das auch schon vor Friendica.
Aber wenn dich so Sachen wie ber 500 Zeichen am Stck, Fettschrift, Kursivschrift,
...und "komische" Mentions stren, dann steht es dir frei, durch die Instanzenlisten von allem, was nicht Mastodon ist, zu gehen und sie alle fr dich zu blockieren. Links zu solchen Listen findest du unter anderem .
Ich jedenfalls komme zwar Mastodon einigermaen entgegen, aber komplett verbiegen und mich komplett auf das beschrnken, was Mastodon 3.x konnte, werde ich definitiv nicht. Dann gbe es von mir nmlich auch keine Bilder mehr, weil ich meine Bilder nicht in 1500 Zeichen oder weniger beschreiben kann.
CC:
#Long #LongPost #CWLong #CWLongPost #Lang #LangerPost #CWLang #CWLangerPost #Fediverse #Mastodon #NichtNurMastodon #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Weil Mastodon doppelt soviele Nutzer hat wie alles andere zusammen.
Und weil 99,9% dieser Nutzer die ersten Monate ihrer Zeit auf Mastodon glaubten, das Fediverse sei nur Mastodon. Fr sie hat Eugen Rochko sowohl das Fediverse als auch ActivityPub erfunden. Und als sie erstmals erfuhren, da es im Fediverse noch was anderes gibt, weil sie einen "Trt" mit ber 500 Zeichen oder Textformatierung oder einem Zitat oder so sahen, empfanden sie alles, was nicht Mastodon ist, als Eindringlinge in ihr schnes, gemtliches, flauschiges Mastodon-Fediverse.
Genau diese Leute htten es am liebsten, wenn das Fediverse nur Original-Vanilla-Mastodon wre. Am besten das "gute alte" Mastodon 3.x. Alle anderen Projekte haben zu verschwinden. Das wird aber nicht passieren.
Okay, dann sollen die anderen Projekte eben zu 100%igen Mastodon-3.x-Klonen werden und alle ihre Spezialfeatures aufgeben. Das wird aber auch nicht passieren, schon gar nicht, wenn hinter einem Projekt ein Mike Macgirvin steckte oder noch steckt.
Tja, dann haben eben alle Mastodon-Instanzen alles zu fediblocken, was nicht Mastodon ist. Nur da das ein Katz-und-Maus-Spiel wird, weil man keine ganzen Projekte am Stck fediblocken kann und stndig neue Nicht-Mastodon-Instanzen auftauchen.
Also haben geflligst die Nutzer aller anderen Projekte sich so zu verhalten, als wren sie auf Mastodon. Alles, was ihre Instanzen knnen, was Mastodon nicht kann, haben sie zu lassen.
ber 500 Zeichen sind nicht erlaubt, weil man auf Vanilla-Mastodon nicht mehr als 500 Zeichen trten kann.
Textformatierung ist nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte und man auch auf Mastodon 4.x sowas nicht selbst machen kann.
Zitate sind nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte und man auch auf Mastodon 4.x nicht zitieren kann.
Quote-Posts sind nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte, Mastodon 4.x die immer noch nur unzureichend darstellt, man auerdem auf Mastodon 4.x nicht selbst quote-posten kann und Quote-Tweets ja sowieso bse sind.
Hashtags fr automatisierte Content-Warning-Filter Darf man auch nicht benutzen. Vor Version 4.0 konnte Mastodon keine Content Warnings per Filter, also sind Content Warnings auf Mastodon nur als ebensolche im Content-Warning-Feld erlaubt. Ungeachtet der Tatsache, da andere Projekte Content-Warning Filter schon hatten, als es Mastodon noch gar nicht gab.
Ach ja, das Content-Warning-Feld ist das Content-Warning-Feld und NUR fr Content Warnings. Und fr nichts anderes. Auch wenn es tausendmal auf Hubzilla schon "Summary" hie, bevor es Mastodon berhaupt gab.
Wenn man auf Friendica, Hubzilla oder (streams) mehrere Bilder postet, hat man die a) nicht in den Post einzubetten, sondern hinten anzuhngen und b) die Bilder in umgekehrter Reihenfolge einzustellen, damit sie auf Mastodon wieder richtigherum sind. Auch wenn man einen Mastodon-Kontakt und 100 Friendica/Hubzilla/(streams)-Kontakte hat.
Friendica-Nutzer haben bitteschn keine Titel einzutragen. Denn wenn sie das tun, gehen ihre Posts nicht als Notes (= Mastodon-"Trts") raus, sondern als Artikel. Und Artikel kennt man auf Mastodon nicht. Also will man die nicht. Lieber einen Thread aus "Trts" von maximal 500 Zeichen machen, weil das der Standard im Fediverse ist. Oder noch besser: den 80.000-Zeichen-Essay, der auf Friendica problemlos in einem Stck postbar wre, auf maximal 500 Zeichen eindampfen.
Ich bin sogar schon dafr kritisiert worden, wie meine Mentions aussehen. Ich sollte bitteschn aufhren, so "komische" Mentions zu machen und statt dessen die ganz "normalen", die man von Mastodon gewhnt ist. Nur da hier auf Hubzilla die Form der Mentions hartgecodet sind, und zwar schon vier Jahre lnger, als es Mastodon berhaupt gibt. Und Mario Vavti wird einen Deibel tun, daran ohne Not was zu ndern.
Und da wundern sich einige, warum so manch ein Nutzer von Friendica, Hubzilla oder (streams) ActivityPub komplett deaktiviert bzw. gar nicht erst aktiviert hat. Sie haben einfach keinen Bock, auf einmal so zu tun, als wren sie auf Mastodon, sobald jemand auf Mastodon ihre Posts lesen kann, und auf all die Features, die Friendica und Hubzilla schon hatten, bevor es Mastodon gab, wegen derer sie berhaupt erst da sind, wo sie sind, zu verzichten.
Ach ja, nur zur Information, : Friendica und Hubzilla sind keine Eindringlinge. Die waren zuerst hier.
Mastodon ist von 2016. Hubzilla ist von 2015 und umbenannt aus der Red Matrix von 2012. Und Friendica ist von 2010 und somit das lteste Fediverse-Projekt, das ActivityPub untersttzt.
Als Mastodon 2016 startete, sprach es sofort eine Sprache, die Friendica und Hubzilla zu dem Zeitpunkt auch schon sprachen: OStatus. Das heit, Friendica und Hubzilla haben sich nicht mit Mastodon verbunden, sondern Mastodon hat sich mit Friendica und Hubzilla verbunden.
Und als 2018 ActivityPub kam, hatte zumindest Hubzilla das auch schon vor Friendica.
Aber wenn dich so Sachen wie ber 500 Zeichen am Stck, Fettschrift, Kursivschrift,
...und "komische" Mentions stren, dann steht es dir frei, durch die Instanzenlisten von allem, was nicht Mastodon ist, zu gehen und sie alle fr dich zu blockieren. Links zu solchen Listen findest du unter anderem .
Ich jedenfalls komme zwar Mastodon einigermaen entgegen, aber komplett verbiegen und mich komplett auf das beschrnken, was Mastodon 3.x konnte, werde ich definitiv nicht. Dann gbe es von mir nmlich auch keine Bilder mehr, weil ich meine Bilder nicht in 1500 Zeichen oder weniger beschreiben kann.
CC:
#Long #LongPost #CWLong #CWLongPost #Lang #LangerPost #CWLang #CWLangerPost #Fediverse #Mastodon #NichtNurMastodon #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaPersonally and regarding my Hubzilla channel here, I'm not too worried about Threads.
First of all, I'm not going to connect to anyone on Threads. Not even when more than those select few can be followed. As if there's anything going on there that's of interest within the scope of this channel.
Second, Threads users can't follow anyone outside Threads anyway yet.
Third, even if they could, doesn't mean I'd let them if I don't want to. It's up to me to decide who connects to my channel and who doesn't. I have to confirm each new connection, and if I don't, that actor doesn't receive anything from me.
Fourth, the typical incentive for non-Threads users to follow me isn't there for Threads users.
One of the two main reasons why Mastodon users follow me is because they expect me to explain the Fediverse outside Mastodon to them. Your typical Threads user neither knows nor cares for the Fediverse. They're on Threads because it's "Twitter by Facebook without Musk".
The other and even bigger reason for Mastodon users to follow me is because they've just arrived from , and they need some Twitter-like background noise in their personal timelines, so they follow everyone they come across. Threads probably forces loads of background noise upon you right away, so you don't have to take care of that yourself.
Fifth, a channel owned by a virtual world avatar that's primarily about obscure virtual worlds with no real-life information isn't worth data-harvesting. Especially not if I keep badmouthing Horizons and using the term "metaverse" for stuff that's both over a decade older than Horizons and more alive than Horizons because that stuff has been using that word for over a decade itself. Meta would probably rather block this channel before anyone on Threads finds it than harvest it. In fact, I could try to make this process quicker with a few well-placed memes.
Sixth, I can easily silence bad actors on Threads with Superblock.
I was about to ask what the odds are that Threads can federate with Hubzilla in the first place, exotic as Hubzilla is with its ActivityPub support through an optional add-on. But I've got in-bound connections from all over the place already now, from Diaspora* to Misskey to GoToSocial to micro.blog.
Then again, I don't know how Threads handles posts with over 500 characters. After all, it was designed to federate with vanilla Mastodon by people who at that point believed that the Fediverse is only vanilla Mastodon. It could actually be that Threads rejects posts with over 500 characters, just like Misskey and its forks reject posts from a certain length upward.
Finally, if bad came to worse, I wouldn't even have to move away. I could switch ActivityPub off entirely. Granted, that'd mean that I'd lose most of my connections, and I'd have to try and remake those to Friendica using the Diaspora* protocol instead. But that'd completely lock Threads out on a protocol level.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Meta #MetaMeta #Threads
But if "the best product" is only defined as "the closest Fediverse project for iOS users to pre-Musk Twitter" and/or "the project the most compatible with Mastodon", then Mastodon wins.
#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Firefish Ironically, lock-in is part of why Mastodon is twice as big as everything else in the Fediverse combined.
At least for Western users, Mastodon is the only gateway into the Fediverse. Mastodon does little to mention that there's more to the Fediverse, much less what more there is. So people spend three to six months believing that the Fediverse is only Mastodon. Long enough to see the other projects as intruders and want their nice and cosy Mastodon-only Fediverse back when they discover there's more to the Fediverse than Mastodon.
Third-party additions, be it Web services, be it mobile or desktop apps, are almost always built against Mastodon first and foremost. This is either because the creators started working on them when they themselves believed the Fediverse is only Mastodon, and when they found out about other micro-blogging projects, it was too late to implement support for these. Or it's because the creators think it isn't worth the extra effort to officially support anything that isn't Mastodon because nobody uses it anyway.
Mastodon itself keeps getting away with being half-incompatible with the rest of the Fediverse. Certain undocumented homebrew features on Mastodon almost only work within Mastodon itself, including obscuring sensitive pictures for which Mastodon has its own solution and refuses to implement the standard ActivityPub way.
Other features on other projects become half-senseless due to Mastodon's deliberate lack of support for them. Or if Mastodon supports them, the support is only half-baked, such as for quote-posts a.k.a. shares which Friendica has already had six years before Mastodon was launched, and which other projects have, too.
And when only displaying something is supported, but not creating them, it deeply disturbs those who believe or until recently believed the Fediverse is only Mastodon when they come across them because they also believe that this shouldn't exist in the Fediverse. Quotes, quote-posts, text formatting, embedded links or even only posts with over 500 characters. There are actually Mastodon users who want everyone everywhere outside of Vanilla mastodon not to use any features that are unavailable on vanilla Mastodon, and who block everyone who does.
If the best product by features won, most people would be on Firefish or even Hubzilla or (streams).
#Long #LongPost #CWLong #CWLongPost #Fediverse #MastodonWhat all the discussions about whether or not to block Threads reveals is a very common attitude on Mastodon:
"I want my preference to be the default setting for everybody because having to configure something makes Mastodon too complicated!"
Or even:
"I want my preference to be hard-coded for everybody because adding one more setting makes Mastodon too complicated!"
I guess it isn't rare for either to go along with wanting the whole Fediverse to be either Mastodon proper or exactly like vanilla Mastodon. Maybe even exactly like Mastodon 3.x before certain features that are common everywhere else in the Fediverse were introduced to Mastodon such as full-text search, displaying text formatting or displaying quotes. Because it's so hard to wrap your mind around there being differences between Mastodon on one side and stuff like Firefish, Friendica or Hubzilla on the other side.
#Fediverse #Mastodon #MastodonIsNotTheFediverse #NotOnlyMastodon #Threads #Meta #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaMeta
One extreme would be what most people would do, namely only generally mention what the chart is about.
The other extreme is what I would do, namely
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #Accessibility #A11y #Graph As far as I can see, there is no general consensus or agreement upon what's the right amount of description for an image. I guess it also really depends on the image. Cat photographs can do with rather short descriptions while other pictures require descriptions so long that you couldn't possibly post them in one piece anywhere on most Mastodon instances. Good thing there's a Fediverse beyond Mastodon.
There are two things I keep in mind for my own image descriptions. One, if something is obscure and niche enough for average Fediverse users to not know anything about it, it needs to be described and explained. That'd better go into the post text itself, but since my image descriptions often grow extremely long, I put them there anyway.
Two, whenever an image description mentions what there is in a picture, blind or visually-impaired people are likely to want to know what it looks like. So any and all descriptions must include that. It's more ableist not to give visual descriptions than to give them and make the image description longer.
I myself tend to try to include whatever I read about that should be part of an image description. Just recently, someone wondered why so few people mention where they've taken a picture. Good thing I've been doing that ever since I've started writing detailied image descriptions.
It's just unfortunate that people rarely give feedback for image descriptions, especially without being asked for it first. My own image descriptions regularly grow so long that they exceed any idea of excessive. What few people have given me feedback so far, including one who has done it out of the blue, liked them, but such a small number of people couldn't possibly represent all of the Fediverse. Then again, I hardly post images anymore because of how long it takes me to describe them, and fewer images mean even less feedback.
But if it looks like I can get away with image descriptions that are way longer than some essays, I think it's hard for alt-text within Mastodon's 1,500-character limit to be too long.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #CharacterCount #Accessibility #A11y
The field that Mastodon users for content warnings was originally created for summaries.
Now you might rub your eyes in disbelief, wondering if you've actually read what you think you've read. Summary Why would a 500-character toot need a summary
Well, the whole Fediverse outside vanilla Mastodon and Threads supports post with way more than 500 characters by default. For example, Friendica, launched as early as 2010, several months before Diaspora* even, doesn't have a defined character limit at all. Neither does Hubzilla which started as a Friendica fork in 2012. Friendica supports summaries by means of a pair of BBcode tags Hubzilla has a dedicated field for them. And when Mastodon was launched in 2016, it was immediately federated with both.
Mastodon itself was originally based on OStatus which has a summary field in its specification. But since Mastodon was intended to be a micro-blogging service with no more than 500 characters, summaries were deemed unnecessary, and the summary field was re-purposed as a content warning field.
While Mastodon was capable of connecting to all kinds of StatusNet and GNU social instances (Pleroma started life as an alternate GNU social frontend three and a half weeks before Mastodon, by the way) as well as Friendica and Hubzilla, actually doing so was obviously never taken into consideration, much less advertised. So lack of compatibility could be shrugged away with, "Compatibility with what"
By the way, at least Hubzilla has its own solution for content warnings: It has an optional "app" that can generate them automatically - for the reader. It's a dead-simple text filter that has only got a text field for configuration. If any one of the comma-separated strings entered into that field is found in a post, the whole post is hidden behind a button, embedded images and other media and all.
Also, Hubzilla supports spoiler tags behind which parts of posts or whole posts can be hidden again, this can include embedded images, videos or whatever.
So from an old-school Hubzilla point of view, using the summary field for content warnings is unnecessary.
#ContentWarning #ContentWarnings #CW #Mastodon #Friendica #Hubzilla #Fediverse #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
...I'm not interested in using it for image descriptions. Thanks, but no, thanks. I'll go on writing them myself.
#ImageDescription #ImageDescriptions #AltText #AI #Long #LongPost #CWLong #CWLongPost I'm not on Mastodon, and Hubzilla, powerful as it is, has no technical way of hiding a profile picture or a title picture behind a content warning, nor has it any way of making Mastodon hide it.
I mean, I could change my profile picture and my title picture to something that doesn't show me at all. After all, I rarely post pictures with eyes anywhere in them anymore. I have no way of making Mastodon hide them in any way either, not even when I have Hubzilla or (streams) users click three or four times, depending on their setup, until they see the picture in question in the very same post. And hardly anyone uses filters as automated content warnings, so even adding the hashtags #EyeContact and #CWEyeContact is pretty futile.
And I'm normally someone who takes the eye contact content warning and other content warnings very seriously. For me, eye contact is not only when a face fills almost the whole picture. It starts when there's even only one eye anywhere in a picture. I've been told that some autistic people are triggered by faces at a sub-pixel level, i.e. whole faces smaller than one pixel, if the context within the image reveals there's a face. I've issued a content warning for pictures with eyes in pictures in pictures in that picture which measure less than 1/10,000 of a pixel.
I've tested linking to images rather than embedding them into posts, and I've found out that Mastodon does not automatically generate a preview if I link to the image page. This makes viewing my posts more inconvenient, but it should reduce the risk of triggering someone. Unfortunately, the Fediverse being what it is, it doesn't remove the necessity of a full image description.
So yes, I might replace both my profile picture and my title picture with something which I hope is trigger-free. But I'll need to find something that a) fits the purpose, b) fits my channel and c) doesn't make spending hours upon hours on writing image descriptions necessary. I mean, my current profile and title pictures are still without a description I'll have to figure out where to put them where there's enough space.
#Long #LongPost #CWLong #CWLongPost #ContentWarning #ContentWarnings #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
I think there is a webpage about the Sendalonde Community Library. Sendalonde has an entry on OpenSimWorld, and the Discovery Grid has its own website. But all three are separate from each other. Also I'd rather not link to anything external, especially if I can't be sure that it's accessible. And anything about OpenSim usually isn't accessible at all.
Besides, it's cumbersome to have to navigate from website to website to understand what I've posted, on a phone much more so than on a desktop/laptop computer.
That said, I would never put an image description of 40,000+ characters into alt-text. At least Mastodon, Glitch, Misskey, Firefish, Sharkey and their other forks cut alt-text off at the 1,500-character mark and discard everything beyond. Even here on Hubzilla with no screen zoom on, it's hard to show even only the first 3,500 characters of alt-text or so because it can't be scrolled. And alt-text can't be navigated with a screen reader like the post text can be navigated. It isn't possible to jump back to a certain point in alt-text it's only possible to jump back to the beginning and start over.
Last but not least, information that is neither available in the post text nor in the image must never, under no circumstances be put only into the alt-text. There are people who can't access alt-text, for example due to physical disabilities. Any information that's only available in alt-text is inaccessible and therefore lost to them.
That's why I always put such image description into the post text body instead of the alt-text, and then I issue a content warning "CW: long (n characters)", and I add the hashtags #Long, #LongPost, #CWLong and #CWLongPost for those who use filters against posts over 500 characters. This saves people from having unexpectedly hyper-massive walls of text slammed into their faces, especially those using mobile apps which were built under the assumption that a) the Fediverse is only vanilla Mastodon, so b) folding posts up is non-sense if posts with over 500 characters are technologically impossible.
The alt-text contains a short image description so the image is described at least a little for those who don't want to open the content warning, and it mentions that the actual, full-size image description is in the post text.
#ImageDescription #ImageDescriptions #AltText #Accessibility #Inclusion #Inclusivity #A11y
Remember, kids, that there already used to be a connection between what's the Fediverse today and what's Meta today. That was in 2011 when Friendica one-sidedly established bidirectional federation with Facebook. No, I'm not even kidding. Friendica was fully federated with Facebook. It did require a Facebook account, but still, you could use Facebook without actually using Facebook. People would mirror their entire Facebook timelines into Friendica.
This ended when Facebook found out and changed its developer TOS: Third-party applications that connect to Facebook were only allowed to send data to Facebook, but no longer to extract data from Facebook. This led to the slow death of Friendica's Facebook connector.
Fast-forward to 2023: Facebook (the corporation) is now Meta. And they've created their own micro-blogging service for the Fediverse, namely Threads. And now they're opening it to the Fediverse.
Remember that Friendica is still part of that self-same Fediverse.
And what do you know: One of the very very very first connections to Threads came from, wait for it, Friendica!
I think this calls for a variation on the good old meme.
#Long #LongPost #CWLong #CWLongPost #Threads #Meta #Fediverse #Friendica #Facebook #Federation #Meme #FediMeme #MoeTossingBarneyOut #TheSimpsons #FediverseMeta #FediMeta #CWFediverseMeta #CWFediMeta #EyeContact #CWEyeContact To be fair, it's undeniable that there are these vastly different factions in the Fediverse.
The Old Guard, is one of them, has been around since long before there was even Mastodon. The Fediverse didn't start with Mastodon. The Fediverse as we have it now started in 2010 with Friendica, almost 6 years before Mastodon, and it also included Hubzilla which started life in 2012. Both projects which were and still are for extreme tech geeks because even Friendica is too unwieldy for your typical casual social media user.
So that Old Guard consists of absolute ber-geeks on Linux PCs and laptops, many of whom run their own instances without any help from Docker or Yunohost. From their perspective, it was Mastodon which had arrived and federated with Friendica and Hubzilla, not the other way around, because Friendica and Hubzilla had been there first, and Mastodon had always spoken a language which they spoke, too.
Needless to say that they find Mastodon ridiculously underequipped and underwhelming. In fact, Mastodon's refusal to even support certain features of other projects makes life harder for them if they want to stay compatible with Mastodon.
Then you have the millions of Twitter refugees, almost all of whom were mollycoddled and railroaded to their first Fediverse home with as little explanation as possible. They're completely different. They're mostly not very interested in technology, and more of them feel disturbed by Linux talk than use Linux. In fact, most of them are on phones.
Many didn't even know that Mastodon is decentralised until a few months in. Most thought that the Fediverse is only vanilla Mastodon for at least their first three months, during which they got used to their nice and cosy and fluffy and friendly Mastodon-only Fediverse with no posts longer than 500 characters and no text formatting and no quotes etc.
As they're so numerous, they managed to shape Fediverse culture around being non-tech and, worse yet, around the Fediverse being only vanilla Mastodon. And yes, completely disregarding the Old Guard because they knew neither the Old Guard nor the places where the Old Guard resides.
When they came across their first "toot" that looked "weird" because it wasn't a vanilla Mastodon toot, they were greatly disturbed. They felt like whatever project that post came from, Akkoma, CalcKey, Friendica, Hubzilla, whatever, had maliciously intruded into their nice and cosy and fluffy and friendly Mastodon-only Fediverse. And they wanted that to go away again.
They did not want to read what they were told then: Friendica and Hubzilla are not intruders. They were here first. They had been here years before there was even Mastodon. There has never been a time during which the Fediverse was only vanilla Mastodon.
It's such people who demand that the users of everything that isn't vanilla Mastodon limit what they do to what's possible on vanilla Mastodon in order not to disturb those who want the Fediverse to be only vanilla Mastodon. No posts longer than 500 characters, no text formatting, no quotes, no embedded images which don't work on Mastodon anyway, no embedded hyperlinks (only URLs in plain sight instead) etc.
I guess it's clear why the users of everything from Akkoma to Firefish to Friendica to Hubzilla refuse to let themselves be limited by the vastly more numerous Mastodon users.
Well, and then there's the third faction. It's those who have never really arrived in the Fediverse. They don't want anything different. They want Twitter without Musk. Now they're sitting on mastodon.social or another big general-purpose instance and patiently waiting for Bluesky to open registrations because Bluesky is much closer to Twitter without Musk.
These people use Mastodon exactly like they used to use Twitter. Official app only, no more than 280 characters, no alt-texts, no hashtags (what do you mean, Mastodon does not have The Algorithm), no content warnings etc. The only way they've adapted to Mastodon, if at all, was
#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Friendica #Hubzilla #TwitterMigration #TwitterRefugees You can definitely do both with Hubzilla.
For one, you can subscribe to RSS and Atom feeds.
And while you can't directly boost blog posts (Hubzilla hasn't re-introduced boosts yet), there's an optional feature called "Channel Sources". What it does is automatically re-post everything coming in from one or multiple selected connections. This can just as well be an RSS or Atom feed.
This has a few downsides, though. It's fully automated, so it isn't interactive. You have absolutely no control over what goes out, and what it looks like. Your Mastodon connections will have full-blown blog posts or news articles with tens of thousands of characters slammed into their faces with no content warnings.
Besides, Mastodon will mangle them, just like it mangles everything else coming in from Friendica, Hubzilla and (streams): It can't embed images within the text, so it rips them out and throws them after the end of the post in reverse order. And it can only handle a maximum of four images, so only the last four images will remain.
Lastly, AFAIR, Channel Sources does not create a link to the original, so any post or article coming in via feed and forwarded by Channel Sources will appear as if you've written it yourself.
#Long #LongPost #CWLong #CWLongPost #RSS #Atom #Hubzilla
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OSCC #OSCC23 #Events #OMRG #OpenMetaverse #Max #Maxwell #Maxine #MeshBody #ArcadiaAsylum
Also, it's hard to generally define when an image description is always too long, not to mention that an 860-character alt-text doesn't mean 860 characters of image description in my case. It rather means an even shorter description and a reference to the actual description which is well over 40,000 characters long. But within a post, it's hard to automatically draw a line between the actual post text and the image description to count their respective characters.
#Long #LongPost #CWLong #CWLongPost Unfortunately, I'm not a seer. I can't know beforehand who discovers my posts in their federated timelines. I can never know whether one of my image posts catches the attention of someone who is interested in and curious about but also completely clueless about what my images show.
So I always write as if this happens. And then I have to go extremely in-depth because my images tend to only show things that almost nobody is even remotely familiar with. I can't just mention what's there. I have to explain what it is. I have to explain how it works and what it does if it actually does anything. And I have to describe in pain-staking detail what it looks like, not only for blind or visually-impaired users, but also for sighted users who are curious about it, but it's too small within the image.
I mean, I could simply mention there's a teleporter somewhere even if it only takes up some 35x35 pixels in an 800x533-pixel image. I could omit it and do as if it's unimportant. What I do instead is use 5,000 words only to describe that teleporter and at least briefly explain it, including 4,000 for the preview image of the teleport destination that's only about 30x10 pixels in the picture. And the other 1,000 characters don't even include a list of all the several dozen pre-programmed teleport destinations, much less explanations what and where they are. Someone may want to know that as well, but I had to draw a line somewhere when I actually wrote that description. I limited myself to transcribing what's actually visible on the teleporter which only includes the names of ten destinations.
But you're right, I can't satisfy everyone. Some may find my image descriptions way too long. Others do love them for how detailed they are. And I can't rule out that yet other people find them still lacking certain details. For example, I've never mentioned the camera position, at least not the altitude above ground.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions Let's not limit this to only image descriptions in alt-text in toots from vanilla Mastodon.
How long is too long for an image description in general, regardless of whether it's in the alt-text or the post text Or specifically when it's part of the post text Is there such a thing as too long
I'm asking because while I'm indirectly bound to Mastodon's 1,500-character limit for alt-text because Mastodon cuts everything that's longer permanently off, I'm not bound to Mastodon's 500-character limit for posts because I'm someplace very different from Mastodon. And my image descriptions tend to grow unimaginably long.
They have to be that long in order to be sufficiently informative. My own pictures are always from non-real-world places that nearly nobody knows, and so they only contain stuff that nearly nobody knows. And they don't always focus on one element so that everything else can be swept under the rug. So I have to describe a lot, and I have to explain a lot.
Let's just say I can no longer write full detailed and sufficiently informative image descriptions within Mastodon's constraints, not even within 1,500 characters. Even a carefully chosen camera angle that shows as few surrounding and background details as possible plus cropping away some more details won't let me stay within the 1,500-character limit.
Now, the thing is I hardly get any feedback for my image descriptions. Most of my image posts get none at all. Some sighted users say they're generally too long, but they never criticise any particular description of mine. Instead, they go by the character counts I tell them.
On the other hand, I've just received from a blind user for (content warning: eye contact) with two pictures and my longest image description to date: The preamble for both images has slightly over 1,300 characters, the description for the first image has almost exactly 40,000 characters, the one for the second image which references and relies on the former has about 6,750 characters.
Mastodon's alt-text police seems not to have discovered my posts yet, probably because none of them follows me. That, or they're perfectly okay with what I write. Without any feedback, I can't know. So I'm asking all of you.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #CharacterCount I guess this has two causes. One, Hubzilla is older than Mastodon and based on something even older. Mastodon didn't play a role in Hubzilla's development. So Hubzilla handles vastly differently from Mastodon. Two, Hubzilla's documentation not only reads more like a technical specification than a user manual, but it's hopelessly outdated and incomplete.
Thus, Hubzilla users know how to make their posts Mastodon-compatible either from hearsay or not at all.
Mastodon's content warning field is Hubzilla's summary field. It's the exact same field. But hardly anyone knows because that isn't documented anywhere. By the way, this is even worse for Friendica users because Friendica has no such field and relies on BBcode tags instead.
Also, Hubzilla doesn't support Mastodon-style content warnings for replies at all. That's because Hubzilla, like Friendica and (streams), has a blog-style/Facebook-style/Tumblr-style one-post-many-comments thread format whereas Mastodon has a posts-and-more-posts thread format.
So replies on Hubzilla are comments which, unlike Mastodon, even have their own dedicated entry field and only one of these. There is no summary (= Mastodon's content warning) field for comments. I mean, why would someone give a summary for a blog comment or a Facebook comment or a Tumblr comment!
Also, especially the old guard on Hubzilla can't comprehend why content warnings need to be issued by the poster in a specific field. They're used to having a dead-simple reader-side filter system called the "NSFW app" which automatically hides posts behind a content warning when it finds one or several from a list of keywords (substrings actually) in a post. It has a tendency for false positives, but still.
Mastodon didn't have anything remotely similar before version 4.0 when its filters grew the ability to hide posts and not only remove them. And now the filters are too complicated for most casual users, not to mention that their favourite mobile app doesn't have filter controls, and they've never touched the Web interface even once. Strangely, this is actually something where Hubzilla manages to be easier to use than Mastodon. So almost nobody uses filters to generate content warnings.
What makes matters worse is that Mastodon hides the post text behind a content warning, but not the images. Hubzilla does, and Hubzilla users who have never seen Mastodon in action assume that so does Mastodon. Instead, however, Mastodon blanks them out. Not only that, but it uses its own homebrew, non-standard, "proprietary" sensitive flag for it which I think isn't documented anywhere except for Mastodon's source code. And it stubbornly refuses to adhere to existing standards. Basically, any other project that wants its images optionally hidden on Mastodon has to reverse-engineer Mastodon's image flagging first.
Hubzilla doesn't have a nifty alt-text entry field like Mastodon either. Some may think that the image description field which is only accessible when uploading an image and then never again is that, but it isn't. On Hubzilla, just like on Friendica and (streams), alt-text has to be manually grafted into the image-embedding BBcode. There is no documentation for this on any of the three either.
Well, and all this collides with the countless Mastodon users who don't know that the Fediverse is more than just Mastodon, much less that everything else isn't just Mastodon with a different UI and one or two extra features.
So you have encounters of Hubzilla users who don't know what alt-text is, much less how to add it because there is no even halfway official source for such information and Mastodon users who don't know that their opposite is not on Mastodon but on something that's as far from being Mastodon as it could ever get.
I guess Friendica accounts and Hubzilla and (streams) channels are being muted and blocked on Mastodon left and right for not following Mastodon's unwritten rules. Not because the users don't care. Not even because the users actually don't know these rules, what with how little exposure most of them have to Mastodon's overarching culture. No, it's often because they simply don't know how to follow the rules.
#Long #LongPost #CWLong #CWLongPost #AltText #ContentWarning #ContentWarnings #Mastodon #Friendica #Hubzilla #Streams
It's called "nomadic identity". It was created by Mike Macgirvin in 2011 with his Zot protocol and first implemented by himself in 2012 in the Red Matrix which became in 2015. It's also part of the Nomad protocol, a successor of Zot, upon which Mike's latest creations commonly referred to as is based.
Nomadic identity allows you to have your channel (similar to what an account is just about everywhere else) on multiple server instances at the same time. Not backup-like static copies, but identical clones which are being kept in sync in near-real-time.
In case any of you don't know yet: Both can use ActivityPub as well, and they're federated with Mastodon. I'm actually writing this from a Hubzilla channel that has one spare clone.
Also, both Hubzilla and (streams) have bidirectional support for another creation of Mike's, a single-sign-on system named OpenWebAuth which automatically recognises your login on compatible instances.
The obvious catch is that neither of these features are available anywhere else, at least not to this extent. Hubzilla and (streams) are the only nomadic federated server applications, and they're also the only ones that with server-side OpenWebAuth support which means that they can recognise OpenWebAuth logins from elsewhere.
And it's safe to say that what doesn't exist on Mastodon may be seen as non-existent in the Fediverse altogether.
CC:
#Long #LongPost #CWLong #CWLongPost #Fediverse #NomadicIdentity #OpenWebAuth #Hubzilla #Streams
Imagine someone made an automatically generated instance filter list for Mastodon that tries to contain all instances of everything that isn't vanilla Mastodon. No matter if it's Glitch or Pixelfed or Lemmy or Sharkey or Hubzilla or Threads or whatever.
Imagine whatever created that filter list even scraped the Communities pages of (streams) instances and then started scraping the Communities pages of new (streams) instances it found there. That'd be the only way to discover (streams) instances. Imagine that scraper even went for the last remaining Osada, Zap, Misty, Redmatrix and Roadhouse instances.
What do you think, how many Mastodon instances would actually include that filter list How many Mastodon users would demand that list be used on whichever instances they're on if they find out that the list exists
#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #NotMastodon #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Dann hier nochmal der Block, der sich an dich richtet:
Ach ja, nur zur Information, : Friendica und Hubzilla sind keine Eindringlinge. Die waren zuerst hier.
Mastodon ist von 2016. Hubzilla ist von 2015 und umbenannt aus der Red Matrix von 2012. Und Friendica ist von 2010 und somit das lteste Fediverse-Projekt, das ActivityPub untersttzt.
Als Mastodon 2016 startete, sprach es sofort eine Sprache, die Friendica und Hubzilla zu dem Zeitpunkt auch schon sprachen: OStatus. Das heit, Friendica und Hubzilla haben sich nicht mit Mastodon verbunden, sondern Mastodon hat sich mit Friendica und Hubzilla verbunden.
Und als 2018 ActivityPub kam, hatte zumindest Hubzilla das auch schon vor Friendica.
Aber wenn dich so Sachen wie ber 500 Zeichen am Stck, Fettschrift, Kursivschrift,
Codeblcke, , ......berschriften...
- ...Listen...
...und "komische" Mentions stren, dann steht es dir frei, durch die Instanzenlisten von allem, was nicht Mastodon ist, zu gehen und sie alle fr dich zu blockieren. Links zu solchen Listen findest du unter anderem .
Ich jedenfalls komme zwar Mastodon einigermaen entgegen, aber komplett verbiegen und mich komplett auf das beschrnken, was Mastodon 3.x konnte, werde ich definitiv nicht. Dann gbe es von mir nmlich auch keine Bilder mehr, weil ich meine Bilder nicht in 1500 Zeichen oder weniger beschreiben kann.
CC:
#Long #LongPost #CWLong #CWLongPost #Lang #LangerPost #CWLang #CWLangerPost #Fediverse #Mastodon #NichtNurMastodon #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Weil Mastodon doppelt soviele Nutzer hat wie alles andere zusammen.
Und weil 99,9% dieser Nutzer die ersten Monate ihrer Zeit auf Mastodon glaubten, das Fediverse sei nur Mastodon. Fr sie hat Eugen Rochko sowohl das Fediverse als auch ActivityPub erfunden. Und als sie erstmals erfuhren, da es im Fediverse noch was anderes gibt, weil sie einen "Trt" mit ber 500 Zeichen oder Textformatierung oder einem Zitat oder so sahen, empfanden sie alles, was nicht Mastodon ist, als Eindringlinge in ihr schnes, gemtliches, flauschiges Mastodon-Fediverse.
Genau diese Leute htten es am liebsten, wenn das Fediverse nur Original-Vanilla-Mastodon wre. Am besten das "gute alte" Mastodon 3.x. Alle anderen Projekte haben zu verschwinden. Das wird aber nicht passieren.
Okay, dann sollen die anderen Projekte eben zu 100%igen Mastodon-3.x-Klonen werden und alle ihre Spezialfeatures aufgeben. Das wird aber auch nicht passieren, schon gar nicht, wenn hinter einem Projekt ein Mike Macgirvin steckte oder noch steckt.
Tja, dann haben eben alle Mastodon-Instanzen alles zu fediblocken, was nicht Mastodon ist. Nur da das ein Katz-und-Maus-Spiel wird, weil man keine ganzen Projekte am Stck fediblocken kann und stndig neue Nicht-Mastodon-Instanzen auftauchen.
Also haben geflligst die Nutzer aller anderen Projekte sich so zu verhalten, als wren sie auf Mastodon. Alles, was ihre Instanzen knnen, was Mastodon nicht kann, haben sie zu lassen.
ber 500 Zeichen sind nicht erlaubt, weil man auf Vanilla-Mastodon nicht mehr als 500 Zeichen trten kann.
Textformatierung ist nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte und man auch auf Mastodon 4.x sowas nicht selbst machen kann.
Zitate sind nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte und man auch auf Mastodon 4.x nicht zitieren kann.
Quote-Posts sind nicht erlaubt, weil Mastodon vor 4.0 die nicht darstellen konnte, Mastodon 4.x die immer noch nur unzureichend darstellt, man auerdem auf Mastodon 4.x nicht selbst quote-posten kann und Quote-Tweets ja sowieso bse sind.
Hashtags fr automatisierte Content-Warning-Filter Darf man auch nicht benutzen. Vor Version 4.0 konnte Mastodon keine Content Warnings per Filter, also sind Content Warnings auf Mastodon nur als ebensolche im Content-Warning-Feld erlaubt. Ungeachtet der Tatsache, da andere Projekte Content-Warning Filter schon hatten, als es Mastodon noch gar nicht gab.
Ach ja, das Content-Warning-Feld ist das Content-Warning-Feld und NUR fr Content Warnings. Und fr nichts anderes. Auch wenn es tausendmal auf Hubzilla schon "Summary" hie, bevor es Mastodon berhaupt gab.
Wenn man auf Friendica, Hubzilla oder (streams) mehrere Bilder postet, hat man die a) nicht in den Post einzubetten, sondern hinten anzuhngen und b) die Bilder in umgekehrter Reihenfolge einzustellen, damit sie auf Mastodon wieder richtigherum sind. Auch wenn man einen Mastodon-Kontakt und 100 Friendica/Hubzilla/(streams)-Kontakte hat.
Friendica-Nutzer haben bitteschn keine Titel einzutragen. Denn wenn sie das tun, gehen ihre Posts nicht als Notes (= Mastodon-"Trts") raus, sondern als Artikel. Und Artikel kennt man auf Mastodon nicht. Also will man die nicht. Lieber einen Thread aus "Trts" von maximal 500 Zeichen machen, weil das der Standard im Fediverse ist. Oder noch besser: den 80.000-Zeichen-Essay, der auf Friendica problemlos in einem Stck postbar wre, auf maximal 500 Zeichen eindampfen.
Ich bin sogar schon dafr kritisiert worden, wie meine Mentions aussehen. Ich sollte bitteschn aufhren, so "komische" Mentions zu machen und statt dessen die ganz "normalen", die man von Mastodon gewhnt ist. Nur da hier auf Hubzilla die Form der Mentions hartgecodet sind, und zwar schon vier Jahre lnger, als es Mastodon berhaupt gibt. Und Mario Vavti wird einen Deibel tun, daran ohne Not was zu ndern.
Und da wundern sich einige, warum so manch ein Nutzer von Friendica, Hubzilla oder (streams) ActivityPub komplett deaktiviert bzw. gar nicht erst aktiviert hat. Sie haben einfach keinen Bock, auf einmal so zu tun, als wren sie auf Mastodon, sobald jemand auf Mastodon ihre Posts lesen kann, und auf all die Features, die Friendica und Hubzilla schon hatten, bevor es Mastodon gab, wegen derer sie berhaupt erst da sind, wo sie sind, zu verzichten.
Ach ja, nur zur Information, : Friendica und Hubzilla sind keine Eindringlinge. Die waren zuerst hier.
Mastodon ist von 2016. Hubzilla ist von 2015 und umbenannt aus der Red Matrix von 2012. Und Friendica ist von 2010 und somit das lteste Fediverse-Projekt, das ActivityPub untersttzt.
Als Mastodon 2016 startete, sprach es sofort eine Sprache, die Friendica und Hubzilla zu dem Zeitpunkt auch schon sprachen: OStatus. Das heit, Friendica und Hubzilla haben sich nicht mit Mastodon verbunden, sondern Mastodon hat sich mit Friendica und Hubzilla verbunden.
Und als 2018 ActivityPub kam, hatte zumindest Hubzilla das auch schon vor Friendica.
Aber wenn dich so Sachen wie ber 500 Zeichen am Stck, Fettschrift, Kursivschrift,
Codeblcke, , ......berschriften...
- ...Listen...
...und "komische" Mentions stren, dann steht es dir frei, durch die Instanzenlisten von allem, was nicht Mastodon ist, zu gehen und sie alle fr dich zu blockieren. Links zu solchen Listen findest du unter anderem .
Ich jedenfalls komme zwar Mastodon einigermaen entgegen, aber komplett verbiegen und mich komplett auf das beschrnken, was Mastodon 3.x konnte, werde ich definitiv nicht. Dann gbe es von mir nmlich auch keine Bilder mehr, weil ich meine Bilder nicht in 1500 Zeichen oder weniger beschreiben kann.
CC:
#Long #LongPost #CWLong #CWLongPost #Lang #LangerPost #CWLang #CWLangerPost #Fediverse #Mastodon #NichtNurMastodon #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaPersonally and regarding my Hubzilla channel here, I'm not too worried about Threads.
First of all, I'm not going to connect to anyone on Threads. Not even when more than those select few can be followed. As if there's anything going on there that's of interest within the scope of this channel.
Second, Threads users can't follow anyone outside Threads anyway yet.
Third, even if they could, doesn't mean I'd let them if I don't want to. It's up to me to decide who connects to my channel and who doesn't. I have to confirm each new connection, and if I don't, that actor doesn't receive anything from me.
Fourth, the typical incentive for non-Threads users to follow me isn't there for Threads users.
One of the two main reasons why Mastodon users follow me is because they expect me to explain the Fediverse outside Mastodon to them. Your typical Threads user neither knows nor cares for the Fediverse. They're on Threads because it's "Twitter by Facebook without Musk".
The other and even bigger reason for Mastodon users to follow me is because they've just arrived from , and they need some Twitter-like background noise in their personal timelines, so they follow everyone they come across. Threads probably forces loads of background noise upon you right away, so you don't have to take care of that yourself.
Fifth, a channel owned by a virtual world avatar that's primarily about obscure virtual worlds with no real-life information isn't worth data-harvesting. Especially not if I keep badmouthing Horizons and using the term "metaverse" for stuff that's both over a decade older than Horizons and more alive than Horizons because that stuff has been using that word for over a decade itself. Meta would probably rather block this channel before anyone on Threads finds it than harvest it. In fact, I could try to make this process quicker with a few well-placed memes.
Sixth, I can easily silence bad actors on Threads with Superblock.
I was about to ask what the odds are that Threads can federate with Hubzilla in the first place, exotic as Hubzilla is with its ActivityPub support through an optional add-on. But I've got in-bound connections from all over the place already now, from Diaspora* to Misskey to GoToSocial to micro.blog.
Then again, I don't know how Threads handles posts with over 500 characters. After all, it was designed to federate with vanilla Mastodon by people who at that point believed that the Fediverse is only vanilla Mastodon. It could actually be that Threads rejects posts with over 500 characters, just like Misskey and its forks reject posts from a certain length upward.
Finally, if bad came to worse, I wouldn't even have to move away. I could switch ActivityPub off entirely. Granted, that'd mean that I'd lose most of my connections, and I'd have to try and remake those to Friendica using the Diaspora* protocol instead. But that'd completely lock Threads out on a protocol level.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Meta #MetaMeta #Threads
- post length (Firefish: 3000 characters default, adjustable by admin Mastodon: 500 characters default, hard-coded in a source code config file)
- quotes (Mastodon: can only display them)
- quote-posts (Mastodon: can only display them and badly)
- text formatting (Mastodon: can only display it and not even all of it)
- groups (Mastodon: needs external stuff like Guppe or direct competitor Friendica)
- full account migration between Firefish instances and from Mastodon to Firefish (Mastodon: limited, requires jumping through hoops)
- polls with more than four options (Mastodon: haha, nope)
- antennas (Mastodon: What's that)
- calendar (Mastodon: nope)
- notes (Mastodon: nope)
- chat (Mastodon: nope)
- etc.
But if "the best product" is only defined as "the closest Fediverse project for iOS users to pre-Musk Twitter" and/or "the project the most compatible with Mastodon", then Mastodon wins.
#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Firefish Ironically, lock-in is part of why Mastodon is twice as big as everything else in the Fediverse combined.
At least for Western users, Mastodon is the only gateway into the Fediverse. Mastodon does little to mention that there's more to the Fediverse, much less what more there is. So people spend three to six months believing that the Fediverse is only Mastodon. Long enough to see the other projects as intruders and want their nice and cosy Mastodon-only Fediverse back when they discover there's more to the Fediverse than Mastodon.
Third-party additions, be it Web services, be it mobile or desktop apps, are almost always built against Mastodon first and foremost. This is either because the creators started working on them when they themselves believed the Fediverse is only Mastodon, and when they found out about other micro-blogging projects, it was too late to implement support for these. Or it's because the creators think it isn't worth the extra effort to officially support anything that isn't Mastodon because nobody uses it anyway.
Mastodon itself keeps getting away with being half-incompatible with the rest of the Fediverse. Certain undocumented homebrew features on Mastodon almost only work within Mastodon itself, including obscuring sensitive pictures for which Mastodon has its own solution and refuses to implement the standard ActivityPub way.
Other features on other projects become half-senseless due to Mastodon's deliberate lack of support for them. Or if Mastodon supports them, the support is only half-baked, such as for quote-posts a.k.a. shares which Friendica has already had six years before Mastodon was launched, and which other projects have, too.
And when only displaying something is supported, but not creating them, it deeply disturbs those who believe or until recently believed the Fediverse is only Mastodon when they come across them because they also believe that this shouldn't exist in the Fediverse. Quotes, quote-posts, text formatting, embedded links or even only posts with over 500 characters. There are actually Mastodon users who want everyone everywhere outside of Vanilla mastodon not to use any features that are unavailable on vanilla Mastodon, and who block everyone who does.
If the best product by features won, most people would be on Firefish or even Hubzilla or (streams).
#Long #LongPost #CWLong #CWLongPost #Fediverse #MastodonWhat all the discussions about whether or not to block Threads reveals is a very common attitude on Mastodon:
"I want my preference to be the default setting for everybody because having to configure something makes Mastodon too complicated!"
Or even:
"I want my preference to be hard-coded for everybody because adding one more setting makes Mastodon too complicated!"
I guess it isn't rare for either to go along with wanting the whole Fediverse to be either Mastodon proper or exactly like vanilla Mastodon. Maybe even exactly like Mastodon 3.x before certain features that are common everywhere else in the Fediverse were introduced to Mastodon such as full-text search, displaying text formatting or displaying quotes. Because it's so hard to wrap your mind around there being differences between Mastodon on one side and stuff like Firefish, Friendica or Hubzilla on the other side.
#Fediverse #Mastodon #MastodonIsNotTheFediverse #NotOnlyMastodon #Threads #Meta #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaMeta
For Wolfie Feral
Art by me
One extreme would be what most people would do, namely only generally mention what the chart is about.
The other extreme is what I would do, namely
- describe the graph itself in even more detail (e.g. the levels being "'Yes!!', slanted for emphasis with two exclamation marks for more emphasis, 'Yes', 'Unclear or neutral', 'No' and 'No!!', slanted for emphasis with two exclamation marks for more emphasis again" and, of course, everything being hand-drawn and all writing being hand-written in all-caps)
- measure and mention the exact position of every single dot on the graph
- mention who recorded which of the songs first and when plus, if people are more familiar with one or multiple covers than with the original, who made those covers and when (e.g. ""Killing Me Softly", actually "Killing Me Softly With His Song", co-written and first recorded by Lori Lieberman in 1971 and released on her self-titled album in 1972, but more well-known as a soul cover by Roberta Flack, released on her 1973 album Killing Me Softly, and a hip-hop cover by the Fugees, released on their only hit album The Score in 1996, sits at 94% on the "Do I Like You" scale and at 51% on the "Do You Like Me" scale.")
- maybe even go as far as explaining why each one of these songs sits where it sits
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #Accessibility #A11y #Graph As far as I can see, there is no general consensus or agreement upon what's the right amount of description for an image. I guess it also really depends on the image. Cat photographs can do with rather short descriptions while other pictures require descriptions so long that you couldn't possibly post them in one piece anywhere on most Mastodon instances. Good thing there's a Fediverse beyond Mastodon.
There are two things I keep in mind for my own image descriptions. One, if something is obscure and niche enough for average Fediverse users to not know anything about it, it needs to be described and explained. That'd better go into the post text itself, but since my image descriptions often grow extremely long, I put them there anyway.
Two, whenever an image description mentions what there is in a picture, blind or visually-impaired people are likely to want to know what it looks like. So any and all descriptions must include that. It's more ableist not to give visual descriptions than to give them and make the image description longer.
I myself tend to try to include whatever I read about that should be part of an image description. Just recently, someone wondered why so few people mention where they've taken a picture. Good thing I've been doing that ever since I've started writing detailied image descriptions.
It's just unfortunate that people rarely give feedback for image descriptions, especially without being asked for it first. My own image descriptions regularly grow so long that they exceed any idea of excessive. What few people have given me feedback so far, including one who has done it out of the blue, liked them, but such a small number of people couldn't possibly represent all of the Fediverse. Then again, I hardly post images anymore because of how long it takes me to describe them, and fewer images mean even less feedback.
But if it looks like I can get away with image descriptions that are way longer than some essays, I think it's hard for alt-text within Mastodon's 1,500-character limit to be too long.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #CharacterCount #Accessibility #A11y
THE 7 HABITS OF HIGHLY EFFECTIVE PEOPLE
Read More from HERE
reads
The field that Mastodon users for content warnings was originally created for summaries.
Now you might rub your eyes in disbelief, wondering if you've actually read what you think you've read. Summary Why would a 500-character toot need a summary
Well, the whole Fediverse outside vanilla Mastodon and Threads supports post with way more than 500 characters by default. For example, Friendica, launched as early as 2010, several months before Diaspora* even, doesn't have a defined character limit at all. Neither does Hubzilla which started as a Friendica fork in 2012. Friendica supports summaries by means of a pair of BBcode tags Hubzilla has a dedicated field for them. And when Mastodon was launched in 2016, it was immediately federated with both.
Mastodon itself was originally based on OStatus which has a summary field in its specification. But since Mastodon was intended to be a micro-blogging service with no more than 500 characters, summaries were deemed unnecessary, and the summary field was re-purposed as a content warning field.
While Mastodon was capable of connecting to all kinds of StatusNet and GNU social instances (Pleroma started life as an alternate GNU social frontend three and a half weeks before Mastodon, by the way) as well as Friendica and Hubzilla, actually doing so was obviously never taken into consideration, much less advertised. So lack of compatibility could be shrugged away with, "Compatibility with what"
By the way, at least Hubzilla has its own solution for content warnings: It has an optional "app" that can generate them automatically - for the reader. It's a dead-simple text filter that has only got a text field for configuration. If any one of the comma-separated strings entered into that field is found in a post, the whole post is hidden behind a button, embedded images and other media and all.
Also, Hubzilla supports spoiler tags behind which parts of posts or whole posts can be hidden again, this can include embedded images, videos or whatever.
So from an old-school Hubzilla point of view, using the summary field for content warnings is unnecessary.
#ContentWarning #ContentWarnings #CW #Mastodon #Friendica #Hubzilla #Fediverse #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Here are 7 lessons on The Black Girl's Guide to Financial Freedom by Paris:
Book:
reads
Valuable lessons from the book "Make Better Decisions" by Helen Edwards and Dave Edwards
visit for 10 Lessons
Book:
reads
10 Valuable lessons from the book "The Perfect Day Formula" by Craig Ballantyne
Book:
reads
- tell from looking at a picture where exactly it was made, even if that place is in an obscure 3-D virtual world
- look at any item in a 3-D virtual world, identify it correctly, no matter how small it is, tell who has made it and judge whether it's important to mention who has made it or even explain who that person was/is
- transcribe text that's less than one pixel high
- transcribe text that's partly or even mostly obscured and even transcribe the invisible parts of the text
- transcribe text that's only partly within the picture and then correctly include the out-of-frame parts
- look at an in-world sales box, rattle down the contents and, if necessary, explain them
- describe images within images or even images within images within images, no matter how tiny, at the same level of detail as the image itself
- not only identify a teleporter as such, no matter what it looks like, but also rattle down a full list of chooseable destinations and explain what these destinations are
- look at an in-world door and tell if it's scripted and how (door-opening script vs teleport script to the other side of the door vs teleport script to entirely elsewhere)
- tell an avatar from an NPC from an animesh figure from a static figure
- identify avatars, no matter how small they are in the picture, and judge whether it's important to mention who they are or even go into more detail
- tell from looking at a picture from an event which event is happening there, no matter how obscure and niche, and, if the event organisers are in the picture, identify them
...I'm not interested in using it for image descriptions. Thanks, but no, thanks. I'll go on writing them myself.
#ImageDescription #ImageDescriptions #AltText #AI #Long #LongPost #CWLong #CWLongPost I'm not on Mastodon, and Hubzilla, powerful as it is, has no technical way of hiding a profile picture or a title picture behind a content warning, nor has it any way of making Mastodon hide it.
I mean, I could change my profile picture and my title picture to something that doesn't show me at all. After all, I rarely post pictures with eyes anywhere in them anymore. I have no way of making Mastodon hide them in any way either, not even when I have Hubzilla or (streams) users click three or four times, depending on their setup, until they see the picture in question in the very same post. And hardly anyone uses filters as automated content warnings, so even adding the hashtags #EyeContact and #CWEyeContact is pretty futile.
And I'm normally someone who takes the eye contact content warning and other content warnings very seriously. For me, eye contact is not only when a face fills almost the whole picture. It starts when there's even only one eye anywhere in a picture. I've been told that some autistic people are triggered by faces at a sub-pixel level, i.e. whole faces smaller than one pixel, if the context within the image reveals there's a face. I've issued a content warning for pictures with eyes in pictures in pictures in that picture which measure less than 1/10,000 of a pixel.
I've tested linking to images rather than embedding them into posts, and I've found out that Mastodon does not automatically generate a preview if I link to the image page. This makes viewing my posts more inconvenient, but it should reduce the risk of triggering someone. Unfortunately, the Fediverse being what it is, it doesn't remove the necessity of a full image description.
So yes, I might replace both my profile picture and my title picture with something which I hope is trigger-free. But I'll need to find something that a) fits the purpose, b) fits my channel and c) doesn't make spending hours upon hours on writing image descriptions necessary. I mean, my current profile and title pictures are still without a description I'll have to figure out where to put them where there's enough space.
#Long #LongPost #CWLong #CWLongPost #ContentWarning #ContentWarnings #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
In ..
Buying from was stuped
55 bucks (with shipping)
I should've waited till 19th and gotten it at a local vendor
Then again.
I buy all my 1st party at ng ..
Guess thats the huh..
I need this game , so I can annoy my lil sibling to play it hahaha.
(This will be a very lol)
I think there is a webpage about the Sendalonde Community Library. Sendalonde has an entry on OpenSimWorld, and the Discovery Grid has its own website. But all three are separate from each other. Also I'd rather not link to anything external, especially if I can't be sure that it's accessible. And anything about OpenSim usually isn't accessible at all.
Besides, it's cumbersome to have to navigate from website to website to understand what I've posted, on a phone much more so than on a desktop/laptop computer.
That said, I would never put an image description of 40,000+ characters into alt-text. At least Mastodon, Glitch, Misskey, Firefish, Sharkey and their other forks cut alt-text off at the 1,500-character mark and discard everything beyond. Even here on Hubzilla with no screen zoom on, it's hard to show even only the first 3,500 characters of alt-text or so because it can't be scrolled. And alt-text can't be navigated with a screen reader like the post text can be navigated. It isn't possible to jump back to a certain point in alt-text it's only possible to jump back to the beginning and start over.
Last but not least, information that is neither available in the post text nor in the image must never, under no circumstances be put only into the alt-text. There are people who can't access alt-text, for example due to physical disabilities. Any information that's only available in alt-text is inaccessible and therefore lost to them.
That's why I always put such image description into the post text body instead of the alt-text, and then I issue a content warning "CW: long (n characters)", and I add the hashtags #Long, #LongPost, #CWLong and #CWLongPost for those who use filters against posts over 500 characters. This saves people from having unexpectedly hyper-massive walls of text slammed into their faces, especially those using mobile apps which were built under the assumption that a) the Fediverse is only vanilla Mastodon, so b) folding posts up is non-sense if posts with over 500 characters are technologically impossible.
The alt-text contains a short image description so the image is described at least a little for those who don't want to open the content warning, and it mentions that the actual, full-size image description is in the post text.
#ImageDescription #ImageDescriptions #AltText #Accessibility #Inclusion #Inclusivity #A11y
Alan Turner - As Long as the World Rolls On (1908)
So Threads is opening itself to the FediverseRemember, kids, that there already used to be a connection between what's the Fediverse today and what's Meta today. That was in 2011 when Friendica one-sidedly established bidirectional federation with Facebook. No, I'm not even kidding. Friendica was fully federated with Facebook. It did require a Facebook account, but still, you could use Facebook without actually using Facebook. People would mirror their entire Facebook timelines into Friendica.
This ended when Facebook found out and changed its developer TOS: Third-party applications that connect to Facebook were only allowed to send data to Facebook, but no longer to extract data from Facebook. This led to the slow death of Friendica's Facebook connector.
Fast-forward to 2023: Facebook (the corporation) is now Meta. And they've created their own micro-blogging service for the Fediverse, namely Threads. And now they're opening it to the Fediverse.
Remember that Friendica is still part of that self-same Fediverse.
And what do you know: One of the very very very first connections to Threads came from, wait for it, Friendica!
I think this calls for a variation on the good old meme.
#Long #LongPost #CWLong #CWLongPost #Threads #Meta #Fediverse #Friendica #Facebook #Federation #Meme #FediMeme #MoeTossingBarneyOut #TheSimpsons #FediverseMeta #FediMeta #CWFediverseMeta #CWFediMeta #EyeContact #CWEyeContact To be fair, it's undeniable that there are these vastly different factions in the Fediverse.
The Old Guard, is one of them, has been around since long before there was even Mastodon. The Fediverse didn't start with Mastodon. The Fediverse as we have it now started in 2010 with Friendica, almost 6 years before Mastodon, and it also included Hubzilla which started life in 2012. Both projects which were and still are for extreme tech geeks because even Friendica is too unwieldy for your typical casual social media user.
So that Old Guard consists of absolute ber-geeks on Linux PCs and laptops, many of whom run their own instances without any help from Docker or Yunohost. From their perspective, it was Mastodon which had arrived and federated with Friendica and Hubzilla, not the other way around, because Friendica and Hubzilla had been there first, and Mastodon had always spoken a language which they spoke, too.
Needless to say that they find Mastodon ridiculously underequipped and underwhelming. In fact, Mastodon's refusal to even support certain features of other projects makes life harder for them if they want to stay compatible with Mastodon.
Then you have the millions of Twitter refugees, almost all of whom were mollycoddled and railroaded to their first Fediverse home with as little explanation as possible. They're completely different. They're mostly not very interested in technology, and more of them feel disturbed by Linux talk than use Linux. In fact, most of them are on phones.
Many didn't even know that Mastodon is decentralised until a few months in. Most thought that the Fediverse is only vanilla Mastodon for at least their first three months, during which they got used to their nice and cosy and fluffy and friendly Mastodon-only Fediverse with no posts longer than 500 characters and no text formatting and no quotes etc.
As they're so numerous, they managed to shape Fediverse culture around being non-tech and, worse yet, around the Fediverse being only vanilla Mastodon. And yes, completely disregarding the Old Guard because they knew neither the Old Guard nor the places where the Old Guard resides.
When they came across their first "toot" that looked "weird" because it wasn't a vanilla Mastodon toot, they were greatly disturbed. They felt like whatever project that post came from, Akkoma, CalcKey, Friendica, Hubzilla, whatever, had maliciously intruded into their nice and cosy and fluffy and friendly Mastodon-only Fediverse. And they wanted that to go away again.
They did not want to read what they were told then: Friendica and Hubzilla are not intruders. They were here first. They had been here years before there was even Mastodon. There has never been a time during which the Fediverse was only vanilla Mastodon.
It's such people who demand that the users of everything that isn't vanilla Mastodon limit what they do to what's possible on vanilla Mastodon in order not to disturb those who want the Fediverse to be only vanilla Mastodon. No posts longer than 500 characters, no text formatting, no quotes, no embedded images which don't work on Mastodon anyway, no embedded hyperlinks (only URLs in plain sight instead) etc.
I guess it's clear why the users of everything from Akkoma to Firefish to Friendica to Hubzilla refuse to let themselves be limited by the vastly more numerous Mastodon users.
Well, and then there's the third faction. It's those who have never really arrived in the Fediverse. They don't want anything different. They want Twitter without Musk. Now they're sitting on mastodon.social or another big general-purpose instance and patiently waiting for Bluesky to open registrations because Bluesky is much closer to Twitter without Musk.
These people use Mastodon exactly like they used to use Twitter. Official app only, no more than 280 characters, no alt-texts, no hashtags (what do you mean, Mastodon does not have The Algorithm), no content warnings etc. The only way they've adapted to Mastodon, if at all, was
s/tweet/toot.#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Friendica #Hubzilla #TwitterMigration #TwitterRefugees You can definitely do both with Hubzilla.
For one, you can subscribe to RSS and Atom feeds.
And while you can't directly boost blog posts (Hubzilla hasn't re-introduced boosts yet), there's an optional feature called "Channel Sources". What it does is automatically re-post everything coming in from one or multiple selected connections. This can just as well be an RSS or Atom feed.
This has a few downsides, though. It's fully automated, so it isn't interactive. You have absolutely no control over what goes out, and what it looks like. Your Mastodon connections will have full-blown blog posts or news articles with tens of thousands of characters slammed into their faces with no content warnings.
Besides, Mastodon will mangle them, just like it mangles everything else coming in from Friendica, Hubzilla and (streams): It can't embed images within the text, so it rips them out and throws them after the end of the post in reverse order. And it can only handle a maximum of four images, so only the last four images will remain.
Lastly, AFAIR, Channel Sources does not create a link to the original, so any post or article coming in via feed and forwarded by Channel Sources will appear as if you've written it yourself.
#Long #LongPost #CWLong #CWLongPost #RSS #Atom #Hubzilla
Hamilton to go ahead with Macassa Lodge redevelopment despite soaring costs
City councillors approved an Emergency and Community Services Committee recommendation to proceed with building a new wing amid a $22.3 million bump in costs.
-termCare
- 11:30 AM-12:30 PM PST/grid time:
Shop during lunch! Hypergrid Shopping Tour: Where to find content
I'm curious where Lyr Lobo will take us. And if she has taken the time to add some of my suggestions as actual destinations. Then again, Juno Rowland or I could probably do an even longer specialise "So you've got a Ruth2 v4, and you're looking for clothes, but you don't want to resort to copybotted Second Life stuff" shopping tour. . - 12:30 PM-1:30 PM PST/grid time:
In Conversation: Mal Burns talks with Tish Shute
Okay, that's a filler, but probably an interesting one, also because it takes a look at early OpenSim. - 1:30 PM-2:00 PM PST/grid time:
The Open Metaverse Research Group
Right now, the appears to be a bunch of idealistic OpenSim users who want to achieve what industry and cryptobros, both with no knowledge of even OpenSim's existence whatsoever, are working on independently themselves. And it doesn't look like the OMRG has any associates outside the OpenSim community. Not to mention the state their very wiki is in. I hope this panel will convince me otherwise. - 2:00 PM-2:30 PM PST/grid time:
Max New Free Mesh bodies for OpenSim Avatars
The most exciting panel of the whole event. Ada Radius presents the new "unisex" mesh body she has created this year, Max, that can be turned into a male variant named Maxwell and a female one named Maxine. It's the official successor of Ruth2 and Roth2 now, and just like them, it's free, , legal and made in and for OpenSim by largely the same team. And it promises to provide a much better dev kit. I'll try to apply as a beta-tester, also because I don't want this body to go out there only lab-tested by its own devs. - 2:30 PM-3:00 PM PST/grid time:
A Home for Arcadia Asylum
Another topic dear to Ada, now joined by Kayaker Magic: the creations of Arcadia Asylum/Aley Arai/Lora Lemon/Aley Resident, at least what was successfully rescued and transferred to OpenSim. Kayaker has recently launched , and tomorrow at 10 AM PST/grid time.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OSCC #OSCC23 #Events #OMRG #OpenMetaverse #Max #Maxwell #Maxine #MeshBody #ArcadiaAsylum
, Day 655: Prepares for Fight v. 's Invasion
Earlier in October, PM Modi had also spoken to the President of Palestinian Authority and reiterated India's long-standing position on the Israel-Palestine conflict
Do you want to Get the best long sleeve polo today.
Then I on to Info you that this 13% Discounted today.
you can chick Here >.
sleeve # sleeve #
Ontario auditor: at least 99 patients placed in LTC homes without their consent
The auditor general's office this week says the government has not been transparent in implementing a law that allows hospital placement co-ordinators to transfer those patients.
-termCare
Ontario auditor: at least 99 patients placed in LTC homes without their consent
The auditor general's office this week says the government has not been transparent in implementing a law that allows hospital placement co-ordinators to transfer those patients.
-termCare
Ontario auditor: at least 99 patients placed in LTC homes without their consent
The auditor general's office this week says the government has not been transparent in implementing a law that allows hospital placement co-ordinators to transfer those patients.
-termCare
-lasting energy for memories
Granted, that tool wouldn't work for me anyway. Not only because Hubzilla doesn't use the Mastodon API, but because my image descriptions don't go into the alt-text. I've always provided both alt-text and image descriptions ever since I've discovered their requirement in the Fediverse, even though I'm still honing and improving my style.Also, it's hard to generally define when an image description is always too long, not to mention that an 860-character alt-text doesn't mean 860 characters of image description in my case. It rather means an even shorter description and a reference to the actual description which is well over 40,000 characters long. But within a post, it's hard to automatically draw a line between the actual post text and the image description to count their respective characters.
#Long #LongPost #CWLong #CWLongPost Unfortunately, I'm not a seer. I can't know beforehand who discovers my posts in their federated timelines. I can never know whether one of my image posts catches the attention of someone who is interested in and curious about but also completely clueless about what my images show.
So I always write as if this happens. And then I have to go extremely in-depth because my images tend to only show things that almost nobody is even remotely familiar with. I can't just mention what's there. I have to explain what it is. I have to explain how it works and what it does if it actually does anything. And I have to describe in pain-staking detail what it looks like, not only for blind or visually-impaired users, but also for sighted users who are curious about it, but it's too small within the image.
I mean, I could simply mention there's a teleporter somewhere even if it only takes up some 35x35 pixels in an 800x533-pixel image. I could omit it and do as if it's unimportant. What I do instead is use 5,000 words only to describe that teleporter and at least briefly explain it, including 4,000 for the preview image of the teleport destination that's only about 30x10 pixels in the picture. And the other 1,000 characters don't even include a list of all the several dozen pre-programmed teleport destinations, much less explanations what and where they are. Someone may want to know that as well, but I had to draw a line somewhere when I actually wrote that description. I limited myself to transcribing what's actually visible on the teleporter which only includes the names of ten destinations.
But you're right, I can't satisfy everyone. Some may find my image descriptions way too long. Others do love them for how detailed they are. And I can't rule out that yet other people find them still lacking certain details. For example, I've never mentioned the camera position, at least not the altitude above ground.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions Let's not limit this to only image descriptions in alt-text in toots from vanilla Mastodon.
How long is too long for an image description in general, regardless of whether it's in the alt-text or the post text Or specifically when it's part of the post text Is there such a thing as too long
I'm asking because while I'm indirectly bound to Mastodon's 1,500-character limit for alt-text because Mastodon cuts everything that's longer permanently off, I'm not bound to Mastodon's 500-character limit for posts because I'm someplace very different from Mastodon. And my image descriptions tend to grow unimaginably long.
They have to be that long in order to be sufficiently informative. My own pictures are always from non-real-world places that nearly nobody knows, and so they only contain stuff that nearly nobody knows. And they don't always focus on one element so that everything else can be swept under the rug. So I have to describe a lot, and I have to explain a lot.
Let's just say I can no longer write full detailed and sufficiently informative image descriptions within Mastodon's constraints, not even within 1,500 characters. Even a carefully chosen camera angle that shows as few surrounding and background details as possible plus cropping away some more details won't let me stay within the 1,500-character limit.
Now, the thing is I hardly get any feedback for my image descriptions. Most of my image posts get none at all. Some sighted users say they're generally too long, but they never criticise any particular description of mine. Instead, they go by the character counts I tell them.
On the other hand, I've just received from a blind user for (content warning: eye contact) with two pictures and my longest image description to date: The preamble for both images has slightly over 1,300 characters, the description for the first image has almost exactly 40,000 characters, the one for the second image which references and relies on the former has about 6,750 characters.
Mastodon's alt-text police seems not to have discovered my posts yet, probably because none of them follows me. That, or they're perfectly okay with what I write. Without any feedback, I can't know. So I'm asking all of you.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #ImageDescriptions #CharacterCount I guess this has two causes. One, Hubzilla is older than Mastodon and based on something even older. Mastodon didn't play a role in Hubzilla's development. So Hubzilla handles vastly differently from Mastodon. Two, Hubzilla's documentation not only reads more like a technical specification than a user manual, but it's hopelessly outdated and incomplete.
Thus, Hubzilla users know how to make their posts Mastodon-compatible either from hearsay or not at all.
Mastodon's content warning field is Hubzilla's summary field. It's the exact same field. But hardly anyone knows because that isn't documented anywhere. By the way, this is even worse for Friendica users because Friendica has no such field and relies on BBcode tags instead.
Also, Hubzilla doesn't support Mastodon-style content warnings for replies at all. That's because Hubzilla, like Friendica and (streams), has a blog-style/Facebook-style/Tumblr-style one-post-many-comments thread format whereas Mastodon has a posts-and-more-posts thread format.
So replies on Hubzilla are comments which, unlike Mastodon, even have their own dedicated entry field and only one of these. There is no summary (= Mastodon's content warning) field for comments. I mean, why would someone give a summary for a blog comment or a Facebook comment or a Tumblr comment!
Also, especially the old guard on Hubzilla can't comprehend why content warnings need to be issued by the poster in a specific field. They're used to having a dead-simple reader-side filter system called the "NSFW app" which automatically hides posts behind a content warning when it finds one or several from a list of keywords (substrings actually) in a post. It has a tendency for false positives, but still.
Mastodon didn't have anything remotely similar before version 4.0 when its filters grew the ability to hide posts and not only remove them. And now the filters are too complicated for most casual users, not to mention that their favourite mobile app doesn't have filter controls, and they've never touched the Web interface even once. Strangely, this is actually something where Hubzilla manages to be easier to use than Mastodon. So almost nobody uses filters to generate content warnings.
What makes matters worse is that Mastodon hides the post text behind a content warning, but not the images. Hubzilla does, and Hubzilla users who have never seen Mastodon in action assume that so does Mastodon. Instead, however, Mastodon blanks them out. Not only that, but it uses its own homebrew, non-standard, "proprietary" sensitive flag for it which I think isn't documented anywhere except for Mastodon's source code. And it stubbornly refuses to adhere to existing standards. Basically, any other project that wants its images optionally hidden on Mastodon has to reverse-engineer Mastodon's image flagging first.
Hubzilla doesn't have a nifty alt-text entry field like Mastodon either. Some may think that the image description field which is only accessible when uploading an image and then never again is that, but it isn't. On Hubzilla, just like on Friendica and (streams), alt-text has to be manually grafted into the image-embedding BBcode. There is no documentation for this on any of the three either.
Well, and all this collides with the countless Mastodon users who don't know that the Fediverse is more than just Mastodon, much less that everything else isn't just Mastodon with a different UI and one or two extra features.
So you have encounters of Hubzilla users who don't know what alt-text is, much less how to add it because there is no even halfway official source for such information and Mastodon users who don't know that their opposite is not on Mastodon but on something that's as far from being Mastodon as it could ever get.
I guess Friendica accounts and Hubzilla and (streams) channels are being muted and blocked on Mastodon left and right for not following Mastodon's unwritten rules. Not because the users don't care. Not even because the users actually don't know these rules, what with how little exposure most of them have to Mastodon's overarching culture. No, it's often because they simply don't know how to follow the rules.
#Long #LongPost #CWLong #CWLongPost #AltText #ContentWarning #ContentWarnings #Mastodon #Friendica #Hubzilla #Streams
Resident of central Ontario long-term care home died by homicide, police allege
Police say a man who lived at a central Ontario long-term care home has died after an alleged homicide at the facility.
-termcarehome
24 Nova Scotia long-term care homes currently dealing with COVID-19 outbreaks
There are currently two dozen COVID-19 outbreaks reported at long-term care homes across Nova Scotia, and some health-care officials are concerned about a lack of COVID protocols.
-19 -termCare
24 Nova Scotia long-term care homes currently dealing with COVID-19 outbreaks
There are currently two dozen COVID-19 outbreaks reported at long-term care homes across Nova Scotia, and some health-care officials are concerned about a lack of COVID protocols.
-19 -termCare
It's called "nomadic identity". It was created by Mike Macgirvin in 2011 with his Zot protocol and first implemented by himself in 2012 in the Red Matrix which became in 2015. It's also part of the Nomad protocol, a successor of Zot, upon which Mike's latest creations commonly referred to as is based.
Nomadic identity allows you to have your channel (similar to what an account is just about everywhere else) on multiple server instances at the same time. Not backup-like static copies, but identical clones which are being kept in sync in near-real-time.
In case any of you don't know yet: Both can use ActivityPub as well, and they're federated with Mastodon. I'm actually writing this from a Hubzilla channel that has one spare clone.
Also, both Hubzilla and (streams) have bidirectional support for another creation of Mike's, a single-sign-on system named OpenWebAuth which automatically recognises your login on compatible instances.
The obvious catch is that neither of these features are available anywhere else, at least not to this extent. Hubzilla and (streams) are the only nomadic federated server applications, and they're also the only ones that with server-side OpenWebAuth support which means that they can recognise OpenWebAuth logins from elsewhere.
And it's safe to say that what doesn't exist on Mastodon may be seen as non-existent in the Fediverse altogether.
CC:
#Long #LongPost #CWLong #CWLongPost #Fediverse #NomadicIdentity #OpenWebAuth #Hubzilla #Streams
Last updated: 2023-12-26
All text and images © eLoc8.is-fabulous.com