Power lines.
Many people say that alt-text is not only useful in the many cases when someone can't see the image, but it can also help understand an image. I've actually read advice for Fediverse users to use alt-text to explain their images to those who know nothing or don't know enough about them.
When I post an image, it's almost always about something that the majority of my audience don't know enough about. And the above remarks give me the impression that especially the Fediverse loves explanations for stuff it doesn't understand being served on a silver platter. So I consider it good manners for myself to explain everything down to the level on which I can assume the general Fediverse public to be.
However, explanations don't belong into alt-text because not everyone can access alt-text. Also, my explanations tend to be too long for alt-text. Hence, I put them into the post. Everyone who can access my posts in some whay can also access the explanations.
This goes even more for my meme posts than for my original images. And I consider it insufficient to only explain the image itself. For when I post a meme, I actually post a meme, i.e. not a random im age with text on it, but an image macro based on a meme template that is established as such. Not everyone always gets these templates, so I have to explain them. Even fewer people get what my meme images are about, or what do you think how many people know right off the bat what FEP-ef61 is So I have to explain that as well.
Well, and then I have to explain my explanations. A KnowYourMeme-level explanation of the One Does Not Simply Walk Into Mordor meme template is not understandable for people who don't know what an image macro is or what a snowclone is. A KnowYourMeme-level explanation of snowclones is not understandable for people who don't know what 4chan is. My explanation of FEP-ef61 is not understandable for people who don't know what nomadic identity is, what Hubzilla is and what the streams repository is. And so forth.
So if I have to explain everything in my post because people find clicking or tapping links inconvenient, I have to really break everything down to the absolute basics and write absolutely massive explanation sections. But if I don't explain anything, my image posts, my meme posts in particular, go whoosh above people's heads, and they feel discriminated by another nerdy "techbro" who can't be bothered to explain anything, or who intentionally doesn't explain anything to keep "normies" away.
What I do now is give links to whatever can be explained externally and explain everything else myself.
CC:
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes
Einige scheinen zu glauben, wenn sie gegen alles um sie herum vorgehen, das darauf hindeutet, da das Fediverse nicht nur Mastodon ist, dann wird das Fediverse wieder zu nur Mastodon, und alle Instanzen von allem anderen verschwinden.
Auch wenn das Fediverse zu keinem Zeitpunkt je nur Mastodon war. (Nein, war es wirklich nie. Auch 2016 nicht.)
So manch einer scheint auch wirklich aktiv an einem Fediverse fr sich selbst zu bauen, das wirklich nur Mastodon ist. Jeder, der von einem Fediverse jenseits von Mastodon schreibt, wird gemutet oder geblockt. Jeder, der ganz offenkundig selbst nicht auf Mastodon ist (Textformatierung, "komische" Erwhnungen und Hashtags, oft auch ber 500 Zeichen), wird gemutet oder geblockt. Oder am besten gleich die ganze Instanz.
Und dann gibt's Leute, die gengend ffentliche Reichweite haben, da sie darber versuchen knnen, das Nicht-Mastodon-Fediverse zu zerstren, indem sie dessen Existenz aktiv leugnen und bestreiten.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediMeta #Fediverse #Mastodon #NichtNurMastodon Long Vor allem sind die Hubzilla-Zahlen noch verzerrter als die Mastodon- und Friendica-Zahlen, weil die FediDB nicht nur nichts von mehreren Kanlen auf einem Konto wei (was auch gut ist, weil die Alternative das Graben in der Datenbank und das Erfassen und Registrieren individueller Nutzer erfordern wrde), sondern auch nichts von Klonen. Hubzillas Siteinfo rckt ja nur mit der Zahl der Kanle raus, aber weder mit der Zahl der Konten noch mit der Zahl der Kanle, die Hauptinstanzen sind und keine Klone und schon gar nicht mit der Zahl der Konten, die Kanal-Hauptinstanzen enthalten. (Wre mal ein Feature Request.)
Das heit, wenn du ein Konto auf einem Hub hast, aber fnf Kanle auf dem Konto, sind das fr die FediDB fnf User. Wenn du einen Kanal hast, von dem aber zur Sicherheit drei Klone, sind das fr die FediDB vier User. Drei Kanle auf demselben Konto, davon dann jeweils zwei Klone auf zwei anderen Hubs, und die FediDB sieht das als neun User.
Auerdem zhlt auf Hubzilla sowieso sehr viel als User, auch wenn es nicht mit Mastodon interagiert. ist ein Hubzilla-Kanal, zhlt also als User. Hchstwahrscheinlich ist sie geklont und zhlt dann als mehrere User. Jedes Forum zhlt als mindestens ein User. Jeder Kanal, der einfach nur als persnlicher CalDAV- und CardDAV-Server und vielleicht noch als WebDAV-Fileserver genutzt wird, aber nirgendwohin fderiert, zhlt als mindestens ein User. Jeder Kanal, der als RSS/Atom-Aggregator luft, aber auch nirgendwohin fderiert, zhlt als mindestens ein User. Und Stichwort Bots: Jeder Kanal, der berhaupt als reiner Channel-Source-Bot luft, zhlt auch als User.
Was die MAUs angeht, werden allerdings nur die gerechnet, die sich wirklich eingeloggt haben. Das drfte die Bots rausrechnen, denn wer loggt sich regelmig in seinen Bot ein
Auch wenn du dich in deine Klone einen Monat lang nicht einloggst, gelten die nicht als "aktive User", auch wenn sie natrlich weiterlaufen. In der Praxis ist also auf Hubzilla der Anteil derjenigen, die wirklich noch bei der Stange sind, relativ hoch, weil ein wohl nicht zu unterschtzender Teil der "inaktiven User" auf Klone, Channel-Source-Bots und reine Webpage-Kanle entfllt.
Auf Friendica ist er so niedrig, weil Friendica schon uralt ist und wahrscheinlich noch ein paar uralte Nodes hat mit Karteileichen, die seit vielen Jahren nicht mehr dabei sind. Gleichzeitig hat es da nie den groen Hype gegeben, der zwischendurch neue User reingesplt htte. Andererseits hinterlassen auch auf Hubzilla sowohl Newbies als auch erfahrene User inaktive Kanle. Erstere, weil sie eh nie ihre toten Accounts beseitigen, letztere, weil sie wissen, da es aufwendig wre, auf demselben Hub einen Kanal mit demselben Namen neu anzulegen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Statistik #Friendica #Hubzilla #NomadischeIdentitt Ganz ehrlich: Die Zweckentfremdung des Zusammenfassungsfelds von StatusNet fr CWs, die 2017 von einem Nutzer (!) in Mastodon implementiert wurde, ist eine ble Krcke von jemandem, der keine Ahnung hatte, wie das Fediverse auerhalb von Mastodon aussah.
Zum einen: Wenn man bestimmten Content wirklich loswerden will, dann sollte man den eh rausfiltern. Es bringt nix, sich auf Dauer von allen anderen verhtscheln und bettern zu lassen. Eigeninitiative bringt hier mehr. Dafr braucht es aber Schlsselwrter in den Beitrgen, die die Filter auslsen.
Zum anderen: Wenn man bestimmten Content einfach nicht offen angezeigt haben will, dann geht das sehr viel lnger sehr viel eleganter, als es Mastodon berhaupt gibt. CWs sollten eigentlich individuell leserseitig generiert und nicht allen Nutzern identisch aufgezwungen werden. Und das ist keine Raketenwissenschaft.
Friendica hat wahrscheinlich schon seit 2010 eine Funktion namens "NSFW". Die ist optional, besteht einfach nur aus einer Wortliste und versteckt alles, was irgendwas enthlt, was auf der Wortliste ist, hinter einem Button. Hubzilla, (streams) und Forte haben das auch, und mindestens diese drei knnen auch RegEx in der Wortliste. Sogar Mastodon kann mit seinen Filtern seit zwei Jahren CWs generieren.
Nichts davon scheint aber irgendjemand zu wissen. Alle wollen sie verhtschelt und in Watte gepackt werden mit CWs, die fr sie individuell zugeschnitten sind, die aber alle da drauen gleichermaen so bekommen. Und gleichzeitig macht sich praktisch niemand die Mhe, unangenehme Posts mit entsprechenden Hashtags oder Schlsselwrtern zu versehen, um die Filter auszulsen. Statt dessen kann man auf den Sack bekommen sowohl fr fehlende CWs als auch fr mehr als vier Hashtags.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Filter Speaking of meme posts, how do you prefer them explained, if at all
Neither the meme nor the topic
The meme not at all, the topic with links, if possible, otherwise not at all
The meme not at all, the topic with links, if possible, otherwise extensively in the post
The meme not at all, the topic extensively in the post
Both with links, if possible, otherwise not at all
Both with links, if possible, otherwise extensively in the post
Both extensively in the post
I'm asking because my meme posts tend to be about very obscure topics such as virtual worlds that not even 50 people in the whole Fediverse know or the Fediverse beyond Mastodon. On the one hand, I've got the impression that many people would love to have everything explained in such a way that no special prior knowledge is necessary. On the other hand, I know that they nope out when I tell them how long a full set of explanations can be.
I've actually tested a full set of explanations with . By the way, that place is very much part of the Fediverse. I ended up with a whole of nine explanations. One for the image itself. One for the meme template. Five in order for people to understand the meme template and the explanations for the meme template. One for the topic. One in order for people to understand the topic.
I've served people just about all information they may need to get the image, but it took me over 25,000 characters to do so.
CC:
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes Well, the quality and usefulness of image descriptions in general and alt-text in particular can not only vary greatly, depending on the circumstances, but it's also very subjective.
One user could say that an alt-text of 200 characters is sufficient, or even that a longer alt-text is too long. Another user could say about the same image that they need a full, detailed description of all visual elements plus explanations of everything they aren't familiar with because the content of the image is apparently very interesting, but too obscure.
I myself prefer to err on the side of "too much", sometimes taking several days to describe one measly image. Not everyone likes the outcome, but some applaud it.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Auf gar keinen Fall sollte man den Leuten beim Onboarding ins Gesicht lgen, da das Fediverse ausdrcklich Mastodon, nur Mastodon und nichts als Mastodon ist. Auch nicht der Einfachheit halber.
Es gibt jetzt schon zuviele Leute auf Mastodon, die der felsenfesten berzeugung sind, da das Fediverse nur Mastodon ist. Das Harmloseste ist noch, wenn sie fr "das Fediverse" Features fordern, die das Fediverse schon fnfeinhalb Jahre lnger hat, als es Mastodon berhaupt gibt.
Wenn sie zu lange glauben, das Fediverse ist nur Mastodon, gewhnen sie sich auch dran. Das Fediverse, das ist fr sie ihr liebes, nettes, flauschiges Wollmammut und sonst nichts. So, und wenn dann aber ein Post oder Kommentar daherkommt wie der hier, der aber sowas von nicht von Mastodon ist, dann kacken sie vor Schreck ber das, was so nie htte passieren knnen, Ziegelsteine in die Hose und gehen in eine Abwehrstarre ber.
hnlich dramatisch kann es enden, wenn man versucht, ihnen zu erklren, da das Fediverse nicht nur Mastodon ist. Egal, ob sie sich gerade ber einen ber-500-Zeichen-"Trt" von einer "gehackten Mastodon-Instanz" aufregen. Egal, ob sie flschlicherweise direktweg behaupten, das Fediverse und Mastodon seien dasselbe. Egal, ob sie der absolut felsenfesten berzeugung sind, im Fediverse gibt's keine Quote-Posts (doch, die gibt's, die gibt's auch schon fnfeinhalb Jahre lnger als Mastodon). Mitunter wird man erst angeschnauzt und dann blockiert. Das wollen diese Leute nicht hren. Die wollen, da das Fediverse nur Mastodon ist.
Frag mal . Der ist auf Friendica, das eben schon fnfeinhalb Jahre lter ist als Mastodon. Der hat mal einer Mastodon-Nutzerin mit mehr als 500 Zeichen geantwortet. Die hat sich ber seinen viel zu langen "Trt" aufgeregt und, ich meine, auch ber seine angeblich manipulierte Mastodon-Instanz.
Er mute ihr dann erst erklren: Nein, er ist nicht auf Mastodon. Er ist auf Friendica. Nein, Friendica ist keine Mastodon-Instanz. Friendica ist ein komplett eigenstndiges Produkt. Ja, es ist mit Mastodon verbunden. Ja, das ist normal. Nein, das Fediverse ist nicht nur Mastodon.
Das endete dann damit, da sie ihn blockiert hat, weil er in ihren Augen ein bser Black-Hat-Hacker ist, der sich mit seinem bsen Black-Hat-Hackertool Friendica illegalerweise ins Mastodon-Fediverse reingehackt hat. Kein Witz, das ist so passiert. Frag ihn.
berhaupt regt sich die "Fediverse = Mastodon"-Fraktion schnell auf, wenn man etwas macht, was entweder auf Mastodon technisch nicht mglich ist oder gem Mastodon-Kultur verpnt oder beides. Diese Leute wollen die Mastodon-Kultur im ganzen Fediverse durchsetzen, und zwar mit aller Gewalt und gegen alle Widerstnde.
Als Hubzilla-Nutzer bin ich dann immer in Erklrungsnotstand. Hubzilla ist keine Mastodon-Instanz. Es funktioniert komplett anders als Mastodon. "Die" haben das anders gemacht als Mastodon, weil "die" es vor Mastodon gemacht haben. Hubzilla ist zehn Monate lter als Mastodon und basiert auf einem Fork von Friendica, das fnfeinhalb Jahre lter als Mastodon ist. Das Fediverse ist also nicht nur nicht nur Mastodon, sondern es wurde auch nicht mit Mastodon erfunden.
Trotzdem wird man dazu gezwungen,
Noch was: Ich wei nicht, ob du schon davon gehrt hast, aber Mastodon will ja Quote-Posts einfhren. Da gab es vor geraumer Zeit einen Feature Request auf GitHub. Aber die Anfragerin wollte dazu noch zwei Dinge. Zum einen einen Opt-in-Schalter, mit dem man erst quotepostbar wird. So eine Funktion wird aber von ActivityPub nicht untersttzt, das wre also ein proprietres Non-Standard-Feature, das nur Mastodon htte. Und sie forderte eine Regel fr alle Mastodon-Instanzen, da Instanzen, die sich an den Opt-in nicht halten, gefediblockt werden sollen.
Aus "Mastodon = Fediverse"-Sicht klingt das erstmal gut, oder Was soll daran schon schlimm sein
Wie ich schon schrieb: Das Fediverse hat Quote-Posts jetzt schon. Mastodon hat sie nicht, aber das Fediverse hat sie. Stand damals gab es Quote-Posts unter anderem auf Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla und (streams). Die waren alle damals schon im Fediverse, die waren alle damals schon mit Mastodon fderiert, und somit konnten die alle damals schon ohne groe Probleme Mastodon-Trts quote-posten.
Wenn aber Mastodon so ein Opt-in-Eigengezcht einfhrt, dann haben die das nicht automatisch auch alle. Noch einmal: Mastodon wird sich dabei an keine Standards halten, weil es dafr keinen Standard gibt. Das bedeutet: Stand heute wren alle, aber auch wirklich alle Instanzen von Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, Iceshrimp, Catodon, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla, (streams) und Forte problemlos in der Lage, Mastodon-Trts auch dann zu quote-posten, wenn der Opt-in-Schalter aus ist.
Wenn also auch die Regel dazukme, mten alle Mastodon-Instanzen mit sofortiger Wirkung alle Instanzen von Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla und (streams) fediblocken. Nur weil da eine Regel durchgedrckt wurde von jemandem, der nicht mal damit rechnet, da es im Fediverse noch etwas anderes als Mastodon geben knnte.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon Here's a list that I've compiled over the years. It may be incomplete, though.
That's because the place where I am, which is federated with Mastodon but has nothing at all to do with Mastodon, has its own content warning culture: Instead of forcing content warnings on everyone in the summary field (yes, it actually is the summary field), we have our own individual content warnings automatically generated reader-side from a customisable keyword list. However, in order for this to work, the keywords need to be present in the to-be-warned-about content. This works best with hashtags.
That, and I've got no means to add Mastodon-style content warnings to replies.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CW #CWs #CWMetaDa aber der Gruppenserver von QOTO der einzige moderierte Gruppenserver im ganzen Fediverse ist, ist vollkommener Bldsinn. Jeder Friendica-Node, jeder Hubzilla-Hub, jede (streams)-Instanz und, na ja, die momentan eine Forte-Instanz untersttzen moderierte Gruppen, und das im Falle von Friendica schon sehr viel lnger, als es Mastodon berhaupt gibt. Auerdem haben alle vier im Gegensatz zu Mastodon schon im Kern von vornherein volle Untersttzung von Gruppen.
brigens scheint der Gruppenserver im Moment eh funktionslos zu sein.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QOTO #Friendica #Hubzilla #Streams #(streams) #Forte #GruppenPower lines.
exposure
Hubzilla can have
IANAL, but AFAIK, at least by German law, an admin can be held liable for anything that happens on their website. A Hubzilla hub admin can be held liable for anything nasty that's being washed onto their hub from one of their users' connections, and that shows up in the public stream. There's little to nothing they can do against it. They can moderate the public stream, but that'd require constantly watching the public stream they can't be online 24/7 to do so. And since Hubzilla is all about self-promotion, no Hubzilla hub will ever have a moderator team located all around the globe.
It's simply safer to keep the public stream off.
Now, a lot of public Hubzilla hubs are German, and so are a lot of public Friendica nodes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla That said, you can't point fingers and put the blame on non-Mastodon server applications because they don't work exactly like Mastodon.
They've got different premises. Friendica was designed to be an alternative to Facebook, and it pre-dates Mastodon by five and a half years. Hubzilla, (streams) and Forte are in the same family of forks by the same creator with more or less the same premise. Socialhome is another Facebook alternative, and the fact that it can federate with diaspora*, just like Friendica and Hubzilla, goes to show how old it is. It should be clear that neither of the five is an add-on to Mastodon.
Nobody can demand from them to throw their entire conversation support overboard and become more like Mastodon, just because Mastodon is the biggest Fediverse project, and to more people than not, Mastodon is the Fediverse. That is, people can try, but they can't expect this to happen.
It's even less likely to happen than Friendica throwing its old native culture, geared towards its feature set and its conversation support, out of the window and completely replace it with Mastodon's culture which is largely incompatible with Friendica's technology.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Socialhome
As far as contact discovery goes, that point goes to the actual social networking server apps in the Fediverse, the Facebook alternatives, rather than the microblogging server apps that are being misused as social networks. I think doesn't suggest potential new contacts to you, and Mastodon definitely doesn't. But Facebook does, and so do Friendica and the rest of its family (Hubzilla, (streams), Forte). (streams) could be the king of this because it can find both all kinds of ActivityPub actors (unlike Hubzilla) and actors using the nomadic protocols on which Hubzilla and (streams) itself are based (unlike Friendica), if only it had more and especially larger public instances.
By the way, only a week ago, I wrote .
Also, all four are better equipped for finding your own kind of people. You don't need instances for specific target audiences which newbies will almost never hear of. You don't have to fumble around with hashtags, not even knowing what the "right" hashtag for a certain topic is.
That's because all four have native built-in support for discussion groups. Pretty much all the Fediverse can connect to these groups, but it's here where these groups are at home, and Mastodon doesn't even understand the concept of groups. Not to mention that, unlike Guppe groups, these groups can be moderated. And at least on Hubzilla, (streams) and Forte, they can be fully private so that non-members can't look inside and even hidden from public directories.
As far as moderation goes, especially Hubzilla, (streams) and Forte are geared towards self-moderation. They have extensive permissions systems on three levels (per channel, per contact, per post). In combination with their understanding and system of conversations (which Mastodon completely lacks as well), you can moderate your own threads and even delete offending comments. Unfortunately, you can't have them purged from the whole Fediverse.
Also, the reliance on self-moderation means that neither of the three has a Report button or even only a report system built in, so they don't understand Mastodon's report system either. If you need to report something to one of the instance admins, you'll have to send them a DM. Most public Hubzilla hubs only reveal who the admins are in the JSON-formatted siteinfo. On (streams) and Forte, you'll have to go to the directory, have only local channels shown, sort them by age and guess which of the oldest actually local channels are admins.
That said, Hubzilla, (streams) and Forte have much more radical methods at hand for keeping unwanted stuff out than Mastodon. Most Fediverse server applications allow for admins to block entire instances, many, (streams) and Forte included, even give users this power. But (streams) and Forte have received a new feature called "user agent filter" in September which is capable of blocking entire Fediverse projects on a per-instance level. It was mainly designed as a more advanced counter-measure against Threads, but it can just as well be used to lock out the entirety of Mastodon, Glitch included, or the entirety of Pleroma, for example. It can even operate on an allowlist which, in addition to (streams)/Forte's own instances, only allows certain other server apps.
And since Hubzilla and (streams) both aren't based on ActivityPub, and ActivityPub is optional on both, they can theoretically completely raise the drawbridge and cut everything based on ActivityPub off in one fell swoop. In this case, they can only interact with each other, and Hubzilla can also optionally interact with diaspora* and Friendica via the diaspora* protocol. In fact, I know one (streams) group where ActivityPub was deactivated with the very intention to keep Mastodon out.
The main issue of all four has to be UX. None of the four has an official iOS and/or Android app. Friendica is from 2010 and designed for standard desktop browsers, and the others are the only survivors of a long family of forks. They can all be set up as progressive Web apps, but nobody knows what that even is, much less how to do that. Also, people need something with the same name as the server application that they can install from the Apple App Store or the Google Play Store.
Friendica is the only one of the four with third-party apps with a native mobile UI. Even then, there's exactly one app readily available in the Apple App Store and the Google Play Store, RaccoonForFriendica, and it's so brand-new that it has only just had its first "stable" release (version 0.1.0). All that Hubzilla has is Nomad, an app only available on F-Droid that's a specialised browser for the Web interface, and that has last seen a new version almost five years ago. (streams) has nothing, Forte even less because it's so new and bleeding-edge that it currently has exactly one private instance with exactly one user.
Truth be told, a mobile app with a fully native mobile UI for (streams) and Forte would be so deep that it'd rival K-9 Mail in complexity, and such an app for Hubzilla would be even more complex.
Friendica supports the Mastodon client API, but no app out there that can be used with Friendica covers more than a small subset of Friendica's features. Basically, unless it's Fedilab, you're forced to use Friendica like Mastodon. In this regard, it'd be completely foolish to add the Mastodon client API to Hubzilla, (streams) or Forte. It wouldn't happen anyway because the devs refuse to have too much proprietary, non-standard Mastodon technology on board.
One could say that the UX is a general issue. This is partially because, again, Friendica was geared towards the desktop almost one and a half decades ago with a Web UI designed by a protocol developer. At least, its UI has taken some cues from Misskey apparently.
Hubzilla's only remaining theme was dolled up this year with more colour configuration options, but otherwise, its only available theme and therefore its entire UX is stuck in 2012 when it was still named Red. New third-party themes are still in development. And while (streams) got a brand-new, fresh theme (appropriately named Fresh) which Forte inherited, it isn't modelled in the style of a 2024 mobile app either.
It certainly doesn't help that Friendica is a very complex piece of software. Forte is more complex. (streams) is another bit more complex. and Hubzilla is the most complex one of the four by far and, while technologically still more advanced than most of the Fediverse, stuck in 2012 in other UX-related things. In addition, Hubzilla is the only one of the four where you have to turn ActivityPub support on, and finding that "switch" is anything but straight-forward.
What doesn't help either is people's expectations. I'd say that people escaping from Facebook might get used to Friendica without too many problems, probably more easily than Mastodon which works entirely differently.
But what most people coming to the Fediverse are looking for is Twitter. Or something as close to Twitter as possible. You see it in the many Mastodonians who keep using Mastodon like Twitter.
Bluesky is an all-out, 1:1 clone of Twitter from about ten years ago, all the way to appearing to be (and actually mostly being) a centralised, monolithic silo just like Twitter.
Mastodon already repels people escaping from by both not really looking and feeling like Twitter and the prospect of having to choose an instance (which is FUD because the official app railroads newbies to mastodon.social). The millions who joined two years ago only joined because the vast majority of them were basically "told" that Mastodon, and therefore the Fediverse, is only one website: mastodon.social. Or mas.to. Or mstdn.social. You get the point, I guess.
Friendica, Hubzilla, (streams) and Forte aren't Twitter clones. They don't aim to be just like Twitter with all its shortcomings included. They aim to be sort of like Facebook, but better, with extra features and with Facebook's shortcomings removed. Facebook looks, feels and works nothing like . It never has. And so, these four are about as far away from being anything like as they could possibly be. And that's by design.
But it isn't user-friendly to those who are looking for the closest thing to the official mobile app.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Onboarding #Moderation #UI #UX
In other words, a centralised, monolithic, walled-up silo for total dumb-dumbs with Twitter's UI and Twitter's UX. An even closer Twitter clone than Bluesky.
And if it can't be centralised and monolithic and walled-up because it's a) decentralised itself and b) in the Fediverse, it must still present itself to the general public and everyone on as centralised, monolithic and walled-up. That's all they can handle. It even has to lie to the users on its own lighthouse instance to keep them on board.
.
#Long #LongPost #CWLong #CWLongPost #Twitter # #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse
Im Grunde ist es so einfach, wie Hubzilla eben ist. Wenn du Hubzilla zum Bloggen nehmen willst, ist das ein Kanal wie jeder andere auch, nur da du ihn eben als Blog fhrst. Da sind deine Posts dann Blogposts. Und neben dem ganzen Fediverse (unter den Apps ActivityPub nicht vergessen zu aktivieren) kann man dir auch per Atom-Feed (mit oder ohne Kommentare, wie es sich gehrt) und optional auch auf diaspora* (mu auch erst aktiviert werden) folgen.
Und sollte dir Mastodon mal auf den Keks gehen, kannst du unter deinem Hubzilla-Account einen zweiten Kanal fr dein Social Networking anlegen und zwischen dem und deinem Blog einfach hin- und herschalten.
Du kannst ja mit Hubzilla alles Mgliche und Unmgliche machen. Einfach mal Der Pepe (Hubzilla) folgen, der wirbt gerne dafr und schreibt gerade die Dokumentation neu. Der ist auch von ihm.
ffentliche, offene Hubzilla-Hubs gibt's einige, gerade in Deutschland, zumal Hubzilla von Deutschland aus maintaint wird. Ich bin selbst auf den beiden grten Hubs Netzgemeinde updatet schnell auf neue Versionen und hat den Chefentwickler als Co-Admin.
Wenn dir weder Friendica noch Hubzilla vertraut sind, solltest du eh auf einem ffentlichen Hub anfangen. Umziehen kannst du immer noch, gibt ja nomadische Identitt.
Wenn du aber unbedingt deinen eigenen Hub aufziehen willst, frag mal , der baut an einem spezialisierten Blog-Theme, das ein bichen mehr in Richtung Medium, WriteFreely oder Plume geht. Vielleicht willst du das installieren, dann hat er ein Versuchskaninchen mehr.
Was es aus der Familie sonst noch gbe, so der Vollstndigkeit halber:
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Blog #Hubzilla #Streams #(streams) #Forte Twitter support on Friendica and Hubzilla is technically still implemented, but factually ended when Twitter closed their API for third-party clients. That was when Musk was already at the helm.
Facebook support on Friendica must have started in late 2011 when Mike still maintained it, and it already ended in 2012, but that might have been when the community maintained Facebook.
By the way, diaspora* support came to Friendica in mid-2011 after about half a year of work, including a lot of reverse-engineering. Hubzilla, being a Friendica fork, has had it since it was launched.
OStatus support was removed from Hubzilla with version 6. I'd have to look up when it came out. Whether Friendica still supports it, no idea.
The uafilter was introduced to (streams) and Forte in September, 2024.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #StatusNet #diaspora* #Tumblr #Twitter #Facebook #Friendica #Hubzilla #Streams #(streams) #Forte The creations of one Mike Macgirvin (all of which were or still are in the Fediverse and connected to Mastodon, by the way) made all of this possible in some way.
Friendica was created in 2010 with connecting to everything and then some as a goal. It connects to the entire Fediverse, to diaspora*, to Tumblr, to Bluesky (without the Bridgy Fed bridge), even to e-mail, it can subscribe to RSS and Atom feeds while generating an Atom feed itself, and it used to connect to the OStatus protocol of StatusNet and GNU social, until fairly recently to Twitter and, for a while in the early 2010s, even to Facebook. I'm not kidding, really not. I was there myself.
Granted, the connections to Bluesky, Tumblr, Twitter and Facebook don't/didn't work like those to diaspora*, StatusNet and the ActivityPub-based Fediverse when Friendica still had its own protocol. You still need(ed) an account on the other side, but you integrate(d) that account into your Friendica account, and you post(ed) to your connections on Bluesky and Tumblr and Twitter and Mastodon just like to all your other connections.
However, especially Twitter and Facebook didn't want that. Twitter kept changing their API with no prior announcement, not only to keep third-party clients out, but probably also to keep Friendica and later Hubzilla out, at least for a while.
And Facebook changed its rules for developers (as a Friendica node admin, you needed to be registered as a dev on Facebook to be able to connect the Facebook add-on on your node to Facebook): Sending data to Facebook was still allowed, but extracting data was forbidden from then on. This made the whole Facebook add-on useless.
The only Fediverse server apps that really have something like this implemented are by Mike Macgirvin, too: (streams) from 2021 and Forte from August (he is currently the only user of the latter). They have a per-instance "user agent filter" that can operate either in a blocklist mode which keeps certain user agents out or in an allowlist mode which only lets certain user agents in. This filter is designed to also let through/keep out certain Fediverse server applications, including but not limited to Threads.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #StatusNet #diaspora* #Tumblr #Twitter #Facebook #Friendica #Hubzilla #Streams #(streams) #Forte That's why my image descriptions for my original images are so extensive: so that people learn what they need to know about the obscure virtual worlds my images are from to understand the images.
If they have the patience to read through one massive alt-text and, in addition, one frequently absolutely gargantuan long image description in the post, that is. (No character limit here.)
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Metaverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Four points:
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -exposure
Yup. For many fully sighted people, image-describing AI is a nicely convenient fire-and-forget alt-text generator. They've never seen any of their own alt-texts, much less edited any of them.
Threads uses the exact same image-describing AI as Facebook. It's infamous for how bad it is. I mean, there'll never be an AI that lives up to my standards, but seriously, Meta's AI is horrible.
CC:
#Long #LongPost #CWLong #CWLongPost #Meta #Threads #Facebook #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta (streams) and probably also Forte already offer two features in this direction.
One, they can import contact lists from ActivityPub or CSV files. Okay, that still requires the handling of files, knowledge where they are on your device and knowledge what files are in the first place. But you can connect to up to 1,000 actors in one fell swoop, provided you're willing to manage that many contacts.
Two, and this is for those who want to pick people or things to follow one by one: built-in connection discovery and connection suggestions la Facebook. A feature as old as Friendica, and Friendica is the oldest surviving Fediverse project, pre-dating Mastodon by five and a half years.
On your stream page which is hard-coded as your landing page, you have an area with two randomly changing connection suggestions on the left. It includes a link to a whole page dedicated to suggestions. On your connections page (which, unlike on Mastodon, is not buried in the settings it can actually be added to the navigation bar if you so desire so you can get there with one click), there's the same suggestion area. Right below it, there's a small area for searching for contacts which has another link to the suggestions page.
The suggestions page is actually only the directory of almost all Fediverse actors known to that server instance, but filtered for what may be interesting for you according to your profile. Of course, the results improve when you actually fill out your profile some, especially the keywords field. Each suggestion is presented with their various profile fields (if they've given permission to see their profile), numbers of followers and followed for ActivityPub actors (even though (streams) and Forte themselves don't distinguish between them), a handy big green button for connecting and a similarly big yellow button for removing that actor from the suggestions. Not just like on Facebook, but better than Facebook. This is what you may wish dating portals were like.
If the suggestions aren't sufficient, you may also peruse the whole directory. It contains all Fediverse actors known to that (streams) instance. My two (streams) channels are on an instance with only 13 channels altogether, but it still knows lots of actors from all over the Fediverse. The directory looks largely the same as when acting as a suggestions list, only without the Ignore button. You still get complete profile previews and, for ActivityPub actors, follower/followed counts.
The directory can be filtered by keyword, either by search field or by tag cloud. In addition, it can show
Again, it's impressive how much a (streams) instance with only 13 channels knows. A much bigger and much more diverse instance would also have a vastly bigger directory.
This, by the way, is also why topic-specialised or community-specialised instances make even more sense on (streams) and Forte than on Mastodon. For one, there's more interesting stuff and less uninteresting clutter in the directory. Besides, this goes doubly for the directory in local mode. Lastly, nomadic identity allows you to have the same channel on multiple instances anyway.
Granted, this is not as easy and convenient as following several dozen gamers or Linux users or climate activists with two clicks. But it goes well beyond what Mastodon offers already now.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Onboarding #StarterPacks #Streams #(streams) #Forte Und wenn man ihnen widerspricht, schreien sie "Reply Guying" und blockieren einen.
Nicht etwa, weil man eine Wahrheit ausgesprochen hat, die ihnen unbequem ist (wie bei all den Leuten, die unbedingt wollen, da das Fediverse nur Mastodon ist). Sondern weil man ihnen mit etwas widersprochen hat, das leider nicht offensichtlichermaen Unfug ist, sondern aussehen knnte, als htte es Hand und Fu.
Da behauptest du zwei Jahre lang steif und fest, das Fediverse ist nur Mastodon. Dann kommt einer von Firefish oder Friendica oder Hubzilla und sagt dir, das Fediverse ist nicht nur Mastodon, und Mastodon ist noch mit ganz anderen Sachen verbunden. Du wrdest das gerne als Schwachsinn abtun, um deinen eigenen Hintern zu retten. Ist nur eben bld, da der Umstand, da dir gerade einer geantwortet hat, der selber nicht auf Mastodon ist, direktweg der Gegenbeweis fr deine Behauptungen ist.
Aber genau deswegen sollte man solche Leute erst recht "reply-guyen" und "fedisplainen". Wer sich so auffhrt, hat das verdient. Leider werden sie das dann nur selber lesen und nicht ihre Followers, weil Mastodon keine Konversationen untersttzt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #ReplyGuy #ReplyGuys #Fedisplaining
These people only learn about the existence of a Fediverse outside of Mastodon either from a post that does loads of things which are completely impossible on Mastodon or from a reply guy on Akkoma, Firefish, Friendica, Hubzilla etc.
At least this guy did not freak out when he learned about the existence of a Fediverse outside of Mastodon. That is, I don't know how he'll react once a very un-Mastodon post hits his timeline.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Akkoma #Firefish #Friendica #Hubzilla #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #ReplyGuy #Fedisplaining
I was tempted to jump in myself and correct that guy about the Fediverse allegedly only being Mastodon. But this has been taken care of.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #ReplyGuy #FedisplainingI've just come to the realisation that putting long descriptions into external documents in the file space of my Hubzilla channel and then linking to them is a dumb idea. It's especially so for the use-case for which it was considered for, and that's posts with multiple embedded images.
It's untested. It's experimental. It might not even work for all I know. It's inconvenient for mobile users because their browser will pop up when they tap the link to the long image description in their Mastodon apps. That is, if it works they way I intend it to work. Which, again, I'm not sure about.
But most of all, it creates too much redundancy.
If I put all my long image descriptions into separate documents, then everything that's in all images likewise will have to be described in all its details once for each image. And all explanations that usually come with my long image descriptions will have to be there once for each image. If I have four images, I need four times the same explanation of way over 1,000 characters where the images were made even though they were all made in the very same place.
That's because I can't expect everyone to open and read all long descriptions. In fact, I can't count on everyone opening and reading the first long description. Thus, I can't explain everything only in the first long description. If someone only opens the second or third or fourth long description, they'll be missing a whole lot of explanation because it's only in the first description.
Sure, I could tell people where the explanations are. But that'd mean that the alt-text for the fourth image would tell them about the long description for the fourth image, but the long description for the fourth image would be very incomplete and refer people to the long descriptions of the first three images. Having to read five descriptions in five separate places in two apps for one image is even more cumbersome than having to read two descriptions in two different places in two apps for one image.
On the other hand, if I put all my long image descriptions into the post itself like I've always done since I've started taking image descriptions seriously, they wouldn't be right below the images proper in a post with multiple images embedded in-between text. But they'd be in the very same place as the images.
More importantly, they'd all be in the same place, full stop. I could do as I've always done recently. I could start with a common preamble for all four image descriptions in which I explain common stuff, and in which I even describe common stuff. And then I could let the specific descriptions for the individual images follow. Each bit of information would be there only once in one place and not four times over in four separate places.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta If they notice.
Thing is: If someone on Pleroma, Akkoma, Mitra, Friendica, Hubzilla, (streams) or Forte quote-posts someone else, that someone else is notified as if they've been mentioned. If they're notified when they're mentioned by a non-contact out of the blue, that is. Mods might not notice.
If someone on Misskey or any of its various still active forks and fork-forks quote-posts someone else, that someone else is not notified, and neither are any mods unless they happen upon the quote-post.
Also, nobody and nothing on Mastodon can prevent anybody outside of Mastodon from quote-posting anyone on Mastodon. And there's a whole lot outside of Mastodon that can and will always be able to quote-post Mastodon toots with zero resistance. See my start post in this thread for 18 server apps that can do that.
However, this much should be said: Friendica has had quote-posts for over 14 years. Hubzilla has had quote-posts for, technically speaking, almost 13 years. And never in all these years have quote-posts been used on either to harass anyone on Friendica, on Hubzilla, on Mastodon or elsewhere.
Sounds hard to believe for people who only know Twitter and Mastodon, I know. But Friendica and Hubzilla aren't almost entirely populated by people who came from Twitter. They aren't Twitter alternatives anyway. Friendica is a Facebook alternative, and Hubzilla is a Facebook alternative on coke and steroids. Both have a totally, completely different culture from Twitter as well as from Mastodon, both early Mastodon and today's Mastodon. There is no influence from Twitter on them whatsoever.
In fact, until Hubzilla 9.0 which came out this year, Hubzilla did not even have repeats (= retweets = boosts). It had always used quote-posts (= shared posts in Hubzilla lingo) for this purpose.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate Scott M. Stolz
More specifically:
On Twitter/, hateful right-wing people harass members of marginalised minorities (BIPoC, 2SLGBTQIA+ etc.) by quote-tweeting one of their tweets, mocking them in the tweet that quote-tweets them and then having others mock them even more in the replies. This is so commonplace that it feels like the only use-case that quote-tweets still have on .
#Long #LongPost #CWLong #CWLongPost #Twitter # #QuoteTweet #QuoteTweetsTejan Ausland Yes, but many on Mastodon don't understand this.
For them, the Mastodon devs are the creators and keepers of the Fediverse itself as well as "the good guys" who have made the single most awesome piece of server software in decades. If the Mastodon devs even only imply that an opt-out or opt-in switch for quote-posts will bring absolute safety from being quote-posted, they take it at face value.
So when they opt out of being quote-posted, and someone from outside of Mastodon quote-posts them anyway, they won't blame it on the Mastodon devs having promised them something impossible. Never would the Mastodon devs do that.
Rather, the devs behind whatever that someone is using are the bad guys. They're rogues, they're evil hackers who have introduced quote-posts just to be able to spite and harass Mastodon users. Why else would something introduce quote-posts after all
The one thing that'll protect wherever that someone is from their wrath is that most of them won't be able to figure out what that someone is using. Just because Mastodon users can look up a post at its source, doesn't mean they know they can, much less they actually do.
So they may try to get allegedly rogue instances Fediblocked just because these instances are non-Mastodon instances doing what they regularly do. They may succeed because at least some blocklist maintainers don't have a clue about the Fediverse outside Mastodon, its capabilities and its culture either. But it's unlikely that they'll pinpoint this culprit having used Sharkey, have all of Sharkey Fediblocked for being able to "circumvent" Mastodon's quote-post opt-out/opt-in, then pinpoint that the next quote-poster is using Akkoma and have all of Akkoma Fediblocked and so forth.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Blocklist #Blocklists #BlocklistMeta #FediblockMetaBy the way, there's exactly one way of being safe from being quote-posted in the Fediverse:
Move to Hubzilla or (streams). Keep all optional communications protocols off, including ActivityPub. Disallow quoting and mirroring of your posts entirely in your channel role (on Hubzilla) or keep your channel type on Limited ((streams)). Make sure that none of your contact roles (Hubzilla) or permission roles ((streams)) allows it. Try to live with only contacts on Hubzilla and (streams) none of them would ever use quote-posts for nefarious reasons, but better safe than sorry. Always post to a restricted audience so that sharing your posts isn't possible anyway. And never comment on public posts so that sharing your comments isn't possible either.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebateOne of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace
When I post an image, it's almost always about something that the majority of my audience don't know enough about. And the above remarks give me the impression that especially the Fediverse loves explanations for stuff it doesn't understand being served on a silver platter. So I consider it good manners for myself to explain everything down to the level on which I can assume the general Fediverse public to be.
However, explanations don't belong into alt-text because not everyone can access alt-text. Also, my explanations tend to be too long for alt-text. Hence, I put them into the post. Everyone who can access my posts in some whay can also access the explanations.
This goes even more for my meme posts than for my original images. And I consider it insufficient to only explain the image itself. For when I post a meme, I actually post a meme, i.e. not a random im age with text on it, but an image macro based on a meme template that is established as such. Not everyone always gets these templates, so I have to explain them. Even fewer people get what my meme images are about, or what do you think how many people know right off the bat what FEP-ef61 is So I have to explain that as well.
Well, and then I have to explain my explanations. A KnowYourMeme-level explanation of the One Does Not Simply Walk Into Mordor meme template is not understandable for people who don't know what an image macro is or what a snowclone is. A KnowYourMeme-level explanation of snowclones is not understandable for people who don't know what 4chan is. My explanation of FEP-ef61 is not understandable for people who don't know what nomadic identity is, what Hubzilla is and what the streams repository is. And so forth.
So if I have to explain everything in my post because people find clicking or tapping links inconvenient, I have to really break everything down to the absolute basics and write absolutely massive explanation sections. But if I don't explain anything, my image posts, my meme posts in particular, go whoosh above people's heads, and they feel discriminated by another nerdy "techbro" who can't be bothered to explain anything, or who intentionally doesn't explain anything to keep "normies" away.
What I do now is give links to whatever can be explained externally and explain everything else myself.
CC:
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes
Das ist von der Diskussionskultur im Fediverse brig geblieben. Die "gebildeten" stecken sich Knetw in die Ohren und singen laut la la la, um die Wahrheit nicht horen zu mssen
Einige scheinen zu glauben, wenn sie gegen alles um sie herum vorgehen, das darauf hindeutet, da das Fediverse nicht nur Mastodon ist, dann wird das Fediverse wieder zu nur Mastodon, und alle Instanzen von allem anderen verschwinden.
Auch wenn das Fediverse zu keinem Zeitpunkt je nur Mastodon war. (Nein, war es wirklich nie. Auch 2016 nicht.)
So manch einer scheint auch wirklich aktiv an einem Fediverse fr sich selbst zu bauen, das wirklich nur Mastodon ist. Jeder, der von einem Fediverse jenseits von Mastodon schreibt, wird gemutet oder geblockt. Jeder, der ganz offenkundig selbst nicht auf Mastodon ist (Textformatierung, "komische" Erwhnungen und Hashtags, oft auch ber 500 Zeichen), wird gemutet oder geblockt. Oder am besten gleich die ganze Instanz.
Und dann gibt's Leute, die gengend ffentliche Reichweite haben, da sie darber versuchen knnen, das Nicht-Mastodon-Fediverse zu zerstren, indem sie dessen Existenz aktiv leugnen und bestreiten.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediMeta #Fediverse #Mastodon #NichtNurMastodon Long Vor allem sind die Hubzilla-Zahlen noch verzerrter als die Mastodon- und Friendica-Zahlen, weil die FediDB nicht nur nichts von mehreren Kanlen auf einem Konto wei (was auch gut ist, weil die Alternative das Graben in der Datenbank und das Erfassen und Registrieren individueller Nutzer erfordern wrde), sondern auch nichts von Klonen. Hubzillas Siteinfo rckt ja nur mit der Zahl der Kanle raus, aber weder mit der Zahl der Konten noch mit der Zahl der Kanle, die Hauptinstanzen sind und keine Klone und schon gar nicht mit der Zahl der Konten, die Kanal-Hauptinstanzen enthalten. (Wre mal ein Feature Request.)
Das heit, wenn du ein Konto auf einem Hub hast, aber fnf Kanle auf dem Konto, sind das fr die FediDB fnf User. Wenn du einen Kanal hast, von dem aber zur Sicherheit drei Klone, sind das fr die FediDB vier User. Drei Kanle auf demselben Konto, davon dann jeweils zwei Klone auf zwei anderen Hubs, und die FediDB sieht das als neun User.
Auerdem zhlt auf Hubzilla sowieso sehr viel als User, auch wenn es nicht mit Mastodon interagiert. ist ein Hubzilla-Kanal, zhlt also als User. Hchstwahrscheinlich ist sie geklont und zhlt dann als mehrere User. Jedes Forum zhlt als mindestens ein User. Jeder Kanal, der einfach nur als persnlicher CalDAV- und CardDAV-Server und vielleicht noch als WebDAV-Fileserver genutzt wird, aber nirgendwohin fderiert, zhlt als mindestens ein User. Jeder Kanal, der als RSS/Atom-Aggregator luft, aber auch nirgendwohin fderiert, zhlt als mindestens ein User. Und Stichwort Bots: Jeder Kanal, der berhaupt als reiner Channel-Source-Bot luft, zhlt auch als User.
Was die MAUs angeht, werden allerdings nur die gerechnet, die sich wirklich eingeloggt haben. Das drfte die Bots rausrechnen, denn wer loggt sich regelmig in seinen Bot ein
Auch wenn du dich in deine Klone einen Monat lang nicht einloggst, gelten die nicht als "aktive User", auch wenn sie natrlich weiterlaufen. In der Praxis ist also auf Hubzilla der Anteil derjenigen, die wirklich noch bei der Stange sind, relativ hoch, weil ein wohl nicht zu unterschtzender Teil der "inaktiven User" auf Klone, Channel-Source-Bots und reine Webpage-Kanle entfllt.
Auf Friendica ist er so niedrig, weil Friendica schon uralt ist und wahrscheinlich noch ein paar uralte Nodes hat mit Karteileichen, die seit vielen Jahren nicht mehr dabei sind. Gleichzeitig hat es da nie den groen Hype gegeben, der zwischendurch neue User reingesplt htte. Andererseits hinterlassen auch auf Hubzilla sowohl Newbies als auch erfahrene User inaktive Kanle. Erstere, weil sie eh nie ihre toten Accounts beseitigen, letztere, weil sie wissen, da es aufwendig wre, auf demselben Hub einen Kanal mit demselben Namen neu anzulegen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Statistik #Friendica #Hubzilla #NomadischeIdentitt Ganz ehrlich: Die Zweckentfremdung des Zusammenfassungsfelds von StatusNet fr CWs, die 2017 von einem Nutzer (!) in Mastodon implementiert wurde, ist eine ble Krcke von jemandem, der keine Ahnung hatte, wie das Fediverse auerhalb von Mastodon aussah.
Zum einen: Wenn man bestimmten Content wirklich loswerden will, dann sollte man den eh rausfiltern. Es bringt nix, sich auf Dauer von allen anderen verhtscheln und bettern zu lassen. Eigeninitiative bringt hier mehr. Dafr braucht es aber Schlsselwrter in den Beitrgen, die die Filter auslsen.
Zum anderen: Wenn man bestimmten Content einfach nicht offen angezeigt haben will, dann geht das sehr viel lnger sehr viel eleganter, als es Mastodon berhaupt gibt. CWs sollten eigentlich individuell leserseitig generiert und nicht allen Nutzern identisch aufgezwungen werden. Und das ist keine Raketenwissenschaft.
Friendica hat wahrscheinlich schon seit 2010 eine Funktion namens "NSFW". Die ist optional, besteht einfach nur aus einer Wortliste und versteckt alles, was irgendwas enthlt, was auf der Wortliste ist, hinter einem Button. Hubzilla, (streams) und Forte haben das auch, und mindestens diese drei knnen auch RegEx in der Wortliste. Sogar Mastodon kann mit seinen Filtern seit zwei Jahren CWs generieren.
Nichts davon scheint aber irgendjemand zu wissen. Alle wollen sie verhtschelt und in Watte gepackt werden mit CWs, die fr sie individuell zugeschnitten sind, die aber alle da drauen gleichermaen so bekommen. Und gleichzeitig macht sich praktisch niemand die Mhe, unangenehme Posts mit entsprechenden Hashtags oder Schlsselwrtern zu versehen, um die Filter auszulsen. Statt dessen kann man auf den Sack bekommen sowohl fr fehlende CWs als auch fr mehr als vier Hashtags.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Filter Speaking of meme posts, how do you prefer them explained, if at all
Neither the meme nor the topic
The meme not at all, the topic with links, if possible, otherwise not at all
The meme not at all, the topic with links, if possible, otherwise extensively in the post
The meme not at all, the topic extensively in the post
Both with links, if possible, otherwise not at all
Both with links, if possible, otherwise extensively in the post
Both extensively in the post
I'm asking because my meme posts tend to be about very obscure topics such as virtual worlds that not even 50 people in the whole Fediverse know or the Fediverse beyond Mastodon. On the one hand, I've got the impression that many people would love to have everything explained in such a way that no special prior knowledge is necessary. On the other hand, I know that they nope out when I tell them how long a full set of explanations can be.
I've actually tested a full set of explanations with . By the way, that place is very much part of the Fediverse. I ended up with a whole of nine explanations. One for the image itself. One for the meme template. Five in order for people to understand the meme template and the explanations for the meme template. One for the topic. One in order for people to understand the topic.
I've served people just about all information they may need to get the image, but it took me over 25,000 characters to do so.
CC:
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes Well, the quality and usefulness of image descriptions in general and alt-text in particular can not only vary greatly, depending on the circumstances, but it's also very subjective.
One user could say that an alt-text of 200 characters is sufficient, or even that a longer alt-text is too long. Another user could say about the same image that they need a full, detailed description of all visual elements plus explanations of everything they aren't familiar with because the content of the image is apparently very interesting, but too obscure.
I myself prefer to err on the side of "too much", sometimes taking several days to describe one measly image. Not everyone likes the outcome, but some applaud it.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Auf gar keinen Fall sollte man den Leuten beim Onboarding ins Gesicht lgen, da das Fediverse ausdrcklich Mastodon, nur Mastodon und nichts als Mastodon ist. Auch nicht der Einfachheit halber.
Es gibt jetzt schon zuviele Leute auf Mastodon, die der felsenfesten berzeugung sind, da das Fediverse nur Mastodon ist. Das Harmloseste ist noch, wenn sie fr "das Fediverse" Features fordern, die das Fediverse schon fnfeinhalb Jahre lnger hat, als es Mastodon berhaupt gibt.
Wenn sie zu lange glauben, das Fediverse ist nur Mastodon, gewhnen sie sich auch dran. Das Fediverse, das ist fr sie ihr liebes, nettes, flauschiges Wollmammut und sonst nichts. So, und wenn dann aber ein Post oder Kommentar daherkommt wie der hier, der aber sowas von nicht von Mastodon ist, dann kacken sie vor Schreck ber das, was so nie htte passieren knnen, Ziegelsteine in die Hose und gehen in eine Abwehrstarre ber.
hnlich dramatisch kann es enden, wenn man versucht, ihnen zu erklren, da das Fediverse nicht nur Mastodon ist. Egal, ob sie sich gerade ber einen ber-500-Zeichen-"Trt" von einer "gehackten Mastodon-Instanz" aufregen. Egal, ob sie flschlicherweise direktweg behaupten, das Fediverse und Mastodon seien dasselbe. Egal, ob sie der absolut felsenfesten berzeugung sind, im Fediverse gibt's keine Quote-Posts (doch, die gibt's, die gibt's auch schon fnfeinhalb Jahre lnger als Mastodon). Mitunter wird man erst angeschnauzt und dann blockiert. Das wollen diese Leute nicht hren. Die wollen, da das Fediverse nur Mastodon ist.
Frag mal . Der ist auf Friendica, das eben schon fnfeinhalb Jahre lter ist als Mastodon. Der hat mal einer Mastodon-Nutzerin mit mehr als 500 Zeichen geantwortet. Die hat sich ber seinen viel zu langen "Trt" aufgeregt und, ich meine, auch ber seine angeblich manipulierte Mastodon-Instanz.
Er mute ihr dann erst erklren: Nein, er ist nicht auf Mastodon. Er ist auf Friendica. Nein, Friendica ist keine Mastodon-Instanz. Friendica ist ein komplett eigenstndiges Produkt. Ja, es ist mit Mastodon verbunden. Ja, das ist normal. Nein, das Fediverse ist nicht nur Mastodon.
Das endete dann damit, da sie ihn blockiert hat, weil er in ihren Augen ein bser Black-Hat-Hacker ist, der sich mit seinem bsen Black-Hat-Hackertool Friendica illegalerweise ins Mastodon-Fediverse reingehackt hat. Kein Witz, das ist so passiert. Frag ihn.
berhaupt regt sich die "Fediverse = Mastodon"-Fraktion schnell auf, wenn man etwas macht, was entweder auf Mastodon technisch nicht mglich ist oder gem Mastodon-Kultur verpnt oder beides. Diese Leute wollen die Mastodon-Kultur im ganzen Fediverse durchsetzen, und zwar mit aller Gewalt und gegen alle Widerstnde.
Als Hubzilla-Nutzer bin ich dann immer in Erklrungsnotstand. Hubzilla ist keine Mastodon-Instanz. Es funktioniert komplett anders als Mastodon. "Die" haben das anders gemacht als Mastodon, weil "die" es vor Mastodon gemacht haben. Hubzilla ist zehn Monate lter als Mastodon und basiert auf einem Fork von Friendica, das fnfeinhalb Jahre lter als Mastodon ist. Das Fediverse ist also nicht nur nicht nur Mastodon, sondern es wurde auch nicht mit Mastodon erfunden.
Trotzdem wird man dazu gezwungen,
- seine "Trts" auf maximal 500 Zeichen zu beschrnken, auch wenn man noch nie irgendein Zeichenlimit hatte, und lngere "Trts" in Threads aufzubrechen (der Friendica-Nutzer wird dich fr genau dieses Verhalten brigens blockieren)
- keinerlei Textformatierung zu verwenden, weil das strt
- nicht nur CWs wie bei Mastodon zu verwenden, auch wenn Mastodons CW-Feld auf Hubzilla schon lnger ein Zusammenfassungsfeld ist, als es auf Mastodon ein CW-Feld ist, sondern geflligst das "CW-Feld" nur fr CWs zu verwenden und nicht fr Zusammenfassungen (brigens kann ich bei Antworten keine CWs anfgen)
- nicht mehr als vier Hashtags zu verwenden, scheiegal, ob Hubzilla selbst die braucht, um seine eigenen automatisierten leserseitigen CWs zu generieren
Noch was: Ich wei nicht, ob du schon davon gehrt hast, aber Mastodon will ja Quote-Posts einfhren. Da gab es vor geraumer Zeit einen Feature Request auf GitHub. Aber die Anfragerin wollte dazu noch zwei Dinge. Zum einen einen Opt-in-Schalter, mit dem man erst quotepostbar wird. So eine Funktion wird aber von ActivityPub nicht untersttzt, das wre also ein proprietres Non-Standard-Feature, das nur Mastodon htte. Und sie forderte eine Regel fr alle Mastodon-Instanzen, da Instanzen, die sich an den Opt-in nicht halten, gefediblockt werden sollen.
Aus "Mastodon = Fediverse"-Sicht klingt das erstmal gut, oder Was soll daran schon schlimm sein
Wie ich schon schrieb: Das Fediverse hat Quote-Posts jetzt schon. Mastodon hat sie nicht, aber das Fediverse hat sie. Stand damals gab es Quote-Posts unter anderem auf Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla und (streams). Die waren alle damals schon im Fediverse, die waren alle damals schon mit Mastodon fderiert, und somit konnten die alle damals schon ohne groe Probleme Mastodon-Trts quote-posten.
Wenn aber Mastodon so ein Opt-in-Eigengezcht einfhrt, dann haben die das nicht automatisch auch alle. Noch einmal: Mastodon wird sich dabei an keine Standards halten, weil es dafr keinen Standard gibt. Das bedeutet: Stand heute wren alle, aber auch wirklich alle Instanzen von Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, Iceshrimp, Catodon, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla, (streams) und Forte problemlos in der Lage, Mastodon-Trts auch dann zu quote-posten, wenn der Opt-in-Schalter aus ist.
Wenn also auch die Regel dazukme, mten alle Mastodon-Instanzen mit sofortiger Wirkung alle Instanzen von Pleroma, Akkoma, Misskey, Firefish, Sharkey, CherryPick, allen anderen Misskey-Forks, Mitra, Friendica, Hubzilla und (streams) fediblocken. Nur weil da eine Regel durchgedrckt wurde von jemandem, der nicht mal damit rechnet, da es im Fediverse noch etwas anderes als Mastodon geben knnte.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon Here's a list that I've compiled over the years. It may be incomplete, though.
- Ableism
- Abuse
- Alcohol (Alc)
- Animal cruelty
- Animal death
- Autism
- Blood
- Menstruation
- Caps
- Cars
- Cats
- COVID/COVID-19/Coronavirus/Pandemic
- Crying
- Death
- Disability
- Drugs
- Extremism
- Eye contact (EC)
- Facebook links
- Family
- Fascism
- Flashing images
- Food
- Diet
- Healthy food
- Meat
- Gore
- Gross
- Guns
- Gun violence
- Health/Illness
- Bodily fluids
- Medicine
- Mental health (MH)
- Physical health (PH)
- Teeth
- Homophobia
- Horror
- Insects
- Instagram links
- Long/Long Post (anything that exceeds 500 characters)
- Meta
- Fediblock
- MastoAdmin/FediAdmin
- Misogyny
- Money
- Natural Disaster
- Earthquake
- Flood
- Nazis
- Needles
- News
- Not safe for work (NSFW)/Lewd
- Nudity
- Partial nudity (anything that covers less than a pair of boxer shorts plus, for persons or human or anthropomorphic characters with female physical characteristics, a typical bikini top)
- Police
- Politics (Pol)
- Australian politics (AUSPol)
- Belgian politics (BEPol)
- Brazilian politics (BRPol)
- British politics (UKPol)
- Canadian politics (CANPol)
- Chinese politics (CNPol)
- Danish politics (DKPol)
- Dutch politics (NLPol)
** European Union politics/EU politics (EUPol) - French politics (FRPol)
- German politics (DEPol)
- Israeli politics (ILPol)
- New Zealand politics (NZPol)
- Norwegian politics (NOPol)
- Palestinian politics (PSPol)
- Polish politics (PLPol)
- Russian politics (RUSPol)
- Swedish politics (SVPol)
- US politics (USPol)
- California politics (CAPol)
- Florida politics (FLPol)
- Georgia politics (GAPol)
- Illinois politics (ILPol)
- New York politics (NYPol)
- Texas politics (TXPol)
- etc.
- Pregnancy
- Abortion
- Public display of affection (PDA)
- Racism
- Religion
- Science
- Selfie
- Sex
- Sexism
- Sexual violence
- Rape
- Shitpost
- Snakes
- Spiders
- Spoilers
- Suicide
- Suicidal ideation/Suicidal thoughts (SuI)
- Thread
- Transmisia
- Transphobia
- Twitter/X
- Twitter/X links
- Ukraine
- Unfriendly for screen readers
- Violence
- Weight loss
- Wordle
- Work
- YouTube links
- Content warning meta
- Fediverse meta
- Fediverse beyond Mastodon meta (if Mastodon and other Fediverse server applications are mentioned)
- non-Mastodon Fediverse meta (if only Fediverse server applications that aren't Mastodon are mentioned
- Hashtag meta
- Image description meta
- Alt-text meta
That's because the place where I am, which is federated with Mastodon but has nothing at all to do with Mastodon, has its own content warning culture: Instead of forcing content warnings on everyone in the summary field (yes, it actually is the summary field), we have our own individual content warnings automatically generated reader-side from a customisable keyword list. However, in order for this to work, the keywords need to be present in the to-be-warned-about content. This works best with hashtags.
That, and I've got no means to add Mastodon-style content warnings to replies.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CW #CWs #CWMetaDa aber der Gruppenserver von QOTO der einzige moderierte Gruppenserver im ganzen Fediverse ist, ist vollkommener Bldsinn. Jeder Friendica-Node, jeder Hubzilla-Hub, jede (streams)-Instanz und, na ja, die momentan eine Forte-Instanz untersttzen moderierte Gruppen, und das im Falle von Friendica schon sehr viel lnger, als es Mastodon berhaupt gibt. Auerdem haben alle vier im Gegensatz zu Mastodon schon im Kern von vornherein volle Untersttzung von Gruppen.
brigens scheint der Gruppenserver im Moment eh funktionslos zu sein.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QOTO #Friendica #Hubzilla #Streams #(streams) #Forte #GruppenPower lines.
exposure
Power lines.
exposure
Russia says U.S. missile decision could raise the stakes in Ukraine war
Washington is easing limits on what Ukraine can strike with U.S.-made weaponry, U.S. officials told The Associated Press on Sunday.
-rangemissiles
Hubzilla can have
- a local public stream or
- a federated public stream
- to anyone or
- to anyone who can be recognised as logged in, either locally or remotely via OpenWebAuth, or
- only to logged-in local users or
- to nobody
IANAL, but AFAIK, at least by German law, an admin can be held liable for anything that happens on their website. A Hubzilla hub admin can be held liable for anything nasty that's being washed onto their hub from one of their users' connections, and that shows up in the public stream. There's little to nothing they can do against it. They can moderate the public stream, but that'd require constantly watching the public stream they can't be online 24/7 to do so. And since Hubzilla is all about self-promotion, no Hubzilla hub will ever have a moderator team located all around the globe.
It's simply safer to keep the public stream off.
Now, a lot of public Hubzilla hubs are German, and so are a lot of public Friendica nodes.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla That said, you can't point fingers and put the blame on non-Mastodon server applications because they don't work exactly like Mastodon.
They've got different premises. Friendica was designed to be an alternative to Facebook, and it pre-dates Mastodon by five and a half years. Hubzilla, (streams) and Forte are in the same family of forks by the same creator with more or less the same premise. Socialhome is another Facebook alternative, and the fact that it can federate with diaspora*, just like Friendica and Hubzilla, goes to show how old it is. It should be clear that neither of the five is an add-on to Mastodon.
Nobody can demand from them to throw their entire conversation support overboard and become more like Mastodon, just because Mastodon is the biggest Fediverse project, and to more people than not, Mastodon is the Fediverse. That is, people can try, but they can't expect this to happen.
It's even less likely to happen than Friendica throwing its old native culture, geared towards its feature set and its conversation support, out of the window and completely replace it with Mastodon's culture which is largely incompatible with Friendica's technology.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Socialhome
Russia says U.S. missile decision could raise the stakes in Ukraine war
Washington is easing limits on what Ukraine can strike with U.S.-made weaponry, U.S. officials told The Associated Press on Sunday.
-rangemissiles
As far as contact discovery goes, that point goes to the actual social networking server apps in the Fediverse, the Facebook alternatives, rather than the microblogging server apps that are being misused as social networks. I think doesn't suggest potential new contacts to you, and Mastodon definitely doesn't. But Facebook does, and so do Friendica and the rest of its family (Hubzilla, (streams), Forte). (streams) could be the king of this because it can find both all kinds of ActivityPub actors (unlike Hubzilla) and actors using the nomadic protocols on which Hubzilla and (streams) itself are based (unlike Friendica), if only it had more and especially larger public instances.
By the way, only a week ago, I wrote .
Also, all four are better equipped for finding your own kind of people. You don't need instances for specific target audiences which newbies will almost never hear of. You don't have to fumble around with hashtags, not even knowing what the "right" hashtag for a certain topic is.
That's because all four have native built-in support for discussion groups. Pretty much all the Fediverse can connect to these groups, but it's here where these groups are at home, and Mastodon doesn't even understand the concept of groups. Not to mention that, unlike Guppe groups, these groups can be moderated. And at least on Hubzilla, (streams) and Forte, they can be fully private so that non-members can't look inside and even hidden from public directories.
As far as moderation goes, especially Hubzilla, (streams) and Forte are geared towards self-moderation. They have extensive permissions systems on three levels (per channel, per contact, per post). In combination with their understanding and system of conversations (which Mastodon completely lacks as well), you can moderate your own threads and even delete offending comments. Unfortunately, you can't have them purged from the whole Fediverse.
Also, the reliance on self-moderation means that neither of the three has a Report button or even only a report system built in, so they don't understand Mastodon's report system either. If you need to report something to one of the instance admins, you'll have to send them a DM. Most public Hubzilla hubs only reveal who the admins are in the JSON-formatted siteinfo. On (streams) and Forte, you'll have to go to the directory, have only local channels shown, sort them by age and guess which of the oldest actually local channels are admins.
That said, Hubzilla, (streams) and Forte have much more radical methods at hand for keeping unwanted stuff out than Mastodon. Most Fediverse server applications allow for admins to block entire instances, many, (streams) and Forte included, even give users this power. But (streams) and Forte have received a new feature called "user agent filter" in September which is capable of blocking entire Fediverse projects on a per-instance level. It was mainly designed as a more advanced counter-measure against Threads, but it can just as well be used to lock out the entirety of Mastodon, Glitch included, or the entirety of Pleroma, for example. It can even operate on an allowlist which, in addition to (streams)/Forte's own instances, only allows certain other server apps.
And since Hubzilla and (streams) both aren't based on ActivityPub, and ActivityPub is optional on both, they can theoretically completely raise the drawbridge and cut everything based on ActivityPub off in one fell swoop. In this case, they can only interact with each other, and Hubzilla can also optionally interact with diaspora* and Friendica via the diaspora* protocol. In fact, I know one (streams) group where ActivityPub was deactivated with the very intention to keep Mastodon out.
The main issue of all four has to be UX. None of the four has an official iOS and/or Android app. Friendica is from 2010 and designed for standard desktop browsers, and the others are the only survivors of a long family of forks. They can all be set up as progressive Web apps, but nobody knows what that even is, much less how to do that. Also, people need something with the same name as the server application that they can install from the Apple App Store or the Google Play Store.
Friendica is the only one of the four with third-party apps with a native mobile UI. Even then, there's exactly one app readily available in the Apple App Store and the Google Play Store, RaccoonForFriendica, and it's so brand-new that it has only just had its first "stable" release (version 0.1.0). All that Hubzilla has is Nomad, an app only available on F-Droid that's a specialised browser for the Web interface, and that has last seen a new version almost five years ago. (streams) has nothing, Forte even less because it's so new and bleeding-edge that it currently has exactly one private instance with exactly one user.
Truth be told, a mobile app with a fully native mobile UI for (streams) and Forte would be so deep that it'd rival K-9 Mail in complexity, and such an app for Hubzilla would be even more complex.
Friendica supports the Mastodon client API, but no app out there that can be used with Friendica covers more than a small subset of Friendica's features. Basically, unless it's Fedilab, you're forced to use Friendica like Mastodon. In this regard, it'd be completely foolish to add the Mastodon client API to Hubzilla, (streams) or Forte. It wouldn't happen anyway because the devs refuse to have too much proprietary, non-standard Mastodon technology on board.
One could say that the UX is a general issue. This is partially because, again, Friendica was geared towards the desktop almost one and a half decades ago with a Web UI designed by a protocol developer. At least, its UI has taken some cues from Misskey apparently.
Hubzilla's only remaining theme was dolled up this year with more colour configuration options, but otherwise, its only available theme and therefore its entire UX is stuck in 2012 when it was still named Red. New third-party themes are still in development. And while (streams) got a brand-new, fresh theme (appropriately named Fresh) which Forte inherited, it isn't modelled in the style of a 2024 mobile app either.
It certainly doesn't help that Friendica is a very complex piece of software. Forte is more complex. (streams) is another bit more complex. and Hubzilla is the most complex one of the four by far and, while technologically still more advanced than most of the Fediverse, stuck in 2012 in other UX-related things. In addition, Hubzilla is the only one of the four where you have to turn ActivityPub support on, and finding that "switch" is anything but straight-forward.
What doesn't help either is people's expectations. I'd say that people escaping from Facebook might get used to Friendica without too many problems, probably more easily than Mastodon which works entirely differently.
But what most people coming to the Fediverse are looking for is Twitter. Or something as close to Twitter as possible. You see it in the many Mastodonians who keep using Mastodon like Twitter.
Bluesky is an all-out, 1:1 clone of Twitter from about ten years ago, all the way to appearing to be (and actually mostly being) a centralised, monolithic silo just like Twitter.
Mastodon already repels people escaping from by both not really looking and feeling like Twitter and the prospect of having to choose an instance (which is FUD because the official app railroads newbies to mastodon.social). The millions who joined two years ago only joined because the vast majority of them were basically "told" that Mastodon, and therefore the Fediverse, is only one website: mastodon.social. Or mas.to. Or mstdn.social. You get the point, I guess.
Friendica, Hubzilla, (streams) and Forte aren't Twitter clones. They don't aim to be just like Twitter with all its shortcomings included. They aim to be sort of like Facebook, but better, with extra features and with Facebook's shortcomings removed. Facebook looks, feels and works nothing like . It never has. And so, these four are about as far away from being anything like as they could possibly be. And that's by design.
But it isn't user-friendly to those who are looking for the closest thing to the official mobile app.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Onboarding #Moderation #UI #UX
Russia says U.S. missile decision could raise the stakes in Ukraine war
Washington is easing limits on what Ukraine can strike with U.S.-made weaponry, U.S. officials told The Associated Press on Sunday.
-rangemissiles
Russia says U.S. missile decision could raise the stakes in Ukraine war
Washington is easing limits on what Ukraine can strike with U.S.-made weaponry, U.S. officials told The Associated Press on Sunday.
-rangemissiles
Biden OKs Ukraines use of U.S.-supplied long-range missiles in Russia .S.Official .s.SuppliedLongRangeMissile
What the masses fleeing from Twitter want is Twitter. Twitter without Musk, but otherwise Twitter.In other words, a centralised, monolithic, walled-up silo for total dumb-dumbs with Twitter's UI and Twitter's UX. An even closer Twitter clone than Bluesky.
And if it can't be centralised and monolithic and walled-up because it's a) decentralised itself and b) in the Fediverse, it must still present itself to the general public and everyone on as centralised, monolithic and walled-up. That's all they can handle. It even has to lie to the users on its own lighthouse instance to keep them on board.
.
#Long #LongPost #CWLong #CWLongPost #Twitter # #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse
Ploumanach by cbreadwine
Hubzilla-Veteran hier.Im Grunde ist es so einfach, wie Hubzilla eben ist. Wenn du Hubzilla zum Bloggen nehmen willst, ist das ein Kanal wie jeder andere auch, nur da du ihn eben als Blog fhrst. Da sind deine Posts dann Blogposts. Und neben dem ganzen Fediverse (unter den Apps ActivityPub nicht vergessen zu aktivieren) kann man dir auch per Atom-Feed (mit oder ohne Kommentare, wie es sich gehrt) und optional auch auf diaspora* (mu auch erst aktiviert werden) folgen.
Und sollte dir Mastodon mal auf den Keks gehen, kannst du unter deinem Hubzilla-Account einen zweiten Kanal fr dein Social Networking anlegen und zwischen dem und deinem Blog einfach hin- und herschalten.
Du kannst ja mit Hubzilla alles Mgliche und Unmgliche machen. Einfach mal Der Pepe (Hubzilla) folgen, der wirbt gerne dafr und schreibt gerade die Dokumentation neu. Der ist auch von ihm.
ffentliche, offene Hubzilla-Hubs gibt's einige, gerade in Deutschland, zumal Hubzilla von Deutschland aus maintaint wird. Ich bin selbst auf den beiden grten Hubs Netzgemeinde updatet schnell auf neue Versionen und hat den Chefentwickler als Co-Admin.
Wenn dir weder Friendica noch Hubzilla vertraut sind, solltest du eh auf einem ffentlichen Hub anfangen. Umziehen kannst du immer noch, gibt ja nomadische Identitt.
Wenn du aber unbedingt deinen eigenen Hub aufziehen willst, frag mal , der baut an einem spezialisierten Blog-Theme, das ein bichen mehr in Richtung Medium, WriteFreely oder Plume geht. Vielleicht willst du das installieren, dann hat er ein Versuchskaninchen mehr.
Was es aus der Familie sonst noch gbe, so der Vollstndigkeit halber:
- , das eigentlich namenlos ist, ist ein Urur...enkel von Hubzilla, ziemlich verschlankt, aber noch fortschrittlicher und in der Bedienung streckenweise
einfacherweniger kompliziert.
Vorteil eventuell: Du kannst auch Markdown und HTML nutzen und nicht nur BBcode.
Nachteil: Leider gibt's eigentlich nur noch eine ffentliche Instanz mit auch nur halboffener Registrierung, die man empfehlen kann. Die ist in den USA, und da mu man den Beitritt begrnden. Klar kann man das auch selber aufsetzen, aber wenn man es noch nicht kennt, sollte man erst woanders probefahren. - ist ganz neu, erst ein Vierteljahr alt, und es hat erst einen einzigen Nutzer, nmlich Mike Macgirvin selber. Im Prinzip ist es ein auf ActivityPub reduziertes (streams), das ansonsten alles kann, was auch (streams) kann. Zum Early Adopten ist es wohl noch etwas frh, nomadische Identitt ber ActivityPub ist noch nicht in freier Wildbahn getestet worden, wenn berhaupt, und Mike macht selbst noch keine groe Werbung dafr ich wollte es nur mal erwhnt haben.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Blog #Hubzilla #Streams #(streams) #Forte Twitter support on Friendica and Hubzilla is technically still implemented, but factually ended when Twitter closed their API for third-party clients. That was when Musk was already at the helm.
Facebook support on Friendica must have started in late 2011 when Mike still maintained it, and it already ended in 2012, but that might have been when the community maintained Facebook.
By the way, diaspora* support came to Friendica in mid-2011 after about half a year of work, including a lot of reverse-engineering. Hubzilla, being a Friendica fork, has had it since it was launched.
OStatus support was removed from Hubzilla with version 6. I'd have to look up when it came out. Whether Friendica still supports it, no idea.
The uafilter was introduced to (streams) and Forte in September, 2024.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #StatusNet #diaspora* #Tumblr #Twitter #Facebook #Friendica #Hubzilla #Streams #(streams) #Forte The creations of one Mike Macgirvin (all of which were or still are in the Fediverse and connected to Mastodon, by the way) made all of this possible in some way.
Friendica was created in 2010 with connecting to everything and then some as a goal. It connects to the entire Fediverse, to diaspora*, to Tumblr, to Bluesky (without the Bridgy Fed bridge), even to e-mail, it can subscribe to RSS and Atom feeds while generating an Atom feed itself, and it used to connect to the OStatus protocol of StatusNet and GNU social, until fairly recently to Twitter and, for a while in the early 2010s, even to Facebook. I'm not kidding, really not. I was there myself.
Granted, the connections to Bluesky, Tumblr, Twitter and Facebook don't/didn't work like those to diaspora*, StatusNet and the ActivityPub-based Fediverse when Friendica still had its own protocol. You still need(ed) an account on the other side, but you integrate(d) that account into your Friendica account, and you post(ed) to your connections on Bluesky and Tumblr and Twitter and Mastodon just like to all your other connections.
However, especially Twitter and Facebook didn't want that. Twitter kept changing their API with no prior announcement, not only to keep third-party clients out, but probably also to keep Friendica and later Hubzilla out, at least for a while.
And Facebook changed its rules for developers (as a Friendica node admin, you needed to be registered as a dev on Facebook to be able to connect the Facebook add-on on your node to Facebook): Sending data to Facebook was still allowed, but extracting data was forbidden from then on. This made the whole Facebook add-on useless.
each independent instance can select which other platforms to federate with (similar to now).
The only Fediverse server apps that really have something like this implemented are by Mike Macgirvin, too: (streams) from 2021 and Forte from August (he is currently the only user of the latter). They have a per-instance "user agent filter" that can operate either in a blocklist mode which keeps certain user agents out or in an allowlist mode which only lets certain user agents in. This filter is designed to also let through/keep out certain Fediverse server applications, including but not limited to Threads.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #StatusNet #diaspora* #Tumblr #Twitter #Facebook #Friendica #Hubzilla #Streams #(streams) #Forte That's why my image descriptions for my original images are so extensive: so that people learn what they need to know about the obscure virtual worlds my images are from to understand the images.
If they have the patience to read through one massive alt-text and, in addition, one frequently absolutely gargantuan long image description in the post, that is. (No character limit here.)
#Long #LongPost #CWLong #CWLongPost #VirtualWorlds #Metaverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Four points:
- Don't use line feeds in alt-text. Always make it one paragraph.
- Always end your sentences properly, e.g. with a full stop (that's a period for y'all Americans).
- Don't use quotes like on a computer keyboard. They may break alt-text. No, seriously, they may. Use actual, typographically correct quote () instead.
- All-caps may irritate screen readers. I know that all text in an image must be transcribed verbatim, but all-caps are an exception. Transcribe them normally and, if you deem it important, tell people separately that the text is in all-caps.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta -exposure
But Id be willing to bet that most of the people who would do Alt with AI are in fact willing to just offer a second-class experience to the disabled.
Yup. For many fully sighted people, image-describing AI is a nicely convenient fire-and-forget alt-text generator. They've never seen any of their own alt-texts, much less edited any of them.
BTW I think that 100% of images coming to Fedi from Threads have this kind of Alt and it's generally lousy, in fact worse than I think modern Ai should be able to do.
Threads uses the exact same image-describing AI as Facebook. It's infamous for how bad it is. I mean, there'll never be an AI that lives up to my standards, but seriously, Meta's AI is horrible.
CC:
#Long #LongPost #CWLong #CWLongPost #Meta #Threads #Facebook #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta (streams) and probably also Forte already offer two features in this direction.
One, they can import contact lists from ActivityPub or CSV files. Okay, that still requires the handling of files, knowledge where they are on your device and knowledge what files are in the first place. But you can connect to up to 1,000 actors in one fell swoop, provided you're willing to manage that many contacts.
Two, and this is for those who want to pick people or things to follow one by one: built-in connection discovery and connection suggestions la Facebook. A feature as old as Friendica, and Friendica is the oldest surviving Fediverse project, pre-dating Mastodon by five and a half years.
On your stream page which is hard-coded as your landing page, you have an area with two randomly changing connection suggestions on the left. It includes a link to a whole page dedicated to suggestions. On your connections page (which, unlike on Mastodon, is not buried in the settings it can actually be added to the navigation bar if you so desire so you can get there with one click), there's the same suggestion area. Right below it, there's a small area for searching for contacts which has another link to the suggestions page.
The suggestions page is actually only the directory of almost all Fediverse actors known to that server instance, but filtered for what may be interesting for you according to your profile. Of course, the results improve when you actually fill out your profile some, especially the keywords field. Each suggestion is presented with their various profile fields (if they've given permission to see their profile), numbers of followers and followed for ActivityPub actors (even though (streams) and Forte themselves don't distinguish between them), a handy big green button for connecting and a similarly big yellow button for removing that actor from the suggestions. Not just like on Facebook, but better than Facebook. This is what you may wish dating portals were like.
If the suggestions aren't sufficient, you may also peruse the whole directory. It contains all Fediverse actors known to that (streams) instance. My two (streams) channels are on an instance with only 13 channels altogether, but it still knows lots of actors from all over the Fediverse. The directory looks largely the same as when acting as a suggestions list, only without the Ignore button. You still get complete profile previews and, for ActivityPub actors, follower/followed counts.
The directory can be filtered by keyword, either by search field or by tag cloud. In addition, it can show
- only channels on the same server instance as you
- only group actors (Friendica groups, Hubzilla forums, (streams) groups, Forte groups if there were any, Guppe groups, Lemmy communities, /kbin magazines, Mbin magazines, NodeBB subforums, Flipboard magazines etc.)
- only actors not flagged NSFW (at least Hubzilla, (streams) and Forte channels can be flagged NSFW as a whole)
- only actors that have fairly recently been active
Again, it's impressive how much a (streams) instance with only 13 channels knows. A much bigger and much more diverse instance would also have a vastly bigger directory.
This, by the way, is also why topic-specialised or community-specialised instances make even more sense on (streams) and Forte than on Mastodon. For one, there's more interesting stuff and less uninteresting clutter in the directory. Besides, this goes doubly for the directory in local mode. Lastly, nomadic identity allows you to have the same channel on multiple instances anyway.
Granted, this is not as easy and convenient as following several dozen gamers or Linux users or climate activists with two clicks. But it goes well beyond what Mastodon offers already now.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Onboarding #StarterPacks #Streams #(streams) #Forte Und wenn man ihnen widerspricht, schreien sie "Reply Guying" und blockieren einen.
Nicht etwa, weil man eine Wahrheit ausgesprochen hat, die ihnen unbequem ist (wie bei all den Leuten, die unbedingt wollen, da das Fediverse nur Mastodon ist). Sondern weil man ihnen mit etwas widersprochen hat, das leider nicht offensichtlichermaen Unfug ist, sondern aussehen knnte, als htte es Hand und Fu.
Da behauptest du zwei Jahre lang steif und fest, das Fediverse ist nur Mastodon. Dann kommt einer von Firefish oder Friendica oder Hubzilla und sagt dir, das Fediverse ist nicht nur Mastodon, und Mastodon ist noch mit ganz anderen Sachen verbunden. Du wrdest das gerne als Schwachsinn abtun, um deinen eigenen Hintern zu retten. Ist nur eben bld, da der Umstand, da dir gerade einer geantwortet hat, der selber nicht auf Mastodon ist, direktweg der Gegenbeweis fr deine Behauptungen ist.
Aber genau deswegen sollte man solche Leute erst recht "reply-guyen" und "fedisplainen". Wer sich so auffhrt, hat das verdient. Leider werden sie das dann nur selber lesen und nicht ihre Followers, weil Mastodon keine Konversationen untersttzt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #ReplyGuy #ReplyGuys #Fedisplaining
Joe Coles 13/1 Bet Builder
Scott M. Stolz That, and they've never been told that something, anything, exists in the Fediverse outside of Mastodon that's connected to Mastodon. Whoever pulled them on board either deemed this information unnecessary or confusing, or they didn't know it themselves either.These people only learn about the existence of a Fediverse outside of Mastodon either from a post that does loads of things which are completely impossible on Mastodon or from a reply guy on Akkoma, Firefish, Friendica, Hubzilla etc.
At least this guy did not freak out when he learned about the existence of a Fediverse outside of Mastodon. That is, I don't know how he'll react once a very un-Mastodon post hits his timeline.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Akkoma #Firefish #Friendica #Hubzilla #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #ReplyGuy #Fedisplaining
Versace Bright Crystal Absolu: Long-Lasting Floral Elegance
Formulated for lasting impact, this perfume features fruity top notes of yuzu and pomegranate, layered with delicate lotus and peony, and finished with a warm amber-musk base.For More Visit:
Bright Crystal Absolu
-lasting floral fragrance
fruity perfume
- The start poster literally states that the Fediverse and Mastodon are the exact same thing. He has been on Mastodon for two years, since immediately after Musk has bought Twitter out.
- Another Mastodon user applauds.
- A Friendica user reply-guys the start poster and Fedisplains that the Fediverse is, in fact, not only Mastodon.
I was tempted to jump in myself and correct that guy about the Fediverse allegedly only being Mastodon. But this has been taken care of.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #ReplyGuy #FedisplainingI've just come to the realisation that putting long descriptions into external documents in the file space of my Hubzilla channel and then linking to them is a dumb idea. It's especially so for the use-case for which it was considered for, and that's posts with multiple embedded images.
It's untested. It's experimental. It might not even work for all I know. It's inconvenient for mobile users because their browser will pop up when they tap the link to the long image description in their Mastodon apps. That is, if it works they way I intend it to work. Which, again, I'm not sure about.
But most of all, it creates too much redundancy.
If I put all my long image descriptions into separate documents, then everything that's in all images likewise will have to be described in all its details once for each image. And all explanations that usually come with my long image descriptions will have to be there once for each image. If I have four images, I need four times the same explanation of way over 1,000 characters where the images were made even though they were all made in the very same place.
That's because I can't expect everyone to open and read all long descriptions. In fact, I can't count on everyone opening and reading the first long description. Thus, I can't explain everything only in the first long description. If someone only opens the second or third or fourth long description, they'll be missing a whole lot of explanation because it's only in the first description.
Sure, I could tell people where the explanations are. But that'd mean that the alt-text for the fourth image would tell them about the long description for the fourth image, but the long description for the fourth image would be very incomplete and refer people to the long descriptions of the first three images. Having to read five descriptions in five separate places in two apps for one image is even more cumbersome than having to read two descriptions in two different places in two apps for one image.
On the other hand, if I put all my long image descriptions into the post itself like I've always done since I've started taking image descriptions seriously, they wouldn't be right below the images proper in a post with multiple images embedded in-between text. But they'd be in the very same place as the images.
More importantly, they'd all be in the same place, full stop. I could do as I've always done recently. I could start with a common preamble for all four image descriptions in which I explain common stuff, and in which I even describe common stuff. And then I could let the specific descriptions for the individual images follow. Each bit of information would be there only once in one place and not four times over in four separate places.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta If they notice.
Thing is: If someone on Pleroma, Akkoma, Mitra, Friendica, Hubzilla, (streams) or Forte quote-posts someone else, that someone else is notified as if they've been mentioned. If they're notified when they're mentioned by a non-contact out of the blue, that is. Mods might not notice.
If someone on Misskey or any of its various still active forks and fork-forks quote-posts someone else, that someone else is not notified, and neither are any mods unless they happen upon the quote-post.
Also, nobody and nothing on Mastodon can prevent anybody outside of Mastodon from quote-posting anyone on Mastodon. And there's a whole lot outside of Mastodon that can and will always be able to quote-post Mastodon toots with zero resistance. See my start post in this thread for 18 server apps that can do that.
However, this much should be said: Friendica has had quote-posts for over 14 years. Hubzilla has had quote-posts for, technically speaking, almost 13 years. And never in all these years have quote-posts been used on either to harass anyone on Friendica, on Hubzilla, on Mastodon or elsewhere.
Sounds hard to believe for people who only know Twitter and Mastodon, I know. But Friendica and Hubzilla aren't almost entirely populated by people who came from Twitter. They aren't Twitter alternatives anyway. Friendica is a Facebook alternative, and Hubzilla is a Facebook alternative on coke and steroids. Both have a totally, completely different culture from Twitter as well as from Mastodon, both early Mastodon and today's Mastodon. There is no influence from Twitter on them whatsoever.
In fact, until Hubzilla 9.0 which came out this year, Hubzilla did not even have repeats (= retweets = boosts). It had always used quote-posts (= shared posts in Hubzilla lingo) for this purpose.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate Scott M. Stolz
Some people abuse them. They quote someone and then mock them for what they said.
More specifically:
On Twitter/, hateful right-wing people harass members of marginalised minorities (BIPoC, 2SLGBTQIA+ etc.) by quote-tweeting one of their tweets, mocking them in the tweet that quote-tweets them and then having others mock them even more in the replies. This is so commonplace that it feels like the only use-case that quote-tweets still have on .
#Long #LongPost #CWLong #CWLongPost #Twitter # #QuoteTweet #QuoteTweetsTejan Ausland Yes, but many on Mastodon don't understand this.
For them, the Mastodon devs are the creators and keepers of the Fediverse itself as well as "the good guys" who have made the single most awesome piece of server software in decades. If the Mastodon devs even only imply that an opt-out or opt-in switch for quote-posts will bring absolute safety from being quote-posted, they take it at face value.
So when they opt out of being quote-posted, and someone from outside of Mastodon quote-posts them anyway, they won't blame it on the Mastodon devs having promised them something impossible. Never would the Mastodon devs do that.
Rather, the devs behind whatever that someone is using are the bad guys. They're rogues, they're evil hackers who have introduced quote-posts just to be able to spite and harass Mastodon users. Why else would something introduce quote-posts after all
The one thing that'll protect wherever that someone is from their wrath is that most of them won't be able to figure out what that someone is using. Just because Mastodon users can look up a post at its source, doesn't mean they know they can, much less they actually do.
So they may try to get allegedly rogue instances Fediblocked just because these instances are non-Mastodon instances doing what they regularly do. They may succeed because at least some blocklist maintainers don't have a clue about the Fediverse outside Mastodon, its capabilities and its culture either. But it's unlikely that they'll pinpoint this culprit having used Sharkey, have all of Sharkey Fediblocked for being able to "circumvent" Mastodon's quote-post opt-out/opt-in, then pinpoint that the next quote-poster is using Akkoma and have all of Akkoma Fediblocked and so forth.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Blocklist #Blocklists #BlocklistMeta #FediblockMetaBy the way, there's exactly one way of being safe from being quote-posted in the Fediverse:
Move to Hubzilla or (streams). Keep all optional communications protocols off, including ActivityPub. Disallow quoting and mirroring of your posts entirely in your channel role (on Hubzilla) or keep your channel type on Limited ((streams)). Make sure that none of your contact roles (Hubzilla) or permission roles ((streams)) allows it. Try to live with only contacts on Hubzilla and (streams) none of them would ever use quote-posts for nefarious reasons, but better safe than sorry. Always post to a restricted audience so that sharing your posts isn't possible anyway. And never comment on public posts so that sharing your comments isn't possible either.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebateOne of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:
- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace
Last updated: 2024-11-20
All text and images © eLoc8.is-fabulous.com