VOA Correspondent Kane Farabaugh Reflects on

VOA Correspondent Kane Farabaugh Reflects on Long Relationship with Former President JimmyCarter

For 17 years, VOA Correspondent Kane Farabaugh has covered the life and legacy of Jimmy Carter, developing a close friendship with Americas 39th president. He shares his personal reflections about the late world leader and influential humanitarian.

Kleiner Hinweis: Der Crash der Schwarzen Witwe an der Kreuzung war ein echter Unfall. Die Szene, in der der Konvoi zgig ber diese Kreuzung kurven sollte, war eigentlich entworfen fr leere Laster mit tiefem Schwerpunkt, und alle anderen Laster im Film waren leer. Die Schwarze Witwe hatte als einzige auf ihrem Laster Ladung, weil ein leerer Flachauflieger bld ausgesehen htte. Damit war der Schwerpunkt aber fr die schnelle Kurvenfahrt zu hoch.
Die Szene, wo der Laster umkippt, hat man kurzerhand dringelassen, obwohl sie eigentlich fr die Handlung sogar hinderlich war. Aber zu Actionfilmen gehren eben spektakulre Crashszenen, und da haben sie einen Crash frei Haus geliefert bekommen. Die Stelle, wo die Schwarze Witwe sich nach dem Crash ber den Laster beschwert, ist genauso geadlibt wie fast alle anderen Dialoge im Film.
Im Originalton heit die Schwarze Witwe brigens "Widow Woman", und im Drehbuch ist sie nicht ausdrcklich schwarz. Sie wurde nur eben von Madge Sinclair gespielt, die zufllig schwarz war.
Spider Mike wiederum sollte von vornherein den Stereotyp des "armen Niggers" bedienen, der als Fernfahrer mit Familie sowenig Geld zur Seite schaffen kann, da er immer noch eine Zugmaschine aus den 60ern fhrt. Genau dieser Stereotyp war damals in den spten 70ern im lndlichen Sden der USA noch allgegenwrtig.
Genauso allgegenwrtig war da auch der Rassismus bis hin zu rassistischen Polizisten, wie der Sheriff von Alvarez sie verkrpert. Guck dir den Film mal aufmerksam an und achte mal drauf, wie Lyle Wallace reagiert, als er sieht, wie der Sheriff von Alvarez Spider Mike zugerichtet hat. Der sollte Spider Mike eigentlich nur rausziehen und inhaftieren, aber nicht zu Mus prgeln.
Das war also Absicht. Und die Absicht war, den damals allgegenwrtigen Rassismus anzuprangern, ebenso wie die brutale Selbstjustiz, zu denen damals schon Kleinstadtsheriffs neigten (siehe auch Rambo oder Flashback).
Lyle ist brigens kein Rassist. Er hat nur Trucker, und zwar alle. Er stellt ihnen Fallen und lockt sie dann mit schmutzigen Tricks rein, was wahrscheinlich auch in den USA und speziell in Arizona illegal sein drfte. Der Grund, warum er Spider Mike am Anfang des Films sein ganzes Bargeld abknpft, ist, weil Mike eine groe Klappe hat.
berhaupt mag ich die Charaktere in dem Streifen.

• Lyle Wallace, der truckerhassende Sheriff, der in seinem Wahn nicht wei, wo Schlu ist, nicht mal an der Grenze von Natosha County, Arizona, auerhalb von der er eigentlich gar keine Befugnisse hat, dessen Grenzen wir aber in Alvarez sehen
• Rubber Duck, der zufllig zum Leithammel eines riesigen Konvoi wird, der aber keinen Bock hat, fr irgendwen auer sich selbst Verantwortung zu bernehmen, und seinem persnlichen Konflikt mit Lyle noch einen draufsetzt, indem er was mit Lyles Frau hat, was Lyle nicht mal merkt
• Lovemachine Pigpen, der mit seiner mehrfarbig metalliclackierten Zugmaschine nebst Wasserbett am CB den groen Zampano mimt, aber besagte Klappe nicht aufkriegt, wenn's drauf ankommt
• Melissa, die offensichtliche Grostdterin, die in Arizona liegenbleibt am Steuer eines Exoten, fr den es im ganzen Bundesstaat und auf jeden Fall die nchsten sechs Wochen keine Ersatzteile gibt, die aber als einzige sowas wie diplomatisches Geschick hat
• Jerry Haskins, der Gouverneur von New Mexico, der Trucker eigentlich auch nicht leiden kann und Rubber Duck aus rein wahlkampftaktischen Grnden ausnutzen will, um nach D.C. zu kommen abgesehen davon stnde er als Gouverneur nicht gut da, wenn der Konvoi oder ganz speziell Rubber Ducks rollende Bombe in seinem Bundesstaat eine mittelschwere Katastrophe auslsen wrde
• der Verschwrungstheoretiker in dem Wohnmobil, aus dessen Geschwurbel die Grnde, warum er im Konvoi mitfhrt, auch nicht ersichtlich sind

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #Convoy

Und btw, der Selbstvergleich mit echten Marginalisierten besttigt schlimme Vorurteile und geht gar nicht!

