The Long Drive

The Long Drive

It's funny. It is a drive that I have done plenty of times. Tomorrow I will do the usual twelve hour drive from Switzerland to around Alicante, and I will do so with minimal stops.

In essence the drive is easy. I take the motorway from Nyon all the way to Ondara, with a small segment on open roads around Grenoble. It's long, but easy.

There is a difficulty that I face. I always do this drive alone. Whilst it gives me the freedom to drive at my speed, stop when I want to and more, it also reminds me that I am still solitary. I always feel a little fragile before a trip, especially one like this.

If I was going to Barcelona it would be an easy eight hour drive, but to go towards Ondara is a twelve hour drive. That's twelve hours of podcasts, audio books and more. With a good audio book the drive is easy.

Some people would stop along the way, and I have considered it. I don't know where I would stop. If I stopped I could break the journey in two, but would that increase fatigue over two days

In reality this drive is a fun challenge. It's liberating to drive for twelve hours, and to listen to an audio book from cover to cover. it's fun to travel through three countries in a car like this. From the road to Grenoble in the dark to the sunrise near Valence to getting to see the Motorway after Marseille, to the wind and more as I head to the Spanish border, and then the congestion around Barcelona, before the quieter roads toward Valencia and beyond. The road is familiar, and it has memories.

It would be nice to do this trip as a person in a relationship, rather than solo. I was reading The Midnight Library and this is one of those situations. When I travel my subconscious feels the presence of the book of regrets, so rather than excitement I feel regret until I start to drive, and then I feel the adrenaline of the open road. It's the waiting for a trip that plays with us.

Yesterday I spoke to someone who said doing this trip solo would be boring. That's why podcasts and audio books are good.

I considered taking the bike but that adds a layer of complexity. This time is different. I have my climbing stuff with me. If an occasion to climb comes up then I can take that opportunity to do something a little different.

I think the problem is that I have too much time to think before a trip. If I had no time to think about the journey I'd be excited, and impatient. I should be excited and impatient. I will read most of Nexus, in theory. I finished Sapiens while eating lunch today.

Tomorrow I drive a familiar road that is one thousand two hundred kilometres long. In the US such a distance is ordinary. In Europe it's less ordinary.

#contemplation #drive #endurance #long #reading

AVA/USDT

Leverage: 20-75x
Entry Targets:
2.32
2.28
Take-Profit Target :
1)2.45
2)2.55
3)2.70
4)3.20

Stop-Loss: 2.00

TURBO/USDT

Leverage: 20-75x
Entry Targets:
0.01107
0.01000
Take-Profit Target :
1)0.01200
2)0.01300
3)0.01500
4)0.01800

Stop-Loss: 0.009400

MOODENG/USDT

Leverage: 20-75x
Entry Targets:
0.358
0.330
Take-Profit Target :
1)0.370
2)0.390
3)0.420
4)0.450

Stop-Loss: 0.300
MOODENG/USDT

Dolphins In Depth: Was signing Odell Beckham a mistake for Miami

Long

XRP/USDT

Entry price : - 2.45 - 2.35

(SCALP)
Target 1: 2.50
Target 2: 2.60
Target 3: 2.70

(SWING TRADE)
Target 1: 2.75
Target 2: 3.20

Stop loss : 2.25

Leverage: 5x

Allocate only 1-3% of our deposit for each trade

Attention-Worthy Links for December 13th, 2024

-term -rays

Until the people behind FediDevs honestly try to fix it by adding compatibility with the rest of the Fediverse, I'll consider this an act of intentional discrimination against everything that isn't Mastodon and keeping the non-Mastodon server apps and their users out of everything they do.
It isn't like the FediDevs people don't know that there is more to the Fediverse than Mastodon. They do know. At least some do. There is that did work with Mastodon and other Fediverse server apps. But it hasn't been used in nine months.
At the same time, the FediDevs website is clearly not built against any Mastodon API. If it was, then server apps that have the same API implemented would work with it. But the only non-Mastodon thing I've seen slip through is one watched Catodon instance. Catodon uses Iceshrimp's technology to mimic Mastodon, so I guess it happens to be close enough.
For the whole thing looks like built against Mastodon's inner workings without the use of any API. Why would someone build it like that Either it's cluelessness. It definitely wasn't cluelessness. At least someone had to have knowledge of a Fediverse outside of Mastodon see the Friendica group.
Or it's intentional malice. It's like someone is secretly waging war against everything in the Fediverse that is not Mastodon. That seems to be why the Friendica group was abandoned, namely in order to stop using and thus promoting something that isn't Mastodon.
And FediDevs looks like it was built the way it was built in order to make bloody sure it will always stay a Mastodon-exclusive thing by making it as incompatible with the rest of the Fediverse as possible, at least probably without as blatantly obvious means as rejecting user agents. The "Fedi" in the name is the cherry on top to a) drive the point home that the Fediverse is (or should be) only Mastodon and b) flip the bird at the non-Mastodon Fediverse.
The whole backend code seems to be built against Mastodon directly also to make it as difficult as possible to add compatibility with other Fediverse server applications because that would require the whole backend to be redesigned and rewritten from the ground up.
I'd really like the FediDevs staff to prove me wrong by actually opening their site to the non-Mastodon Fediverse.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs

/USDT

ZONE: 28.80 - 28.22
LEVERAGE: Isolated 20x
Targets:
1) 29.02
2) 29.38
3) 29.66
4) 29.95
5) 30.24
6) 30.53

STOPLOSS: 27.48

it's not what most former Bluesky users would be looking for, exactly.

They're looking for a drop-in replacement of pre-Musk Twitter. For one, Misskey and the Forkeys are actually closer to pre-Musk Twitter in UX than Mastodon.
Besides, if you keep doing what has been done for almost three years now, railroad everyone to Mastodon without even telling them that there's more to the Fediverse than Mastodon in order to keep things simple, you'll end up with even more people who spend months or years in Mastodon-only bubbles. Who then get used to a Fediverse which allegedly is only Mastodon.
Who end up very irritated and defensive of their "Mastodon Fediverse" when an alleged "intruder" that's nothing like Mastodon shows up in their timeline.
And who try hard to force non-Mastodon users to abandon their own culture, only adopt Mastodon's culture, use whatever they're on exactly like Mastodon and stop using any features that Mastodon 3 didn't have because Mastodon's entire culture is defined by Mastodon 3's features.
Trust me, it really is that bad. I'm a Hubzilla user. I speak from personal experience.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Misskey #Forkey #Forkeys #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse I think it'll stay incomplete.
FediDevs looks to me like it was built hard against only Mastodon. Not against any Mastodon API, but directly against Mastodon's inner workings. And intentionally so. The only thing I've seen that managed to work with FediDevs in at least one case is Catodon which mimics Mastodon itself.
FediDevs used to have its own Friendica discussion group. It was last used nine months ago.
I'd be pleasantly surprised if any of this changed. But right now, it looks to me like FediDevs has explicitly positioned itself against the non-Mastodon Fediverse now.
And still, they have the audacity to call it FediDevs.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs

Audrey Hepburn with long hair!!

It definitely is. Whether Meta like it or not.
Facebook may be "the Internet" for the entire Third World, but Meta need the European market. Desperately. And be it out of fear that the Facebook and Instagram killers may come out of Europe where people can no longer use "the real deal" after they were banned from the EU.
I dare say that Meta aren't a bunch of dumb jingoists who can barely grasp the idea of Europe having electricity. I'm pretty sure they know about the pile of social networks that were launched in Germany alone. I'm not even talking about Mastodon and Pleroma. I'm talking about StudiVZ/MeinVZ, Wer-kennt-wen and StayFriends, just to name the formerly biggest three. In fact, when Facebook was new, it had a hard time entering the German market because its entire potential target audience was on StudiVZ or MeinVZ and/or Wer-kennt-wen already.
So if Meta Platforms were banned from the EU market in its entirety, chances wouldn't be bad that someone whips up replacements.
And Meta know pretty well that this wouldn't even be necessary. There are already alternatives for everything the offer, even free, open-source, decentralised ones in all cases, and Meta know about at least some of them. They've known Friendica since at least 2012, for example. If Meta were forced to leave the EU, some of these alternatives would grow huge enough to have the chance to become serious competition to Meta outside the EU.
And so they're connecting Threads to the Fediverse just barely enough for the EU to shut up and leave them alone. I mean, why don't they go all-in instead if they're allegedly so eager to get their filthy hands on the Fediverse
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaPlatforms #Facebook #Instagram #WhatsApp #Threads #Horizonworlds #Horizons #EU #EuropeanUnion

