The of the week is LENT/LONG/LENGTH
Der Artikel ist eine Macroblogging-Beitragsform bei Hubzilla und z.B. geeignet fr echte Blogbeitrge. Im Gegensatz zu normalen Beitrgen, die im gesamten Netzwerk (inklusive Fediverse) verteilt werden, verbleiben Artikel beim eigenen Hub. Sie sind fr Nutzer anderer Instanzen und Nutzer, die keinen Account im Fediverse haben also nur ber ihre URL erreichbar. Die URL kann selbstverstndlich geteilt werden, so dass der Artikel trotzdem im Fediverse bekannt wird und abgerufen werden kann.
Einen Artikel erstellt man ber die App (Hamburger-Men ) "Artikel". Ruft man diese auf, werden smtliche erstellten Artikel angezeigt und man hat die Mglichkeit, einen neuen Artikel anzulegen ("Artikel hinzufgen").
Das Erstellen eines Artikels hnelt dem Erstellen eines normalen Beitrags. Das Eingabe-Formular weist aber zwei zustzliche Felder auf: "Summary (optional)" und "Link zur Seite".
Das Summary ist eine kurze Zusammenfassung des Inhalts, die beim Aufrufen des Artikels zunchst angezeigt wird.
Mit dem Link zum Artikel kann man die URL festlegen, ber welche man den Artikel erreichen kann (z.B. zum Teilen). Gibt man dort z.B. "ein-testartikel" ein, so lautet die URL: /articles//ein-testartikel
Den Link kann man aber z.B. auch einfach kopieren, indem man den Artikel ber das Kontextmen () "Link zur Quelle"aufruft und den Link zum Artikel aus dem Adressfeld des Browsers verwendet.
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost"Write your posts as long as you want," they say.
"Don't be apologetic about it," they say.
"Literally everyone in the whole Fediverse has gotten used to posts over 500 characters, and nobody minds anymore," they say.
"Literally everyone on Mastodon is perfectly okay with all of Hubzilla's antics," they say.
"Nobody wants the Fediverse to only be vanilla Mastodon," they say.
Oh, really Then I've probably faked this shared post here.
Being able to mute or filter posts that exceed 500 characters would be great.
Search is not good because it returns too many dissertations.
#Long #LongPost #CWLong #CWLongPost #LongPosts #LongToots #LongPostMeta #CWLongPostMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteBoost #CharacterCount #CharacterLimit #CharacterLimits #500Characters #Sarcasm
Well, Hubzilla is a direct descendant of Friendica. And Friendica's concept was and still is to federate with everything that moved and then some. StatusNet (which included early Mastodon and Pleroma, by the way), Diaspora*, Tumblr, Libertree, Twitter, e-mail, even Facebook for a few months, although that definitely required a Facebook account.
Hubzilla took a lot of that over. And Hubzilla was actually the first Fediverse project to adopt ActivityPub, even before its standardisation and two months before Mastodon.
But ActivityPub is actually optional both for the whole hub (on by default) and for each channel (off by default). So it's actually possible to run an entire Hubzilla hub with no ActivityPub at all.
Zap, a fork of Osada which itself was a slimmed-down fork of Hubzilla, had no ActivityPub at all in its early stages. Mike created it as a testbed for Zot6, and he expected Zot6 to be incompatible with non-nomadic protocols such as ActivityPub, so Zap only knew Zot6 and no other protocol, and Osada which lacked nomadic identity was to be used as a bridge between Zap and the rest of the Fediverse. Later on, Zot6 did become compatible with non-nomadic protocols, so Zap got ActivityPub support after all. And there was actually much rejoicing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla
You know that, I know that, but there are not exactly few people on Mastodon who don't know that.
Even when they learn that the Fediverse is not only Mastodon, much to their surprise, they tend to believe that if Mastodon isn't the only Fediverse project, it must still have been the first. And everything that isn't Mastodon is either bolted onto Mastodon or an intruder.
Disturbingly long posts. Non-Mastodon users are banned for exceeding 500 characters once. And I'm pretty sure that Mastodon users try to have non-Mastodon users sanctioned by their admins for breaking this unwritten Fediverse rule.
Quote-posts. For Hubzilla users, it's called sharing, and it has been the equivalent to Mastodon's boosts since 2015 because Hubzilla can't boost. Not until Hubzilla 9 is out. For minorities on Mastodon, it's the exact same thing as the quote-tweets that were used on Twitter to harass them. And Hubzilla doesn't let them opt in, not even opt out. Hubzilla can quote-post anyone on Mastodon, always.
I'm not even sure if every last first-wave and second-wave Twitter refugee who got used to Mastodon 3 is used to seeing things on Mastodon that were absolutely impossible on Mastodon 3 such as text formatting.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #HubzillaThis is interesting to watch.
The cat's out of the bag. Mike Macgirvin 's is in the news all over the Fediverse. Of course, you can't expect everyone in the Fediverse to know what nomadic identity is, so the explanation is that it's that stuff that Hubzilla does.
Which, in many cases, is the very first time that Mastodon users even read that name and learn about the existence of that project. I mean, I've seen a poll just yesterday, according to which three out of four Fediverse users have never heard of Hubzilla.
This, in turn, piques their interest. All of a sudden, lots of Mastodon users are curious about Hubzilla as it's said to be able to do things that Mastodon can't, but that they wish Mastodon could.
Some like who haven't used any other Fediverse projects than Mastodon so far actually , only to discover something probably absolutely unexpected: Hubzilla works and handles absolutely nothing like Mastodon. And that's not simply due to the formerly-default-and-now-only UI that's perpetually stuck in 2012.
They may actually wonder why Mike had the audacity to build something that's so much different from Mastodon instead of just aping Mastodon and slapping extra stuff on. And I guess they're even more surprised when you tell them that Hubzilla was made before Mastodon. Which means that there was a Fediverse before Mastodon.
It occurred to me only recently just how many ways Hubzilla has to completely blow Mastodon users' minds.
However, it isn't like people who have come from Twitter to Mastodon to Hubzilla over the last year and a half are all happy about how Hubzilla is different from Mastodon. Switching from Mastodon to Hubzilla takes more getting used to than switching from Twitter to Mastodon, especially if you expect Mastodon to be a standard that everything else has to follow.
There are, in fact, lots of things about Hubzilla that'll irritate people used to Mastodon to no end. The confusing difference between account and channel. The unusual conversation model that sends posts to other people than on Mastodon which doesn't have a conversation model. Separate editors for posts and comments. In fact, posts and comments being something different. ActivityPub not being on by default, and instead of having a simple opt-in switch in the settings, you have to "install" an "app" to be able to connect to Mastodon. No CW field (it's the summary field, but there's none for comments). No alt-text field. No distinction between followers and followed. Stuff in the settings not being where you'd expect it to be from your experience with Mastodon.
And I'm not even talking about the vast permission options yet. Or the filters which even I say need improvements. Or Hubzilla being unable to boost (shall be fixed with Hubzilla 9) and follow hashtags. Or people telling you that you have to type code manually if you want to have alt-text.
Even those who learn about Hubzilla without trying it are confused. Why is it so different Why does it have to be so different Why can't it be like Mastodon
In fact, it doesn't really occur rarely that Mastodon users consider almost everything in which Hubzilla differs from Mastodon a bug which they think can be fixed. It seems to be hard to imagine that what they take for a bug is part of Hubzilla's concept, and it has often been part of the concept since the early days of Mistpark back in 2010, almost six years before Mastodon came out.
I think over the next days and weeks, Hubzilla will increasingly be considered not only weirdly different, but disturbingly different. Along with that, more and more Mastodon users will become aware of the "atrocities" from a Mastodon point of view which Hubzilla users commit in the Fediverse, and which they justify with their different culture. Enormously long posts, text formatting, quotes, quote-posts, as if it's all the most normal thing in the world. Which, for Hubzilla users, it is.
In the near future, Mastodon will likely produce two more forms of drama. One is strong opposition against nomadic identity anywhere in the Fediverse, not so much because it's "un-Mastodon-like", but because it's expected to be used in malicious ways.
The other one is increasing opposition against Hubzilla itself and more and more calls for Fediblocking it in its entirety, along with all Mastodon or otherwise Fediverse instances that don't Fediblock all Hubzilla hubs. All because it's got that disturbing stuff like nomadic identity and huge posts well over 500 characters and quote-posts with no opt-out for anyone. And because more and more Mastodon users become aware of it.
I hope it won't happen, but I can't exclude it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla
Yes, nomadic identity was created along with the Zot protocol as early as 2011. Zot was first implemented on the Red Matrix which is based on a Friendica fork, which had its 1.0 release in 2013, and which was renamed into Hubzilla and repositioned with a different set of features in 2015. So all this happened before Mastodon was released.
Nomadic identity has been in daily, stable use for over a decade.
Like Friendica's DFRN before, Zot was never meant to be an officially standardised protocol like ActivityPub that other, completely different and independent server applications could use. Zot and Hubzilla have always been firmly tied to one another. Zot is not nearly as vague as ActivityPub. And Zot not only covers nomadic identity, but also Hubzilla's permission system which exceeds even a Mastodon user's wildest imagination by magnitudes.
Over the years, Mike advanced Zot further and further, often requiring new forks to test Zot. In 2018, two different Osadas and Zap became the testbeds for Zot6 which Hubzilla would later be upgraded to, and short-lived Zap even saw stable releases. In 2020, another Osada and two more projects which resurrected the names Mistpark and Redmatrix were the testbeds for Zot8 which was so advanced that it had become impossible or at least unfeasable to upgrade Hubzilla to it.
Roadhouse from early 2021, a fork of the third Osada, Redmatrix 2020 and/or Mistpark 2020 (they had the same code base), was either the last application on Zot8 or the first one on what would have been Zot11, but what was so advanced that it had become incompatible with Zot6. Therefore, it was renamed Nomad. And it became the base protocol for the nameless, brandless server application in the Streams repository which Mike is currently maintaining and constantly advancing. And current Nomad would be Zot12 if it was still Zot.
The reason why nomadic identity has only ever been implemented in PHP is because the only one who has ever built server applications with nomadic identity was Mike Macgirvin who also created the protocols behind them. And being built in PHP, everything that Mike has ever created from 2010's Mistpark to 2021's (streams) can be installed on a run-of-the-mill LAMP stack without having to fumble around with stuff like Ruby on Rails.
If you come from a "Fediverse = ActivityPub" background, all this may seem strange. But it was the only way for nomadic identity, Zot, Nomad and their implementations to advance to such power so quickly. Mike is still the sole keeper and maintainer of Nomad and its only implementation. This means that nobody else can meddle with it, and Nomad and (streams) are perfectly matched to each other. Thus, (streams) is probably the most quickly advancing Fediverse project currently.
That said, it is not a fully closed ecosystem. However, the idea behind developing stuff for Nomad is vastly different from the idea behind developing stuff for ActivityPub.
If you want to make something for ActivityPub, you usually sit down and start from scratch, from completely zero, except for the ActivityPub spec.
If you want to make something for Nomad, the recommended ways involve (streams). See, unlike Mastodon, (streams), just like Hubzilla, is not an enclosed monolith. It's modular. It can be expanded. And, in fact, both come with official add-ons right away. ActivityPub support itself is an add-on. A big difference is that Hubzilla comes with more add-ons whereas (streams) is slimmed down in this regard to make development easier. But it's possible to add third-party add-on repositories to server installations of both.
So if you want to make something for Nomad, you start with (streams). No need to start from scratch.
Either you simply develop add-ons for (streams) and offer them in a third-party repository that can be added to (streams) instances. Or you could soft-fork (streams), its core is in the public domain, add your stuff, slap a name on it and offer it as a new project.
I myself wouldn't recommend a hard fork, though, seeing as how rapidly (streams) is evolving and improving.
Sure, it'd be possible to develop something against Zot6 or Nomad completely from scratch. But if you build against Zot6 to stay compatible with Hubzilla, you're at Mario Vavti's mercy because he is the main dev of Hubzilla and therefore the keeper of Zot6 now, although I guess he doesn't change much about the protocol anymore.
And if you build against Nomad, you're at Mike's mercy, and Mike keeps advancing Nomad constantly and (streams) along with it. Also, if you build against Nomad, you must go multi-protocol because Hubzilla doesn't understand Nomad, so you also have to implement Zot6.
Standardising Nomad and handing it over to a W3C commission so it's no longer in the hands of one individual would be the worst that could possibly happen to it. Such a commission would water it down and remove stuff that they deem unnecessary. And Mike, no longer in control over Nomad, would have to play along and water (streams) down.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #Zot6 #Nomad #Hubzilla #Streams #(streams) #NomadicIdentity
Vielleicht nicht auf Mastodon. Aber das Fediverse ist nicht nur Mastodon. Und das Fediverse ist auch nicht nur Mastodon und Zeug, das Mastodon nachfft.
Ich erklr's dir mal. Aber Achtung: Das wird jetzt brutal lang. Und nein, ich werde das nicht in 500-Zeichen-Hppchen zerschnipseln. Falls du diagonal lesen willst: Das Wesentliche ist fett gesetzt.
Friendica ist absolut nicht wie Mastodon. Hubzilla ist indirekt ein Friendica-Fork und ist auch nicht wie Mastodon. (streams) ist indirekt ein Hubzilla-Fork und ist auch nicht wie Mastodon.
Friendica setzt seit 2010 auf vollautomatisch fr jeden Leser individuell per Textfilter generierte CWs. Das ist fast sechs Jahre lnger, als es Mastodon berhaupt gibt. Hubzilla tat das auch schon immer, und auch Hubzilla ist lter als Mastodon. Auch (streams) tut das.
Alle drei haben nicht nur diese vollautomatischen CWs und haben diese bombenfest als Teil ihrer Kultur, so wie Mastodon das CW-Feld bombenfest als Teil seiner Kultur hat. Nein, keins von den dreien hat berhaupt ein mastodonmiges CW-Feld.
Was auf Mastodon eine CW ist, ist auf allen dreien immer noch das, was es war, bevor Mastodon es zweckentfremdet hat: ein Summary. Eine Zusammenfassung.
Hubzilla und (streams) haben also statt eines CW-Feldes ein Summary-Feld. Das funktioniert genauso, da steht aber nicht CW drauf, sondern Summary. Viele wissen nicht mal, da das Mastodons CW ist.
Und: Hubzilla und (streams) haben das Summary-Feld, also quasi Mastodons CW-Feld, nur fr Posts, die keine Antworten sind. Die sind ja keine twittermigen Microbloggingdienste mit einem Eingabefeld fr alles. Die sind eher aufgebaut wie Blogs mit einem Eingabefeld fr Posts, mit dem man nicht antworten kann, und separaten Eingabefeldern unter jedem Post fr Kommentare.
Zusammenfassungen fr Blogkommentare sind aber Kokolores, das macht keiner. Folglich gibt's fr Kommentare kein Summary-Feld. Folglich kann man auf Hubzilla und (streams) keine Mastodon-CWs auf Antworten setzen. Es ist ganz einfach technisch nicht mglich, weil es die dafr ntigen Mittel gar nicht gibt, weil die aus Hubzillas Sicht berhaupt keinen Sinn ergeben wrden.
Friendica, das lteste von den dreien, ist noch extremer: Da gibt es berhaupt kein solches Feld. Nicht fr Posts, nicht fr Kommentare, gar nicht.
Friendica macht das mit BBcode-Tags. Friendica, Hubzilla und (streams) nutzen ja BBcode auch fr so Sachen wie Textformatierung, Listen, Tabellen, eingebettete Bilder usw. Und Friendica nutzt das auch fr Zusammenfassungen.
Der Vorteil ist: Das geht auch in Kommentaren. Der Nachteil: Da das berhaupt geht, wird nur aus der Nutzerhilfe ersichtlich. Und es ist auch wieder nicht allen klar, da Friendicas
Was wieder allen dreien gemein ist: Deren Nutzer finden die Idee, das Summary komplett fr posterseitige, also allen aufgezwungene CWs zu mibrauchen, kompletten Humbug. Sie haben ja seit 2010 etwas fr CWs, was tausendmal besser ist: NSFW. Das generiert CWs nmlich vollautomatisch. Auf der Leserseite. Und zwar zum einen nur optional und zum anderen individuell fr jeden Nutzer.
Und dann kam sechs Jahre spter dieses Mastodon daher, erfand das Rad neu, ignorierte alles, aber auch wirklich alles, was es schon gab - auch wenn es sich sofort mit Friendica und Hubzilla verband -, und versucht seitdem allein durch seine zahlenmige Dominanz im Fediverse, allen anderen Projekten seinen Non-Standard-Bldsinn aufzuzwingen. Auch weil 99% der Mastodon-Nutzer zu wissen glauben, da Mastodon die Referenzimplementation von ActivityPub sei.
Genau das kann NSFW seit 2010. Genau dafr ist es da. Und genau das knnen seit letztem Jahr auch die Filter von Mastodon.
Hier auf Hubzilla geht NSFW so: Du hast im Prinzip nicht mehr als ein Textfeld, wo du Schlsselwrter und Hashtags eintragen kannst, die dich stren. Standardmig eingetragen sind "nsfw" und "contentwarning". Das ist alles, was es an Einstellungen gibt.
Standardmig ist es berhaupt nicht aktiviert bzw. "installiert", wie es hier heit. Standardmig wird also gar nichts gefiltert. NSFW ist hier auf Hubzilla eine "App", die erst auf deinem Kanal (= Account auf Mastodon) "installiert" werden mu. Aber dann ist es sofort scharfgeschaltet.
Wenn jetzt in einem Post "NSFW" oder "nsfw" steht, entdeckt NSFW das vollautomatisch. Dann versteckt es den kompletten Post hinter einem gelben Rechteck, auf dem "nsfw - ansehen" steht. Und zwar wirklich den ganzen Post inklusive Hashtags und sogar inklusive allen Bildern.
Wenn du das gelbe Rechteck klickst, siehst du den Post.
Oder sagen wir, du willst nichts ber deutsche Politik lesen. Dann gehst du zur NSFW-App und trgst in der Wortliste "depol" ein. Jeder Post, jeder Kommentar, jede DM mit "depol" oder "DEpol" oder "#depol" drin wird dann komplett hinter einem gelben Rechteck mit "depol - ansehen" verborgen.
Das heit, Hubzilla sagt dir sogar vollautomatisch, wovor es dich warnt. Natrlich nur, wenn es etwas Entsprechendes in einem Post oder Kommentar oder einer DM findet. Da ist es abhngig von der Kooperation derer, die die Posts, Kommentare und DMs schreiben. Dann aber definitiv.
Auf Friendica und (streams) ist es ziemlich genauso.
Der einzige wirkliche Nachteil ist, da NSFW so simpel ist, da es keine Worterkennung hat. Es springt also immer auf Wortbestandteile an. Das heit, wenn du "trump" in der Wortliste hast, springt NSFW auch auf "trumpet" und "Strumpf" an. Aber vielleicht kann ich da zumindest auf Hubzilla noch eine Verbesserung durchsetzen.
Aber ein Hashtag "#depol" unter einen Post zu setzen, ist ein geringerer Aufwand, als "CW: depol" ins Summary bzw. ins CW-Feld zu schreiben.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta #Friendica #Hubzilla #Streams #(streams) #NichtNurMastodonI've updated the in my Ruth2 and Roth2 wiki.
Some changes:
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #RuthAndRoth #Ruth2 #VirtualClothing #VirtualFashion
They are.
The channel is a container which contains your Fediverse identity with everything attached to it. Posts, connections, settings, files and such.
The account is only there for you to be able to log onto a server on which your channel resides and access your channel.
That "revolution" is from 2012 when Mike Macgirvin took his own Friendica, forked it into Friendica Red and then re-wrote the whole thing against his new Zot protocol to support nomadic identity, thus creating Red, later known as the Red Matrix.
Hubzilla itself was renamed from the Red Matrix in 2015.
For comparison: Mastodon is from 2016, exactly ten months after the Red Matrix was renamed Hubzilla.
The Fediverse has had channels and nomadic identity in daily, productive, stable use for longer than Mastodon has been around.
Yes. Also because nobody can tell which channels are on which account (except the admin who has to dive into the SQL database to figure that out). So you can have lots of secret identities.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NomadicIdentity Long It goes far beyond what Mastodon can do.
Moving means moving everything. Literally absolutely everything. Or at least everything that isn't firmly tied to one specific instance such as login credentials.
Let's suppose you want to move from your own instance, kotaro.me, to fosstodon.org.
First, nomadic identity will copy everything over. All your posts, all your images, all your files, all your settings, all your filters, all your lists, all your mutes and blocks, even all your contacts, both followers and followed and mutuals (Hubzilla and (streams) don't distinguish between these because mutuals are the default).
Then it will re-write your entry on all your followers' followed lists from kotarokotaro.me to kotarofosstodon.org. Or at least it would if Mastodon was like Hubzilla or (streams) and understood nomadic identity. All your followers will automagically follow you in your new place.
Finally, it will wipe out your old stuff on kotaro.me. You won't leave a dead account behind.
Mind blown yet Because nomadic identity can do even wilder stuff. Namely clone.
Roughly translated from Hubzilla/(streams) to Mastodon, you could create an absolutely identical clone of your account on Fosstodon. Not only a dumb copy like what Mastodon can do now. A clone that will always stay identical.
Nomadic identity syncs your main and your clone with each other, bidirectionally, in near-real-time. Like a live backup of your Fediverse identity. One that'll never have to be restored because you can use the backup like you can use the original.
You post something on your main, the post is sync'd to your clone. You receive a post on your main, that post is sync'd to your clone. You change a setting on your main, that change is sync'd to your clone. You create a filter on your clone, that filter is sync'd back to your main. Fully automatically.
Your instance server crashes beyond repair Your home instance is dead Doesn't matter. You can carry on with your clone as if nothing had happened because the clone is always identical to the main and the other clones if you have some. You can declare your clone your new main and make one or more new clones.
Okay, on Hubzilla and (streams), matters are a wee bit more complicated. Your account is not your identity, and your stuff is not stored in your account. Instead, there are . Your posts, your files, your everything is stored in such a channel, and that channel is your identity. You only need an account to log onto a server and access your channel. A channel is basically an identity container.
You can have as many channels as you want on one account, nobody can tell that all these channels belong to the same account, and each one of your channels can reside simultaneously on as many instances as you want.
At the end of the day, however, channels make nomadic identity easier. Nomadic identity doesn't have to pry apart what can be cloned and what's firmly tied to this one instance. On Hubzilla and (streams), nomadic identity can simply move or clone a channel as a whole.
It also makes moving cleaner. At the end of a move, the copy of the channel on the old instance is easily deleted. And if there isn't any other channel on the account, the account is deleted, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NomadicIdentityShopping City in Astralia has lost almost all its appeal now.
Cloe Kegel has ripped out the last remaining shops that offered legal mesh clothes and replaced them with more outlets for stolen SL clothes for stolen SL bodies. For some of the items in these shops, Shopping City was the very last place all over the Hypergrid where you could get them. Now they're gone. No longer available anywhere.
Some two dozen tank top and miniskirt sets textured by Illiana Blachere and based on Damien Fate meshes, gone. Another Damien Fate-based set by Avia Bonne with an exclusive handbag which, I think, Avia has made herself, gone. And so forth. At least Oddball Otoole's Damien Fate texturings are still available at Riverford in Craft-World.
But Shopping City has lost the best reason to go there.
Maybe, just maybe I can get into contact with Cloe or the former owner of La Tortuga and ask them if they've still got the sales boxes, and if I can have them to keep the content alive. It'll certainly be more difficult and require more luck than my successful rescue of the Deva Moda clothes and make-up, and I'll have permissions to fix.
If that fails, I guess Juno Rowland and I will have some god-moding, permission-fixing and repackaging to do. Unfortunately, there are some items of which I don't know who made the textures because Cloe probably accidentally overwrote all credentials at some point in the past.
It's such a pity that so many who offer custom-textured Clutterfly or Damien Fate clothes or even obscure old layer clothes are or were sloppy, careless shopkeeps who never check what they slap against their shop walls, much less repair what's broken. Otherwise I'd be in possession of many many more sales boxes.
Sometimes, the only way to save content that's becoming increasingly rare is actually by copybotting it out-right because the items or sales boxes have botched rights, they can't be picked up in any "legal" way, and the shop owner can't be bothered to fix them. I'm almost tempted to take a copybot viewer to Sinus and save the Damien Fate stuff from Eva Kraai's shop because Eva flat-out refuses to fix her old content as she told me herself.
This wouldn't be so bad if the Ruth2 and Roth2 families didn't have to rely on Clutterfly and especially Damien Fate for legal mesh clothes. Chances are that the Max family will eventually get brand-new mesh clothes rigged just for these bodies, but Ruth2 and Roth2 with their unusable dev kits will probably rely on that slowly vanishing old stuff for good, even though Damien Fate makes Ruth2 v4 look pudgy and Roth2 v2 look thin as a twig.
#Long #LongPost #CWLong #CWLongPost #Astralia #DamienFate #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #VirtualClothing #VirtualFashion
And I'm very certain that AI won't be able to perfectly cover every last niche topic out there at the Fediverse's staggeringly high quality standards.
No, It won't. I should know because the primary topic of this Hubzilla channel of mine is about an extreme niche, namely a certain, very obscure kind of 3-D virtual worlds.
I rarely post pictures, but I sometimes do. I always write my image descriptions myself. And as this topic is so obscure that a whole lot of explanation is required for a casual audience that comes across my image posts on their federated Mastodon timelines to understand my posts and my pictures. One of the reasons why I write the longest image descriptions in the whole Fediverse.
An AI would require massive amounts of knowledge from partly tiniest niches from all over the world to give similarly detailed, accurate, informative explanations.
I also have to describe a whole lot. I mean, what do blind or visually-impaired people know what a virtual world they've never heard of looks like What anything in such a world looks like Maybe they're curious to know nonetheless. And they have a right to know.
An AI may recognise that the picture is from a virtual world, but it's unaware of the implications. It can't tell by looking at an image that the virtual world shown in the image is extremely obscure, that the audience that'll come across this image is mostly casual and clueless, and that therefore a very detailed description is necessary.
Also, AI can only see what's in the picture. But when I describe a picture from a virtual world, I don't describe it by looking at the picture. I describe it by looking at the real thing, standing in that world, looking around in that world with a nigh-infinite, lossless zoom factor readily at hand, able to move the camera or my avatar to wherever necessary in order to examine details. AI can't do that.
Lastly, there's a rule that says that any and all text within the borders of an image must be transcribed, full stop. There is no rule, however, on whether this applies to text that's so small that it's illegible, to text that's so tiny that it's practically invisible at the image's resolution or to text that's partly obscured by something that's standing in front of it.
Using the above method, I can transcribe just about all text in-world, even text in a picture in that picture when the former picture is takes up only 100 pixels or so. And I've done so. AI will never be able to do that.
By the way, some two weeks ago, I've actually pitted an image-describing AI against my own image describing with my most recent picture as the test object. The AI came up with 558 characters of visual description, but with no explanations, with no mention where the picture was made and even with some factual errors. My description of the same image clocked in at 25,271 characters, and this is guaranteed to not be a typo.
which includes both descriptions at full length, so it's a whole lot to read. Right below as a comment, where I dissect the AI description, pointing out where the AI was vague or out-right wrong and where it simply didn't provide vital information.
Do you really, honestly, unironically believe that it won't be long until AI can do absolutely everything I can do at the same level, if not even better
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AIScott M. Stolz
As far as I can see, it doesn't. It works wholly differently from nomadic identity.
Currently, Hubzilla hubs are like clients with full data storage that sync their data peer-to-peer.
Now imagine Hubzilla hubs being thin clients with no data storage whatsoever. Next to these hubs, there's another kind of server where your data is stored. Let's call it data server. It's fully independent from the hubs where you have your channel.
You can have as many instances of your identity on as many thin client hubs as you like. One goes down, doesn't matter, you've got more. But all your data is stored on one data server. With one account. One. Every last one of your channel clones on all those thin client hubs is connected to this one data storage.
You may be able to choose where to park your data. But you can only choose exactly one data server where you want to park your data for all your channel clones. You can not clone or mirror your data storage. You've only ever got one instance of that.
If that server goes bellies-up, have fun starting over from scratch. If you're lucky, you may have a backup. If you don't have an up-to-date backup because you haven't made one in a while, or you've never made one in the first place, well, then you're fucked.
It'll be even more fun if Solid won't let you make backups of your data in the first place.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #Zot6 #Nomad #Hubzilla #Streams #(streams) #Solidphanisvara (streams)
Richtig. Und wenn man sich mal auf Mastodon umguckt, und ich meine auf Mastodon direkt und nicht in dem, was einem von Mastodon auf den eigenen Channel Stream gesplt wird, dann sieht man jede Menge Schneeflocken, die fordern, da alle CWs setzen fr $THEMA, weil $THEMA sie irgendwie strt.
Ungelogen: Es gibt Leute, die wollen CWs fr Katzenbilder, weil ihnen die ganzen Katzenbilder auf den Keks gehen.
Ich glaube, es gibt auch Mastodon-Instanzen, die ganze andere Instanzen blocken, weil die nicht in ihren Regeln CWs fr bestimmte Themen zwingend fordern. Egal, ob das jetzt eine Mastodon-Instanz ist oder ein Hubzilla-Hub, wo es berhaupt kein Feld namens "CW" gibt und auch nirgendwo dokumentiert ist, da Hubzillas Summary Mastodons CW ist. Mal ganz davon abgesehen, da CWs im Summary in Hubzillas Kultur nicht vorkommen, weil Hubzilla so einen Kasperkram gar nicht braucht, weil es fr Empfindliche die schne NSFW-App hat.
Ich auch nicht. Aber so macht man das eben auf Mastodon, und so hat das geflligst das ganze Fediverse zu machen.
Filter sind aber "nicht Mastodon-mig". Filter, die automatisch CWs generieren, schon mal erst recht nicht, zumal es die erst seit letztem Jahr gibt.
Auf Mastodon hat man CWs im Summary, ohne zu wissen, da das eigentlich das Summary ist und eben nicht von Rochko fr CWs komplett neu erfunden wurde. Und, bitte, das gesamte brige Fediverse hat sich auch geflligst daran zu halten. Zumal diejenigen, die glauben, Rochko htte das Fediverse erfunden, wahrscheinlich die groe Mehrheit stellen.
Ich bin schon Leuten begegnet, die ganz unironisch das Fehlen eines so beschrifteten CW-Feldes auf Friendica, Hubzilla und (streams) als Bug ansahen und sagten: "Aber das kann man doch leicht beheben, oder"
Die meisten Mastodon-Nutzer kratzen ja eh nur an der Oberflche, entweder der Web-Oberflche oder, noch viel hufiger, der ihrer Smartphone-App. Viele wissen gar nicht, da Mastodon Filter hat, geschweige denn, wie man sie benutzt. Ungelogen: Vor ein paar Wochen habe ich als Hubzilla-Nutzer einem Mastodon-Nutzer Schritt fr Schritt erklrt, wie man auf der Weboberflche Filter einrichtet. Also, wirklich jeden Schritt einzeln. Und der war schon lnger dabei und nutzte standardmig die Weboberflche.
Selbst von denen, die schon deutlich ber ein Jahr dabei sind, wissen die allerwenigsten, da Mastodon jetzt auch CWs per Filter automatisch generieren kann. Wahrscheinlich sehen viele von denen das auch als unntzes Gimmick an, wo Mastodon doch schon das schne CW-Feld hat, das ja sowieso der Mastodon-Standard ist und der universelle Fediverse-Standard sein sollte.
Fr erfahrene Friendica-, Hubzilla- oder (streams)-Nutzer ist es das Natrlichste der Welt, die optionale NSFW-App zu haben, die vollautomatisch individuelle CWs generiert und dafr von denen, die Posts oder Kommentare schreiben, eigentlich nur verlangt, da sie entsprechende Schlsselwrter in ihre Posts oder Kommentare einbauen.
Fr typische Mastodon-Nutzer ist das aber komplett befremdlich, wenn nicht gnzlich unbekannt. Also wollen sie das gar nicht, zumal sie Mastodon sowieso als den alleinigen Goldstandard im Fediverse ansehen. Sie glauben ja auch, Mastodon ist deswegen am grten, weil es unterm Strich am besten ist.
Dazu kommt aber noch was: Mastodon-Nutzer sind es gewohnt, verhtschelt zu werden. Blo keine Eigeninitiative ergreifen fr irgendwas. Egal, was ist, irgendjemand anders soll sich drum kmmern. Wenn sie selbst sich an irgendwelchen Inhalten stren, sollen die 14 Millionen anderen Fediverse-Nutzer sie bitteschn davor warnen.
So, und dann kommen die, die sich an den vielen fr sie unntigen CWs stren und dagegen das Wort erheben.
Da fragt man sich doch: Warum setzen sich da nicht mal welche virtuell zusammen und diskutieren darber Ganz einfach: weil man auf Mastodon nicht diskutieren kann. Aufgrund technischer Design-Entscheidungen.
Mastodon hat keine Gruppen, weil Twitter keine hat. Mastodon kennt auch keine Gruppen, weil es eben keine hat, und was der Rest des Fediverse hat, wird von Mastodon geflissentlich ignoriert. Und Mastodon kennt auch das Konzept von Konversationen nicht, weil es auch die auf Twitter nicht gibt.
Fr uns auf Friendica, Hubzilla und (streams) ist es das Normalste der Welt, nicht nur Gruppen und Foren zu haben, sondern auch, da, wenn man einen Post im Stream hat, man dann automatisch auch smtliche Kommentare bekommt. Und man kann ganzen Threads sogar folgen. So sollte es sein.
So ist es aber auf Twitter nicht, also ist es so auch auf Mastodon nicht. Da gibt's keine Konversationen. Wenn du da irgendwas mit mehreren Leuten diskutieren willst, dann mu jedes Mal jeder in der Diskussion alle anderen einzeln erwhnen. Ansonsten werden die nmlich ber neue Diskussionsbeitrge nicht benachrichtigt.
Deswegen blken auf Mastodon alle ziellos in die Menge und werden nur von ihren eigenen Followers gehrt, sofern sie nicht gezielt irgendjemanden erwhnen. Und so blken auch alle aneinander vorbei. Und jeder kann die uneingeschrnkte Durchsetzung der eigenen Maximalforderungen einfordern, ohne davon zu lesen, da die eigenen Maximalforderungen eventuell mit den Wnschen anderer Nutzer kollidieren.
Vielleicht gibt es ein paar wenige, die es gern htten, wenn Mastodon mehr wie z. B. Friendica wre. Aber es gibt um Grenordnungen mehr, die wollen, da Mastodon und das ganze Fediverse mehr werden wie Twitter unmittelbar vor der bernahme durch Musk, weil das fr sie persnlich bequemer wre.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta
In general, when Mastodon users learn that the Fediverse is more than just Mastodon, they don't fight it because that'd be senseless. They're okay with there being something else than Mastodon in the Fediverse as long as this something else plays by Mastodon's unwritten rules, and it doesn't disturb Mastodon users. This something else is highly likely to break Mastodon's unwritten rules, either due to its own cultures being different from Mastodon's or due to design choices or both, but even then, I guess most rather resort to blocking individual rule-breaking users.
There are a few who don't accept something else being connected to Mastodon, and who want the Fediverse to be only Mastodon. But they aren't vocal.
With ActivityPub, the case is different. Those who want the Fediverse to be only ActivityPub-based projects are vocal. And what they actually want is the Fediverse to stay only ActivityPub-based projects. Which implies that they think this the Fediverse currently is only ActivityPub-based projects. Which, in turn, means they know neither Hubzilla nor (streams).
If you tell them that there are also Hubzilla and (streams), they're okay with that. That's because they think that Hubzilla and (streams) are and have always been based on ActivityPub themselves. Because, like, everything in the Fediverse has always been based on ActivityPub, right Can't be any different, right
But then you tell them that Hubzilla is based on a protocol called Zot6. And (streams) is based on a successor of Zot named Nomad. And in both cases, ActivityPub is implemented via a bridge plug-in named PubCrawl. PubCrawl is an official add-on, so it isn't third-party, and there is one of these bridges per channel and not one for all instances. But still, both Hubzilla and (streams) are not based on ActivityPub, and they're both bridged to Mastodon. Oh, and Hubzilla has been both in the Fediverse and using ActivityPub before Mastodon.
Then they have two options. They can accept Hubzilla and (streams) because they're free, open-source and non-commercial and reduce their anti-bridge stance to an anti-third-party-bridge-to-commercial-platforms stance which more reasonable Mastodon users already have, and which they express when you tell them that Hubzilla and (streams) are bridged, too.
Or they can stand their case and demand the full defederation of both Hubzilla and (streams). I've never seen anyone do that, but I guess that's because these people really don't know Hubzilla and (streams). Until I write to them, they've never come across a single post from either of these. But I guess if they're frequently enough exposed to posts from Hubzilla or (streams) that break Mastodon's unwritten rules, and if they can draw a line between the rules being broken and the users in question being on Hubzilla or (streams), that could trigger them to demanding full defederation.
In this regard, it's hard to be safe anywhere in the Fediverse.
Once you move elsewhere, be it Akkoma or Iceshrimp or something, you start using your new home project as you're supposed to use it. You start making use of features that aren't available on Mastodon, just like Mastodon users started making use of features that aren't available on . It's only natural.
But in doing so, you break Mastodon's unwritten rules, and you trigger Mastodon's Fediverse purity police into going ballistic. Posting over 500 characters at once is bad enough already. Text formatting is even worse. Quote-posts are generally associated with harassment, so they're just about the worst crime you can possibly commit in the Fediverse, along with quotes because the Mastodon purists can't see the difference between these two.
Never mind that pretty much everything outside of Mastodon supports all of this. I think even the 2SLGBTQIA+ community on Sharkey gleefully makes use of all of this, quote-posts included, the same people who, according to the Mastodon purists, should be against quote-posts the most fiercely because quote-tweets were used to harass them on .
However, if the general, non-Fediverse public becomes aware of the "Make the Fediverse only Mastodon again" purists, they'll automatically make fools out of themselves. A demand to make the Fediverse only Mastodon again implies something which both mass media and tech media currently prefer to ignore for simplicity's sake, namely that there is actually more to the Fediverse than Mastodon.
If media took the time and effort to dig deeper in this case, they'll be told that a) this is normal, b) this is by design, c) this is the very concept of the Fediverse, and d) some Fediverse projects have actually been there before Mastodon. So the Fediverse has actually never been only Mastodon which renders "Make the Fediverse only Mastodon again" delirious rubbish.
"Make the Fediverse only Mastodon" wouldn't look much more sensible in this light either. Why would everything that isn't Mastodon have to be excluded from the same Fediverse that was founded by parts of this very same everything Because it doesn't play by rules that aren't written down anywhere Because it's different By design even
This would be the very revelation that there's intolerance and "digital racism" in the Fediverse, not to mention attempted colonialism.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fediverse
There already is, but it's far from perfect, no matter who says otherwise.
And if legal accessibility requirements include minimum standards for image descriptions, namely that they have to be correct and at a certain minimum level of accuracy, then not only putting non-sense into the alt-text is out, but so is AI.
Sure, when it comes to describing casual images like cat pictures, AI is usually as good as humans. But when it comes to special interest images, AI would have to be absolutely as good as the very best actual or imaginable experts in the field, if not even better, no matter how niche the topic is. It would even have to learn about all new developments immediately so that it could describe them correctly and accurately right off the bat.
All LLM AIs out there that can be tasked with describing images would have to be absolutely omniscient. I think it's clear that this will never happen.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AIMike Macgirvin
This. Plus millions of Mastodon users who think that Eugen Rochko created both the Fediverse and ActivityPub, and therefore, Mastodon is the reference implementation of ActivityPub.
And some of them have created and still maintain popular mobile apps for Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
These aren't necessary problems of the whole Fediverse. Mastodon maybe, but not the whole Fediverse. Just because Mastodon's self-moderation capabilities are limited to mute and block, doesn't mean this goes for all the other Fediverse projects just the same.
Just to give you one example: Here on , I've got 17 general interaction permission settings, each with multiple values to choose from. I could even limit who is allowed to reply to my posts to:
The other 16 settings have at least the last seven of these options, sometimes all eight.
And that's only Hubzilla and only a part of it. goes even further than that. If you want a safe haven social network, and you don't absolutely have to be mollycoddled with maximum ease-of-use, then (streams) could be your safe haven. And yes, (streams) is part of the Fediverse and federated with Mastodon if you want to stay in contact with your old acquaintances.
In general, if you're discontent with both and Mastodon, the remaining alternatives aren't only Threads and Bluesky. The Fediverse is not only Mastodon, and the non-Mastodon Fediverse is not just simply Mastodon with more characters and a different UI. There are places in the Fediverse that can do things beyond most Mastodon users' imagination.
About the Mastodon users who completely flipped their shit upon the Bridgy Fed Bluesky bridge announcement, and every last one of them was on Mastodon: I've taken a closer look at their behaviour. They seemed fully convinced that they know everything about the Fediverse, but even some of those who had joined in November, 2022 apparently also thought that the Fediverse is only Mastodon, and none of them really knew how far the Fediverse actually stretches.
Proof: There was a lot of demanding the Fediverse be ActivityPub-only with no bridges to anywhere whatsoever. What these people actually meant was for the Fediverse to stay ActivityPub-only.
What they don't know, however: The Fediverse isn't ActivityPub-only right now. It wasn't at that point. And it has never been. Hubzilla runs on Zot6, and it's bridged to ActivityPub. (streams) runs on Nomad, and it's bridged to ActivityPub. Until recently, Friendica ran on DFRN, and it was bridged to ActivityPub. By that logic, all instances of all these three projects would have to be Fediblocked.
In fact, the Fediverse itself started long before ActivityPub. Friendica, the oldest current member of the Fediverse, dates back to 2010. The term "Fediverse" was first used in 2012. ActivityPub, on the other hand, became a W3C-appointed standard in 2018 and was first used in 2017. No, not by Mastodon. Hubzilla was faster by two months.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
The major problem with this, however, is that the worst offender is also two thirds of the whole Fediverse and perceived as the actual Fediverse standard. Just about everyone who joins the Fediverse now spends weeks, if not months, only exposed to Mastodon and thinking the Fediverse is only Mastodon. Some have joined in the second Twitter migration wave in November, 2022, but they still think the Fediverse is only Mastodon. For most of those who don't, the Fediverse is Mastodon and weird, alien non-Mastodon stuff, and only Mastodon counts as normal.
This actually goes as far as Mastodon users thinking that whenever something is different from Mastodon on another project, that's a bug that should be fixed. And I'm talking about things like Friendica not having Mastodon's alt-text field. That's something that doesn't disrupt communication, and it's independent from the ActivityPub standard. But if actual communication fails because one side strictly adheres to the ActivityPub spec, and the other side is Mastodon, a majority of Fediverse users will believe it's the non-Mastodon side that's broken.
It doesn't help that all kinds of news outlets simplify the Fediverse down to "Mastodon and stuff that doesn't matter" or even actually only Mastodon while stating that Mastodon is built against ActivityPub and thus implying it's cleanly built against ActivityPub.
Thus, playing by the official rulebook only and ignoring Mastodon's non-standard quirks is playing with high stakes.
It could work out, though. The "strictly ActivityPub" side just needs more projects to join. More server apps to make themselves independent from Mastodon by going the pure ActivityPub way. Even clients that exchange the Mastodon API for actual ActivityPub.
It probably wouldn't be that much work for Friendica and Hubzilla. I can also see *key developers turn their backs on Mastodon if they perceive it as toxic and show it by joining the "strictly ActivityPub" side. The best case would be if Iceshrimp or even Misskey itself did that because they'd drag a whole number of soft forks along.
If only (streams) goes pure ActivityPub while everything else sticks to "but muh Mastodon compatibility", (streams) will be seen as broken by design, even if someone filed a bug on Mastodon's GitHub repository because of some incompatibility with (streams), even if that bug report includes proof that it's Mastodon that goes against the ActivityPub standard while (streams) sticks to it.
But if someone filed a bug on Mastodon's GitHub repository because Mastodon ignoring the ActivityPub standard can be proven to break compatibility with 15 different server applications, at least five of which aren't "never heard of that" material but actually well-known, and a bunch of popular iPhone and Android apps on top, all of which chose to stick to ActivityPub only, it's obvious that it's Mastodon that's broken.
In this regard, the thought of the Fediverse splitting in two becomes kind of interesting. One side is fed up with Mastodon's antics and sticks to the W3C spec, even if it breaks compatibility with Mastodon. The other side is Mastodon which has just lost control over one third of the free, non-commercial Fediverse, and which is left with Threads as its only playmate.
Unfortunately, Threads is not being built against the W3C ActivityPub standard, but only against Mastodon which makes breakage with everything that isn't Mastodon highly likely already now. It'd be fun if Meta had decided to go by the ActivityPub spec only and then openly declared that Mastodon is faulty because of how utterly incompatible it is to something that follows the spec to a tee.
On the other hand, the breakage might keep Threads at a distance from the non-Mastodon Fediverse and more so from the "strictly ActivityPub" Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub It most likely won't. I guess it'd be "un-Mastodon-like".
My advice to Mastodon users who crave certain features that Mastodon doesn't have, but that are readily available elsewhere in the Fediverse is: Don't sit and wait until your Mastodon instance introduces that feature. If you want it, go where you can have it.
I've written a very long post on this topic almost a year ago.
Might open in Mastodon:
Original:
If you really want to be able to quote, it isn't worth waiting for quotes to be implemented on Mastodon. Try Iceshrimp or Sharkey instead the latter even lets you import your post backlog from Mastodon AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta It's called a quote. Standard feature on Friendica, Hubzilla (where I am), (streams), the now-deceased rest of the family, Misskey and all its forks etc., basically everywhere that isn't Mastodon.
Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
(streams) also has ways of doing that with Markdown or HTML.
There are various different ways of getting that code, also depending on whether one replies to a post or a comment.
ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.
Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText If you mean an update that makes Friendica handle 100% like Mastodon to make things easier for Mastodon converts, then no. That'd sacrifice image embedding.
Essentially, Friendica would need an alt-text field for Mastodon-style file attachment images, and it'd need an even more advanced WYSIWYG post editor which includes some kind of alt-text field for each embedded image.
Also, AFAIK, there are no dedicated mobile apps for Friendica, and Friendica doesn't support the Mastodon API due to both being so vastly different from Mastodon in its architecture and six years older than Mastodon. What few general Fediverse apps work with Friendica only work barely so and don't even support a tiny fraction of what Friendica can do. Friendica is typically used in a standard Web browser.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #AltText It does support alt-text, technically speaking. It just doesn't have Mastodon's easy-peasy alt-text entry field. And I think if you want to have alt-text on Friendica, you must not handle images the Mastodon way by uploading them to a post draft as file attachments, but you must upload them to your file storage and then embed them, blog-style.
Once you have the image embedding code in your post draft, you must manually graft the alt-text into that code. I'd walk you through it step by step if I could, but I don't know how exactly the code in Friendica looks like.
I can tell you what it looks like and how it works on Hubzilla, though, and since Hubzilla is Friendica's descendant, it should be similar, only that Friendica probably still uses
So when you embed an image into a post on Hubzilla, the code looks like this:
The first thing you do is cut the image file URL and paste it over the image size in the
On Hubzilla, this works absolutely well. I've done it myself countless times already.
I think Friendica works largely the same, only that it uses
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #AltTextImplementing encryption in ActivityPub would require a way to find out which instance or which actor supports which ways of encryption, if any.
Encryption would break compatibility more than nomadic identity ever could. If one project implements mandatory, no-opt-out encryption, and another project doesn't implement it at all, then actors using the second project won't be able to communicate with those using the first project.
And there will be projects that won't implement encryption as well as projects that won't even implement nomadic identity. Not exactly few Fediverse projects are highly opinionated what their creators don't like and/or don't find useful enough and/or think makes things too complicated won't be implemented. Sadly, Mastodon is one of the worst, also because it shows this "we don't implement what we haven't invented ourselves" mindset, and because it can afford becoming incompatible with the rest of the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NomadicIdentity Looks like many mobile apps for Mastodon were made by people who were new to Mastodon, totally giddy about it, eager to improve the mobile experience, but at the same time clueless. They didn't distinguish much between ActivityPub and the Mastodon API, and at that point, they didn't even know that the Fediverse is more than just Mastodon.
That's also why there are apps that technically support everything that uses the Mastodon API, but that don't have any features beyond vanilla Mastodon 3.x and don't even support over 500 characters.
At the same time, I think, there isn't a single app purely built against the ActivityPub standard and for the Fediverse in general. It simply wouldn't be compatible with Mastodon. Even supporting the full ActivityPub standard next to the Mastodon API seems unattractive.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #MastodonThe recent statistics:
The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records. There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the View article View summary OpenSim area continues growth streak
The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records.
There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the total number of registered users went up by more than 1,338. The number of active users fell, however, by over 2,100, partly due to grid outages. , for example, which reported over 400 active users last month, was down this month. And two other grids that reported drops of more than 500 active each may have had database issues, including and .
Im now tracking a total of 2,654 public grids, of which 308 were active, and 244 published their statistics this month. If you have a stats page that were not tracking, please email me at that way, your grid will be mentioned in this report every month, for additional visibility with both search engines and users.
Also, Im no longer sending out a monthly email blast reminding OpenSim grid owners to send me news and updates for this report. If you have news, please email me before the tenth of the month if you want a short item included in this monthly wrap-up. For longer news, feel free to send me press releases at any time.
OpenSim land area for March 2024. (Hypergrid Business Data.).
Our stats do not include many of the grids running on which is a distribution of OpenSim since these tend to be private grids.
OpenSim is a free open-source, virtual world platform, thats similar to Second Life and allows people with no technical skills to quickly and cheaply create virtual worlds and teleport to other virtual worlds. Those with technical skills can run OpenSim worlds on their servers for free using either DreamGrid, for those who are more technically inclined, or any other distribution, while commercial hosting starts at less than $5 a region.
A list of . Download the and find out .
Every month on the 15th right after the stats report comes out we will be sending out a newsletter with all the OpenSim news from the previous month. You can or fill out the form below.
Please leave this field empty
Get our monthly stats and all other OpenSim news delivered right to your mailbox every month.
Email Address *
We dont spam! Read our for more info.
Check your inbox or spam folder to confirm your subscription.
When it comes to general-purpose social grids, especially closed grids, the rule of thumb is the busier the better. People looking to make new friends look for grids that already have the most users. Merchants looking to sell content will go to the grids with the most potential customers. Event organizers looking for the biggest audience you get the idea.
Top 25 most popular grids this month:
All region counts on this list are, whenever available, in terms of standard region equivalents. Active user counts include hypergrid visitors whenever possible.
Many school, company, or personal grids do not publish their numbers.
. . And here is a and their hypergrid addresses, sorted by popularity. This is very useful if you are creating a hyperport.
You can see all the , including polls and surveys, dating all the way back to 2009.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OpenSimStatistics #HypergridBusiness
Bei sehr vielen Fediverse-Diensten (#mastodon, #misskey und Misskey-Forks = #forkey , #pleroma ,...) hat das Handle folgende Form:
Mein Handle z.B. fr meinen Mastodon-Account lautet:
Bei vielen anderen Fediversediensten, wie z.B. #hubzilla , #streams , #friendica etc. unterscheidet sich das Handle (und die Bezeichnung... hier meistens als "Kanal" bezeichnet) ein wenig. Es hat die Form:
Das ""am Anfang wird weggelassen.
Diese Tatsache ist wichtig und kann bei Nichtbeachtung zu Problemen fhren.
Mchte man bei Hubzilla (und Verwandten) nach einem Handle suchen oder einen Kontakt hinzufgen, der von anderen Diensten stammt, dann muss man das fhrende "" weglassen!
Mchte man bei einem anderen Fediverse-Dienst (z.B. Mastodon) nach einem Hubzilla-Nutzer (Hubzilla-Kanal) suchen oder diesem folgen, muss man das "" am Anfang ergnzen!
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost Der Pepe (Hubzilla) That, and the typical Fediverse experience nowadays is a) Mastodon while barely or not at all knowing anything else exists and b) on a phone through a dedicated app.
The average Fediverse user doesn't start by joining Hubzilla on a desktop or laptop computer. They're fed up with Twitter and what became of it. They're told about Mastodon and the Fediverse which is implied to them to be one and the same thing.
So they grab their phones, they "install Mastodon" (the official app they've never in their lives used any online platform through an app that doesn't have the same name as the platform), and they register an account. On mastodon.social.
For at least the first three months, the Fediverse to them is Mastodon. Vanilla Mastodon with no more features than what Mastodon 3.x had. They actually think 500 characters are a lot, and they cannot imagine for the lives of them that it's possible for posts with more posts to exist in the Fediverse. How could they possibly The Fediverse is only Mastodon, after all.
Needless to say that they're deeply shocked and disturbed once they come across a post that does anything they took for absolutely impossible in the Fediverse. It's usually 500 characters, regardless of whether they come from Glitch or Misskey or Hubzilla.
At this point, they've gotten used to the Fediverse not allowing for more than 500 characters, not having text formatting, not having quotes, not having quote-tweets etc. etc. and of course being Mastodon and only Mastodon. And then this happens.
Those who are still on the official app are the poorest saps. The official Mastodon app is mercilessly hard-coded against vanilla Mastodon only with absolute and staunch disregard of the existence of anything else in the Fediverse. It totally refuses to take the existence of both Mastodon forks and non-Mastodon projects into account because that'd mean that Mastodon acknowledges the existence of Fediverse projects that have features that Mastodon a) lacks and b) flat-out refuses to introduce. So those on the official app get all long posts slammed right into their faces in the shape of unshortened walls of text.
Granted, the official Web front-end isn't that much better. It does fold long posts in. But it only folds posts in if they're ca. 2,000 characters or longer, and then it folds them in to ca. 1,500 characters.
Still, long posts can upset Mastodon users regardless of front-end. They're something that these users didn't expect. Something they don't want. Something they say doesn't belong into Mastodon and therefore into the Fediverse. Something that must be abolished.
For some even something they're willing to fight against until it's gone from the Fediverse, until the Fediverse is again what they thought it was when they were new: only vanilla Mastodon with only vanilla Mastodon's capabilities.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #500Characters Because 2010/2011 was when this federation was established. And not 2012 or 2016 or 2024.
It doesn't matter if Diaspora* has introduced an official API years later. There was no API in 2010/2011. There was no technical documentation in 2010/2011. There was no interest in connecting to anything else in 2010/2011.
But there was Mistpark/Friendika, then still developed by Mike, that had federating with everything that could possibly be federated with as one of its primary goals. No matter the odds. Even including Twitter and Facebook.
In autumn 2010, shortly after the very first public alpha of Diaspora* had come out, there were no signs of things improving, no signs of there being a stable API anytime soon, if ever. Diaspora* gave the impression of only wanting to federate with itself. So trying to wait for an appropriate server-to-server API appeared to be futile, and Mike had to start working on that federation without an API.
And besides, while Diaspora* did evolve to a certain degree, Mistpark evolved more from March, 2010 to July, 2010 than Diaspora* did from May, 2010 to now. And I'm not even talking about what came after Mistpark/Friendika/Friendica, namely the Red Matrix, Hubzilla, Osada, Zap etc. and eventually (streams).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica I'm not talking about 2016.
Friendica, then named Friendika, introduced its federation with Diaspora* on March 19th, 2011 (see also ). This means that work on federating Friendika with Diaspora* had started as early as 2010 when the original four devs were still in charge.
If simply asking them had worked, all that hassle with reverse-engineering from source code and cracking encryption would have been unnecessary, and Friendika would have federated with Diaspora* in 2010 already.
And don't tell me that Mike Macgirvin didn't want to get into contact with the Diaspora* devs and intentionally do all the federation behind their backs. Mike has actually contributed to Diaspora*'s protocol, and unlike his attempted contributions to ActivityPub, they were even accepted AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica
Did Diaspora* ever do anything to facilitate federation for Friendica or Hubzilla or (streams)
Did it ever actively try to stop them
Did it at least officially acknowledge that these three are federated with it
It's my description of how difficult it was to federate Friendica with Diaspora*.
Back in the day, Diaspora* had no API and no documentation on its protocol. Diaspora* was all about only federating with itself. Still, Friendica wanted to federate with it because Friendica federated with everything, full stop.
The "drilling into a computer case with a diamond drill" represents the several months it took the Friendica devs to crack Diaspora*'s undocumented encryption.
The "soldering wires onto circuit boards" represents how the Friendica devs had to reverse-engineer Diaspora* by studying its source code because there was no technical documentation whatsoever, and how Friendica could only federate with Diaspora* by latching directly onto Diaspora*'s inner workings instead of making use of any interface because there was no interface to use whatsoever.
Ask Mike Macgirvin .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica In the long run, however, it's bad.
It'll lead to wide-spread segregation of not only single Mastodon users, but entire instances from users that regularly post over 500 characters and instances with such users.
To say that's inconvenient puts it mildly, seeing as the secondary topic of my Hubzilla channel is the Fediverse in general and educating Mastodon users about the Fediverse outside of Mastodon in particular. If these very same Mastodon users can't read my posts anymore because someone else on their instance has talked their instance admin into blocking either my channel or the entirety of hub.netzgemeinde.eu, calling it inconvenient is an understatement.
It also makes explaining that "the Metaverse" is neither Zuckerberg's invention nor dependent on blockchains, cryptocurrencies and NFTs, and that decentralised 3-D virtual worlds have been around for over a decade and a half, much more difficult. And that's the primary topic of this channel.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaphanisvara (streams) Yes, but many Mastodon users can't stand to see posts with over 500 characters. Not only do they refuse to read "long" posts, but some actually block anyone who exceeds 500 characters in a post even only once.
I'm pretty sure some ask their Mastodon instance admins to deal with such people. Have them blocked instance-wide. Have their whole Hubzilla hub blocked on that Mastodon instance.
Or they try to use Mastodon's report feature to report that Hubzilla user to the admin of that Hubzilla hub, or they have their admin try and get into contact with the admin of that Hubzilla hub, just to have that Hubzilla user sanctioned for breaking some unwritten Mastodon etiquette by posting over 500 characters in one chunk.
Of course, they fail in both cases. Hubzilla doesn't support Mastodon's report feature, and mentioning Hubzilla users, in this case the admin, in a public post won't work either. Verdict: That Hubzilla hub is unmoderated and therefore has to be blocked or even out-right Fediblocked.
On the grounds of the assumption that Hubzilla works exactly like Mastodon. Which I'm trying to debunk with this series of posts.
As at least one of my polls has revealed, there seems to be a not insignificant number of Mastodon users who demand posts with over 500 characters be banned absolutely everywhere in the Fediverse. Including in conversation between users on other projects, regardless of whether overly long posts from that conversation might leak into Mastodon or not.
And, of course, there's the Mastodon police that try to urge non-Mastodon users to limit their posts to a maximum of 500 characters, regardless of whether they're aware that the user in question is on something else than Mastodon or not. They're fully convinced that Mastodon was here first, and all the other projects are intruders in Mastodon's Fediverse and have to follow Mastodon's rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterCount #CharacterLimit #CharacterLimits #500Characters #Mastodon
It would have to exist within ActivityPub. The only alternative would be the whole Fediverse having to adopt yet another non-standard Mastodon hack that isn't documented anywhere because Mastodon didn't intend it to be adopted by other projects.
But if you don't want stuff to leak out through Hubzilla, it would also have to be included into the Zot6 protocol. And if you don't want stuff to leak out through (streams), it would have to be included into the Nomad protocol.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
You've basically described . Established, free, open-source and decentralised since 2007, interconnected since 2008, today with thousands of individual worlds ("grids"), most of which are connected to the Hypergrid, and over four times the land area of Second Life.
Oh, and the OpenSim community has had "metaverse" as a regular part of their vocabulary since 2007 as well.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds
Einen Artikel erstellt man ber die App (Hamburger-Men ) "Artikel". Ruft man diese auf, werden smtliche erstellten Artikel angezeigt und man hat die Mglichkeit, einen neuen Artikel anzulegen ("Artikel hinzufgen").
Das Erstellen eines Artikels hnelt dem Erstellen eines normalen Beitrags. Das Eingabe-Formular weist aber zwei zustzliche Felder auf: "Summary (optional)" und "Link zur Seite".
Das Summary ist eine kurze Zusammenfassung des Inhalts, die beim Aufrufen des Artikels zunchst angezeigt wird.
Mit dem Link zum Artikel kann man die URL festlegen, ber welche man den Artikel erreichen kann (z.B. zum Teilen). Gibt man dort z.B. "ein-testartikel" ein, so lautet die URL: /articles//ein-testartikel
Den Link kann man aber z.B. auch einfach kopieren, indem man den Artikel ber das Kontextmen () "Link zur Quelle"aufruft und den Link zum Artikel aus dem Adressfeld des Browsers verwendet.
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost"Write your posts as long as you want," they say.
"Don't be apologetic about it," they say.
"Literally everyone in the whole Fediverse has gotten used to posts over 500 characters, and nobody minds anymore," they say.
"Literally everyone on Mastodon is perfectly okay with all of Hubzilla's antics," they say.
"Nobody wants the Fediverse to only be vanilla Mastodon," they say.
Oh, really Then I've probably faked this shared post here.
Being able to mute or filter posts that exceed 500 characters would be great.
Search is not good because it returns too many dissertations.
#Long #LongPost #CWLong #CWLongPost #LongPosts #LongToots #LongPostMeta #CWLongPostMeta #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteBoost #CharacterCount #CharacterLimit #CharacterLimits #500Characters #Sarcasm
I think #Hubzilla would have been more cool and successful if it didn't had #ActivityPub app and was its own alternative Fediverse. I wonder if there probably are Hubzilla instances without it.
Well, Hubzilla is a direct descendant of Friendica. And Friendica's concept was and still is to federate with everything that moved and then some. StatusNet (which included early Mastodon and Pleroma, by the way), Diaspora*, Tumblr, Libertree, Twitter, e-mail, even Facebook for a few months, although that definitely required a Facebook account.
Hubzilla took a lot of that over. And Hubzilla was actually the first Fediverse project to adopt ActivityPub, even before its standardisation and two months before Mastodon.
But ActivityPub is actually optional both for the whole hub (on by default) and for each channel (off by default). So it's actually possible to run an entire Hubzilla hub with no ActivityPub at all.
Zap, a fork of Osada which itself was a slimmed-down fork of Hubzilla, had no ActivityPub at all in its early stages. Mike created it as a testbed for Zot6, and he expected Zot6 to be incompatible with non-nomadic protocols such as ActivityPub, so Zap only knew Zot6 and no other protocol, and Osada which lacked nomadic identity was to be used as a bridge between Zap and the rest of the Fediverse. Later on, Zot6 did become compatible with non-nomadic protocols, so Zap got ActivityPub support after all. And there was actually much rejoicing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla
Mastodon came after Hubzilla. Hubzilla was built on its own protocol and Hubzilla added the ActivityPub protocol long time back to connect to the whole Fediverse (not just Mastodon).
You know that, I know that, but there are not exactly few people on Mastodon who don't know that.
Even when they learn that the Fediverse is not only Mastodon, much to their surprise, they tend to believe that if Mastodon isn't the only Fediverse project, it must still have been the first. And everything that isn't Mastodon is either bolted onto Mastodon or an intruder.
Don't see what issues Mastodon users may have with it, as it has connected for ages.
Disturbingly long posts. Non-Mastodon users are banned for exceeding 500 characters once. And I'm pretty sure that Mastodon users try to have non-Mastodon users sanctioned by their admins for breaking this unwritten Fediverse rule.
Quote-posts. For Hubzilla users, it's called sharing, and it has been the equivalent to Mastodon's boosts since 2015 because Hubzilla can't boost. Not until Hubzilla 9 is out. For minorities on Mastodon, it's the exact same thing as the quote-tweets that were used on Twitter to harass them. And Hubzilla doesn't let them opt in, not even opt out. Hubzilla can quote-post anyone on Mastodon, always.
I'm not even sure if every last first-wave and second-wave Twitter refugee who got used to Mastodon 3 is used to seeing things on Mastodon that were absolutely impossible on Mastodon 3 such as text formatting.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #HubzillaThis is interesting to watch.
The cat's out of the bag. Mike Macgirvin 's is in the news all over the Fediverse. Of course, you can't expect everyone in the Fediverse to know what nomadic identity is, so the explanation is that it's that stuff that Hubzilla does.
Which, in many cases, is the very first time that Mastodon users even read that name and learn about the existence of that project. I mean, I've seen a poll just yesterday, according to which three out of four Fediverse users have never heard of Hubzilla.
This, in turn, piques their interest. All of a sudden, lots of Mastodon users are curious about Hubzilla as it's said to be able to do things that Mastodon can't, but that they wish Mastodon could.
Some like who haven't used any other Fediverse projects than Mastodon so far actually , only to discover something probably absolutely unexpected: Hubzilla works and handles absolutely nothing like Mastodon. And that's not simply due to the formerly-default-and-now-only UI that's perpetually stuck in 2012.
They may actually wonder why Mike had the audacity to build something that's so much different from Mastodon instead of just aping Mastodon and slapping extra stuff on. And I guess they're even more surprised when you tell them that Hubzilla was made before Mastodon. Which means that there was a Fediverse before Mastodon.
It occurred to me only recently just how many ways Hubzilla has to completely blow Mastodon users' minds.
However, it isn't like people who have come from Twitter to Mastodon to Hubzilla over the last year and a half are all happy about how Hubzilla is different from Mastodon. Switching from Mastodon to Hubzilla takes more getting used to than switching from Twitter to Mastodon, especially if you expect Mastodon to be a standard that everything else has to follow.
There are, in fact, lots of things about Hubzilla that'll irritate people used to Mastodon to no end. The confusing difference between account and channel. The unusual conversation model that sends posts to other people than on Mastodon which doesn't have a conversation model. Separate editors for posts and comments. In fact, posts and comments being something different. ActivityPub not being on by default, and instead of having a simple opt-in switch in the settings, you have to "install" an "app" to be able to connect to Mastodon. No CW field (it's the summary field, but there's none for comments). No alt-text field. No distinction between followers and followed. Stuff in the settings not being where you'd expect it to be from your experience with Mastodon.
And I'm not even talking about the vast permission options yet. Or the filters which even I say need improvements. Or Hubzilla being unable to boost (shall be fixed with Hubzilla 9) and follow hashtags. Or people telling you that you have to type code manually if you want to have alt-text.
Even those who learn about Hubzilla without trying it are confused. Why is it so different Why does it have to be so different Why can't it be like Mastodon
In fact, it doesn't really occur rarely that Mastodon users consider almost everything in which Hubzilla differs from Mastodon a bug which they think can be fixed. It seems to be hard to imagine that what they take for a bug is part of Hubzilla's concept, and it has often been part of the concept since the early days of Mistpark back in 2010, almost six years before Mastodon came out.
I think over the next days and weeks, Hubzilla will increasingly be considered not only weirdly different, but disturbingly different. Along with that, more and more Mastodon users will become aware of the "atrocities" from a Mastodon point of view which Hubzilla users commit in the Fediverse, and which they justify with their different culture. Enormously long posts, text formatting, quotes, quote-posts, as if it's all the most normal thing in the world. Which, for Hubzilla users, it is.
In the near future, Mastodon will likely produce two more forms of drama. One is strong opposition against nomadic identity anywhere in the Fediverse, not so much because it's "un-Mastodon-like", but because it's expected to be used in malicious ways.
The other one is increasing opposition against Hubzilla itself and more and more calls for Fediblocking it in its entirety, along with all Mastodon or otherwise Fediverse instances that don't Fediblock all Hubzilla hubs. All because it's got that disturbing stuff like nomadic identity and huge posts well over 500 characters and quote-posts with no opt-out for anyone. And because more and more Mastodon users become aware of it.
I hope it won't happen, but I can't exclude it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla
It's true that Nomadic Identity is largely only implemented by Streams and Hubzilla at this time, which are PHP implementations of the Zot/Nomad protocol. Admittedly, it's a bit hard to find quality documentation on these. Paradoxically, the implementations are quite mature, and have been around for years at this point.
Yes, nomadic identity was created along with the Zot protocol as early as 2011. Zot was first implemented on the Red Matrix which is based on a Friendica fork, which had its 1.0 release in 2013, and which was renamed into Hubzilla and repositioned with a different set of features in 2015. So all this happened before Mastodon was released.
Nomadic identity has been in daily, stable use for over a decade.
Like Friendica's DFRN before, Zot was never meant to be an officially standardised protocol like ActivityPub that other, completely different and independent server applications could use. Zot and Hubzilla have always been firmly tied to one another. Zot is not nearly as vague as ActivityPub. And Zot not only covers nomadic identity, but also Hubzilla's permission system which exceeds even a Mastodon user's wildest imagination by magnitudes.
Over the years, Mike advanced Zot further and further, often requiring new forks to test Zot. In 2018, two different Osadas and Zap became the testbeds for Zot6 which Hubzilla would later be upgraded to, and short-lived Zap even saw stable releases. In 2020, another Osada and two more projects which resurrected the names Mistpark and Redmatrix were the testbeds for Zot8 which was so advanced that it had become impossible or at least unfeasable to upgrade Hubzilla to it.
Roadhouse from early 2021, a fork of the third Osada, Redmatrix 2020 and/or Mistpark 2020 (they had the same code base), was either the last application on Zot8 or the first one on what would have been Zot11, but what was so advanced that it had become incompatible with Zot6. Therefore, it was renamed Nomad. And it became the base protocol for the nameless, brandless server application in the Streams repository which Mike is currently maintaining and constantly advancing. And current Nomad would be Zot12 if it was still Zot.
The reason why nomadic identity has only ever been implemented in PHP is because the only one who has ever built server applications with nomadic identity was Mike Macgirvin who also created the protocols behind them. And being built in PHP, everything that Mike has ever created from 2010's Mistpark to 2021's (streams) can be installed on a run-of-the-mill LAMP stack without having to fumble around with stuff like Ruby on Rails.
If you come from a "Fediverse = ActivityPub" background, all this may seem strange. But it was the only way for nomadic identity, Zot, Nomad and their implementations to advance to such power so quickly. Mike is still the sole keeper and maintainer of Nomad and its only implementation. This means that nobody else can meddle with it, and Nomad and (streams) are perfectly matched to each other. Thus, (streams) is probably the most quickly advancing Fediverse project currently.
That said, it is not a fully closed ecosystem. However, the idea behind developing stuff for Nomad is vastly different from the idea behind developing stuff for ActivityPub.
If you want to make something for ActivityPub, you usually sit down and start from scratch, from completely zero, except for the ActivityPub spec.
If you want to make something for Nomad, the recommended ways involve (streams). See, unlike Mastodon, (streams), just like Hubzilla, is not an enclosed monolith. It's modular. It can be expanded. And, in fact, both come with official add-ons right away. ActivityPub support itself is an add-on. A big difference is that Hubzilla comes with more add-ons whereas (streams) is slimmed down in this regard to make development easier. But it's possible to add third-party add-on repositories to server installations of both.
So if you want to make something for Nomad, you start with (streams). No need to start from scratch.
Either you simply develop add-ons for (streams) and offer them in a third-party repository that can be added to (streams) instances. Or you could soft-fork (streams), its core is in the public domain, add your stuff, slap a name on it and offer it as a new project.
I myself wouldn't recommend a hard fork, though, seeing as how rapidly (streams) is evolving and improving.
Sure, it'd be possible to develop something against Zot6 or Nomad completely from scratch. But if you build against Zot6 to stay compatible with Hubzilla, you're at Mario Vavti's mercy because he is the main dev of Hubzilla and therefore the keeper of Zot6 now, although I guess he doesn't change much about the protocol anymore.
And if you build against Nomad, you're at Mike's mercy, and Mike keeps advancing Nomad constantly and (streams) along with it. Also, if you build against Nomad, you must go multi-protocol because Hubzilla doesn't understand Nomad, so you also have to implement Zot6.
Standardising Nomad and handing it over to a W3C commission so it's no longer in the hands of one individual would be the worst that could possibly happen to it. Such a commission would water it down and remove stuff that they deem unnecessary. And Mike, no longer in control over Nomad, would have to play along and water (streams) down.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #Zot6 #Nomad #Hubzilla #Streams #(streams) #NomadicIdentity
Leute, die sich zu fein sind CWs zu setzen, setzen Hashtags Neee.
Vielleicht nicht auf Mastodon. Aber das Fediverse ist nicht nur Mastodon. Und das Fediverse ist auch nicht nur Mastodon und Zeug, das Mastodon nachfft.
Ich erklr's dir mal. Aber Achtung: Das wird jetzt brutal lang. Und nein, ich werde das nicht in 500-Zeichen-Hppchen zerschnipseln. Falls du diagonal lesen willst: Das Wesentliche ist fett gesetzt.
Friendica ist absolut nicht wie Mastodon. Hubzilla ist indirekt ein Friendica-Fork und ist auch nicht wie Mastodon. (streams) ist indirekt ein Hubzilla-Fork und ist auch nicht wie Mastodon.
Friendica setzt seit 2010 auf vollautomatisch fr jeden Leser individuell per Textfilter generierte CWs. Das ist fast sechs Jahre lnger, als es Mastodon berhaupt gibt. Hubzilla tat das auch schon immer, und auch Hubzilla ist lter als Mastodon. Auch (streams) tut das.
Alle drei haben nicht nur diese vollautomatischen CWs und haben diese bombenfest als Teil ihrer Kultur, so wie Mastodon das CW-Feld bombenfest als Teil seiner Kultur hat. Nein, keins von den dreien hat berhaupt ein mastodonmiges CW-Feld.
Was auf Mastodon eine CW ist, ist auf allen dreien immer noch das, was es war, bevor Mastodon es zweckentfremdet hat: ein Summary. Eine Zusammenfassung.
Hubzilla und (streams) haben also statt eines CW-Feldes ein Summary-Feld. Das funktioniert genauso, da steht aber nicht CW drauf, sondern Summary. Viele wissen nicht mal, da das Mastodons CW ist.
Und: Hubzilla und (streams) haben das Summary-Feld, also quasi Mastodons CW-Feld, nur fr Posts, die keine Antworten sind. Die sind ja keine twittermigen Microbloggingdienste mit einem Eingabefeld fr alles. Die sind eher aufgebaut wie Blogs mit einem Eingabefeld fr Posts, mit dem man nicht antworten kann, und separaten Eingabefeldern unter jedem Post fr Kommentare.
Zusammenfassungen fr Blogkommentare sind aber Kokolores, das macht keiner. Folglich gibt's fr Kommentare kein Summary-Feld. Folglich kann man auf Hubzilla und (streams) keine Mastodon-CWs auf Antworten setzen. Es ist ganz einfach technisch nicht mglich, weil es die dafr ntigen Mittel gar nicht gibt, weil die aus Hubzillas Sicht berhaupt keinen Sinn ergeben wrden.
Friendica, das lteste von den dreien, ist noch extremer: Da gibt es berhaupt kein solches Feld. Nicht fr Posts, nicht fr Kommentare, gar nicht.
Friendica macht das mit BBcode-Tags. Friendica, Hubzilla und (streams) nutzen ja BBcode auch fr so Sachen wie Textformatierung, Listen, Tabellen, eingebettete Bilder usw. Und Friendica nutzt das auch fr Zusammenfassungen.
Der Vorteil ist: Das geht auch in Kommentaren. Der Nachteil: Da das berhaupt geht, wird nur aus der Nutzerhilfe ersichtlich. Und es ist auch wieder nicht allen klar, da Friendicas
abstract/abstract oder abstract=apub/abstract = Mastodons CW ist.Was wieder allen dreien gemein ist: Deren Nutzer finden die Idee, das Summary komplett fr posterseitige, also allen aufgezwungene CWs zu mibrauchen, kompletten Humbug. Sie haben ja seit 2010 etwas fr CWs, was tausendmal besser ist: NSFW. Das generiert CWs nmlich vollautomatisch. Auf der Leserseite. Und zwar zum einen nur optional und zum anderen individuell fr jeden Nutzer.
Und dann kam sechs Jahre spter dieses Mastodon daher, erfand das Rad neu, ignorierte alles, aber auch wirklich alles, was es schon gab - auch wenn es sich sofort mit Friendica und Hubzilla verband -, und versucht seitdem allein durch seine zahlenmige Dominanz im Fediverse, allen anderen Projekten seinen Non-Standard-Bldsinn aufzuzwingen. Auch weil 99% der Mastodon-Nutzer zu wissen glauben, da Mastodon die Referenzimplementation von ActivityPub sei.
Ausserdem will ich es nicht nicht lesen, ich will nur wissen, ob ich jetzt oder spter draufklicke.
Genau das kann NSFW seit 2010. Genau dafr ist es da. Und genau das knnen seit letztem Jahr auch die Filter von Mastodon.
Hier auf Hubzilla geht NSFW so: Du hast im Prinzip nicht mehr als ein Textfeld, wo du Schlsselwrter und Hashtags eintragen kannst, die dich stren. Standardmig eingetragen sind "nsfw" und "contentwarning". Das ist alles, was es an Einstellungen gibt.
Standardmig ist es berhaupt nicht aktiviert bzw. "installiert", wie es hier heit. Standardmig wird also gar nichts gefiltert. NSFW ist hier auf Hubzilla eine "App", die erst auf deinem Kanal (= Account auf Mastodon) "installiert" werden mu. Aber dann ist es sofort scharfgeschaltet.
Wenn jetzt in einem Post "NSFW" oder "nsfw" steht, entdeckt NSFW das vollautomatisch. Dann versteckt es den kompletten Post hinter einem gelben Rechteck, auf dem "nsfw - ansehen" steht. Und zwar wirklich den ganzen Post inklusive Hashtags und sogar inklusive allen Bildern.
Wenn du das gelbe Rechteck klickst, siehst du den Post.
Oder sagen wir, du willst nichts ber deutsche Politik lesen. Dann gehst du zur NSFW-App und trgst in der Wortliste "depol" ein. Jeder Post, jeder Kommentar, jede DM mit "depol" oder "DEpol" oder "#depol" drin wird dann komplett hinter einem gelben Rechteck mit "depol - ansehen" verborgen.
Das heit, Hubzilla sagt dir sogar vollautomatisch, wovor es dich warnt. Natrlich nur, wenn es etwas Entsprechendes in einem Post oder Kommentar oder einer DM findet. Da ist es abhngig von der Kooperation derer, die die Posts, Kommentare und DMs schreiben. Dann aber definitiv.
Auf Friendica und (streams) ist es ziemlich genauso.
Der einzige wirkliche Nachteil ist, da NSFW so simpel ist, da es keine Worterkennung hat. Es springt also immer auf Wortbestandteile an. Das heit, wenn du "trump" in der Wortliste hast, springt NSFW auch auf "trumpet" und "Strumpf" an. Aber vielleicht kann ich da zumindest auf Hubzilla noch eine Verbesserung durchsetzen.
Aber ein Hashtag "#depol" unter einen Post zu setzen, ist ein geringerer Aufwand, als "CW: depol" ins Summary bzw. ins CW-Feld zu schreiben.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta #Friendica #Hubzilla #Streams #(streams) #NichtNurMastodonI've updated the in my Ruth2 and Roth2 wiki.
Some changes:
- Kaydi Rose Designs is a new entry.
- I've also added the fashion store I run at Nautilus Anchorage Landing in OSgrid it currently mostly serves as another Deva Moda backup store plus some hard-to-acquire additional Taarna Welles footwear. I've still got two floors to fill, though.
- The Great Canadian Grid is gone again, so the two shops there were removed.
- Astralia ShoppingCity lost the retextured Clutterfly and Damien Fate content, so the shops there were removed, too.
- Birch Grove is now Birch Grove Winter and currently inaccessible. I've changed one shop that's at all four Birch Groves to Birch Grove Spring and suspended the other two. That said, Jamie Wright/Anna Cooper has a new sim in the making which will permanently offer stuff from at least one of these shops.
- Shopaholic was torn down and completely rebuilt quite a while ago. Sabi no longer offers her textured Damien Fate clothes. Thus, Shopaholic was removed.
- The Public World went offline by the turn of the year with no announcement. I'll keep Loru Destiny's shop at the TPW-Mall suspended until things clear up.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #RuthAndRoth #Ruth2 #VirtualClothing #VirtualFashion
You say some interesting things. As if the account and the microblogging stream originating from the account are separate entities.
They are.
The channel is a container which contains your Fediverse identity with everything attached to it. Posts, connections, settings, files and such.
The account is only there for you to be able to log onto a server on which your channel resides and access your channel.
I see. That's a revolution.
That "revolution" is from 2012 when Mike Macgirvin took his own Friendica, forked it into Friendica Red and then re-wrote the whole thing against his new Zot protocol to support nomadic identity, thus creating Red, later known as the Red Matrix.
Hubzilla itself was renamed from the Red Matrix in 2015.
For comparison: Mastodon is from 2016, exactly ten months after the Red Matrix was renamed Hubzilla.
The Fediverse has had channels and nomadic identity in daily, productive, stable use for longer than Mastodon has been around.
Does that make the concept of sub-accounts unnecessary
Yes. Also because nobody can tell which channels are on which account (except the admin who has to dive into the SQL database to figure that out). So you can have lots of secret identities.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NomadicIdentity Long It goes far beyond what Mastodon can do.
Moving means moving everything. Literally absolutely everything. Or at least everything that isn't firmly tied to one specific instance such as login credentials.
Let's suppose you want to move from your own instance, kotaro.me, to fosstodon.org.
First, nomadic identity will copy everything over. All your posts, all your images, all your files, all your settings, all your filters, all your lists, all your mutes and blocks, even all your contacts, both followers and followed and mutuals (Hubzilla and (streams) don't distinguish between these because mutuals are the default).
Then it will re-write your entry on all your followers' followed lists from kotarokotaro.me to kotarofosstodon.org. Or at least it would if Mastodon was like Hubzilla or (streams) and understood nomadic identity. All your followers will automagically follow you in your new place.
Finally, it will wipe out your old stuff on kotaro.me. You won't leave a dead account behind.
Mind blown yet Because nomadic identity can do even wilder stuff. Namely clone.
Roughly translated from Hubzilla/(streams) to Mastodon, you could create an absolutely identical clone of your account on Fosstodon. Not only a dumb copy like what Mastodon can do now. A clone that will always stay identical.
Nomadic identity syncs your main and your clone with each other, bidirectionally, in near-real-time. Like a live backup of your Fediverse identity. One that'll never have to be restored because you can use the backup like you can use the original.
You post something on your main, the post is sync'd to your clone. You receive a post on your main, that post is sync'd to your clone. You change a setting on your main, that change is sync'd to your clone. You create a filter on your clone, that filter is sync'd back to your main. Fully automatically.
Your instance server crashes beyond repair Your home instance is dead Doesn't matter. You can carry on with your clone as if nothing had happened because the clone is always identical to the main and the other clones if you have some. You can declare your clone your new main and make one or more new clones.
Okay, on Hubzilla and (streams), matters are a wee bit more complicated. Your account is not your identity, and your stuff is not stored in your account. Instead, there are . Your posts, your files, your everything is stored in such a channel, and that channel is your identity. You only need an account to log onto a server and access your channel. A channel is basically an identity container.
You can have as many channels as you want on one account, nobody can tell that all these channels belong to the same account, and each one of your channels can reside simultaneously on as many instances as you want.
At the end of the day, however, channels make nomadic identity easier. Nomadic identity doesn't have to pry apart what can be cloned and what's firmly tied to this one instance. On Hubzilla and (streams), nomadic identity can simply move or clone a channel as a whole.
It also makes moving cleaner. At the end of a move, the copy of the channel on the old instance is easily deleted. And if there isn't any other channel on the account, the account is deleted, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NomadicIdentityShopping City in Astralia has lost almost all its appeal now.
Cloe Kegel has ripped out the last remaining shops that offered legal mesh clothes and replaced them with more outlets for stolen SL clothes for stolen SL bodies. For some of the items in these shops, Shopping City was the very last place all over the Hypergrid where you could get them. Now they're gone. No longer available anywhere.
Some two dozen tank top and miniskirt sets textured by Illiana Blachere and based on Damien Fate meshes, gone. Another Damien Fate-based set by Avia Bonne with an exclusive handbag which, I think, Avia has made herself, gone. And so forth. At least Oddball Otoole's Damien Fate texturings are still available at Riverford in Craft-World.
But Shopping City has lost the best reason to go there.
Maybe, just maybe I can get into contact with Cloe or the former owner of La Tortuga and ask them if they've still got the sales boxes, and if I can have them to keep the content alive. It'll certainly be more difficult and require more luck than my successful rescue of the Deva Moda clothes and make-up, and I'll have permissions to fix.
If that fails, I guess Juno Rowland and I will have some god-moding, permission-fixing and repackaging to do. Unfortunately, there are some items of which I don't know who made the textures because Cloe probably accidentally overwrote all credentials at some point in the past.
It's such a pity that so many who offer custom-textured Clutterfly or Damien Fate clothes or even obscure old layer clothes are or were sloppy, careless shopkeeps who never check what they slap against their shop walls, much less repair what's broken. Otherwise I'd be in possession of many many more sales boxes.
Sometimes, the only way to save content that's becoming increasingly rare is actually by copybotting it out-right because the items or sales boxes have botched rights, they can't be picked up in any "legal" way, and the shop owner can't be bothered to fix them. I'm almost tempted to take a copybot viewer to Sinus and save the Damien Fate stuff from Eva Kraai's shop because Eva flat-out refuses to fix her old content as she told me herself.
This wouldn't be so bad if the Ruth2 and Roth2 families didn't have to rely on Clutterfly and especially Damien Fate for legal mesh clothes. Chances are that the Max family will eventually get brand-new mesh clothes rigged just for these bodies, but Ruth2 and Roth2 with their unusable dev kits will probably rely on that slowly vanishing old stuff for good, even though Damien Fate makes Ruth2 v4 look pudgy and Roth2 v2 look thin as a twig.
#Long #LongPost #CWLong #CWLongPost #Astralia #DamienFate #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #VirtualClothing #VirtualFashion
The of the week is LENT/LONG/LENGTH
I'm sure this won't be the case as AI matures.
And I'm very certain that AI won't be able to perfectly cover every last niche topic out there at the Fediverse's staggeringly high quality standards.
No, It won't. I should know because the primary topic of this Hubzilla channel of mine is about an extreme niche, namely a certain, very obscure kind of 3-D virtual worlds.
I rarely post pictures, but I sometimes do. I always write my image descriptions myself. And as this topic is so obscure that a whole lot of explanation is required for a casual audience that comes across my image posts on their federated Mastodon timelines to understand my posts and my pictures. One of the reasons why I write the longest image descriptions in the whole Fediverse.
An AI would require massive amounts of knowledge from partly tiniest niches from all over the world to give similarly detailed, accurate, informative explanations.
I also have to describe a whole lot. I mean, what do blind or visually-impaired people know what a virtual world they've never heard of looks like What anything in such a world looks like Maybe they're curious to know nonetheless. And they have a right to know.
An AI may recognise that the picture is from a virtual world, but it's unaware of the implications. It can't tell by looking at an image that the virtual world shown in the image is extremely obscure, that the audience that'll come across this image is mostly casual and clueless, and that therefore a very detailed description is necessary.
Also, AI can only see what's in the picture. But when I describe a picture from a virtual world, I don't describe it by looking at the picture. I describe it by looking at the real thing, standing in that world, looking around in that world with a nigh-infinite, lossless zoom factor readily at hand, able to move the camera or my avatar to wherever necessary in order to examine details. AI can't do that.
Lastly, there's a rule that says that any and all text within the borders of an image must be transcribed, full stop. There is no rule, however, on whether this applies to text that's so small that it's illegible, to text that's so tiny that it's practically invisible at the image's resolution or to text that's partly obscured by something that's standing in front of it.
Using the above method, I can transcribe just about all text in-world, even text in a picture in that picture when the former picture is takes up only 100 pixels or so. And I've done so. AI will never be able to do that.
By the way, some two weeks ago, I've actually pitted an image-describing AI against my own image describing with my most recent picture as the test object. The AI came up with 558 characters of visual description, but with no explanations, with no mention where the picture was made and even with some factual errors. My description of the same image clocked in at 25,271 characters, and this is guaranteed to not be a typo.
which includes both descriptions at full length, so it's a whole lot to read. Right below as a comment, where I dissect the AI description, pointing out where the AI was vague or out-right wrong and where it simply didn't provide vital information.
Do you really, honestly, unironically believe that it won't be long until AI can do absolutely everything I can do at the same level, if not even better
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AIScott M. Stolz
I am not sure if Solid has the concept of clones or syncing,
As far as I can see, it doesn't. It works wholly differently from nomadic identity.
Currently, Hubzilla hubs are like clients with full data storage that sync their data peer-to-peer.
Now imagine Hubzilla hubs being thin clients with no data storage whatsoever. Next to these hubs, there's another kind of server where your data is stored. Let's call it data server. It's fully independent from the hubs where you have your channel.
You can have as many instances of your identity on as many thin client hubs as you like. One goes down, doesn't matter, you've got more. But all your data is stored on one data server. With one account. One. Every last one of your channel clones on all those thin client hubs is connected to this one data storage.
You may be able to choose where to park your data. But you can only choose exactly one data server where you want to park your data for all your channel clones. You can not clone or mirror your data storage. You've only ever got one instance of that.
If that server goes bellies-up, have fun starting over from scratch. If you're lucky, you may have a backup. If you don't have an up-to-date backup because you haven't made one in a while, or you've never made one in the first place, well, then you're fucked.
It'll be even more fun if Solid won't let you make backups of your data in the first place.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Zot #Zot6 #Nomad #Hubzilla #Streams #(streams) #Solidphanisvara (streams)
wollen es allen recht machen, auch den sehr empfindlichen, nehme ich an.
Richtig. Und wenn man sich mal auf Mastodon umguckt, und ich meine auf Mastodon direkt und nicht in dem, was einem von Mastodon auf den eigenen Channel Stream gesplt wird, dann sieht man jede Menge Schneeflocken, die fordern, da alle CWs setzen fr $THEMA, weil $THEMA sie irgendwie strt.
Ungelogen: Es gibt Leute, die wollen CWs fr Katzenbilder, weil ihnen die ganzen Katzenbilder auf den Keks gehen.
Ich glaube, es gibt auch Mastodon-Instanzen, die ganze andere Instanzen blocken, weil die nicht in ihren Regeln CWs fr bestimmte Themen zwingend fordern. Egal, ob das jetzt eine Mastodon-Instanz ist oder ein Hubzilla-Hub, wo es berhaupt kein Feld namens "CW" gibt und auch nirgendwo dokumentiert ist, da Hubzillas Summary Mastodons CW ist. Mal ganz davon abgesehen, da CWs im Summary in Hubzillas Kultur nicht vorkommen, weil Hubzilla so einen Kasperkram gar nicht braucht, weil es fr Empfindliche die schne NSFW-App hat.
halte ich aber fr keinen praktikablen oder vernnftigen ansatz.
Ich auch nicht. Aber so macht man das eben auf Mastodon, und so hat das geflligst das ganze Fediverse zu machen.
macht viel mehr sinn, wenn sich jede(r) seine eigenen filter zusammenstellen kann, wie bei hubzilla / streams. erfordert ein wenig mehr sachkenntnis, aber funktioniert halt.
Filter sind aber "nicht Mastodon-mig". Filter, die automatisch CWs generieren, schon mal erst recht nicht, zumal es die erst seit letztem Jahr gibt.
Auf Mastodon hat man CWs im Summary, ohne zu wissen, da das eigentlich das Summary ist und eben nicht von Rochko fr CWs komplett neu erfunden wurde. Und, bitte, das gesamte brige Fediverse hat sich auch geflligst daran zu halten. Zumal diejenigen, die glauben, Rochko htte das Fediverse erfunden, wahrscheinlich die groe Mehrheit stellen.
Ich bin schon Leuten begegnet, die ganz unironisch das Fehlen eines so beschrifteten CW-Feldes auf Friendica, Hubzilla und (streams) als Bug ansahen und sagten: "Aber das kann man doch leicht beheben, oder"
Die meisten Mastodon-Nutzer kratzen ja eh nur an der Oberflche, entweder der Web-Oberflche oder, noch viel hufiger, der ihrer Smartphone-App. Viele wissen gar nicht, da Mastodon Filter hat, geschweige denn, wie man sie benutzt. Ungelogen: Vor ein paar Wochen habe ich als Hubzilla-Nutzer einem Mastodon-Nutzer Schritt fr Schritt erklrt, wie man auf der Weboberflche Filter einrichtet. Also, wirklich jeden Schritt einzeln. Und der war schon lnger dabei und nutzte standardmig die Weboberflche.
Selbst von denen, die schon deutlich ber ein Jahr dabei sind, wissen die allerwenigsten, da Mastodon jetzt auch CWs per Filter automatisch generieren kann. Wahrscheinlich sehen viele von denen das auch als unntzes Gimmick an, wo Mastodon doch schon das schne CW-Feld hat, das ja sowieso der Mastodon-Standard ist und der universelle Fediverse-Standard sein sollte.
Fr erfahrene Friendica-, Hubzilla- oder (streams)-Nutzer ist es das Natrlichste der Welt, die optionale NSFW-App zu haben, die vollautomatisch individuelle CWs generiert und dafr von denen, die Posts oder Kommentare schreiben, eigentlich nur verlangt, da sie entsprechende Schlsselwrter in ihre Posts oder Kommentare einbauen.
Fr typische Mastodon-Nutzer ist das aber komplett befremdlich, wenn nicht gnzlich unbekannt. Also wollen sie das gar nicht, zumal sie Mastodon sowieso als den alleinigen Goldstandard im Fediverse ansehen. Sie glauben ja auch, Mastodon ist deswegen am grten, weil es unterm Strich am besten ist.
Dazu kommt aber noch was: Mastodon-Nutzer sind es gewohnt, verhtschelt zu werden. Blo keine Eigeninitiative ergreifen fr irgendwas. Egal, was ist, irgendjemand anders soll sich drum kmmern. Wenn sie selbst sich an irgendwelchen Inhalten stren, sollen die 14 Millionen anderen Fediverse-Nutzer sie bitteschn davor warnen.
So, und dann kommen die, die sich an den vielen fr sie unntigen CWs stren und dagegen das Wort erheben.
Da fragt man sich doch: Warum setzen sich da nicht mal welche virtuell zusammen und diskutieren darber Ganz einfach: weil man auf Mastodon nicht diskutieren kann. Aufgrund technischer Design-Entscheidungen.
Mastodon hat keine Gruppen, weil Twitter keine hat. Mastodon kennt auch keine Gruppen, weil es eben keine hat, und was der Rest des Fediverse hat, wird von Mastodon geflissentlich ignoriert. Und Mastodon kennt auch das Konzept von Konversationen nicht, weil es auch die auf Twitter nicht gibt.
Fr uns auf Friendica, Hubzilla und (streams) ist es das Normalste der Welt, nicht nur Gruppen und Foren zu haben, sondern auch, da, wenn man einen Post im Stream hat, man dann automatisch auch smtliche Kommentare bekommt. Und man kann ganzen Threads sogar folgen. So sollte es sein.
So ist es aber auf Twitter nicht, also ist es so auch auf Mastodon nicht. Da gibt's keine Konversationen. Wenn du da irgendwas mit mehreren Leuten diskutieren willst, dann mu jedes Mal jeder in der Diskussion alle anderen einzeln erwhnen. Ansonsten werden die nmlich ber neue Diskussionsbeitrge nicht benachrichtigt.
Deswegen blken auf Mastodon alle ziellos in die Menge und werden nur von ihren eigenen Followers gehrt, sofern sie nicht gezielt irgendjemanden erwhnen. Und so blken auch alle aneinander vorbei. Und jeder kann die uneingeschrnkte Durchsetzung der eigenen Maximalforderungen einfordern, ohne davon zu lesen, da die eigenen Maximalforderungen eventuell mit den Wnschen anderer Nutzer kollidieren.
Vielleicht gibt es ein paar wenige, die es gern htten, wenn Mastodon mehr wie z. B. Friendica wre. Aber es gibt um Grenordnungen mehr, die wollen, da Mastodon und das ganze Fediverse mehr werden wie Twitter unmittelbar vor der bernahme durch Musk, weil das fr sie persnlich bequemer wre.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta
Theres no discussion that the Fediverse goes beyond Mastodon and ActivityPub, youre 100% correct to remind this.
In general, when Mastodon users learn that the Fediverse is more than just Mastodon, they don't fight it because that'd be senseless. They're okay with there being something else than Mastodon in the Fediverse as long as this something else plays by Mastodon's unwritten rules, and it doesn't disturb Mastodon users. This something else is highly likely to break Mastodon's unwritten rules, either due to its own cultures being different from Mastodon's or due to design choices or both, but even then, I guess most rather resort to blocking individual rule-breaking users.
There are a few who don't accept something else being connected to Mastodon, and who want the Fediverse to be only Mastodon. But they aren't vocal.
With ActivityPub, the case is different. Those who want the Fediverse to be only ActivityPub-based projects are vocal. And what they actually want is the Fediverse to stay only ActivityPub-based projects. Which implies that they think this the Fediverse currently is only ActivityPub-based projects. Which, in turn, means they know neither Hubzilla nor (streams).
If you tell them that there are also Hubzilla and (streams), they're okay with that. That's because they think that Hubzilla and (streams) are and have always been based on ActivityPub themselves. Because, like, everything in the Fediverse has always been based on ActivityPub, right Can't be any different, right
But then you tell them that Hubzilla is based on a protocol called Zot6. And (streams) is based on a successor of Zot named Nomad. And in both cases, ActivityPub is implemented via a bridge plug-in named PubCrawl. PubCrawl is an official add-on, so it isn't third-party, and there is one of these bridges per channel and not one for all instances. But still, both Hubzilla and (streams) are not based on ActivityPub, and they're both bridged to Mastodon. Oh, and Hubzilla has been both in the Fediverse and using ActivityPub before Mastodon.
Then they have two options. They can accept Hubzilla and (streams) because they're free, open-source and non-commercial and reduce their anti-bridge stance to an anti-third-party-bridge-to-commercial-platforms stance which more reasonable Mastodon users already have, and which they express when you tell them that Hubzilla and (streams) are bridged, too.
Or they can stand their case and demand the full defederation of both Hubzilla and (streams). I've never seen anyone do that, but I guess that's because these people really don't know Hubzilla and (streams). Until I write to them, they've never come across a single post from either of these. But I guess if they're frequently enough exposed to posts from Hubzilla or (streams) that break Mastodon's unwritten rules, and if they can draw a line between the rules being broken and the users in question being on Hubzilla or (streams), that could trigger them to demanding full defederation.
What I meant was that as the largest platform on the Fediverse, what happens on Mastodon sets the tone for the Fediverse more broadly, at least partially. This is that worried me, as there is this vocal, and toxic, minority on Mastodon that has very few limits.
In this regard, it's hard to be safe anywhere in the Fediverse.
Once you move elsewhere, be it Akkoma or Iceshrimp or something, you start using your new home project as you're supposed to use it. You start making use of features that aren't available on Mastodon, just like Mastodon users started making use of features that aren't available on . It's only natural.
But in doing so, you break Mastodon's unwritten rules, and you trigger Mastodon's Fediverse purity police into going ballistic. Posting over 500 characters at once is bad enough already. Text formatting is even worse. Quote-posts are generally associated with harassment, so they're just about the worst crime you can possibly commit in the Fediverse, along with quotes because the Mastodon purists can't see the difference between these two.
Never mind that pretty much everything outside of Mastodon supports all of this. I think even the 2SLGBTQIA+ community on Sharkey gleefully makes use of all of this, quote-posts included, the same people who, according to the Mastodon purists, should be against quote-posts the most fiercely because quote-tweets were used to harass them on .
However, if the general, non-Fediverse public becomes aware of the "Make the Fediverse only Mastodon again" purists, they'll automatically make fools out of themselves. A demand to make the Fediverse only Mastodon again implies something which both mass media and tech media currently prefer to ignore for simplicity's sake, namely that there is actually more to the Fediverse than Mastodon.
If media took the time and effort to dig deeper in this case, they'll be told that a) this is normal, b) this is by design, c) this is the very concept of the Fediverse, and d) some Fediverse projects have actually been there before Mastodon. So the Fediverse has actually never been only Mastodon which renders "Make the Fediverse only Mastodon again" delirious rubbish.
"Make the Fediverse only Mastodon" wouldn't look much more sensible in this light either. Why would everything that isn't Mastodon have to be excluded from the same Fediverse that was founded by parts of this very same everything Because it doesn't play by rules that aren't written down anywhere Because it's different By design even
This would be the very revelation that there's intolerance and "digital racism" in the Fediverse, not to mention attempted colonialism.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fediverse
I'm sure there would be AI that can do it for you etc.
There already is, but it's far from perfect, no matter who says otherwise.
And if legal accessibility requirements include minimum standards for image descriptions, namely that they have to be correct and at a certain minimum level of accuracy, then not only putting non-sense into the alt-text is out, but so is AI.
Sure, when it comes to describing casual images like cat pictures, AI is usually as good as humans. But when it comes to special interest images, AI would have to be absolutely as good as the very best actual or imaginable experts in the field, if not even better, no matter how niche the topic is. It would even have to learn about all new developments immediately so that it could describe them correctly and accurately right off the bat.
All LLM AIs out there that can be tasked with describing images would have to be absolutely omniscient. I think it's clear that this will never happen.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AIMike Macgirvin
When Mastodon came along, they completely ignored all the existing fediverse conventions, and yet you'll get blocked and muted and never hear the end of it if you ignore theirs.
This. Plus millions of Mastodon users who think that Eugen Rochko created both the Fediverse and ActivityPub, and therefore, Mastodon is the reference implementation of ActivityPub.
And some of them have created and still maintain popular mobile apps for Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
Is there any plan to run an episode, or even several, on some of the issues that are documented within the Fediverse In particular, the racism that pushed many Black users out of the platform, the reply guy problem (Im considering stopping publishing on Mastodon because of that), or the many moral panics targeted at projects a vocal, but toxic, minority doesnt understand
These aren't necessary problems of the whole Fediverse. Mastodon maybe, but not the whole Fediverse. Just because Mastodon's self-moderation capabilities are limited to mute and block, doesn't mean this goes for all the other Fediverse projects just the same.
Just to give you one example: Here on , I've got 17 general interaction permission settings, each with multiple values to choose from. I could even limit who is allowed to reply to my posts to:
- everyone, authenticated or not
- everyone who is authenticated (this is the default)
- all Hubzilla users, but nobody on any other connected platform/project (Diaspora*, Mastodon, the rest of the Fediverse etc.)
- everyone on the same hub as the main instance of my channel (hub.netzgemeinde.eu)
- all my connections, accepted by me or not
- only my accepted connections
- only users whom I explicitly grant that permission
- only myself
The other 16 settings have at least the last seven of these options, sometimes all eight.
And that's only Hubzilla and only a part of it. goes even further than that. If you want a safe haven social network, and you don't absolutely have to be mollycoddled with maximum ease-of-use, then (streams) could be your safe haven. And yes, (streams) is part of the Fediverse and federated with Mastodon if you want to stay in contact with your old acquaintances.
In general, if you're discontent with both and Mastodon, the remaining alternatives aren't only Threads and Bluesky. The Fediverse is not only Mastodon, and the non-Mastodon Fediverse is not just simply Mastodon with more characters and a different UI. There are places in the Fediverse that can do things beyond most Mastodon users' imagination.
About the Mastodon users who completely flipped their shit upon the Bridgy Fed Bluesky bridge announcement, and every last one of them was on Mastodon: I've taken a closer look at their behaviour. They seemed fully convinced that they know everything about the Fediverse, but even some of those who had joined in November, 2022 apparently also thought that the Fediverse is only Mastodon, and none of them really knew how far the Fediverse actually stretches.
Proof: There was a lot of demanding the Fediverse be ActivityPub-only with no bridges to anywhere whatsoever. What these people actually meant was for the Fediverse to stay ActivityPub-only.
What they don't know, however: The Fediverse isn't ActivityPub-only right now. It wasn't at that point. And it has never been. Hubzilla runs on Zot6, and it's bridged to ActivityPub. (streams) runs on Nomad, and it's bridged to ActivityPub. Until recently, Friendica ran on DFRN, and it was bridged to ActivityPub. By that logic, all instances of all these three projects would have to be Fediblocked.
In fact, the Fediverse itself started long before ActivityPub. Friendica, the oldest current member of the Fediverse, dates back to 2010. The term "Fediverse" was first used in 2012. ActivityPub, on the other hand, became a W3C-appointed standard in 2018 and was first used in 2017. No, not by Mastodon. Hubzilla was faster by two months.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
do not usually when i am .
before i the and i'm looking at my 's .
The major problem with this, however, is that the worst offender is also two thirds of the whole Fediverse and perceived as the actual Fediverse standard. Just about everyone who joins the Fediverse now spends weeks, if not months, only exposed to Mastodon and thinking the Fediverse is only Mastodon. Some have joined in the second Twitter migration wave in November, 2022, but they still think the Fediverse is only Mastodon. For most of those who don't, the Fediverse is Mastodon and weird, alien non-Mastodon stuff, and only Mastodon counts as normal.
This actually goes as far as Mastodon users thinking that whenever something is different from Mastodon on another project, that's a bug that should be fixed. And I'm talking about things like Friendica not having Mastodon's alt-text field. That's something that doesn't disrupt communication, and it's independent from the ActivityPub standard. But if actual communication fails because one side strictly adheres to the ActivityPub spec, and the other side is Mastodon, a majority of Fediverse users will believe it's the non-Mastodon side that's broken.
It doesn't help that all kinds of news outlets simplify the Fediverse down to "Mastodon and stuff that doesn't matter" or even actually only Mastodon while stating that Mastodon is built against ActivityPub and thus implying it's cleanly built against ActivityPub.
Thus, playing by the official rulebook only and ignoring Mastodon's non-standard quirks is playing with high stakes.
It could work out, though. The "strictly ActivityPub" side just needs more projects to join. More server apps to make themselves independent from Mastodon by going the pure ActivityPub way. Even clients that exchange the Mastodon API for actual ActivityPub.
It probably wouldn't be that much work for Friendica and Hubzilla. I can also see *key developers turn their backs on Mastodon if they perceive it as toxic and show it by joining the "strictly ActivityPub" side. The best case would be if Iceshrimp or even Misskey itself did that because they'd drag a whole number of soft forks along.
If only (streams) goes pure ActivityPub while everything else sticks to "but muh Mastodon compatibility", (streams) will be seen as broken by design, even if someone filed a bug on Mastodon's GitHub repository because of some incompatibility with (streams), even if that bug report includes proof that it's Mastodon that goes against the ActivityPub standard while (streams) sticks to it.
But if someone filed a bug on Mastodon's GitHub repository because Mastodon ignoring the ActivityPub standard can be proven to break compatibility with 15 different server applications, at least five of which aren't "never heard of that" material but actually well-known, and a bunch of popular iPhone and Android apps on top, all of which chose to stick to ActivityPub only, it's obvious that it's Mastodon that's broken.
In this regard, the thought of the Fediverse splitting in two becomes kind of interesting. One side is fed up with Mastodon's antics and sticks to the W3C spec, even if it breaks compatibility with Mastodon. The other side is Mastodon which has just lost control over one third of the free, non-commercial Fediverse, and which is left with Threads as its only playmate.
Unfortunately, Threads is not being built against the W3C ActivityPub standard, but only against Mastodon which makes breakage with everything that isn't Mastodon highly likely already now. It'd be fun if Meta had decided to go by the ActivityPub spec only and then openly declared that Mastodon is faulty because of how utterly incompatible it is to something that follows the spec to a tee.
On the other hand, the breakage might keep Threads at a distance from the non-Mastodon Fediverse and more so from the "strictly ActivityPub" Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub It most likely won't. I guess it'd be "un-Mastodon-like".
My advice to Mastodon users who crave certain features that Mastodon doesn't have, but that are readily available elsewhere in the Fediverse is: Don't sit and wait until your Mastodon instance introduces that feature. If you want it, go where you can have it.
I've written a very long post on this topic almost a year ago.
Might open in Mastodon:
Original:
If you really want to be able to quote, it isn't worth waiting for quotes to be implemented on Mastodon. Try Iceshrimp or Sharkey instead the latter even lets you import your post backlog from Mastodon AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta It's called a quote. Standard feature on Friendica, Hubzilla (where I am), (streams), the now-deceased rest of the family, Misskey and all its forks etc., basically everywhere that isn't Mastodon.
Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
quoteif the process is really that involved and if they can fix it/quote(streams) also has ways of doing that with Markdown or HTML.
There are various different ways of getting that code, also depending on whether one replies to a post or a comment.
ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.
Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText If you mean an update that makes Friendica handle 100% like Mastodon to make things easier for Mastodon converts, then no. That'd sacrifice image embedding.
Essentially, Friendica would need an alt-text field for Mastodon-style file attachment images, and it'd need an even more advanced WYSIWYG post editor which includes some kind of alt-text field for each embedded image.
Also, AFAIK, there are no dedicated mobile apps for Friendica, and Friendica doesn't support the Mastodon API due to both being so vastly different from Mastodon in its architecture and six years older than Mastodon. What few general Fediverse apps work with Friendica only work barely so and don't even support a tiny fraction of what Friendica can do. Friendica is typically used in a standard Web browser.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #AltText It does support alt-text, technically speaking. It just doesn't have Mastodon's easy-peasy alt-text entry field. And I think if you want to have alt-text on Friendica, you must not handle images the Mastodon way by uploading them to a post draft as file attachments, but you must upload them to your file storage and then embed them, blog-style.
Once you have the image embedding code in your post draft, you must manually graft the alt-text into that code. I'd walk you through it step by step if I could, but I don't know how exactly the code in Friendica looks like.
I can tell you what it looks like and how it works on Hubzilla, though, and since Hubzilla is Friendica's descendant, it should be similar, only that Friendica probably still uses
url=/url and img=/img instead of zrl=/zrl and zmg=/zmg.So when you embed an image into a post on Hubzilla, the code looks like this:
zrl=URL of image viewing page in your file storagezmg=WidthxHeightURL of Image file/zmg/zrlThe first thing you do is cut the image file URL and paste it over the image size in the
zmg= tag. The image size is usually quite unnecessary, and it degrades the quality of the image.zrl=URL of image viewing page in your file storagezmg=WidthxHeightURL of Image file/zmg/zrl
zrl=URL of image viewing page in your file storagezmg=URL of Image file/zmg/zrlzmg= and /zmg.zrl=URL of image viewing page in your file storagezmg=URL of Image fileAlt-text/zmg/zrlOn Hubzilla, this works absolutely well. I've done it myself countless times already.
I think Friendica works largely the same, only that it uses
url=/url instead of zrl=/zrl and img=/img instead of zmg=/zmg.#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #AltTextImplementing encryption in ActivityPub would require a way to find out which instance or which actor supports which ways of encryption, if any.
Encryption would break compatibility more than nomadic identity ever could. If one project implements mandatory, no-opt-out encryption, and another project doesn't implement it at all, then actors using the second project won't be able to communicate with those using the first project.
And there will be projects that won't implement encryption as well as projects that won't even implement nomadic identity. Not exactly few Fediverse projects are highly opinionated what their creators don't like and/or don't find useful enough and/or think makes things too complicated won't be implemented. Sadly, Mastodon is one of the worst, also because it shows this "we don't implement what we haven't invented ourselves" mindset, and because it can afford becoming incompatible with the rest of the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NomadicIdentity Looks like many mobile apps for Mastodon were made by people who were new to Mastodon, totally giddy about it, eager to improve the mobile experience, but at the same time clueless. They didn't distinguish much between ActivityPub and the Mastodon API, and at that point, they didn't even know that the Fediverse is more than just Mastodon.
That's also why there are apps that technically support everything that uses the Mastodon API, but that don't have any features beyond vanilla Mastodon 3.x and don't even support over 500 characters.
At the same time, I think, there isn't a single app purely built against the ActivityPub standard and for the Fediverse in general. It simply wouldn't be compatible with Mastodon. Even supporting the full ActivityPub standard next to the Mastodon API seems unattractive.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #MastodonThe recent statistics:
OpenSim area continues growth streak
The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records. There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the View article View summary OpenSim area continues growth streak
The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records.
There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the total number of registered users went up by more than 1,338. The number of active users fell, however, by over 2,100, partly due to grid outages. , for example, which reported over 400 active users last month, was down this month. And two other grids that reported drops of more than 500 active each may have had database issues, including and .
Im now tracking a total of 2,654 public grids, of which 308 were active, and 244 published their statistics this month. If you have a stats page that were not tracking, please email me at that way, your grid will be mentioned in this report every month, for additional visibility with both search engines and users.
Also, Im no longer sending out a monthly email blast reminding OpenSim grid owners to send me news and updates for this report. If you have news, please email me before the tenth of the month if you want a short item included in this monthly wrap-up. For longer news, feel free to send me press releases at any time.
OpenSim land area for March 2024. (Hypergrid Business Data.).
Our stats do not include many of the grids running on which is a distribution of OpenSim since these tend to be private grids.
OpenSim is a free open-source, virtual world platform, thats similar to Second Life and allows people with no technical skills to quickly and cheaply create virtual worlds and teleport to other virtual worlds. Those with technical skills can run OpenSim worlds on their servers for free using either DreamGrid, for those who are more technically inclined, or any other distribution, while commercial hosting starts at less than $5 a region.
A list of . Download the and find out .
Hypergrid Business newsletter is now available
Every month on the 15th right after the stats report comes out we will be sending out a newsletter with all the OpenSim news from the previous month. You can or fill out the form below.
Please leave this field empty
Get our monthly stats and all other OpenSim news delivered right to your mailbox every month.
Email Address *
We dont spam! Read our for more info.
Check your inbox or spam folder to confirm your subscription.
Top 25 grids by active users
When it comes to general-purpose social grids, especially closed grids, the rule of thumb is the busier the better. People looking to make new friends look for grids that already have the most users. Merchants looking to sell content will go to the grids with the most potential customers. Event organizers looking for the biggest audience you get the idea.
Top 25 most popular grids this month:
- : 5,276 active users
- : 5,271 active users
- : 2,221 active users
- : 2,138 active users
- : 1,971 active users
- : 1,342 active users
- : 1,196 active users
- : 1,111 active users
- : 1,000 active users
- : 989 active users
- : 972 active users
- : 879 active users
- : 864 active users
- : 848 active users
- : 750 active users
- : 678 active users
- : 658 active users
- : 650 active users
- : 632 active users
- : 618 active users
- : 553 active users
- : 553 active users
- : 550 active users
- : 518 active users
- : 511 active users
Top 40 grids by land area
All region counts on this list are, whenever available, in terms of standard region equivalents. Active user counts include hypergrid visitors whenever possible.
Many school, company, or personal grids do not publish their numbers.
. . And here is a and their hypergrid addresses, sorted by popularity. This is very useful if you are creating a hyperport.
You can see all the , including polls and surveys, dating all the way back to 2009.
- : 28,496 regions
- : 27,145 regions
- : 18,216 regions
- : 11,687 regions
- : 9,995 regions
- : 7,896 regions
- : 5,094 regions
- : 3,543 regions
- : 1,579 regions
- : 1,464 regions
- : 1,072 regions
- : 952 regions
- : 916 regions
- : 872 regions
- : 854 regions
- : 816 regions
- : 784 regions
- : 653 regions
- : 577 regions
- : 515 regions
- : 430 regions
- : 400 regions
- : 387 regions
- : 378 regions
- : 373 regions
- : 311 regions
- : 305 regions
- : 298 regions
- : 241 regions
- : 196 regions
- : 183 regions
- : 173 regions
- : 167 regions
- : 164 regions
- : 148 regions
- : 144 regions
- : 141 regions
- : 140 regions
- : 127 regions
- : 126 regions
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OpenSimStatistics #HypergridBusiness
New Brunswick long-term care unprepared for next generation of aging seniors
New Brunswick's seniors advocate says the province will need to rethink its long-term care offerings to respond to the needs of an increasingly diverse population.
-termCare 'Advocate
New Brunswick long-term care unprepared for next generation of aging seniors
New Brunswick's seniors advocate says the province will need to rethink its long-term care offerings to respond to the needs of an increasingly diverse population.
-termCare 'Advocate
New Brunswick long-term care unprepared for next generation of aging seniors
New Brunswick's seniors advocate says the province will need to rethink its long-term care offerings to respond to the needs of an increasingly diverse population.
-termCare 'Advocate
Bei sehr vielen Fediverse-Diensten (#mastodon, #misskey und Misskey-Forks = #forkey , #pleroma ,...) hat das Handle folgende Form:
<BENUTZERNAME><INSTANZ-URL>.Mein Handle z.B. fr meinen Mastodon-Account lautet:
hvetinariburningboard.netBei vielen anderen Fediversediensten, wie z.B. #hubzilla , #streams , #friendica etc. unterscheidet sich das Handle (und die Bezeichnung... hier meistens als "Kanal" bezeichnet) ein wenig. Es hat die Form:
<BENUTZERNAME><INSTANZ-URL>.Das ""am Anfang wird weggelassen.
Diese Tatsache ist wichtig und kann bei Nichtbeachtung zu Problemen fhren.
Mchte man bei Hubzilla (und Verwandten) nach einem Handle suchen oder einen Kontakt hinzufgen, der von anderen Diensten stammt, dann muss man das fhrende "" weglassen!
Mchte man bei einem anderen Fediverse-Dienst (z.B. Mastodon) nach einem Hubzilla-Nutzer (Hubzilla-Kanal) suchen oder diesem folgen, muss man das "" am Anfang ergnzen!
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost Der Pepe (Hubzilla) That, and the typical Fediverse experience nowadays is a) Mastodon while barely or not at all knowing anything else exists and b) on a phone through a dedicated app.
The average Fediverse user doesn't start by joining Hubzilla on a desktop or laptop computer. They're fed up with Twitter and what became of it. They're told about Mastodon and the Fediverse which is implied to them to be one and the same thing.
So they grab their phones, they "install Mastodon" (the official app they've never in their lives used any online platform through an app that doesn't have the same name as the platform), and they register an account. On mastodon.social.
For at least the first three months, the Fediverse to them is Mastodon. Vanilla Mastodon with no more features than what Mastodon 3.x had. They actually think 500 characters are a lot, and they cannot imagine for the lives of them that it's possible for posts with more posts to exist in the Fediverse. How could they possibly The Fediverse is only Mastodon, after all.
Needless to say that they're deeply shocked and disturbed once they come across a post that does anything they took for absolutely impossible in the Fediverse. It's usually 500 characters, regardless of whether they come from Glitch or Misskey or Hubzilla.
At this point, they've gotten used to the Fediverse not allowing for more than 500 characters, not having text formatting, not having quotes, not having quote-tweets etc. etc. and of course being Mastodon and only Mastodon. And then this happens.
Those who are still on the official app are the poorest saps. The official Mastodon app is mercilessly hard-coded against vanilla Mastodon only with absolute and staunch disregard of the existence of anything else in the Fediverse. It totally refuses to take the existence of both Mastodon forks and non-Mastodon projects into account because that'd mean that Mastodon acknowledges the existence of Fediverse projects that have features that Mastodon a) lacks and b) flat-out refuses to introduce. So those on the official app get all long posts slammed right into their faces in the shape of unshortened walls of text.
Granted, the official Web front-end isn't that much better. It does fold long posts in. But it only folds posts in if they're ca. 2,000 characters or longer, and then it folds them in to ca. 1,500 characters.
Still, long posts can upset Mastodon users regardless of front-end. They're something that these users didn't expect. Something they don't want. Something they say doesn't belong into Mastodon and therefore into the Fediverse. Something that must be abolished.
For some even something they're willing to fight against until it's gone from the Fediverse, until the Fediverse is again what they thought it was when they were new: only vanilla Mastodon with only vanilla Mastodon's capabilities.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #500Characters Because 2010/2011 was when this federation was established. And not 2012 or 2016 or 2024.
It doesn't matter if Diaspora* has introduced an official API years later. There was no API in 2010/2011. There was no technical documentation in 2010/2011. There was no interest in connecting to anything else in 2010/2011.
But there was Mistpark/Friendika, then still developed by Mike, that had federating with everything that could possibly be federated with as one of its primary goals. No matter the odds. Even including Twitter and Facebook.
In autumn 2010, shortly after the very first public alpha of Diaspora* had come out, there were no signs of things improving, no signs of there being a stable API anytime soon, if ever. Diaspora* gave the impression of only wanting to federate with itself. So trying to wait for an appropriate server-to-server API appeared to be futile, and Mike had to start working on that federation without an API.
And besides, while Diaspora* did evolve to a certain degree, Mistpark evolved more from March, 2010 to July, 2010 than Diaspora* did from May, 2010 to now. And I'm not even talking about what came after Mistpark/Friendika/Friendica, namely the Red Matrix, Hubzilla, Osada, Zap etc. and eventually (streams).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica I'm not talking about 2016.
Friendica, then named Friendika, introduced its federation with Diaspora* on March 19th, 2011 (see also ). This means that work on federating Friendika with Diaspora* had started as early as 2010 when the original four devs were still in charge.
If simply asking them had worked, all that hassle with reverse-engineering from source code and cracking encryption would have been unnecessary, and Friendika would have federated with Diaspora* in 2010 already.
And don't tell me that Mike Macgirvin didn't want to get into contact with the Diaspora* devs and intentionally do all the federation behind their backs. Mike has actually contributed to Diaspora*'s protocol, and unlike his attempted contributions to ActivityPub, they were even accepted AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica
Where did you read that diaspora* never cared about federation outside of diaspora*
Did Diaspora* ever do anything to facilitate federation for Friendica or Hubzilla or (streams)
Did it ever actively try to stop them
Did it at least officially acknowledge that these three are federated with it
Where did you read that connecting to diaspora* is like to drill in a computer!
It's my description of how difficult it was to federate Friendica with Diaspora*.
Back in the day, Diaspora* had no API and no documentation on its protocol. Diaspora* was all about only federating with itself. Still, Friendica wanted to federate with it because Friendica federated with everything, full stop.
The "drilling into a computer case with a diamond drill" represents the several months it took the Friendica devs to crack Diaspora*'s undocumented encryption.
The "soldering wires onto circuit boards" represents how the Friendica devs had to reverse-engineer Diaspora* by studying its source code because there was no technical documentation whatsoever, and how Friendica could only federate with Diaspora* by latching directly onto Diaspora*'s inner workings instead of making use of any interface because there was no interface to use whatsoever.
Ask Mike Macgirvin .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica In the long run, however, it's bad.
It'll lead to wide-spread segregation of not only single Mastodon users, but entire instances from users that regularly post over 500 characters and instances with such users.
To say that's inconvenient puts it mildly, seeing as the secondary topic of my Hubzilla channel is the Fediverse in general and educating Mastodon users about the Fediverse outside of Mastodon in particular. If these very same Mastodon users can't read my posts anymore because someone else on their instance has talked their instance admin into blocking either my channel or the entirety of hub.netzgemeinde.eu, calling it inconvenient is an understatement.
It also makes explaining that "the Metaverse" is neither Zuckerberg's invention nor dependent on blockchains, cryptocurrencies and NFTs, and that decentralised 3-D virtual worlds have been around for over a decade and a half, much more difficult. And that's the primary topic of this channel.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaphanisvara (streams) Yes, but many Mastodon users can't stand to see posts with over 500 characters. Not only do they refuse to read "long" posts, but some actually block anyone who exceeds 500 characters in a post even only once.
I'm pretty sure some ask their Mastodon instance admins to deal with such people. Have them blocked instance-wide. Have their whole Hubzilla hub blocked on that Mastodon instance.
Or they try to use Mastodon's report feature to report that Hubzilla user to the admin of that Hubzilla hub, or they have their admin try and get into contact with the admin of that Hubzilla hub, just to have that Hubzilla user sanctioned for breaking some unwritten Mastodon etiquette by posting over 500 characters in one chunk.
Of course, they fail in both cases. Hubzilla doesn't support Mastodon's report feature, and mentioning Hubzilla users, in this case the admin, in a public post won't work either. Verdict: That Hubzilla hub is unmoderated and therefore has to be blocked or even out-right Fediblocked.
On the grounds of the assumption that Hubzilla works exactly like Mastodon. Which I'm trying to debunk with this series of posts.
As at least one of my polls has revealed, there seems to be a not insignificant number of Mastodon users who demand posts with over 500 characters be banned absolutely everywhere in the Fediverse. Including in conversation between users on other projects, regardless of whether overly long posts from that conversation might leak into Mastodon or not.
And, of course, there's the Mastodon police that try to urge non-Mastodon users to limit their posts to a maximum of 500 characters, regardless of whether they're aware that the user in question is on something else than Mastodon or not. They're fully convinced that Mastodon was here first, and all the other projects are intruders in Mastodon's Fediverse and have to follow Mastodon's rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterCount #CharacterLimit #CharacterLimits #500Characters #Mastodon
It would be best for such a thing to exist within ActivityPub itself, yes.
It would have to exist within ActivityPub. The only alternative would be the whole Fediverse having to adopt yet another non-standard Mastodon hack that isn't documented anywhere because Mastodon didn't intend it to be adopted by other projects.
But if you don't want stuff to leak out through Hubzilla, it would also have to be included into the Zot6 protocol. And if you don't want stuff to leak out through (streams), it would have to be included into the Nomad protocol.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta
Essentially you'll need a server that hosts a virtual world, a client to consume it, and a way to transfer seamlessly between servers. The underlying protocol should be open, so other implementations can reuse that.
You go from online game to metaverse the moment anyone can author & host their own server, determine what the client experience is like, and connect it to the existing pool of servers in a decentralized way.
You've basically described . Established, free, open-source and decentralised since 2007, interconnected since 2008, today with thousands of individual worlds ("grids"), most of which are connected to the Hypergrid, and over four times the land area of Second Life.
Oh, and the OpenSim community has had "metaverse" as a regular part of their vocabulary since 2007 as well.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds
Last updated: 2024-03-21
All text and images © eLoc8.is-fabulous.com