Doch, der Vergleich geht sehr wohl. Und ich werde darber noch einen Post schreiben.
Nicht-Mastodon-Nutzer sind im Fediverse nmlich lngst real marginalisiert. Wie gesagt: Nur weil reine oder weit berwiegende Mastodon-Nutzer das nicht sehen, heit das nicht, da es nicht passiert.
Es ist nicht okay, jemanden wegen Hautfarbe, Geschlecht, sexueller Orientierung oder Behinderung zu marginalisieren. Viele Weie bzw. Cishet-Personen tun das aber unbewut, und einige tun das mit voller Absicht.
Aber es ist ebensowenig okay, jemanden dafr zu marginalisieren, wo er oder sie im Fediverse ist. Viele Mastodon-Nutzer tun das aber unbewut, und einige tun das mit voller Absicht.
Frag den Calckey-Nutzer . Dem hat mal ein Mastodon-Nutzer gesagt, er solle geflligst seine Posts auf maximal 500 Zeichen limitieren oder sich aus dem Fediverse verpissen.
Auch ich bin schon so manches Mal angepampt worden, weil meine Posts ber 500 Zeichen lang sind, und davon auch so manches Mal direkt danach blockiert worden.
Frag den Friendica-Nutzer . Den hat mal eine Mastodon-Nutzerin blockiert, ganz einfach, weil er nicht auf Mastodon war. Sie dachte, er sei ein bser Hacker und Friendica ein bses Hackertool, mit dem er sich verbotenerweise ins Mastodon-Fediverse reingehackt habe.
Guck dir die ganzen Entwicklungen an, die "Fedi" oder "Fediverse" im Namen haben, die aber knallhart ausschlielich gegen Mastodon gebaut sind und deren Entwickler keinen Bock haben, daran was zu ndern.
Klar, jetzt knnte man sagen: Die Hautfarbe kann man nicht whlen. Auch eine Behinderung kann man nicht wegwhlen. Man kann sich selbst auch nicht dazu zwingen, cisgender oder heterosexuell zu sein. Man kann aber die Fediverse-Software jederzeit frei whlen. Von daher hinkt der Vergleich ganz gewaltig.
Das hiee: Man knnte selbst dafr sorgen, da man im Fediverse akzeptiert und nicht marginalisiert wird, indem man einfach wie die gewaltige Mehrheit Mastodon nutzt und nicht irgendwas anderes. Man kann es ja frei whlen, was man nutzt.
Nur knnte man dann eben nicht mehr frei whlen, was man nutzt, wenn man akzeptiert werden will. Wenn man akzeptiert werden will, htte man zu Mastodon, und zwar Vanilla-Mastodon mit 500-Zeichen-Limit, keine Alternative mehr.
Viele von uns wollen Mastodon aber eben gerade nicht nutzen, weil ihnen da essentielle Features fehlen wrden, die sie auch fr mehr Akzeptanz nicht bereit wren aufzugeben.
Da kann und sollte man als Mastodon-Nutzer nicht einfach mit der Schulter zucken und sagen: "Ja, dann seid ihr eben selber schuld, wenn ihr gemobbt und diskriminiert werdet." Ebensowenig kann man als Mastodon-Nutzer weiterhin mit der Schulter zucken und sagen: "Ich sehe nicht, da ihr irgendwo diskriminiert werdet, also sind das nur Hirngespinste, und niemand mu irgendwas anders machen."
Statt dessen mu generell damit aufgehrt werden, das Fediverse als nur Mastodon zu verkaufen. Auch in Medien mit mehr Reichweite. Auch Neulingen gegenber, damit die sich von vornherein daran gewhnen, da einige Leute im Fediverse Sachen nutzen, die total anders sind als Mastodon, und das vllig normal ist. Jeder sollte auch wissen, da das Fediverse auch nicht mit Mastodon anfing.
Neuentwicklungen im Fediverse, von denen das ganze Fediverse profitieren knnte, drfen nicht mehr nur gegen Mastodon gebaut werden, sondern sie mssen projektneutral gestaltet werden.
Das Fediverse braucht wieder eine neue Kultur. Die Kultur von 2022, die nur Vanilla-Mastodon bercksichtigt, mu ersetzt werden durch eine, die alles bercksichtigt.
Niemand darf mehr dafr attackiert werden, Posts zu schreiben, die auf Vanilla-Mastodon so nicht mglich sind (ber 500 Zeichen, Textformatierung, Listen etc.). Niemand darf mehr dafr attackiert werden, auf Posts oder Kommentare zu reagieren, die der- oder diejenige aus Mastodon-Sicht nicht auf natrlichem Wege htte empfangen knnen.
Quote-Posts mssen als unverrckbarer Teil der Fediverse-Kultur anerkannt werden. Auch wenn Mastodon sie nicht hat: So ziemlich alles, was nicht Mastodon ist, hat sie. Jetzt. Das Fediverse hatte schon Quote-Posts fnfeinhalb Jahre, bevor es Mastodon gab. So ziemlich alles, was nicht Mastodon ist, kann auch jederzeit Mastodon-Trts quote-posten. Und es sollte auch anerkannt und akzeptiert werden, da eine mastodoneigene, mastodoninterne, auf keinem Standard aufbauende Opt-Out- oder Opt-In-Funktion nicht fediverseweit funktionieren kann und wird.
Die Fediverse-Kultur darf keine Funktionen zwingend erforderlich machen, die Nicht-Mastodon-Anwendungen evtl. nicht haben. Beispielsweise CWs la Mastodon in Kommentaren, die von Hubzilla kommen. Oder "Unlisted", das es auch lngst nicht berall gibt.
Die Fediverse-Kultur darf keine Funktionen oder Features verteufeln, die Mastodon nicht hat. Beispielsweise Posts mit mehr als 500 Zeichen oder Zusammenfassungen in dem, was auf Mastodon das CW-Feld ist, oder Textformatierung oder Posts mit eingebetteten Bildern, die auf Mastodon "komisch" aussehen, weil die Bilder eben nicht mehr eingebettet sind.
Die Fediverse-Kultur mu aufhren, Mastodon als den Standard anzusehen und danach zu agieren. Und nein, Nutzerzahlen definieren keinen Standard. Nein, tun sie wirklich nicht.
Die Fediverse-Kultur mu aufhren, alles, was nicht wie (auf) Mastodon ist, als entweder kaputt oder falsch oder bse darzustellen.
Und jeder Mastodon-Nutzer, der sich jetzt in eine Defensivposition begibt, um Mastodon und die mastodon-normative Fediverse-Kultur zu verteidigen, ist aktiver Teil des Problems.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #Diskriminierung Es ist doch immer so.
Irgendjemand auf Mastodon behauptet aus felsenfester berzeugung, das Fediverse sei nur Mastodon oder sogar, wie hier, Mastodon sei das einzige dezentrale soziale Netzwerk, das je existiert hat.
Sich darber beklagen tun nur Nicht-Mastodon-Nutzer. Von den Mastodon-Nutzern wei es mindestens eine Hlfte auch nicht besser, und der Rest strt sich nicht an der Aussage.
Und wenn sich Nicht-Mastodon-Nutzer darber beklagen und mit Widerworten kommen, heit es von den Mastodon-Nutzern gerne: "Ist doch scheiegal, reg dich nicht auf, ist doch nicht so schlimm, wieso berhaupt die Aufregung"
Wohlgemerkt, von beiden Sorten von Mastodon-Nutzern. Die einen haben gerade eben erst von den Nicht-Mastodon-Nutzern zum allerersten Mal berhaupt davon gehrt, da das Fediverse noch was anderes sein soll als Mastodon. Den anderen ist alles, was nicht Mastodon ist, einfach scheiegal.
Und dann gibt's da noch die Mastodon-Fundamentalisten. Die halten gerne wacker dagegen. Die einen tun das aus Rechthaberei, um zu verhindern, da diese Nicht-Mastodon-Nutzer sie ungefragterweise eines Besseren belehren. Das nennt man nmlich auch "Fedisplaining". Die anderen tun das, damit das Fediverse um sie herum zumindest gefhlt weiterhin nur Mastodon bleibt. Zwischen den beiden Gruppen gibt es eine groe Schnittmenge.
Da werden Nicht-Mastodon-Nutzer schon mal angegriffen. Da wird schon mal behauptet, da es die Nicht-Mastodon-Nutzer seien, die falsch lgen, und ja, es gbe tatschlich ein in sich geschlossenes "Mastodon-Netzwerk", und schlimmstenfalls sogar, das Fediverse wre per definitionem tatschlich nur Mastodon, weil Eugen Rochko das doch erfunden hat und so weiter. Und es wird fleiig stummgeschaltet und blockiert in verzweifelten Versuchen, die Nicht-Mastodon-Nutzer fediverseweit mundtot zu machen.
Leider ist es tatschlich so: Je reichweitenstrker und einflureicher Mastodon-Nutzer sind, desto weniger scheren sie sich um das Fediverse auerhalb von Mastodon. Es gibt Fediverse-"Influencer" und Leute, die sehr viel im Fediverse ber "das Fediverse" schreiben, die laufend so tun, als sei das Fediverse nur Mastodon. Da kann man dagegen kommentieren, soviel man will, die machen damit so weiter.
Inzwischen ist es im Fediverse fr Nicht-Mastodon-Nutzer hnlich wie fr Schwarze, Schwule oder Transpersonen. Im Fediverse gilt der weie Cishet-Mann auf Mastodon als der Standard. Und wenn z. B. Schwarze oder Schwule, aber auch Nicht-Mastodon-Nutzer von sowohl Unterdrckungstendenzen als auch von tatschlichen Angriffen schreiben, ist die Reaktion von Weien, Heten und Mastodon-Nutzern immer: "Nee, kann ich mir nicht vorstellen, da das passiert. Hab ich nie gesehen, und ist mir auch nie passiert. Ist doch alles nur Einbildung/nicht so schlimm."
Natrlich nicht. Wer selbst wei/hetero/auf Mastodon ist, ist selbst kein Ziel, und wer in einer Bubble lebt, in der jeder wei/hetero/auf Mastodon ist, bekommt auch nichts davon mit.
Das Fediverse stellt sich selbst ja gern als Ort dar, der fr alle offen ist, der alle willkommen heit, und an dem sich jeder frei entfalten kann. Leider gilt das immer weniger fr Leute, die nicht auf Mastodon sind. Und die Mastodon-Mehrheit bemerkt diese Art von Unterdrckung noch am wenigsten.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon It could.
But it was the intention of the creator, Mike Macgirvin , for all his works to be under the MIT license. The current Hubzilla maintainers, Mario Vavti and Harald Eilertsen, certainly won't relicense Hubzilla under the GPL in any shape or form, otherwise they would have done that.
It isn't even worth doing so just to have code from Friendica. After all, Friendica's backend is vastly different from Hubzilla's. Friendica is based on a mixture of ActivityPub and its own DFRN whereas Hubzilla is based on Zot with ActivityPub available through an optional add-on. On Friendica, your account is your identity it doesn't have Hubzilla's channel model, nor does it have nomadic identity.
Red came to exist by Mike forking Friendica and rewriting the whole thing against his new Zot protocol. Hubzilla hardly has any old Friendica code left over. So it's safe to assume that Friendica's code is incompatible with Hubzilla anyway.
Generally, there's nothing on Friendica that'd be worth taking over for Hubzilla. Not even themes because theming works entirely differently on Hubzilla.
Asking Mario and Harald to relicense Hubzilla under any form of the GPL is as likely to succeed as asking them to implement all kinds of proprietary Mastodon stuff to make Hubzilla more compatible with Mastodon and Mastodon apps:
Not going to happen.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #MITLicense #GPL #AGPL I guess one reason is to make it easy to adopt code from Hubzilla or fork it.
Friendica, which Hubzilla was forked from, used to be under the MIT license itself until the community relicensed it to the AGPLv3 post-fork. This, however means that while Friendica can theoretically use code from Hubzilla (if it can make that code fit), Hubzilla can't adopt code from Friendica.
The youngest publicly-used member of the family, , a fork of a fork of three forks of a fork (of a fork) of Hubzilla, was intentially released into the public domain, save for third-party add-ons in the official add-on repository under different licenses. The idea was to make forking it into FLOSS easy and forking it into something proprietary a nightmare.
I think it's fair to mention that everything from Friendica to (streams) came from the same creator who has been developing software for a living since the 1970s.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) Es gibt auch noch . Das basiert auf etwas, was (streams) vor etwa einem Jahr eingefhrt hat. Bis dahin hatte (streams) dasselbe Konversationsmodell wie Hubzilla, das wieder dem von Friendica hnlich ist. Und vor einer Woche hat Hubzilla selbst Conversation Containers eingefhrt.
Davon mal abgesehen knnte das gesamte Threadiverse (Lemmy, Mbin, PieFed...) ohne ein Konzept von Konversationen auch nicht funktionieren.
Es geht also schon. Auch mit reinem ActivityPub. Die Entwickler mssen nur wollen. Aber Mastodon will im Grunde nichts, was Twitter vor Musk nicht auch hatte.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #ConversationContainers #FEP171b I do hope the "Mastodon equals Fediverse, and it must stay this way" crowd won't push only having one account and one identity in the Fediverse into the same "Mastodon culture" that's being forced upon the whole Fediverse by some Mastodon fundamentalists.
That would essentially "outlaw" two features that almost nobody in the Fediverse has ever heard of, but that have been available in the Fediverse for longer than Mastodon itself, both introduced by a Friendica fork from 2012 named Red, known since 2015 as . And at least three out of four Fediverse users have never even read that name before.
One feature is : You can have "clones", live, hot, bidirectional backups of your Fediverse identity on multiple server instances. Imagine having copies of your Mastodon accounts on other servers, but these copies include everything (posts/DMs, followers, followeds, settings, timelines, filters, lists etc. etc.), and these copies keep each other in sync all the time whenever something happens on them. That's nomadic identity.
You can long into your clones and use them just like you can use your main instance. You can make one of your clones your new main instance. Your Fediverse identity is safe from vanishing with the shutdown of a Fediverse server. And other servers that understand nomadic identity see all instances of your identity as one.
Currently, at least to non-developers, nomadic identity is only available on Hubzilla, using Zot, and (streams), using Nomad, and you can only clone between instances of the same server software. But the implementation using ActivityPub is being worked on, and the goal is to one day be able to have the same identity on servers of different applications.
Nomadic identity not only fulfills the dream of being able to move between instances with everything, but it goes way beyond. In many cases, it means you don't even have to move.
Nomadic identity means that you've got multiple accounts, but one identity.
The other feature is a byproduct of the creation of nomadic identity: multiple identities on the same account, the same login. Hubzilla and (streams) call them .
It actually makes sense to have multiple of these because (streams) channels can be versatile and Hubzilla channels even more so. On both, you can run a channel as a public or private discussion group. Or you can run a channel as you personal WebDAV/CalDAV/CardDAV server that's independent from your main social networking identity. Or you can run a channel as a blog that's separate from your main social networking identity. Or, on Hubzilla, you can run a channel as a wiki or a website.
You can run as many channels on one account as you want. The advantage of having multiple channels on one account over having one account per channel is that you can switch between channels without having to log out and back in.
In both cases, your Fediverse identity is detached from your login. A concept completely alien to most of the Fediverse. And I guess the only reason why Hubzilla users aren't mass-blocked for this is because sensitive Mastodon users often don't notice any of this.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadicIdentity

I went to the Cobra museum and unexpectedly bumped into an exhibition by Jeroen Krabb. Most Dutch know him as an actor, but in addition Ive enjoyed seeing his work now and again since the early 90-ies. Yesterday I learned hes third generation painter and already started as a painter way before his acting career. One of the exhibits was a movie of all the pages of a notebook his dad made for him for a trip to Paris. A trip it was. 5/2017

Dolphins In Depth: Could Sunday be Calais Campbells final game in a Dolphins uniform

It isn't just because of compression, nor is it because I scale my images down from my original 2100x1400 renderings to 800x533.
As I've said: I don't describe the image with the things in it. I describe the things. Not as they appear in the image, but as they are in-world where I can walk closer to them or move the camera closer to them. It's like an image with a near-infinite resolution.
For example, if there's a light grey blob in the image, four pixels wide, three pixels high, I describe it as what it is in-world, a white sign with three lines of black writing on it. I transcribe the text on the sign 100% verbatim including all spelling mistakes, I translate it afterwards if it isn't in English, I may even explain the text if someone out there needs an explanation, and I may go as far as naming and describing the typeface.
Or if there are two by two pixels on different levels between red and white, I describe them as what they are in-world, a strawberry cocktail in a conical glass, somewhat like a Martini glass. And I slap an "alcohol" content warning on the whole post. Nowadays, I'd even flag the image sensitive just because of these four pixels.
I used to go as far as describing images within my image and even images within images within my image at higher levels of detail than anyone else would describe their own images. I used to describe things that weren't even visible in-world in the place shown in the image. Pictures of places that I would have to walk or even teleport to to be able to describe them. Textures that I would have to make visible otherwise to be able to see all details.
The last time I've described an image in an image with details not visible in the place shown in my image was in . I used almost 5,000 characters to describe a poster on the info board. I had to walk to the place displayed in the image on the poster to be able to describe it. The description of the image within the image got so lengthy that, when I was done, I had to remind the reader that I'm returning to describing "my" image. And I actually "cheated" by adjusting the camera in such a way that one of the three posters on the info board is entirely concealed behind a tree trunk because it would have been painfully difficult to describe.
I stopped going that deep when I wrote the image description for . The long description was already growing absolutely humongous, and it's my longest one to date with over 60,000 characters. I had actually thought this scene would be easy to describe.
The problem I encountered was that there were simply too many images within images within my image. There's one teleporter near the left-hand edge with a preview image that made me reconsider. In-world, no matter how close I move the camera to the preview image, it mostly shows a square area that appear to be tan all over except for something dark and unidentifiable in the middle.
Actually, however, the place shown in the preview image has hundreds of single-destination teleporters. Several dozen of them are activated and have one preview image each of their destination. I teleported there to take closer looks at everything. I was actually about to write a description of that "teleport station" when I realised that I also had to describe every single one of these preview images, at least those that face the camera in the preview image on the teleporter in the place that I was originally describing. And some of these preview images had images in them in turn.
I would have had to describe probably over a hundred images. In dozens of images. On teleporters which are shown in yet another image on a sub-pixel level. In an image description which was already going out of hand length-wise. On the second day that I was working on that image description. I would have had to teleport at least three times from the place shown in my image to be able to describe these sub-sub-subimages.
That was when I decided to sacrifice details for convenience and only describe what's visible in-world within the borders of the image, excluding both objects that are entirely obstructed by something else and surfaces that entirely face away from the point of view. I do fully transcribe any text that's partially obstructed, though, although I'm considering two transcripts of such texts, namely one transcript of what's visible and one full transcript for better understanding.
#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta I always consider "let them ask if they want to know" bad style for such elementary information. It seems to me like one of these things where Mastodon's good alt-text proponents may criticise you for not mentioning it right away.
That is, I wouldn't put that information into the alt-text. I only have about 900 or 1,000 characters at my disposal for describing an image in alt-text. Mastodon, Misskey and their forks chop alt-texts over 1,500 characters off in posts from outside, and I need the rest of the characters to explain where a longer and more detailed description can be found for as long as there are still instances of Mastodon under 4.4 around.
This is information that would go into said long description. I've always put the long description into the post itself where I technically don't have any character limits. The limit of 100,000 characters above which Mastodon may completely reject posts is not much to worry about either as long as I don't have multiple highly detailed images with little in common to describe.
Leaving out the information where an image is from, unless I have very good reasons to keep the location secret, feels like not giving a long description at all. And not giving the long and detailed description, in the case of my original images, is like omitting the alt-text for "normal" images entirely.
I've asked the above question because I have a series of images which are special cases. If surroundings were visible in the images and not too generic, I would definitely explain where the image was made, not although, but because next to nobody in the Fediverse could tell from looking at the image where it was made because even the sighted users would never have seen anything like it before.
I want to give everyone in the Fediverse the chance to see the image not only like any sighted person sees it, but like I see the original. This is also why I describe details and transcribe text so tiny that they're basically invisible in the image at its given resolution.
But in this special case, the images don't carry any information at all on where they're from. In other words, the information where they're from might be completely useless. Or it might not.
#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #Inclusivity #A11y #Accessibility