The people who wrote the Fediverse

There were no "people who wrote the Fediverse". These was no committee who laid down the standards.
The Fediverse was invented by . In 2008. By first creating a centralised Twitter alternative silo named Identi.ca.
And then open-sourcing the underlying technology as Laconi.ca, later StatusNet (merged into GNU social in 2013).
And then laying the protocol open as OpenMicroBlogging, later superseded by OStatus.
Then, in 2010, Mike Macgirvin decided that the world needs a free, open-source, decentralised, secure alternative to Facebook that's better than Facebook. And so he made Mistpark, today .
But the features he wanted Friendica to have were impossible to achieve with any existing protocol. OStatus wasn't even that good for microblogging, much less Mike's ambitious plans. Besides, he's an experienced protocol designer. So he created a whole new protocol, DFRN, and built Friendica on top of it. Friendica did adopt OStatus as an extra protocol, though, because Friendica's goal was and still is to federate with everything and then some.
In 2011, Mike had seen many public Friendica nodes shut down with or without warning and people always losing everything and having to start over from scratch. So he decided to do something against it.
He invented . And built a new protocol around it, Zot, because there was no way DFRN could take care of this, let alone OStatus.
In 2012, he forked Friendica into Red and rewrote the whole backend against Zot, which, however, required the creation of yet another identity scheme.
For one, one login could now have multiple fully separate and independent identities on it. For example, my Hubzilla channel URL is .
Besides, one identity could now reside on multiple server instances which is what nomadic identity means.
Red was later renamed Red Matrix and, in 2015, refactored, redesigned and renamed into .
Mastodon and Pleroma started in 2016 as OStatus-based alternative UIs for GNU social. Mastodon was the first to be turned into a stand-alone project with not much interest in connecting to anything outside, all in spite of already being federated with Pleroma, GNU social, Friendica and Hubzilla via OStatus.
ActivityPub came out in 2017. No, not 2018. It was standardised in 2018. But it came out in 2017.
In July, 2017, Hubzilla was the first Fediverse project to integrate ActivityPub. Next to its own Zot, next to diaspora*, next to OStatus etc. On the one hand, Hubzilla tried to stay as close to the ActivityPub spec as possible and feasible. On the other hand, Hubzilla had to make its ActivityPub integration, which has always been an optional add-on, compatible to its own technology, to its own Zot protocol, to the way it works.
In September, Mastodon was the second Fediverse project to adopt ActivityPub. But Mastodon was more interested in doing its own thing and being as close to Twitter as it could than in sticking to a protocol spec, much less connecting to non-Mastodon stuff such as Hubzilla with which it already shared two protocols now.
Mastodon was the one that added Webfinger. ActivityPub doesn't even require Webfinger. The ActivityPub spec doesn't contain Webfinger. But Mastodon requires Webfinger. It can't live without Webfinger. So everything that wants to properly federate with Mastodon needs to implement Webfinger.
After ActivityPub had become a standard, more projects adopted it. But as lax a specification as ActivityPub is, it allowed for a lot of liberties.
Some devs looked at how Mastodon had integrated ActivityPub, decided it was rubbish and did it their own way.
Some devs looked at how Mastodon had integrated ActivityPub, decided they couldn't do it the same way because what they did was too different from Mastodon and did it their own way.
Some devs didn't look at what anyone else did and did it their own way.
Probably none of them looked at how Hubzilla had integrated ActivityPub because none of them even knew that Hubzilla existed. Except for those who were maintaining Friendica now. And Friendica had to make it compatible with DFRN and with the way it had been working since 2010.
Fast-forward to 2023. Mike's current piece of work was which contains an intentionally nameless fork of a fork of three forks of a fork (of a fork) of Hubzilla, slimmed down from Hubzilla, but modernised and technologically even more advanced.
It was then that , creator and maintainer of , got into contact with him because he wanted to add nomadic identity to Mitra. Something that's built on ActivityPub and only supports ActivityPub. A first. No-one had ever done nomadic identity with nothing but ActivityPub before.
So the two started working on how to implement nomadic identity using only ActivityPub. Mike had a vision of a Fediverse with nomadic identity all over and Fediverse identities cloned beyond server application borders. Like, a (streams) channel cloned to Mitra, Mastodon, PeerTube and Mobilizon, all with the same identity.
This, however, required another, brand-new way of identifying Fediverse actors. And so was created.
We're probably in the middle of xkcd 927 now.
Mike set up an experimental branch of (streams) to develop and test nomadic identity via ActivityPub, also since (streams) already had nomadic identity anyway.
Around summer, the "nomadic" branch (for nomadic identity via ActivityPub) seemed reliable enough to merge it into "dev". And in July, "dev" was merged into "release", complete with nomadic-identity-via-ActivityPub code.
It was shortly after that merge that I created my two (streams) channels. The channel URL of my channel for Fediverse memes is . But its DID, which all channels created on accounts registered after that merge got, is . And that's only two IDs of the same channel. There are also others for (streams)' native Nomad protocol, Hubzilla's Zot6 protocol, ActivityPub, OAuth, OAuth2 and probably also OpenWebAuth magic single sign-on, another one of Mike's creations. Not to mention that (streams) channels, like Hubzilla channels and Friendica accounts, can also optionally be group actors.
In fact, this blew up into (streams) users' faces because (streams) confused the various IDs to such degrees that it wouldn't federate at all anymore. It took Mike a whole lot of work to iron this out again, so much that he officially retired from Fediverse development on August 31st.
And in the middle of this, he even created yet another fork, Forte, which is (streams) minus Nomad, minus Zot6, based on and supporting only ActivityPub. My guess is still that one of the reasons to create Forte at that point was to get rid of the Nomad and Zot6 IDs to sort the ID mess out.
Even if nomadic identity via ActivityPub should ever become stable and start spreading, I don't expect DIDs to become the one norm in the Fediverse. Not with all those barely or unmaintained projects and those devs who refuse to acknowledge that devs of other projects do great stuff, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #OStatus #DFRN #Zot #ActivityPub #Nomad #Laconi.ca #Identi.ca #StatusNet #GNUsocial #Friendica #Hubzilla #Mastodon #Pleroma #Streams #(streams) #Forte #FEPef61

Ich mags, dass das alles existiert.

Das ist schon mal positiv. Es gibt Leute, die sich so an ein reines Mastodon-Fediverse gewhnt haben, da sie alles, was anders ist, als strende Eindringlinge empfinden und wieder weg haben wollen.

Ich hab nur gar nicht so viel Sehnsucht nach Ersatzdiensten fr Facebook, Insta, Wasweissich. Entgeht mir da was

