Find the latitude of any place.  

Tauranga beach closed after 2m shark

Tauranga beach closed after 2m shark spotted within 50m from shoreline

Timelapse of these being drawn.

Yet still for

Those are all folks that weren't careful.

Still for

Careful around dry river beds, they can flood quickly and unexpectedly.

For

In case you haven't read that yet: This month, node9.org -) open culture sustainable media is in for a grant from for automated deployment of nodes and instances. I do hope this gives especially (streams) the push it deserves, seeing as it barely has any public instances anymore.

Threadiverse Reproducible Deployment


Reproducible deployment for Threadiverse servers
Fediverse is more than short form microblogging. The ActivityPub protocol connects all kinds of software for various communication needs. Some of those are concentrated on long blogs and threaded discussion forums. A common understanding of conversations in ActivityPub and their secure and safe-from-spam implementation is being developed in several fediverse projects. This project focuses on stable and documented automated deployment for two of them - Hubzilla and Streams, including interoperability tests. This will support threadiverse standardization efforts, and help to bring features like group photoalbums and full channel portability between instances.

Interesting, however, how Hubzilla and (streams) count as parts of the Threadiverse now.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NLnet #Node9 #Hubzilla #Streams #(streams)In case you haven't read that yet: This month, node9.org -) open culture sustainable media is in for a grant from for automated deployment of nodes and instances. I do hope this gives especially (streams) the push it deserves, seeing as it barely has any public instances anymore.

Threadiverse Reproducible Deployment


Reproducible deployment for Threadiverse servers
Fediverse is more than short form microblogging. The ActivityPub protocol connects all kinds of software for various communication needs. Some of those are concentrated on long blogs and threaded discussion forums. A common understanding of conversations in ActivityPub and their secure and safe-from-spam implementation is being developed in several fediverse projects. This project focuses on stable and documented automated deployment for two of them - Hubzilla and Streams, including interoperability tests. This will support threadiverse standardization efforts, and help to bring features like group photoalbums and full channel portability between instances.

Interesting, however, how Hubzilla and (streams) count as parts of the Threadiverse now.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NLnet #Node9 #Hubzilla #Streams #(streams)I think the list can be made more useful for showing it to Mastodon users who have never heard of Hubzilla, especially those who are fully convinced that Mastodon is the bee's knees.
I'm not sure if the line "Social Media" is appropriate. "Social media" usually refers to stuff like Twitter, but Hubzilla is nothing like Twitter. Hubzilla is more of a "social network" which is something like Facebook, but Mastodon, Bluesky and Threads aren't that.
One line that I think is really missing is "Character Limit".

Another three lines that could be useful:

"Polls" could have a number of maximum options which is unlimited on Hubzilla and 4 on Mastodon.
"Multiple Channels per Account" should rather be "Multiple Separate Identities per Account" because people who don't know Hubzilla don't know what "channel" means on Hubzilla. It means something totally different on Friendica, for example.
Likewise, "Block Channels" should be "Block Actors" or something else that everyone understands.
"Applications (Apps)" should be "Add-ons that can be activated by users" or something. When a Mastodon or Bluesky or Threads user reads "apps", they think of something that you can install on your phone.
The X for Hubzilla under Lists/Feeds makes it look like it's impossible to organise connections into groups and send posts only to a certain group on Hubzilla. Also, it looks like Mastodon has invented that feature. But Hubzilla has something like Mastodon's lists: privacy groups. I'd suggest to split this up and also add a line, "Posts Visible Only to Specific Groups of People".
"Prevent Replies to Your Posts" appears to have an explanation somewhere, but it doesn't.
Maybe you could add "WebDAV" under "Files (Cloud Storage)", "CalDAV Server" under "Events / Calendar" and "CardDAV Server", marked optional, under that.
Under "Networks and Protocols", there should be two lines for feeds. One could be "Built-in Feeds" (Hubzilla: yes, Atom Mastodon: yes, RSS), one could be "Subscribe to Feeds" (Hubzilla: yes, Mastodon: no).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Mastodon #Threads #Bluesky You can't. It's impossible without external tools. But you don't have to.
FediMeteo offers Fediverse actors for specific towns and cities which you can follow from Mastodon.
Open . Scroll all the way down. There you'll find links for eight nations: , , , , , , and . FediMeteo is only available for these eight nations.
If you're living in one of these nations, click the link for your home nation. A new page will open with an explanation what FediMeteo is and a list of towns and cities supported by FediMeteo.
If your hometown or a place that's close enough to your hometown is on the list, copy the address of the link to your hometown or that nearby place. Paste it into Mastodon's search. Mastodon should find it and offer you a Follow button.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