New entry of AI-generated and added to our :

A 's

For nikokenox
Art by me

Now I'm wondering again:
Let's suppose I have a series of 3-D virtual world images that have a plain white background because they were intentionally created in front of a plain white background. It's impossible to tell from the images where they were made, and when I post them, it won't matter within the context where they were made.
Any chances that someone out there might still want to know where exactly I've made these images Either someone who doesn't know about these worlds, and who is totally curious about them, or one of those probably fewer than 20 Fediverse users who does know about these worlds, and who wants to know where I've gone to make these images
I can easily spare the few hundred extra characters. The only character limit I have to worry about are the 100,000 characters above which Mastodon probably rejects a post from outside.

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #Inclusivity #A11y #Accessibility Of course, what details need to be described depends on the answer to this question:
Is there a chance that someone who can't see the image might be curious about what an element in the image looks like while definitely not knowing what it looks like
If the answer is, "Yes," then describing that element is at least justified, if not even mandatory. In this case, inclusion overrules convenience.
Beyond that, I've got four things to criticise about the alt-text in that post.
One, double quotation marks from the keyboard do not belong into alt-text. Two, line feeds do not belong into alt-text either. Just because Mastodon renders both as intended, doesn't mean everything renders them as intended.
Hubzilla renders double quotes from the keyboard as &quot. (streams) cuts the alt-text off at the first double quote because it internally uses double quotes as alt-text delimiters. When there's a double quote from the keyboard in alt-text, (streams) thinks it marks the end of the alt-text.
Three, URLs don't belong into alt-text because they can't be opened by a browser from alt-text.
Four, about the URL again, there must never be any information exclusively available in alt-text. Not everyone can access alt-text. Some people are prevented from accessing alt-text due to various physical disabilities. Any information available only in alt-text, but neither in the post itself nor in the image is inaccessible and therefore lost to them.
Explanations of any kind go into the post, regardless of character limits.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #Inclusion #Inclusivity #A11y #Accessibility

For those

who celebrate it
Hope
received some
good Presents
+
had a nice
Dinner
with your loved ones.
Now time for
next

Another
to
back
Unlike
-23 w/
where wall filled
in
had written their names
There
Daisy's hair

Here w/
Daisy's hair
+
If want to compare

To be fair, these aren't all general Fediverse issues. It isn't like the whole Fediverse has them. They just seem to be general Fediverse isses if all you've ever experienced first-hand in the Fediverse is Mastodon, and if you think the Fediverse is mainly a Twitter-like microblogging platform with YouTube, Instagram and TikTok clones glued on.
For example, the issue of replies is mostly one on Mastodon because of how Mastodon has always tried to ape Twitter. Mastodon doesn't know conversations. Those who only know Mastodon are keen to deny this and say that Mastodon does know conversations. But those who have experienced Friendica, Hubzilla and/or (streams), not to mention the Threadiverse, know what support of conversations in the Fediverse can really be like.
A key element of conversations is the distinction between posts and comments. In conversation models, posts only ever stand at the start of a conversation, and everything that follows is not a post, but a comment. And this exists in the Fediverse. It has been around for much, much longer than Mastodon which does not and doesn't want to distinguish between posts and comments.
Friendica was launched in July, 2010, five and a half years before Mastodon. For as long as Mastodon has been around, it has been continuously federated with Friendica.
But Friendica is not another Twitter clone. It was created as an alternative to Facebook, but better than Facebook and with full long-form blogging capabilites among its features. Now, blogs have a one-post-many-comments conversation model, and so does Facebook. So, logically, so does Friendica.
On Friendica, a conversation isn't post-by-post piecemeal, and it isn't shown as piecemeal. It is shown as a whole with the post at the top, a comment tree below and the comment entry mask at the bottom. Same as on blogs or forums or Facebook etc.
Now here comes the actual kicker: Once you receive a post (remember the distinction between posts and comments), you also receive all comments. From people whom you don't follow and who didn't mention you. Even from accounts on instances which the Friendica node you're on has never heard of. Whenever someone replies to a post you've received in the past, whenever someone replies to a comment on a post you've received in the past, you get that reply onto your list of unread activities.
That's because you don't receive that reply from the replier. You receive it from the original poster who owns the whole thread.
Better yet: This entire system works without mentions. Mentions are only for show if you comment on a comment so that it's clear whom exactly you're replying to. That is, on today's Friendica, even that isn't necessary anymore because Friendica has switched from a strictly chronological comment order to a comment tree.
It's funny how the Fediverse sees this as something between utopic science-fiction and entirely inconceivable. But for the Fediverse, Twitter has always been the gold standard, and everything that works differently is weird, even the much, much bigger Facebook.
Hubzilla has inherited this behaviour from Friendica. After all, it was built from a Friendica fork from 2012 by Friendica's own creator, Mike Macgirvin , and it itself emerged in 2015, still ten months before Mastodon. And again, Mastodon has always been federated with Hubzilla. In fact, when Mastodon introduced ActivityPub in September, 2017, even then it connected to Hubzilla via ActivityPub because Hubzilla had implemented it in July.
The key difference is that Hubzilla added extensive permission controls to the mix. On Hubzilla, a conversation always has the same permissions all over. Comments cannot have different permissions than the post, and the original poster can't change the permissions after posting anymore.
Another step in the evolution is the streams repository which contains a decentralised social networking application that's officially nameless, but commonly referred to as "(streams)" in parentheses. It's a fork of a fork of three forks of a fork of probably another fork of Hubzilla, all forks in this chain and all the way back to Friendica are by the same creator, and it's from October, 2021.
Like Friendica in the meantime, and unlike Hubzilla where conversations are still strictly chronological, (streams) has tree-style comments sections.
About a year ago, the conversation model on (streams) was reworked again into something that was named "conversation containers". Mike explains them in :
(Start quote)