Na ja, auf eine Art schon. Was nicht Mastodon ist, ist ja auch nicht Mastodon mit einer anderen Oberflche. Das kann schon ziemlich anders sein.
Zunchst mal sind so Features wie Textformatierung, Zitate oder Drkos/Drukos und sehr viel hhere oder gar keine Zeichenlimits auerhalb von Mastodon gang und gbe. So manch jemand, der bis dahin das Fediverse als reines Vanilla-Mastodon-Netzwerk ansah, kriegt ja einen Riesenschreck, wenn das erste Mal ein Beitrag mit deutlich ber 500 Zeichen auftaucht. Oder mit einem Zitat. Oder mit einer Stichpunkteliste. Oder mit Kursivschrift, aber es ist keine Unicode-Trickserei.
Schon im Microblogging-Bereich gibt's einiges, das ziemlich anders ist als Mastodon. ist ja auf einer der letzten verbliebenen Instanzen von Calckey. Das ist ein Fork des japanischen Misskey, der eigentlich letztes Jahr durch Firefish ersetzt wurde. Misskey hat schon 3000 Zeichen, die wie auf Mastodon hartgecodet sind. Bei den diversen Forkeys (Calckey/Firefish, Sharkey, CherryPick, Iceshrimp, Catodon usw. usf.) liegen die Limits mindestens auf dem Niveau, wenn nicht hher, sind aber durch den Admin konfigurierbar.
Interessanterweise sind Misskey und die Forkeys (wobei Iceshrimp allmhlich kein Fork mehr ist) in der Handhabung trotzdem, und obwohl sie auch noch Features wie Textformatierung mittels einer erweiterten Variante von Markdown und eine sehr konfigurierbare Oberflche haben, dichter an Pr-Musk-Twitter, als es Mastodon ist. Eine Mehrspaltenansicht la TweetDeck haben Mastodon und die *keys, aber vor allem bei denjenigen Forkeys, die gegenber Misskey noch Extrafeatures haben, kannst du damit mehr anstellen.
Die richtig groen Keulen sind dann die von Mike Macgirvin ber gute 14 Jahre auf den Weg gebrachten (mehr oder weniger) Facebook-Alternativen. Friendica existiert schon seit 2010 und hatte von Anfang an schon eine sagenhafte Feature-Palette. Whrend Mastodon versucht, Twitter nachzuffen, hat Friendica nie versucht, Facebook nachzuffen, sondern eher, besser als Facebook zu sein.
So gibt's da beispielsweise auch alles, was man zum Bloggen bruchte. Zeichenlimits gibt's nicht, gab's nie. Dafr gibt's die volle Palette an Textformatierung per erweitertem BBcode. Es gibt einen eingebauten Filespace, wo man z. B. Bilder hochladen und dann beliebig viele davon in Posts einbetten kann, also mit Text darber und Text darunter, statt wie auf Mastodon nur vier davon als Dateien anhngen zu knnen.
Man kann Friendica-Konten auch als moderierte Diskussionsgruppen verwenden, hnlich wie Gruppen auf Facebook. Die Erfahrung hat gezeigt, da Friendica-Gruppen mit groen Teilen des Fediverse kompatibel sind bis hin zu Mastodon, nur da es besonders fr Mastodon-Nutzer nicht ganz straight-forward ist, einen Thread zu starten.
Friendicas eigentliches Killerfeature war aber immer, da es stets versucht hat, sich mit allen mglichen Sachen zu verbinden. Es sollte so eine Art Kommunikationszentrale sein. Friendica kann sich mit diaspora* verbinden, es kann sich ber OStatus mit den Sachen verbinden, die es noch haben, man kann zu WordPress und kompatiblen Blogs crossposten, man kann RSS- und Atom-Feeds abonnieren, und man kann auch per E-Mail oder XMPP kommunizieren.
Man kann auch ein Tumblr- oder Bluesky-Konto ins Friendica-Konto einbinden und sich dann damit bidirektional verbinden, ganz ohne Bridge. Theoretisch ginge das sogar mit , wenn der Node-Betreiber ein Multimillionr wre, der sich die API-Lizenz leisten kann. Und ab 2012 ging es kurzzeitig sogar mit Facebook, bis Facebook das unterbunden hat.
ber Friendica gbe es noch einiges mehr zu erzhlen, was da geht. So manch einer sieht es als das Schweizer Taschenmesser des Fediverse.
Aber wenn Friendica das Schweizermesser ist, dann ist Hubzilla das Leatherman. Hubzilla ist nmlich noch heftiger. Es wird bezeichnet als "dezentrales soziales Content Management System" und vereinigt entsprechend viele Funktionalitten unter einem Dach.
Hubzilla fing ja 2012 an als ein Friendica-Fork namens Red, dann Red Matrix, und war zunchst einmal nicht viel mehr als Friendica mit , und einem ziemlich mchtigen und detaillierten Berechtigungssystem. 2015 wurde es dann in Hubzilla umbenannt und entsprechend featuremig zur eierlegenden Wollmilchsau aufgebohrt.
Man knnte Hubzilla jetzt fr alles Mgliche und Unmgliche nehmen. Beispielsweise habe ich auf diesem Kanal und . Und ist selbst Teil eines Hubzilla-Kanals.
Der Pepe (Hubzilla) hat Hubzilla sehr gut und sehr detailreich in seiner erklrt.
Danach folgte von 2018 bis 2021 eine ganze Reihe von Forks, bei denen Zusatzfeatures und Verbindungsmglichkeiten wieder abgespeckt wurden, die aber allmhlich technisch und in der Handhabung immer weiter aufgefrischt und modernisiert wurden.
Im Oktober 2021 kam dann etwas, was eine ganze Zeitlang als stabil angesehen wurde, was aber auch ziemlich ungewhnlich ist. Es hat nmlich offiziell, mit voller Absicht und aus guten Grnden keinen Namen, keine Markenidentitt, (fast) keine Nodeinfo, und es wurde ebenso mit voller Absicht in die Public Domain gestellt, whrend Mike sonst alles unter die MIT-Lizenz gestellt hat.
Das Code-Repository brauchte aber zwingend einen Namen. Mike hat es Streams genannt, und so wird auch die Anwendung nicht ganz offiziell (streams) genannt, inklusive der Klammern.
Krzlich hat Mike die Readme-Datei aktualisiert, .
Okay, seit Osada und Zap von 2018 hat die Familie keine Artikel mehr, keine Karten, keine Wikis, keine Webpages, der Kalender ist vereinfacht worden usw. Das ganze Zeug gab es ja eh schon auf Hubzilla, und Mike wollte wieder zurck zu reinem Social Networking.
Dafr hat er aber die Handhabung vereinfacht, verschlankt und der Realitt angepat, vor allem auch der Realitt eines Fediverse, das mehr und mehr von ActivityPub dominiert wurde. Deswegen hat (streams) eine bessere ActivityPub-Integration als Hubzilla. Auf beiden ist ActivityPub optional, aber auf (streams) ist es in den Kern eingegossen, und (streams) kann es sich im Gegensatz zu Hubzilla erlauben, ActivityPub standardmig in neuen Kanlen zu aktivieren.
Ganz besonders die Berechtigungssteuerung ist vereinfacht und entschlackt und ermglicht eine direktere Kontrolle darber, welcher Kontakt was darf. Gleichzeitig ist (streams) aber auch sicherer, weil es nicht mehr mglich ist, den ganzen Kanal auf ffentlich zu schalten.
(streams) wird heute noch von Mike mehr oder weniger weiterentwickelt. Aber mit Forte hat er seit August noch ein weiteres Eisen im Feuer. Forte ist im Prinzip (streams), aber es untersttzt nur noch ActivityPub. Das heit auch, da auf Forte nomadische Identitt rein ber ActivityPub abgewickelt wird und nicht mehr ber ein eigens dafr entwickeltes Protokoll. Deswegen ist Forte noch nicht ffentlich, ebenso wie brigens die Entwicklerversion des Microblogging-Projekts Mitra, in der auch nomadische Identitt eingebaut wird.
Aller Komplexitt zum Trotze kann man, wenn man will, alle vier natrlich auch zum Microbloggen nehmen.
Darber hinaus gibt's im Fediverse noch in andere Richtungen spezialisierte Sachen, die also nichts mit Microblogging oder Social Networking zu tun haben.
Mit Lemmy, dem dahinsiechenden /kbin, Mbin, PieFed und dem in Entwicklung befindlichen Sublinks gibt es etwa eine ganze Anzahl an Alternativen zu Reddit oder auch Hacker News.
Mit WriteFreely und Plume gibt's zwei spezialisierte Blogginganwendungen im Stil von Medium. Plume ist von den Features her eigentlich besser, wird aber im Moment nicht weiterentwickelt. Auerdem sind inzwischen viele WordPress-Blogs ans Fediverse angebunden.
PeerTube prsentiert sich als Alternative zu YouTube mit einer Prise Peer-to-Peer zwischen den Instanzen, inklusive Livestreaming. Rein auf Livestreaming la Twitch spezialisiert ist Owncast. Ganz neu ist Loops als TikTok-Ersatz vom Macher unter anderem von Pixelfed und der FediDB, das fderiert aber noch nicht.
Im Audiobereich gibt's Funkwhale, wo man im Prinzip alles hochladen kann, aber nur lizenzmig freie Sachen ffentlich machen sollte, das noch recht junge Bandwagon als Bandcamp-Alternative und Castopod speziell fr Podcasts wie z. B. das auch von gefeaturete .
Es gibt noch einiges mehr, z. B. Mobilizon fr kooperative Eventplanung, BookWyrm als GoodReads-Ersatz oder, auch noch recht neu, Flohmarkt, das ziemlich genau das ist, wonach es sich anhrt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Catodon #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #/kbin #Mbin #PieFed #Sublinks #WriteFreely #Plume #WordPress #PeerTube #Owncast #Loops #Funkwhale #Bandwagon #Castopod #Mobilizon #BookWyrm #Flohmarkt #FediTips FediDevs als Ganzes scheint komplett hart gegen Mastodon, nur Mastodon und nichts als Mastodon gebaut zu sein. Oder was auch immer gengend proprietren Mastodon-Kram eingebaut und sich an Mastodon angepat hat, um kompatibel zu sein.
Beispiel 1: Guckt euch mal unter den die Liste der getrackten Instanzen an. Wieviele Nicht-Mastodon-Instanzen sind da, auer einer einzigen Catodon-Instanz (Catodon soll eine Art Mastodon mit einem Rest Iceshrimp-Backend darunter werden, soweit ich das verstanden habe.)
FEDIDevs impliziert doch, fr Entwickler aus dem ganzen Fediverse zu sein. Es schliet aber fast alles aus, was nicht Mastodon ist, und somit auch die Entwickler vieler Serveranwendungen, die nicht Mastodon sind. Die knnen gar nicht teilnehmen, weil das Backend von FediDevs vermutlich nicht mal gegen eine Mastodon-API gebaut ist, sondern direkt gegen Mastodon-Code.
Beispiel 2: ein Starterpack namens "".
Der ist komplett leer. Da ist genau berhaupt nichts drin.
Warum Weil es ganz augenscheinlich technisch vollkommen unmglich ist, irgendwas da einzutragen, was nicht auf Mastodon ist.
Wer auch immer hinter dem Bau von FediDevs steckt, scheint entweder anzunehmen, da das Fediverse nur aus Mastodon besteht. Oder es war einfacher, FediDevs nur gegen Mastodon zu bauen, statt ~~das eine Promille~~ ~~das eine Prozent~~ ~~die zwei Prozent~~ die knapp 30 Prozent an Fediverse-Nutzern zu bercksichtigen, die nicht auf Mastodon sind.
Ganz offenkundig wei bei FediDevs eine Hand nicht, was die andere tut. Auf der einen Seite gibt's ein Webportal, das nur mit Mastodon funktioniert. Auf der anderen Seite gibt's mit eine Friendica-Gruppe aus denselben Kreisen, wobei die seit einem Dreivierteljahr nicht mehr genutzt wird.
Das, oder dahinter steckt der Vorsatz, das Fediverse (wieder) zu nur Mastodon zu machen, indem alles Mgliche und Unmgliche, was an "Fediverse"-Diensten und -Zusatzfeatures entwickelt und beworben wird, mit voller Absicht gleichzeitig "Fedi" im Namen hat und nur gegen Mastodon gebaut wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #FediDevs