The Mystics are focused on building with long term player development

-womens-sports -page -team-analysis -content

Welcome on board (if you've actually made an avatar, that is)! OpenSim "veteran" of almost five years here (rezday: April 30th, 2020).
OpenSim is similar to Second Life and largely based on the same technology, and it basically uses third-party Second Life viewers because it doesn't have any of its own.
Second Life's learning curve is already intimidating because it's extremely versatile and powerful, and it's very different from what one may be used to from other virtual worlds or MMORPGs. OpenSim's learning curve adds even more on top with even less documentation and no tutorials or mentors whatsoever because the general assumption is that everyone who joins OpenSim has been in Second Life before anyway.
Also, like Second Life, OpenSim is not kind to underpowered hardware. And since the introduction of physically-based rendering with OpenSim 0.9.3.0 and especially Firestorm 7, it isn't worth bothering if you've got on-board graphics or a machine that's over 10 years old. That is, unless you want to stick with Firestorm 6.6.17 (which has at least one known bug that's fixed in Firestorm 7) for all eternity, and even that won't guarantee you smooth FPS.
But look at in-world pictures from Second Life or OpenSim, then look at in-world pictures from virtual worlds made for stand-alone VR headsets such as Horizons, and judge yourself what's looking better. And, for example, my main OpenSim machine is on 2018's mid-range level with a six-core, twelve-thread Ryzen, 16GB of RAM and a Radeon RX 590 with 8GB of VRAM. It's actually faster with Firestorm 7 than with Firestorm 6 because Firestorm 7's multi-threading support removed a nasty bottleneck.
OpenSim does have its advantages. It's fairly easy to build in-world once you've gotten the hang of it. No need to build entire scenes in external editors, export them, convert them etc.
Land is dirt-cheap in comparison with most other virtual worlds. It is not tied to NFTs because OpenSim entirely works without blockchains, without cryptocurrencies and without NFTs. For example, in Second Life, a standard region of 256x256m costs you about $250 a month or more. Many OpenSim grids offer you the same size of land for $10 a month or cheaper. Another example would be 's , the grid with the most monthly active users and one of the two largest grids in terms of landmass. Its default land offering is one sim the size of 16 Second Life standard regions, 1024x1024m, for under $40, depending on the configuration. Some places even offer smaller parcels for free to residents.
You can also create your own land: Some grids let you attach self-hosted sims. , the oldest grid and the other one of the two biggest, doesn't even offer land rentals and only lets its residents attach sims. And you can even run your own grid.
It's hard to wander around Second Life and see everything, also because it's constantly changing. But the Hypergrid has more than four times Second Life's landmass, and both OSgrid and Wolf Territories are larger than Second Life, so you've got even more to explore. (The obvious downside has to be Empty World Syndrome: You're less likely to encounter other avatars unless you go to an in-world event.)
Also, almost all content in OpenSim is free. That is, admittedly, the huge majority of that free content was and is still being pirated from Second Life, many users defend this content piracy, and it's often hard to tell whether something is legal or not. But there are still idealists who try to get as far as they can with only legal content, and some of them still create their own content.
Unfortunately, OpenSim doesn't have an active community in the Fediverse. It's mostly Lone Wolf who occasionally advertises for his grid, unfortunately with no hashtags, Mal Burns announcing videos under , again with no hashtags, and a small bunch of French users. There's also grid owner who also represents her grid on PeerTube under , but I haven't heard of her in the Fediverse in a while.
Lastly, fair warning: I strongly advise against having an underage-looking avatar in OpenSim. If you have one, you will automatically and unavoidably be considered a paedophile, and you will be barred from a whole lot of places.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OSgrid #WolfTerritories #WolfTerritoriesGrid #Groovyverse Das Fediverse ist sehr viel mehr als nur Mastodon. Vor allem ist das Fediverse sehr viel mehr als nur ein Twitter-Klon fr Microblogging.
Beispielsweise gibt es da auch Alternativen zu Facebook, etwa . Genau wie Facebook hat auch Friendica . Und obwohl du auf Mastodon bist, kannst du von da aus einer Gruppe z. B. auf Friendica beitreten und darin teilnehmen.
Noch grer ist das "Threadiverse", was der Sammelbegriff fr die Reddit-"Klone" im Fediverse ist, insbesondere , Mbin und PieFed. Fr Lemmy-Communities (entsprechen Subreddits) gibt es auch . Auch mit denen kann man sich von Mastodon aus verbinden, auch wenn es etwas holprig ist.
Kleine Warnung vielleicht: Generell ist das Erstellen neuer Threads von Mastodon aus in beiden Fllen nicht sehr intuitiv, wenn man bisher praktisch nur Mastodon kennt. Das wird auch dadurch erschwert, da Mastodon keinerlei Untersttzung fr Gruppen in irgendeiner Form hat und gar nicht wei, was das ist. Aber es geht, wenn man wei wie. Und das Anlegen ganz neuer Gruppen/Communities geht nur "vor Ort", nicht von Mastodon aus.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Gruppen #Facebook #Friendica #Reddit #Lemmy #Mbin #PieFed Ich glaube, gerade Volt versucht, junge Leute da zu erreichen, wo die eigene Generation ist. Die allermeisten jungen Leute haben aber noch nie vom Fediverse oder auch nur von Mastodon gehrt, und wenn, ist es ihnen nicht cool und trendy genug.
Dabei knnte gerade Volt anderen Parteien ein ganzes Stck voraus sein und direktweg eine eigene Instanz von z. B. aufziehen, die dann mehr sein kann als ein Drop-in-Ersatz fr . Die deutsche Piratenpartei hat , der wohl die einzige Nicht-Mastodon-Fediverse-Instanz einer politischen Partei weltweit sein drfte. Und den hatte sie schon, bevor es Mastodon berhaupt gab.
Derweil ist fr die Parteien, die es schon zu Adenauers Zeiten gab, das Internet weiterhin immer noch Neuland.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Volt #DEPol I'm not a big psychological or political talker. And this Hubzilla channel of mine is not my personal, all-purpose channel it's actually specialised on two topics, neither of which is politics or psychology.
But especially radical leftists appear to be very emotional, very impulsive and far from reason. They want their extreme solutions for everything, they want them now, and they're unwilling to compromise. They see themselves as the most tolerant people in the world, and yet, they consider any and all opinions and worldviews different from their own fascist.
The primary topic of this channel is a free and open-source system of 3-D virtual worlds. I know a lot of alternative leftists in these worlds, but I used to know a guy who really took the cake. For example, he boycotted the entire World-Wide Web for a while in favour of Geminispace, and he tried to push everyone whom he knew into Geminispace as well, just because of commercial, corporate advertising on the World-Wide Web.
One particular aspect about these worlds is that there's no general economy across all these worlds, and most don't have any economy. Most content is free. But in some worlds, it's possible to acquire content for currencies which can be exchanged with real-life money.
I remember one event where we where, where I mentioned some cool content which, however, is payware. This guy was immediately triggered into yelling out into the local chat, "ALERTA ALERTA ANTIFASCISTA!" He basically considered the existence of payware in our worlds deeply fascist.
In general, he did not tolerate any opinions that weren't his own. Whenever he didn't like something, he was basically eager to go onto a crusade against it. And whenever he did like something, he wanted to convince everyone of it as without alternatives.
Our home grid is led by a couple of mild anarchists, both not the youngest anymore, but even they compared his attitude to the Red Army Faction, an extremist leftist terrorist group that was active in Germany especially in the 1970s and 1980s. Particularly the "second generation" which, starting in 1975, was just senselessly brutal to the point of alienating those German leftists who had previously been in support of the RAF.
#Long #LongPost #CWLong #CWLongPost

exposures and white

Posted into DEPTH OF FIELD

Set Side B 2024 in Review
We used to do monthly summary posts, but they ended up being a lot of work to keep up, and often there would be something interesting I'd want to post about that would preempt them. So in their place, and in recognition of Set Side B's new Bluesky feed (which supplements, but doesn't replace, our Mastodon feed), here's a recap of what I consider to be just some
#2024

To quote Arthur C. Clarke:
Any sufficiently advanced technology is indistinguishable from magic.

And for your average Musk escapees, Mastodon alone is more than sufficiently advanced. These people believe that there's some magic going on that makes their fully public posts private and secure regardless. They want perfect security, but with zero inconvenience, and they think Mastodon provides them with exactly this.
In fact, they expect Mastodon to be an absolutely perfectly safe haven, simply because it isn't a corporate silo. Little do they know how close to being a corporate silo Mastodon is, what with having a US-based company and a lighthouse instance that accounts for 22% of the whole Fediverse in terms of MAUs.
On top of that, more than half of all Mastodon users think the Fediverse is only Mastodon, and most of the rest can't imagine that anything in the Fediverse could possibly have features that Mastodon doesn't have. Not unless you slap them right into their faces like character limits over 500.
They cling hard to and rely on an imagination of the Fediverse that has never even been close to reality and never will.
As for The Bad Space, its blocklist looks like it's curated not by evidence, but by emotional triggers. Generally, some blocklists go so wild that you have to ask yourself whether the reason why nobody has tried to block out everything that isn't vanilla Mastodon is because that'd be too big an effort (two out of three Fediverse instances aren't Mastodon), or whether such people simply don't know how far the Fediverse extends beyond Mastodon, so they don't know what to block. I mean, there should be reasons enough to block everything that isn't Mastodon.
Blocklist import from other instances doesn't make things any better. Just like on all networks where everyone can run a server, the Fediverse, especially Mastodon, has got admins who really shouldn't run a server. It looks very tempting to pick blocklists by length rather than content, the longer, the more "secure", import a bunch of them, but not curate them because that'd be extra effort.
In this light, it's a good thing that when switching from manual list curation to automated list aggregation a while ago. Especially tier 3 would have been easy to exploit with little to no curation, and there certainly were enough sufficiently paranoid Mastodon admins who'd subscribe to tier 3 without ever taking a single peek at the list.
Sometimes I feel like going to Mastodon's GitHub repository and submitting blocking or allowing entire Fediverse server applications by user agent, both for admins and for users, as a feature request, just to see what'll happen. Maybe dumbed down on the user side to a switch that blocks everything that isn't Mastodon. But maybe I should also mention that (streams) already has this feature on the admin side so that the Mastodon devs have to think up a way to sell this as invented by Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta


Epson PowerLite L730U Long Throw 3LCD Projector - Education, Corporate, Digital Signage, Entertainment, Presentation epson

The is not proprietary. Just because it isn't a copyleft license, which the MIT license is not, just because it explicitly has "Copyright" in its license text, which the MIT license does, it is not automatically proprietary and non-free.
The MIT license is compatible with the Debian Free Software Guidelines which means that software under the MIT license is allowed into main on Debian and not forced into non-free. It is approved both by the Free Software Foundation and the Open Source Initiative, and it is compatible with the GPL.
In other words, both Debian and the FSF have officially declared the MIT license a free license.
It is possible and legal by license to pass your MIT-licensed software on to your user community so they can maintain and develop it, and then for the new developers to re-license your MIT-licensed software under the GPL. Exactly this has happened to Friendica.
Mike Macgirvin knew that the Friendica community wanted to re-license Friendica under the GPL. It wasn't a secret. (Proof: the short-lived Free-Friendika fork from very early 2012 that was created for there to always be an MIT-licensed Friendika.)
Also, both the X Window System, the Wayland protocol and the Sway window manager are MIT-licensed. X11 actually has its own variant of the MIT license. curl is MIT-licensed. Both Gitea and GitLab are MIT-licensed. Linux From Scratch is MIT-licensed. The XMPP server Prosody is MIT-licensed. And Ruby on Rails, which Mastodon is built with, is MIT-licensed, too, as is Rust.
The MIT license allows for just the same liberties as all variantes of GPLv2 and GPLv3, but without the restrictions that make all GPL variants viral.
You may argue that the GPLv3 is literally the only free license that has ever existed because all derivatives of GPL-licensed material are automatically GPL-licensed themselves and therefore free software when published.
I'm more on the side that the MIT license is actually freer than any versions and flavours of the GPL because it does not have any such restrictions and grants more liberties.
#Long #LongPost #CWLong #CWLongPost #MITLicense #GPL 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.

#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

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 Long 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:

Common perks for a writer like you:

Extra perks on Friendica and Hubzilla:

Extra perks on Friendica:

Extra perks on Hubzilla and (streams):

Extra perk on Hubzilla:

Extra perks on (streams):

#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


Last updated: 2025-01-05






Affiliates Program which new zealand .is fabulous.com