In the microblog model, Francis posts a message and it goes to all his followers. Taylor responds and the response goes to all her followers. Taylor's response is rarely seen by the rest of Francis's followers. They are different conversations with completely different audiences.
In the conversation model, Francis posts a message to all his followers. Taylor responds (only) to Francis, and Francis relays the comments to all his followers.
In this way, Francis has a contained conversation. There is one audience and one set of messages that are part of the conversation. Francis owns this conversation and decides who is a part of it. Taylor's followers aren't involved in any way.
This type of construct is a requirement for providing private groups and circles/aspects in the fediverse - as these features are by definition "contained conversations". It mostly provides a range of interactions that can't really be provided by the microblog model.

(End quote)
Conversation containers have since been turned into an ActivityPub FEP, . A few days ago, Hubzilla introduced them with version 10.
And indeed, both with conversation containers and their predecessor from Hubzilla, the thread starter is the exclusive owner of the whole thread. The thread starter decides who can see the start post and therefore the whole thread. The thread starter decides by channel role and contact roles who is allowed to comment on their posts as well as on comments on their posts, and on Hubzilla, the thread starter may even optionally forbid comments on a new thread entirely.
However, this is limited when software that doesn't understand any of this comes into the mix, especially Mastodon. What does work is limiting the audience of a post and therefore the whole thread. Mastodon understands anything from Hubzilla or (streams) that isn't public as a DM, and it doesn't let you e.g. boost DMs to your own followers.
But Mastodon doesn't know permissions. Mastodon doesn't know enclosed conversations. And Mastodon doesn't know the concept of permissions being defined by the start post. And so it's possible to change the permissions for a reply to a post from Hubzilla or (streams).
Granted, you can't reply to a restricted-audience thread in public because you can't reply to a Mastodon DM in public. But you may be tempted to make a reply to a public post private and believe it actually is private. It isn't.
Also, while you, as the thread starter, can delete comments from your own threads, you can't fully undo them. A deleted comment is also removed from all copies of the thread on Hubzilla and (streams), maybe also on Friendica. But the deletion is not carried out by all the microblogging instances in the Fediverse, whatever they run. And especially, if the bad comment came from e.g. Mastodon, neither Hubzilla nor (streams) can delete the post that became this comment from the commenter's own Mastodon account.
This is not a limitation on Hubzilla's or (streams)' side. It's a limitation on Mastodon's side. And it can only be fixed by Mastodon adopting conversation containers as well as a permission model like on (streams).
I can already predict that this will not happen. Eugen Rochko is too proud to adopt technology from developers of directly competing Fediverse server applications into Mastodon. His devs are brainwashed into "knowing" that Mastodon is superior to everything else in the Fediverse in any way imaginable. Mastodon itself is constantly trying to force its own proprietary designs upon the rest of the Fediverse. It's supported by Mastodon fundamentalists who think that Mastodon is the Fediverse gold standard, and "different from Mastodon" means "broken".
And adopting technology from elsewhere in the Fediverse would require Mastodon to officially acknowledge the existence of a Fediverse outside of Mastodon (plus commercial players), especially one that does certain things better than Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Conversations #ConversationContainers #FEP171bI'd really like to do some virtual "photo-blogging" with multiple in-world pictures in each post, especially now that so many Christmas-themed and winter-themed sims are online.
But that's completely out of question if it takes me two days or more to adequately describe one measly image. Adequate image descriptions are increasingly becoming mandatory in posts that may end up on Mastodon.
I guess that even applies to Hubzilla articles although they don't federate through the Fediverse, simply because they're on Hubzilla, and Hubzilla is part of the Fediverse. (That said, articles have the advantage over posts of not being butchered by Mastodon's HTML sanitiser.) I do have a (streams) channel for in-world picture posts, but (streams) doesn't have articles, and so it kind of limits me to the maximum of four images per post that Mastodon allows.
Also, I've yet to find a way and a place to add long descriptions for images in posts in which the images are embedded within the text rather than at the end. Mind you, I'm not talking about the alt-text I know where it goes. I'm talking about the long image descriptions which all my original in-world images get. Something that has grown up to 60,000 characters in length for one single image in the past.
So far, I've always added the long descriptions to the post itself. It's fairly easy to do if there's only one image, and it follows the actual post text with no more post text following the image. In that case, I simply add the long description after the image.
If there are multiple images, that's when things get tricky. I've tried adding each description right after the corresponding image for three images. I only had a wee little bit of actual post at the very beginning in this case. Still, there are over 37,000 characters of image description between the first and the second image. If Mastodon supported embedded images, hardly anyone would ever even scrolled down to the second image, much less the third one.
What seems to have worked better was what I did here and here with two images: First the post text, then the images, then the common image description preamble, then the individual image description parts for each image. The major downside is that there's a lot of text between each image and its corresponding description. And still, the actual post text is above the first image in its entirety.
Especially the third link leads to an image post in which I've "cheated" by reducing the surroundings to a minimum and the necessary image-describing effort along with them. It still took me eight hours to describe and explain both images, not including the alt-texts distilled from the long descriptions. And I still ended up with over 20,000 characters for the whole image description block.
Virtual photo-blogging would be something else. It'd show much, much more surroundings, probably more than in the first image post I've linked to. And it'd mean four images per post. Even if I didn't describe, explain or transcribe anything more than once, describing four images with a lot of landscape and decoration in them at sufficient levels of detail would take me well over a week, mornings to evenings, provided I can actually dedicate such a big chunk of time to nothing but describing images.
Also, the resulting image descriptions would be so massive that if I put them into the post, the post probably wouldn't go anywhere but Friendica, Hubzilla and (streams) because it'd simply be too long. Mastodon, where accurate and adequately detailed image descriptions are a must, rejects all post over 100,000 characters as far as I know, and my post would exceed this limit. Pleroma and Akkoma have a lower limit, and I guess Misskey and its forks have even lower limits.
A while ago, someone suggested to me that I could upload the long descriptions someplace else and then link to them in my posts. That'd shorten and clean up the posts immensely, and it'd work with images embedded in-between sections of post text.
I've actually toyed with the idea and how to carry it out without having to rely on anything outside of Hubzilla. Ultimately, I've pretty much nixed it. Not only because it's untested and unreliable, but mostly because every image description except for the first would grow tremendously in length.
That's because all information that's relevant for all four images would have to be in all four image descriptions. If I have four image description files, each one with its own link below the corresponding image, I can't count on everyone opening the first description first, then the second description and so forth. But if someone only opens the description for the third or the fourth image, I want them to have all relevant information regardless without sending them to the previous descriptions.
Granted, it's probably more inconvenient for the readers than for me. If I need something four times, I can copy-paste it three times. The readers, on the other hand, have to endure largely the same unprecedentedly massive infodump up to four times over in one post. Even more often if a photoblog post continues in comments or other posts to include more than four images.
Still, not only do the readers have to deal with a whole lot of information to be able to fully understand my images, but I have to research and write it in the first place. Three or four photo-blogging posts with four images each, and I won't get to do anything else than describe images for a solid month.
Lastly, I'm not going to cut down the detail level of my image descriptions any further. I know that at least some people enjoy them. And I've hardly ever been criticised by sighted people and never by blind or visually-impaired people, let alone sanctioned by Mastodon's alt-text police, for writing too long and/or too detailed image descriptions. Maybe the alt-text police has yet to notice my image posts.

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #Inclusivity #A11y #Accessibility

So why does your post render as text in Mastodon Has Mastodon embraced Hubzilla but still reject writefreely

As I've explained above:

Hubzilla saw this as an act of aggression and of trying to exclude Hubzilla content and reacted upon this by switching from Article-type objects to Note-type objects,

Essentially, Mike Macgirvin, creator and then still maintainer of Hubzilla, saw Mastodon's turning Article-type objects into links as flipping the bird at Hubzilla. Mastodon users couldn't read Hubzilla content at all anymore unless they took the extra step to open it at the source. Even comments. This reeked of either intentionally making Hubzilla look broken from a Mastodon POV or trying to sanitise "the Fediverse" from everything that isn't Mastodon.
Thus, Mike switched Hubzilla from sending Article-type objects to sending Note-type objects. The same type that Mastodon itself sends. Mind you, still with all formatting shebang. Even though that's against the spec.
WriteFreely, on the other hand, still sends Article-type objects. WriteFreely doesn't rely on its posts being read in Mastodon timelines. Also, you can't comment from WriteFreely blog accounts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #WriteFreely #ActivityPub Try Mike Macgirvin's various creations:

• ()
• ()
• the software commonly known as ()

Common perks for a writer like you:

• no character limits to worry about (for example, (streams) is "limited" by the data field size in its database to over 24,000,000 characters)
• title
• summary field (which Mastodon has repurposed as its CW field)
• more-than-complete text formatting
• six levels of headlines
• various kinds of lists
• tables
• embedded links with no visible URL
• upload images to the integrated file space, complete with a simple file manager, and embed them in your posts in-line anywhere you want, as many as you want

Extra perks on Friendica and Hubzilla:

• lots of native connection options, including diaspora* and cross-posting to WordPress and blogs compatible with the WordPress XMLRPC API
• many more public instances available and easier to find (ask me for a (streams) instance)

Extra perks on Friendica:

• even more connection options than Hubzilla, including Bluesky (requires a Bluesky account)
• posts with title go out as Article-type objects, posts without title go out as Note-type objects
• native mobile apps are slowly becoming available

Extra perks on Hubzilla and (streams):

• best instance-to-instance moving in the entire Fediverse
• nomadic identity can make you resilient against instance shutdowns
• extensive and powerful permission management
• file space has WebDAV connectivity (not recommended for uploading images to embed in posts, though)
• CalDAV calendar server and (optional) CardDAV address book server

Extra perk on Hubzilla:

• four additional optional non-federating ways of publishing content (articles, cards, wikis, webpages)

Extra perks on (streams):

• supports not only BBcode, but also standard Markdown and HTML, all within the same post
• can set Mastodon's proprietary sensitive image flag by adding #nsfw and/or #sensitive to a post with images in it

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #LongForm Eine Suche, die 100% des ganzen Fediverse abdeckt, ist im Grunde technisch nicht mglich.
Entweder hast du dezentrale Suche. Also: Jede Fediverse-Instanz kann alles auf jeder Fediverse-Instanz finden. Klingt erstmal geil.
Das heit aber auch: Jede Fediverse-Instanz mu jede Fediverse-Instanz kennen.
Wenn ich meine eigene -Instanz starte (das ist brigens sehr wohl Teil des Fediverse und mit Mastodon verbunden), mssen zigtausend Instanzen von weit ber 100 Fediverse-Serverapplikationen auf der Stelle wissen, da meine (streams)-Instanz existiert. Woher sollen die das wissen
Mal abgesehen, was jede Instanz fr riesige Datenmengen speichern mte. Im Grunde mte jede Instanz im Fediverse alles an Fediverse-Inhalten von berallher speichern und indizieren. Klingt erstmal geil, bis du fr deine kleine private Mastodon-Instanz einen ganzen Server-Cluster fr einige zigtausend Euro im Monat mieten mut mit terabyteweise Massenspeicher und einer Standleitung im Bereich von einigen hundert Gigabit pro Sekunde.
Genau der Grund brigens, warum es so sagenhaft teuer ist, fr Bluesky einen Relay-WebApp-Stack selber zu hosten.
Oder du hast zentrale Suche. Da wrden diese riesigen Datenmengen nur fr einen Servereigentmer anfallen. Fr den wre das aber erstens schon teuer genug.
Zweitens mte auch dieser zentrale Suchserver alle Instanzen im Fediverse kennen. Also es auch sofort erfahren, wenn irgendwo eine neue Instanz startet. Woher soll der Suchserver das wissen
Und drittens knnte eine zentrale Suche auch mal abgeschaltet oder von Elon Musk gekauft werden. Was ein Hauptgrund ist, warum sich alte Fediverse-Recken schon immer mit Zhnen und Klauen dagegen wehren, da das Fediverse von irgendwas Zentralem abhngt.
Ach ja: Falls du oder irgendjemand anders jetzt sagen wrde: "Dann nehmen wir eben nur Mastodon, alles andere ist doch sowieso scheiegal", dann werden euch so einige Nicht-Mastodon-Nutzer, die ich gut kenne, wegen Diskriminierung aufs Dach steigen. Mal abgesehen davon, da das die Probleme kaum lindern wrde.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Suche That's normal and intentional on Mastodon's side.
Whereas Mastodon sends toots as Note-type objects (the preferred type for short messages), WriteFreely sends posts as Article-type objects (the preferred type for full-blown, fully formated blog posts). But Mastodon "renders" Article-type objects as links to the original.
This behaviour dates back to 2017. In July, Hubzilla (which supports full-blown blogging with all shebang and with no character limits) was the first Fediverse project to adopt ActivityPub. In September, Mastodon became the second. Until then, both had only been connected via OStatus. And they remained the only ActivityPub implementations until after the standardisation by the W3C in 2018.
The difference was: Hubzilla went straight by spec and sent posts, comments and PMs as Article-type objects. In-bound, it supports just about everything.
Mastodon, on the other hand, only went with the spec as far as that was convenient, as far as that didn't clash with old-school, purist, minimalist microblogging. It sent and still sends toots as Note-type objects.
However, it refused to treat Article-type objects as required. Mastodon used an HTML "sanitiser" to rip out all HTML in incoming content and reduce it to plain text. Formatting, tables, lists, embedded images, all deleted. Because content with text formatting and embedded in-line images isn't old-school, purist, minimalist microblogging.
Hubzilla complained to Mastodon about the latter's way of completely butchering Hubzilla content. At first, Mastodon only justified its doing, if it reacted at all.
But for one, this meant that most Mastodon users would never see content from Hubzilla as it was intended on Hubzilla's side. Mastodon users wouldn't know that what they saw was not what they were to see, partly because Mastodon users could only tell that something wasn't from Mastodon itself by its length, partly because next to nobody on Mastodon knew that stuff like text formatting or embedded in-line images existed somewhere else in the Fediverse. So literally nobody would ever be bothered to look up content from Hubzilla on Hubzilla itself to see it in its original glory.
Besides, AFAIK, what Mastodon did was against the ActivityPub spec.
So Mastodon was torn between sanitising Hubzilla content to plain text (which angered Hubzilla) and fully rendering it in all its HTML glory (which wouldn't be old-school, purist, minimalist microblogging).
What they did was pick the third option: turn Article-type objects, which only came from Hubzilla at that point, into links to the original and not render them at all.
Hubzilla saw this as an act of aggression and of trying to exclude Hubzilla content and reacted upon this by switching from Article-type objects to Note-type objects, even though that technically went against the ActivityPub spec. Up until October, 2022, when Mastodon 4 came out, it still completely butchered anything from Hubzilla, and even Mastodon 4 only allows a very limited subset of HTML in posts, still excluding embedded images. But at least Hubzilla content is readable on Mastodon.
But this may change. It's no longer only about hobbyist projects like Friendica, Hubzilla or WriteFreely that Mastodon has to headbutt with. It's commercial players such as Flipboard which demand that Mastodon render their Article-type objects as intended. And it looks like Mastodon will cave in some more.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #Flipboard #ActivityPub

/USDT:

ENTRY ZONE- 18850 , 18200

TARGETS - 19100 , 19400 , 19760 , 20050 , 21000 , 23000 , 25000

STOP LOSS - 17200

LEVERAGE - 20x

Long Vielleicht sollte man so einen Shitstorm einfach mal riskieren. Das wrde nmlich eindrucksvoll beweisen, da erhebliche Teile der sich sonst so tolerant und allem gegenber offen gerierenden Mastodon-Community zutiefst xenophob sind, wenn es um das Fediverse geht. Und es wrde beweisen, da diese Leute inzwischen aktiv zur Bekmpfung von allem im Fediverse, was nicht Mastodon ist, bergegangen sind.
Bonuspunkte, wenn das live whrend eines Vortrags passiert, der dann auch noch gestreamt und/oder vom CCC aufgezeichnet wird.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #Shitstorm Richtig, das war 2017, als erst Hubzilla ActivityPub eingefhrt hat und dann zwei Monate spter Mastodon. Die beiden waren vorher schon ber OStatus verbunden und monatelang die einzigen Projekte berhaupt, die ActivityPub untersttzten. Aber sie taten und tun das immer noch sehr unterschiedlich.
Hubzilla hat sich an die Spec gehalten und brav alles als Article-Type Objects gesendet. Immerhin hat Hubzilla wie sein "Vorgnger" Friendica keine Zeichenlimits und sehr weitreichende Textformatierungsmglichkeiten.
Mastodon hat derweil alles durch einen "HTML-Sanitiser" gejagt, der alles, was reinkam, knallhart auf Reintext reduziert hat. Textformatierung raus, Bilder raus usw. Egal, was es war.
Von Hubzilla-Seite her kamen dann Beschwerden, da Mastodon Hubzilla-Content so gnadenlos entstellt, zumal das bei Article-Type Objects knallhart gegen die Spec geht. Von Mastodon-Seite her kam erst weitere Verweigerung der Kooperation. Mastodon setzte ja knallhart auf reines, puristisches Old-School-Original-Gangsta-Microblogging la Twitter, und da gibt's keine Textformatierung und keine eingebetteten Bilder.
Irgendwann hat Mastodon dann doch "eingelenkt". Die "Lsung" sah dann so aus, da Mastodon Article-Type Objects berhaupt nicht mehr renderte und kurzerhand statt dessen aufs Original verlinkte. Immer. Auch bei Kommentaren, weil Mastodon zwischen Posts und Kommentaren nicht unterscheiden kann. Mastodon-Nutzer muten jetzt bei allem, was von Hubzilla kam, erst den Link klicken, um es im Original zu lesen.
Daraufhin hat Hubzilla umgestellt von Article-Type Objects auf Note-Type Objects, die Mastodon weiterhin entstellte und bis heute weitgehend entstellt. So ganz allmhlich gibt's aber auch von kommerzieller Seite her Druck auf Mastodon, endlich mehr HTML-Rendering fr Article-Type Objects zuzulassen.
Die Hubzilla-Entwickler weigern sich weiterhin beharrlich, Article-Type Objects zu senden, und sei es optional, solange Mastodon sie nicht vernnftig und spezifikationskonform rendert.
Friendica untersttzt ActivityPub erst seit 2019, hat sich aber eine elegante Lsung einfallen lassen: Standardmig gehen Posts mit Titel als Article-Type Objects raus (die Mastodon nur als Links darstellt) und ohne Titel als Note-Type Objects (die Mastodon entstellt). Was einem erst wie ein Bug vorkommt, ist also Absicht mit Kalkl dahinter.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Mastodon #Friendica #Hubzilla

AAVE/USDT:

ENTRY:-332 -325

LEVERAGE: ( 10x-20x )

1 340
2 355
3 370

STOP-LOSS: 315

Make those miles count with a reliable . When on the hunt for a good one, figuring out which class of e-bike you need is a key decision point.

New entry of AI-generated and added to our :

The : 's

Doch, gibt es. Allerdings fallen die naturgem nicht so "einfach" aus wie Bildbeschreibungen. Die sind keine Momentaufnahmen der Audioaufzeichnung, sondern sie beschreiben sie kontinuierlich.
Die einfachste Form ist das Transkript. Das funktioniert allerdings nur bei reinen Wortbeitrgen, z. B. Podcast-Folgen. Da wird das, was in der Audiodatei gesprochen wird, 1:1 schriftlich wiedergegeben. Manchmal gibt's sogar einen Timecode, damit bekannt ist, wann wer was gesagt hat.
Die komplexere Form ist die Audiobeschreibung. Darin wird alles an Klangereignissen, was im Kontext von Relevanz ist, beschrieben. Wenn es gesprochenes Wort gibt, ist es weiterhin 1:1 transkribiert. Auch einen Timecode kann es geben.
Das ist aus zwei Grnden nicht sehr weit verbreitet. Zum einen postet kaum jemand Audioinhalte direkt auf Mastodon. Dafr hat das Fediverse bessere spezialisierte Anwendungen.
Zum anderen ist es schlicht und ergreifend ein gigantischer Aufwand. Vielleicht kann man einen Alt-Text fr ein Bild in ein paar Sekunden schreiben, wenn's nicht auf Details ankommt. An der Audiobeschreibung einer einstndigen Podcastfolge, die ber ein Transkript hinausgeht, kann man schon mal einen Tag sitzen oder lnger, wenn man darber brtet, wie man gewisse Gerusche so beschreibt, da sowohl taub Geborene als auch Menschen, die ihr Gehr verloren haben, damit etwas anfangen knnen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Transkript #Audiobeschreibung I'm kind of missing the option that factuality doesn't matter as long as the alt-text is entertaining. I think not exactly few blind or visually-impaired people think this way.
Anyway, I'll stick with facts. It's hard enough for me to describe images factually and then distill my long descriptions down to a size that fits into alt-text. I don't want to be required to add whimsy, especially not in the alt-text itself where I simply don't have any room for whimsy.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Also, "image description" and "alt-text" is not the same.
An alt-text is or should be an image description. But image descriptions don't always have to go into the alt-text. Very long image descriptions and/or image descriptions that have to contain information not available anywhere else in the context may also remain in plain sight, e.g. in the post text if it's a Fediverse post.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I can tell you what not to use in alt-text.
For one, don't put line breaks into your alt-texts. It doesn't matter whether Mastodon renders them. A lot of things in the Fediverse that aren't Mastodon don't render them.
Besides, don't use the quotation marks on your keyboard. They may irritate certain frontends from rendering them as " to ending the alt-text prematurely because they take the first quotation mark in an alt-text for the end of the alt-text.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #FediTips

MORPHO/USDT

Leverage: 20-75x
Entry Targets:
2.33
2.27
Take-Profit Target :
1)2.5
2)2.8
3)3.2
4)3.8