Internazionale by Internazionale
Breve guida alla lunga guerra in Siria

Con la caduta di Assad si conclude larco delle rivolte della primavera araba che hanno ridisegnato la regione. Leggi

Translated:
Short Guide to the Long War in Syria

With the fall of Assad, the arc of the Arab Spring uprisings that have redrawn the region concludes.

Einer der vielen Grnde, warum ich lieber auf Hubzilla oder (streams) bin als auf Mastodon: nomadische Identitt.
Nicht nur knnte ich ohne groe Schwierigkeiten mit meiner kompletten Identitt und allem, was dazugehrt, umziehen. Sondern ich kann sie auch ber mehrere Serverinstanzen klonen. So liegt sie nicht in einer, sondern aktuell in zwei Hnden. Geht eine Instanz mal offline, oder ist sie gestrt, habe ich einen identischen Klon meines Kanals woanders, und zwar mit allem Content, mit allen Kontakten, mit allen Dateien, mit allen Einstellungen, mit allem Drum und Dran.
Und im brigen kann sich im Fediverse jeder aussuchen,

in wessen Hand er seine Daten gibt, denn nicht alles im Fediverse ist in derselben Hand
was er da an Features hat, denn nicht alles im Fediverse ist Mastodon

Wer die technischen Fhigkeiten und Mglichkeiten hat, kann ersteres sogar umschiffen, indem er seine eigene Privatinstanz von was auch immer betreibt, vielleicht gar auf einer Maschine im eigenen Eigentum in den eigenen vier Wnden.
Aber generell habe ich schon genug Erfahrung mit dezentralen Systemen (XMPP, Matrix, OpenSimulator, das Fediverse auch schon seit Anfang der 2010er), da ich sagen kann: So etwas wird sich nie 100% wie ein zentralistisches, kommerzielles Silo anfhlen und auch nie so funktionieren. Und wem das nicht pat, der ist da eben falsch.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadischeIdentitt

Ich glaube, dass man schon mal viel gewinnen wrde, wenn man *mit* seinen Beitrgen auf Servern umziehen kann (nimmt Bedenken, sich vielleicht den "falschen" Server auszusuchen)

Dafr mte Mastodon erst nomadische Identitt einfhren. Dann ginge das ziemlich problemlos. Hubzilla hat das seit Anbeginn, seit 2012. Aber rein ber ActivityPub ist das noch extrem experimentell.

und wenn *alle* Server untereinander bekannt wren und die Suche nach Hashtags & Co eben ber wirklich *alle* Server (minus den Geblockten) gehen wrde und nicht nur denen, die irgendwann mal irgendwie Bekanntschaft geschlossen haben.

Hufig gestellte Forderung. Aber technisch unrealistisch.
Nehmen wir mal an, ich setze meine eigene (streams)-Instanz auf. Alles konfiguriert, alles startklar. Ich gebe #systemctl start httpd ein, und der Webserver erwacht zum allerersten Mal.
In diesem Sekundenbruchteil mten alle zigtausend Fediverse-Instanzen sofort von der Existenz meiner (streams)-Instanz wissen. Instantan. Auf der Stelle. (Du hast "wirklich *alle* Server" geschrieben. Also ohne jegliche Ausnahme.)
Das wre nur auf drei Arten und Weisen vorstellbar.
Erstens: Alle zigtausend Fediverse-Instanzen wissen vorher, da ich vorhabe, diese (streams)-Instanz aufzusetzen. Vorstellbar, aber vollkommen unrealistisch.
Zweitens: Meine (streams)-Instanz kennt alle, aber auch wirklich absolut ausnahmslos alle anderen Fediverse-Instanzen, die zu dem Augenblick existieren, wo der Webserver anspringt. Und zwar ohne dezentrale Hilfsmittel.
Das heit: Der Quellcode im streams-Repository enthlt eine nanosekundenaktuelle Liste aller Fediverse-Instanzen. Die Liste wird beim Klonen des Quellcode auf den Webserver mit runtergeladen. Beim ersten Start macht die (streams)-Instanz als allerallererstes einen git pull, holt sich die nanosekundenaktuelle Liste aller Fediverse-Instanzen und meldet seine Existenz sofort an alle Instanzen auf der Liste.
So eine Liste mu dann im Quellcode von absolut ausnahmslos jeder Fediverse-Serveranwendung eingebaut sein. Auch wenn jemand gerade erst mit einer ganz neuen Fediverse-Serveranwendung anfngt, mu da sofort diese Liste in vollem Umfang rein.
Und natrlich mu sie aktuell gehalten werden. Das heit, jede startende neue Instanz mu sich selbst in die Listen in den Quellcodes aller Anwendungen eintragen.
Meine (streams)-Instanz mte also alle Fediverse-Serveranwendungen kennen, die es berhaupt gibt. Auch wenn ein Fediverse-Entwickler erst eine halbe Sekunde vorher den allerersten git commit einer ganz neuen Fediverse-Serveranwendung gemacht hat.
Das heit auerdem: Meine (streams)-Instanz mte unmittelbar nach dem Start die Quellcodes von weit ber 100 Fediverse-Serveranwendungen git clonen, also herunterladen. Und zwar jeweils alle Branches und alle Forks. Dann die eigene Adresse eintragen, auch wieder in alle Branches. Dann mte sie die nderungen an allen ber 100 Fediverse-Anwendungen als Pull Request git committen. Und jeweils wieder alle Branches und alle Forks. Auch die, die lange nicht maintaint worden sind. Man wei ja nie.
Jetzt kommt's: Die nderungen mssen ja auch noch gemerget werden. Dafr mte mein (streams)-Instanz sich auf hunderten Git-Repositories volle Maintainer-Rechte verschaffen und die eigenen Commits mergen. Und zwar auch, ja, gerade in Produktivcode.
Ich sage ja nicht, da das potentiell unsicher ist.
Auerdem mu das schnell gehen. Hunderte Repositories klonen, ndern, committen, reinhacken und mergen, alles innerhalb eines Nichtsigstels einer Sekunde, damit die experimentelle Iceshrimp.NET-lnstanz, die jemand eine Zehntelsekunde spter startet, auch von meiner eigenen (streams)-Instanz wei und ihre eigene Instanz meiner (streams)-Instanz mitteilen kann.
Noch einmal: Du hast "wirklich *alle* Server" gesagt. Das heit, eine neue Iceshrimp.NET-Instanz mu zwingend und sofort eine neue (streams)-Instanz kennen, die eine Zehntelsekunde frher gestartet ist.
Ach ja, das ganze Theater ist auch vollumfnglich ntig, wann immer

eine Instanz heruntergefahren wird
eine Instanz sich umbenennt
ein Hubzilla-Hub oder eine (streams)-Instanz ActivityPub deaktiviert oder wieder aktiviert, denn was interessiert eine Mastodon-Instanz ein Hubzilla-Hub, mit dem sie eh nicht interagieren kann

Jeder Entwickler wird mir besttigen, da das nicht nur komplett unrealistisch ist, sondern absolut haarstrubend. Alleine schon, weil 99,9% der Commits in den meisten Repositories von Fediverse-Instanzen kommen werden und alle Commits, die hndisch von Entwicklern kommen, darunter ersaufen. Und weil kein Entwickler seine eigenen Sachen so schnell rebasen kann, wie neue Commits mit nderungen an der Instanzenliste reinkommen.
Okay, also bleibt als dritte und einzige noch mgliche Lsung eine zentral verwaltete Liste auf einem zentralen Webserver.
Dieser Server mu verpflichtend in alle Fediverse-Serveranwendungen eingebaut sein. Auch die, die eigentlich gar nicht mehr gewartet werden, aber noch laufende Instanzen haben (Calckey, Plume usw.).
Damit wrde sich das ganze Fediverse bis in den allerhinterletzten Winkel absolut und total abhngig von zentraler Infrastruktur machen.
Warum das schlecht ist Stell dir mal vor, diese Liste geht offline aus irgendeinem Grunde. Oder irgendeiner, z. B. Elon Musk oder Jeff Bezos oder Mark Zuckerberg, kauft den Webserver mit der Liste drauf. Der htte dann die totale Kontrolle ber das Fediverse.
Willst du das
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #git

Making editing posts and alt text easier is a thing that could be done.

But you'll still never be able to edit a Friendica or Hubzilla post from Mastodon. They're too different. Trust me, I know, I've been using both for longer than Mastodon has even been around.
Let's push Hubzilla's massive permissions system that wouldn't let you at Hubzilla content anyway aside.
First of all, Friendica and Hubzilla handle images completely differently from Mastodon. On Mastodon, an image is a file attached to a post, and there can only be four of these. Each image has its own dedicated text field for alt-text.
On Friendica and Hubzilla, an image is a file uploaded to the file space that's part of each Friendica account and Hubzilla channel and then embedded into the post inline as a hotlink. With text above the image and text below the image. Like a blog post. And there can be as many images as you want.
There's no alt-text data field either. Alt-text is part of the image-embedding markup code.
All this has been the way it is since July, 2010, when Friendica was launched, five and a half years before the very first Mastodon alpha version. And Hubzilla is older than Mastodon, too.
So if you want to add alt-text to an image in a post from Friendica or Hubzilla, you inevitably have to edit the post itself.
You have to get your hands dirty on raw BBcode with software-specific additions in an editor box that has zero support for any kind of text formatting or markup code.
You have to figure out what in the code of a post or a comment corresponds to which image to which you want to add alt-text.
You have to turn this...

zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=800x533https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpg/zmg/zrl

...into this...

zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpgDigital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery./zmg/zrl

...all with no WYSIWYG, no documentation at hand, no preview because Mastodon doesn't have a preview button and an editor that may not even support over 500 characters (Friendica and Hubzilla both have no character limits).
And this only covers the UI side. I haven't even talked about what'd have to happen in the background yet.
Again, all this is assuming that Hubzilla lets Mastodon users edit posts in the first place. Which it won't.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Mastodon #Friendica #Hubzilla Still, it's a suggestion that keeps popping up from the many Mastodon-only bubbles in the Fediverse. And it's being cheered and applauded.
For the record, I'm not an alt-text opponent myself. Rather, I put huge efforts into describing and explaining my images at levels I deem sufficient even for random strangers who happen upon my image posts without knowing anything about the subject. can probably confirm it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

Mein Standpunkt ist das viele es schon merken werden ( auch ich hab das am Anfang nicht geblickt).

Nachdem sie sich monate- oder jahrelang an ein Fediverse gewhnt haben, das nur aus dem flauschigen Wollmammut besteht. Da es anders sein knnte, ist fr sie gnzlich unvorstellbar.
Dann luft ihnen ein vermeintlicher "Trt" ber den Weg, der so vllig anders ist als all das, was aus ihrer bisherigen reinen Mastodon-Bubble kam. Mehr als 500 Zeichen. Textformatierung. Ein Zitat. Eine Drko oder Druko (also ein "Quote-Trt").
Das ist fr viele so verstrend wie ein H.R.-Giger-Xenomorph in einer Schafherde. Einige glauben erst an eine "bse", "gehackte" Mastodon-Instanz. Wenn sie dann erfahren, da das von etwas ist, das mit Mastodon verbunden ist, also mit ihnen auf Mastodon, das aber selbst nicht Mastodon ist, sind sie nicht selten noch mehr verstrt.
Und dann wollen sie das weghaben. Sie wollen ihr flauschiges reines Mastodon-Fediverse wiederhaben. So Sachen wie Calckey, das nutzt, oder Friendica oder das von mir genutzte Hubzilla nehmen sie als Eindringlinge wahr, die sich gerade erst unrechtmigerweise ins Mastodon-Fediverse reingehackt haben.
Wohlgemerkt, Hubzilla ist je nach Definition entweder zehn Monate oder knapp vier Jahre lter als Mastodon und Friendica fnfeinhalb Jahre. Und Mastodon ist mit beiden so lange verbunden, wie es selbst existiert.
Auch die Mastodon-Kultur, die viele Mastodon-Nutzer zur verpflichtenden Kultur fr das gesamte Fediverse machen wollen, ist so erschaffen worden von Mastodon-Nutzern, die zu dem Zeitpunkt nicht mal ahnten, da das Fediverse vielleicht mehr ist als nur Mastodon. Sie ist komplett und ausschlielich ausgelegt auf die Features von Mastodon 3.x und auch nur auf die.
Es gibt zwischen Mastodon-Nutzern und Nicht-Mastodon-Nutzern in dieser Hinsicht zwei groe Unterschiede.
Zum einen:
Mastodon-Nutzer haben entweder kein Problem, die Mastodon-Kultur zu leben, oder sie tun es lngst. Immerhin ist die Mastodon-Kultur zugeschnitten auf das, was sie eh nutzen.
Fr Nicht-Mastodon-Nutzer bedeutet die verpflichtende Mastodon-Kultur aber die Aufgabe der Kultur dessen, was sie selbst benutzen, und damit auch die Aufgabe von auch mal 90% der Features von dem, was sie selbst benutzen. Denn die Nutzung dieser Features strt die Mastodon-Kultur.
Zum anderen:
Nicht-Mastodon-Nutzer kennen es vielfach, dafr attackiert zu werden, da sie sich nicht ganz genau so verhalten, wie man es auf Mastodon erwartet.
Mastodon-Nutzer knnen sich dagegen vielfach nicht mal vorstellen, da das berhaupt passiert. Denn ihnen passiert das nicht.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon

3) make it easier to make alt available AFTER a picture has been posted, especially in a way that doesnt add more burden to the OP or requester if they cant do it themselves.

Honestly, as someone who doesn't use Mastodon, but something that's very much not Mastodon, I don't like that very popular idea of users being able to edit alt-texts into other users' image posts with no resistance.
Especially since if Mastodon introduced it, only Mastodon would have it. But Mastodon users could try and pop alt-texts into Friendica or Hubzilla or (streams) posts until they're old and grey, but they won't succeed.
Not only because posts from these three are vastly different from Mastodon toots in the way they're built up (no, seriously, they're absolutely nothing like Mastodon toots), but also because especially Hubzilla and (streams) will never a proprietary and non-standard Mastodon feature that lets anyone on Mastodon circumvent their permissions system and mess around with any content coming from there.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta Alexander Goeres Die Alternative wre ein Mastodon, das sich wirklich wie Twitter anfhlt. Fully-featured App namens "Mastodon", die genau wie die Twitter-App aussieht, aufs Handy laden und lostrten. Vielleicht noch Nutzername und Pawort. Idealerweise bernimmt die App gleich den Nutzernamen und das Pawort aus einer anderen App, z. B. der -App.
Der Nutzer wird natrlich auf mastodon.social geparkt. Die App guckt in anderen installierten Apps, woran der Nutzer interessiert ist, und folgt sofort mindestens 200 bis 300 anderen Mastodon-Konten. (Wohlgemerkt, ausdrcklich nur Mastodon-Konten.) Folgeanfragen, die erst besttigt werden mssen, forciert die App dabei auf der Seite der Gefolgten.
Die App mu dann eine totale Black Box sein und das Konzept von Instanzen komplett verschleiern. Der Nutzer darf nicht mal wissen, was fr eine Website dahintersteckt.
Dann darf der Nutzer aber auch nicht mit Posts verwirrt werden, die irgendwie Rckschlsse auf die Technik oder das Fediverse zulassen. KI-gesttzte Schlsselworterkennung mu alles an Content vom Nutzer fernhalten, was

das Fediverse auerhalb von Mastodon erwhnt
nicht wie von Vanilla-Mastodon aussieht
nicht von Vanilla-Mastodon kommt
das Fediverse berhaupt erwhnt
Instanzen erwhnt oder auch nur das Konzept
irgendwie Fediverse-Technik erwhnt

Und die App mu das auf eine Art und Weise tun, da der Nutzer nicht bemerkt, da da was manipuliert wurde.
Das heit, der Nutzer mu durchgngig verhtschelt werden bis zum Gehtnichtmehr, noch sehr viel mehr als sowieso schon. Wir wollen ihn doch nicht gleich wieder vergraulen, oder
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #UX Well, Mastodon's internal character limits, 500 characters for posts, 1,500 characters for alt-text, are both hard-coded in a file that is being synced by git. It can be changed, but only by modifying what's essentially the source code.
Mastodon's current culture was established in 2022 by people who came in from Twitter in the first migration wave which started in February when Elon Musk announced his intention to take over Twitter. In this migration wave already, so many people came to Mastodon, especially mastodon.social, that it didn't take long for them to only encounter their own likes and hardly come across anyone who had been Mastodon users before 2022. Thus, they created a culture that was completely independent from pre-2022 Mastodon.
Also, not a single one of them knew what the Fediverse really was. For absolutely all of them, the Fediverse was Mastodon and only Mastodon. Vanilla Mastodon with a hard 500-character limit which, in the light of only 280 characters on Twitter, already felt like a lot to them.
They did not know about Misskey with 3,000 hard-coded characters. Or Pleroma and Akkoma with 5,000 configurable characters. Or the various Misskey forks with configurable limits of several thousands of characters. Nor did they know about Friendica, over five years older than Mastodon, or Hubzilla, a Friendica fork that's still almost four years older than Mastodon at its core. These two don't have any arbitrary character limits at all. And especially, they didn't know that all of these were fully, bidirectionally connected to Mastodon and interacting with Mastodon all the time.
In fact, ever since, it has always taken Mastodon newbies quite a while to even learn about Mastodon instances with modified character limits, not to mention Mastodon forks with configurable character limits.
And so it was those recent Twitter-to-Mastodon newbies who defined a whole new culture, based on vanilla Mastodon 3.x, its features and its limitations, but for the entire Fediverse. This culture was set in stone in late October already when the second migration wave started, and Mastodon newcomers who really settled into Mastodon, rather than wanting another Twitter, have been living this culture ever since.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #CharacterLimit #CharacterLimits #AltText #AltTextMeta #CWAltTextMetaThis is going to be one busy day in OpenSim. I'll have to skip the Discovery Grid farewell party, but I've never had close ties to that grid anyway.
OpenSimulator Community Conference starts today Hypergrid Business

HG Safari: Something for the Weekend

#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #DiscoveryGrid #OpenSimulatorCommunityConference #OSCC #OSCC2024 #OSCC24 There's no syntax for it on mastodon.social. You simply can't do it there.
Some users have already mentioned Markdown which is supported by a few Mastodon forks, Pleroma, Akkoma, Misskey and its several forks (including but not limited to Firefish, Iceshrimp, Sharkey and Catodon), Mitra, (streams), Forte and optionally also by Friendica, probably also by others.
For completion's sake, Friendica, Hubzilla, (streams) and Forte mainly use BBcode.
The syntax for quotes is either quoteHere goes the quote/quote or quote="Whoever is quoted"Here goes the quote/quote.
Both in-line code and code blocks are delimited with . At least Hubzilla can also do code highlighting if an appropriate plug-in is installed on the hub and the code tag has one of the following parameters: php, css, mysql, sql, abap, diff, html, perl, ruby, vbscript, avrc, dtd, java, xml, cpp, python, javascript, js, json, sh.
Lastly, (streams) and Forte even support HTML.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Markdown #BBcode #HTML #TextFormatting Well, what I meant with "do what I do anyway" is not what everyone else does.
My Fediverse meme posts have fairly standard image descriptions. What may make them long and complex are the explanations. They matter in this context because everyone else would explain meme images in the alt-text, but explanations don't belong into alt-text. And meme posts about Fediverse things do need a lot of explanation if they go beyond Mastodon, and mine tend to go way beyond Mastodon.
(Content warning: eye contact) was made under the assumption that Mastodon users prefer explanations given to them on a silver platter, right in the post itself which also contains the image. I was told a while ago that external links are bad and inconvenient and probably not accessible, and it's better to explain everything myself.
I always have to explain the meme template, and especially in this case, I also had to explain the topic. So I ended up with nine explanations on four or five levels with some 25,000 characters altogether, more than half of which went into the two explanations for the topic.
I couldn't imagine that this was actually what people wanted, seeing as it was generally Mastodon users who seemed to want me to explain everything, but at the same time, it's Mastodon users who complain the most loudly about long posts. And so on how people actually wanted meme posts to be explained. At least of the few who voted, nobody wanted explanations in the post if they end up tens of thousands of characters long.
Ever since, I've delegated the meme template explanations to KnowYourMeme which I link to.
As for the topic, (content warning: eye contact, guns) . Sometimes (content warning: eye contact, food) . Sometimes (content warning: eye contact) .
But in cases like (content warning: eye contact, swearing) or (content warning: eye contact, anger, crying, Japanese swearing) , I have to write extensive explanations, even if I can link to a whole lot of external information sources.
For my original images, renderings from very obscure 3-D virtual worlds, I do much more. I always write two image descriptions for each image.
One goes into the alt-text, and it's as long as I can make it within the 1500-character limit imposed by Mastodon, Misskey and their forks. And that's the short description that's mostly only there to satisfy the "every image must have alt-text, no matter what" fundamentalists.
There's also a long description in the post itself which is much, much more detailed. It also contains all necessary explanations which I have to write myself because I can't really rely on external links. And if there's any text anywhere within the borders of the image, legible or not, verbatim transcripts of all these bits of text go into the long description.
My most recent example, already on my new image-posting channel, but from four months ago, is (content warning: eye contact) . I've taken care to have as little scenery or surrounding or anything else in the pictures as possible, and still, I ended up with over 20,000 characters of image description. I explain why portraits are easier to describe.
A few examples with scenery, in chronological order, and much longer descriptions, and I consider them all outdated regardless: (content warning: eye contact, food) , (content warning: eye contact) and (content warning: eye contact) .
The first two links also demonstrate how I used to describe pictures within a picture, even on three levels in the case of the second link. But if I had carried on doing this the same way for the image behind the third link, I would have had to describe over a hundred images in various locations on at least four levels. Besides, I would have described details that not only aren't visible in the image, but that aren't visible either in the place shown in the image. Also, this might have revealed eye contact or another trigger of sorts.
So I decided against describing things that cannot be seen in the shown place. This was the first time that I actually imposed a limitation on myself.
I could post many, many, many more scenery pictures, maybe even with actual scenery and with many more details. But it would always take me days to describe one of them. The last two image posts I've linked to required two days to write descriptions.
For example, a month ago. It would have made for a gorgeous picture report. But it would have taken me at least a week and a half to only describe the four images that Mastodon would let through. In fact, Mastodon would have rejected the post anyway because, with the massive image descriptions, it would have exceeded 100,000 characters by far.
If you're wondering why my descriptions of virtual world images have to be so long and so detailed, .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta

Dolphins In Depth: Did Nick Saban issue a warning about Dolphins

I've spent two full days describing one image.
I feel bad when I can't describe something in an image the way I'd like to see myself describe it.
I keep coming across scenes that I think might make for nice pictures. But then I start trying to describe them in my head. And when I discover something that I can't properly describe, I don't even take the picture. I couldn't post it anyway without a description that's up to my standards.
I refuse to post images with realistic-looking buildings in them due to how complex they are to describe. After all, I'd have to first research architectural terminology and then explain it to my readers in the long image description.
A bit over a year ago, while working on an image description which, the next day (!), would , I realised that I had to describe three pictures of stellar nebulae. I didn't even really know how. I was about to abandon the whole image-posting project due to this. What I've eventually written still feels like a sub-par kludge, not to mention outdated a few times over.
I've read about people going back and alt-texting their entire backlog of image posts. I've wondered a few times if it is or should be recommended to go back and edit and improve your old image descriptions after you've learned something new in terms of describing images.
What do you think, is this genuine or not
And seriously, I don't even know whom exactly I'm doing all this for because I almost never get any feedback in any form. I do it for whoever comes across one of my image posts. Since my new channel for original images (which I do these monstrous descriptions for) has only got nine followers, and my channel for Fediverse memes (which at least tend to come with extensive explanations) has only seven, it has to be a very rare occurrence that someone who really needs an image description finds one of my image posts.
But I guess the ultimate solution is to forget about "" and do what I think is right until too many people come complaining. Which will probably amount to indefinitely.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility I think that's part of the issue, even if it's unavoidable: There's no one way to please everyone. And the more niche and special your content is, the harder it becomes to please as many disabled people as possible.
There's a saying: "." Don't assume what disabled people may need. Ask them. Talk to them. Listen to them.
But I guess the attitude in the Fediverse is that everything is said, everything is defined, everything is set in stone, and it'll work in 100% of all cases. No need to talk about it. You're expected to know it. Just do it.
I mean, I could just carry on assuming, based on what I've read here and there, even if that's technically the wrong thing. I know that there are at least some people who enjoy what I do, for whom it may be helpful.
I could just go on doing that and improving that, for any definition of improving. I could go on until enough people complain to me that I'm doing it completely wrong, and that staggering level of detail is bad for magnitudes more people than it helps. But this is unlikely to happen, seeing as how little feedback I receive.
I mean, at the end of the day, I can't really know whom I describe my images for. Do blind or visually impaired users even come across my image posts, seeing as they come from two different channels than this one now Do those come across my image posts who demand sanctions for everyone who doesn't describe their images sufficiently Are my extensive image descriptions and explanations useful for anyone
Still, I go on putting huge efforts into describing them for the random stranger who stumbles upon one of them on some federated timeline, regardless of whether they're visually-impaired, blessed with a terribly slow Internet connection or a fully sighted alt-text enforcer.
And I will most likely go on increasing my efforts where I can. I'm currently polishing my way of describing persons or rather avatars. After all, I can see the alt-text quality requirements in the Fediverse be constantly raised, too. I need to stay ahead of them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #AccessibilityApparently, accessibility is not about trying as hard as you can. It has to be about trying exactly the right amount of hard without even knowing what the right amount is because the right amount is different for everyone.
For the record: I refuse to post any image without sufficient description. And "sufficient description" may mean two descriptions, a short (and still long) one in the alt-text, a massive one in the post. If I can't describe it properly, I don't post it. And I'm trying to up my game and add new tricks and new elements to my descriptions.
On the one hand, disabled people demand being involved in the topic of accessibility. Before you do something, consult with those whom you want to help. Don't just simply assume what they may need. Ask them. Discuss things with them.
On the other hand, apparently, asking too much will get you branded ableist, all the way to your home instance with over users being on the brink of a fediblock.
Here's a comment I've written on by . I've directed it to a blind user whom I may have asked once too much.
Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Here is his reply in which he claims I'm an ableist who actually doesn't want to describe images. This is far from the truth.
You really don't think I remember you do you You ask this question every single time in an attempt to badger users like me into getting away with *not* providing alt text because you wanna be ableist but try to pass it off as perfectionist. You will *never* please everybody, so to even try and to even is patronizing and ableist all by itself. I consider you to be nothing more than a troll. Look dude, if you don't wanna provide alt text then don't fucking provide it, but don't insult my intelligence with this obvious C lion tactic of I'm a perfectionist. I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.
Here is my reply.

I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.

If I didn't care for accessibility, if I didn't want to describe my images, why would I want to satisfy everyone, all the way to random strangers who stumble upon my posts in some federated timeline I shouldn't even want to satisfy anyone!
Why would I spend literal days, morning to evening, Twice per image
Why would I refuse to even take pictures, let alone post them, if they'll be too difficult to describe in a way that I consider sufficient
Why would I pick up any advice on how to describe certain things, like people or colours, and consider any of my image descriptions that don't have this incorporated hopelessly outdated
Why would I transcribe text that's too small for sighted people to read, just because all text in an image has to be described Why would I feel bad about text that I couldn't transcribe and then try to find a source for that piece of text And yes, I do.
Why would I be literally the only one in the entire Fediverse who tries to tell people that and why explanations don't go into the alt-text because people with certain disabilities can't access alt-text, and any information that's only available in alt-text is lost to them
And why would I warn sensitive people about eyes or food that's in the image on a microscopic sub-pixel level if I didn't care And yes, I actually did that. .
Just because I don't just simply shut up and describe my images exactly on point like you personally want them described, doesn't justify insulting me as an ableist.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism
In the meantime, he wrote and sent this post in which he called for a fediblock of either my channel or the entirety of hub.netzgemeinde.eu, the biggest Hubzilla instance.
Link at end. I'm unsure if is on his own instance, but for concerned trolling and ableist behavior by being patronizing to disabled people about alt text. I can't find others on his instance, but every, single time, the person posts the same question over and over and over and over and over and over and over and over and over and over and over again, and expects disabled people to tell this person because you can't describe every thing in an image you don't have to do alt text. Or maybe my temper is just short today, but here's the question. This isn't genuine curiocity because he asks the, same, question, over and over and over and over and over and over and over and over and over again. No answer is to his satisfaction. Nobdoy waste your time with this obnoxious troll. If it turns out I am lashing out of anger and have misjudged, will delete the post but
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuoteBoost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #A11y #Accessibility #Ableist #Ableism #FediblockMeta