Stop-Loss 1.90

Ukraine delivered 200k domestically-produced drones to front-line units so far in December

With equipment from partners, more & more Ukrainian-made weapons are already operating on the frontlines

manufactured drones Kyiv close the gap as they face Russian forces with more shells on

also aims to ramp up the production of -range and

Es gibt da eine Gruppe, die sich irgendwie "FediDevs" nennt.
Die haben unter eine Art Portal eingerichtet, wo man sich registrieren und Starter Packs fr Mastodon anlegen kann, so hnlich, wie es sie auch auf Bluesky gibt. Mastodon-Nutzer knnen dann diese Starter Packs nehmen, um mit einem Mausklick rubbeldiekatz dutzendweise Konten zu folgen.
Problem Nr. 1: Auf kann man sich nur registrieren, wenn man auf einer der Instanzen ist, die FediDevs indiziert. Siehe , da ist eine lange Liste aller indizierten Serverinstanzen. Die allerallermeisten Instanzen sind aber Mastodon-Instanzen, und Pleroma, Akkoma, Hubzilla, (streams) und einige andere werden berhaupt nicht indiziert.
Problem Nr. 2: Es ist ganz offensichtlich technisch unmglich, in den Starter Packs irgendwas einzutragen, was kein Mastodon-Konto ist. Guck dir die Starter Packs an. Nur Mastodon-Konten drin.
Noch besseres Indiz: . Das Starter Pack ist komplett leer. Ganz offenkundig hat der Ersteller versucht, einen Starter Pack mit Nicht-Mastodon-Konten und -Kanlen anzulegen, aber daran dann gescheitert, weil es ganz einfach nicht mglich war, in den Starter Pack irgendwas einzutragen, was nicht auf Mastodon ist.
Problem Nr. 3: Die Starter Packs funktionieren selbst auch nur auf Mastodon. Ich kann sie nicht auf Hubzilla nutzen, du kannst sie nicht auf Akkoma nutzen.
Das Ganze ist also grtenteils absolut mastodonzentrisch und inkompatibel zu allem, was nicht Mastodon ist. Mich beschleicht auch das Gefhl, da die paar wenigen Nicht-Mastodon-Instanzen, die FediDevs indiziert, nur durchgerutscht sind, weil sie an den entscheidenden Stellen hinreichend kompatibel zu Mastodon sind.
Aber trotzdem steht FEDIDevs auf der ganzen Sache drauf.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #FediDevs #StarterPacks Well, it is possible to use the Mastodon client API for features that Mastodon itself doesn't have like text formatting. But, for example, many mobile apps don't support text formatting because Mastodon doesn't, although everything that isn't Mastodon does. They're built only against Mastodon.
And there are things, mostly Web services, that either do the same, use the client API, implement only Mastodon features and depend hard on features that only Mastodon has. Or they skip APIs and build directly against Mastodon, again, requiring the presence of features only available on Mastodon in the required way.
Then they have the audacity to have "Fedi" in their names while being completely incompatible with Pleroma, Misskey, Iceshrimp, Friendica, Hubzilla etc., essentially everything that isn't Mastodon or maybe a Mastodon fork.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonAPI #FediverseDevelopment I guess people who only know Mastodon see this differently from people who actively use something in the Fediverse that is not Mastodon.
The difference is:
If you "implement ActivityPub", it will work with, for example, Mastodon and its forks, Pleroma and its forks, Misskey and its forks, GoToSocial, Friendica, Hubzilla and (streams). As long as they have a reasonable ActivityPub implementation itself.
If you "implement Mastodon", it's only guaranteed to work with Mastodon.
It may or may not work with Mastodon forks, Pleroma and its forks, Misskey and its forks, GoToSocial and Friendica. If it doesn't, it never will because the non-Mastodon Fediverse is not officially supported. In fact, the devs may not even know that there's something in the Fediverse that's federated with Mastodon, but that isn't Mastodon.
It will most likely not work with Hubzilla, which is what I use, and (streams). They, too, are federated with Mastodon, by the way.
But this is the way a whole lot of things in or for the Fediverse are developed.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment Die Starter Packs von FediDevs sind hart ausschlielich gegen Mastodon gebaut. Nicht gegen irgendeine Mastodon-API, sondern direkt gegen Mastodon selbst ohne irgendeine API.
Nicht nur kann man sie nur auf Mastodon nutzen, sondern man kann zu Starter Packs auch nur Mastodon-Konten hinzufgen.
Untersttzung fr Pleroma, Akkoma, Misskey, die Forkeys, Friendica, Hubzilla usw. mte jeweils einzeln Stck fr Stck ins Backend eingebaut werden, weil das Backend von jemandem gebaut wurde, der entweder nicht wute, da das Fediverse mehr ist als nur Mastodon. Das, oder das ganze Backend mte weggeschmissen und neu gebaut werden, und zwar so, da es projektunabhngig funktioniert.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #FediDevs #StarterPacks The Fediverse itself is diverse. And I'm not talking about various Mastodon apps. I'm not talking about Mona vs IceCubes vs Tusky vs Fedilab vs the official Web interface. I'm talking about vastly different server applications: Mastodon vs Iceshrimp vs Hubzilla vs Lemmy vs PeerTube.
The Fediverse is diverse enough for some Mastodon users to actually be disturbed by this diversity. Just look at my profile, look around the entire server instance, and tell me how close it is to Mastodon. Or look at the mention. Mastodon doesn't turn mentions into long names. Or look at the length of this comment. This is not a case of a hacked character limit. This is a case of there never having been any character limit in twelve years.
It's just that many other Mastodon users don't notice it because they're in a bubble that's almost or entirely only Mastodon.
The Mastodon-to-non-Mastodon rate for Fediverse instances is about 1:2. Two out of three Fediverse server instances are not Mastodon.
For monthly active users, it's about 7:3. Around 70% of active Fediverse users are on Mastodon. Admittedly, this is skewed somewhat because there are no stats that count actual users on Hubzilla and (streams) who make use of nomadic identity and/or multiple channels on the same accounts.
But for many Mastodon accounts and entire Mastodon instances, the rate for active Fediverse users known may pretty well be about 100:1. You can take all users from Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon, Mitra, GoToSocial, micro.blog, Socialhome, Friendica, Hubzilla, (streams), Lemmy, /kbin, Mbin, PieFed, Pixelfed, PeerTube, Owncast, Funkwhale etc., you can put them all together, and you can still have a hundred times more Mastodon users.
In fact, I'm quite convinced that there are lots of Mastodon accounts that follow hundreds of other accounts, but they're all only Mastodon accounts which, in turn, only follow Mastodon accounts themselves. Some people have spent all the time from October 30th, 2022 to today quite active on Mastodon, but without noticing anything from outside of Mastodon.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse

Last updated: 2024-12-30

Awards for Dogs