I should have blocked you the first 900 times you asked this fucking obtuse/C lioning/ ableist / patronizing question. If you don't wanna provide alt text, just don't do it and never ask me this question again.

Sometimes its really difficult on Mastodon to follow a thread. Are you saying Hubzilla does that better

Yes, because by default, Hubzilla always displays entire threads at once. Start post on top, ~~replies~~ comments neatly listed below in chronological order. Just like Facebook does. Just like Tumblr does. Just like a blog does. Just like a forum does. Only that if there are more than three comments, Hubzilla only shows the most recent three until you roll out the whole thread.
The Mastodon piecemeal way of making each reply into its own post and showing them one by one as separate items is optionally available, but I've got my doubts that anyone has actually ever used that feature.
I'd show screenshots, but I don't have enough time to adequately describe them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla

Sometimes its really difficult on Mastodon to follow a thread. Are you saying Hubzilla does that better

from those whom you follow
if you're mentioned
if someone whom you follow boosts them

Here on Hubzilla, and actually in the whole family from Friendica to Forte, it's vastly different. Here, a conversation is an enclosed object. A thread, any thread, has exactly one post. That's the start post. Everything else is not a post, it's a comment.
This also means that Friendica, Hubzilla & Co. don't serve you single activities like Mastodon serves you single posts. Threads aren't piecemeal here. Threads come in one piece.
Instead, when you have a post (remember the distinction, "post" only means start post, as in something that isn't a reply to anything else) in your feed/timeline/stream, you also receive all comments on that post. Still under the same post and not as separate activities, not by default anyway.
It's like on Facebook or a blog or in a forum. After all, Friendica, the oldest member of the family, was created as an alternative to Facebook more than five years before Mastodon was made.
There's another big difference between Mastodon on the one side and Friendica, Hubzilla, (streams) and Forte on the other side: The latter four have an unread activities counter and an unread activities list. Mastodon doesn't have either. Mastodon doesn't even have a concept of unread.
On Mastodon, you go to your timeline, and you scroll down until you either hit something that you know you've already read, or you don't have any time anymore, or you don't want anymore. What you don't scroll down to, you will never know you've ever received it.
Here on Hubzilla, I have a counter of unread activities at the top of the the right-hand sidebar. It includes

unread posts on my stream
unread comments on something I have on my stream
unread edits something I have on my stream
unnoticed reposts/boosts/renotes/repeats of something I have on my stream
unnoticed likes/dislikes for something I have on my stream (in theory I've turned this off)

The counter stops at 99, though. If it's 100 or more, the counter shows "99+".
If I open the counter, I get a list of all unread/unnoticed activities. I can apply a filter that only shows me new posts with one click. It's only a list, though it's not the actual activities like in a Mastodon timeline. It only lists up all these activities so I can load them manually.
So what I usually do first is apply the posts-only filter. Then I scroll down to the oldest item on the list. I click it. In the middle (we were in the right-hand sidebar until now), the post with that activity is shown, complete with all comments known to my stream, like a post on Facebook or a blog post with its comments neatly listed right below.
Now, let's suppose this post came with 68 comments and 11 repeats (that's "boosts" in Mastodonese). That's one unread post, 68 unread comments, 11 unnoticed repeats, all loaded and read/noticed in one fell swoop. The unread activites counter goes down by 1+68+11=80 items.
And then I go on with the next new post.
Once I'm through the new posts, I turn the filter off again, and the unread activities list shows me everything that isn't a new post.
I scroll down again. I click on the bottom-most item. Whatever it is, it loads an entire thread with a post and, if there are any, its comments. And whatever was in this thread that I hadn't paid attention to yet is flagged read and removed from the unread activities list, and the counter goes down by that number again.
Now, my situation as described in the post (again, posts vs comments from a Hubzilla point of view) is that the official Mastodon account or Eugen Rochko or some Mastodon devs (intentionally not mentioning either) tend to post stuff which is then boosted by , and which may receive well over 100 replies.
Now let's suppose Eugen Rochko posts something, and Fediverse Report boosts it, and it gets 280 replies. Let's also suppose I only follow Fediverse Report.
On Mastodon, I'd only receive Eugen's post in my timeline. That's it. Unless, of course, someone mentions me in one of the replies, or someone decides to boost one of the replies to me. Then I also receive that one reply. Separately.
Here on Hubzilla, I receive Eugen's post and all 280 replies in my stream. That's 281 unread activities, and that doesn't even include boosts and edits. That's at least 281 pieces of uninteresting clutter on my unread activities list. Granted, when I click one of them, the whole thread loads, and 281 pieces of uninteresting clutter are marked read and removed from the list, and the unread activities counter goes down by 281. And I no longer have to wade through all that clutter to find the actually interesting content.
But I don't necessarily want to see that gunk. I don't want to click it.
And so I've Superblocked the official Mastodon account and the official Mastodon Development account and Eugen Rochko and some devs. In fact, I've also Superblocked a few more Mastodon users who tend to attract replies like lamps attract moths, just in case someone whom I've given permission to send me their boosts (yes, I can disallow that for individual contacts) boosts something from one of them.
Now I don't receive the actual content anymore. But if someone boosts something from someone Superblocked to me, it still shows up on the unread activities counter. It and all replies to it. If Eugen Rochko (Superblocked) posts something, Fediverse Report (not Superblocked, allowed to send me boosts) boosts it, and it gets 280 replies, that's still 281 unread items on the list.
The catch: Since Eugen Rochko's post is blocked, so is the whole thread. I can't load his post, and I can't load any of the replies either because loading any reply would require loading the post. Remember that replies aren't piecemeal here on Hubzilla, unlike on Mastodon.
And if I can't load them, I can't have them marked read the natural way. Mind you, I do have a "Mark everything read" button. The only way to mark that stuff read. But if I used it, I'd also mark the interesting unread stuff read.
So I have to scroll through a list of hundreds of unread replies to Eugen Rochko's post and boosts of such replies and whatnot to find the halfway interesting stuff, pick it out, click it, load it, read it, interact with it etc. Then more scrolling until I find something interesting again. Wash, rinse, repeat.
Only when everything on the list of unread activities is from threads starting with blocked posts, I can click "Mark everything read".
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte That's good.
I've asked because I've got the feeling that alt-text/image description requirements are constantly being refined and raised in the Fediverse, and more and more existing descriptions won't pass anymore.
See, I usually spend hours on meme posts, both describing the image in the alt-text and explaining it in the post. As for my original images, it can take me days to describe them twice over, once in a "short" description in the alt-text that's actually already fairly long, once in a "long" description the size of an essay or even a short story in the post itself.
And I'm honestly waiting for the first to be so dissatisfied with that that they reply with their own alt-text and order me to both replace my alt-text with theirs and remove the long description from my post or else.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Neither is this about DMs (it's about posts from the Mastodon team (almost all of whom I've superblocked) boosted to me by Fediverse Report (which I haven't blocked)).
Nor am I using Mastodon (click my name and look at my profile if that doesn't convince you, also, Mastodon can't create embedded links).
Nor does Hubzilla (where I am) support any proprietary Mastodon APIs, nor are the devs willing to add support for any proprietary, non-standard Mastodon stuff. Which is actually good.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla Honest question from an alt-text and image description perfectionist to a blind user: When is it actually accessible enough that whoever posts an image doesn't have to fear repercussions
Okay, there has to be an alt-text. It has to actually describe the image. So much is clear to me.
And I guess that while at least some blind people in the Fediverse treasure whimsy higher than accuracy, others may want alt-text to be accurate.
But it looks to me like there is a rather narrow margin between alt-text with not enough details and alt-text that's too long and/or too detailed. This isn't communicated anywhere. It's unclear, too, whether that margin is always the same, or whether it shifts with the content of the image, the context and someone's individual idea of who the audience of an image post is.
And seriously, there are images that simply cannot be described in a way that's perfectly ideal and useful for absolutely everyone out there. I've posted such images in the past, and my image descriptions must have broken all length records in the Fediverse. But I think not everyone is happy about having to read through such monsters.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

Last updated: 2024-12-14

The Long Drive

thought