Find the latitude of any place.  

LES SAISONS ET LES LVRES (Supervielle)

LES SAISONS ET LES LVRES (Supervielle)

    LES SAISONS ET LES LVRESLe Printemps est un doux sourireQu'illumine un rayon dor,L'ouragan se change en zphyre,Lorsqu'il est las d'avoir pleur.L't de baisers plus brlantsUnit les lvres demi-closes,Et tous les curs sont palpitantsAux senteurs des lys et des roses.Les lvres unies se dtachentEn l'Automne, et les souvenirsDes ivresses passes se cachentEn longs et langoureux soupirs.Mais les yeux se couvrent de pleurs,L'Hiver, les
You mention better alternatives to Facebook, what do you suggest

Friendica if you're looking for something that isn't that overwhelming, if you're looking for something with native Android apps available (don't ask for iOS apps for anything here), and if you can live without features like polls or nomadic identity.
Hubzilla if you think you can tackle a steep learning curve with some help from a very good user documentation and a helpful community, if you want Facebook with a side of optional CMS and/or groupware features, if you need nomadic identity to make your channel(s) resilient against server issues and shutdowns, and if you don't mind using the Web interface on a phone.
(streams) and Forte if you need something that's a bit more fit for today's Fediverse, if you need something nomadic without Hubzilla's extra features, if you don't mind using the Web interface on a phone, and if you're willing to wait for more public servers or willing to run one yourself.
I have a number of comparison tables that include Mastodon as well.
What I don't like about this draft is that it communicates the existence of exactly four alternatives, two to WhatsApp and Telegram, one to Instagram and, I guess, one to literally everything else.
Oh, and by the way, no, Mastodon is not a good alternative to Facebook. There are dedicated Facebook alternatives in the Fediverse that are much closer to Facebook in functionality than Mastodon right now.
This does not entirely apply to the whole Fediverse. To most of the Fediverse, including Mastodon, but not to all of it.
Some server applications offer something called nomadic identity (). Your identity is defined by one server, but it is not permanently stuck to that server. And all your stuff can not only be moved around from server to server, but even exist on multiple servers simultaneously, constantly kept in sync with each other.
This isn't even new. It was first introduced on a fork of a Friendica fork named Red in 2012. Four Fediverse server applications offer it now:

There's also Mitra that uses a special client, Mini Mitra, to establish nomadic identity on the client side.
Nomadic identity goes way beyond what the ATmosphere promises. The ATmosphere does not give you the option to clone your identity between independent relay/AppView stacks. If you're on bsky.app, and bsky.app is down, you have nothing, and you can't do anything to mitigate this. This Hubzilla channel is cloned between two servers. If one goes down, I still have the other one.
This can't work, and for one particular reason. And you should actually know this reason after eight years in the Fediverse:
The Fediverse is not only Mastodon. It's far from being only Mastodon.
It isn't 10,000 servers running one application. It's 40,000+ servers running over 150 different applications. And I'm not talking about Mastodon and otherwise Mastodon forks either.
From your words, I can clearly see that you want the whole Fediverse to be moderated by Mastodon standards.
But then you have Mastodon mods who are "based and Mastodon-pilled", and for whom the Fediverse either is or shall be only Mastodon. These mods moderate Friendica or Hubzilla or (streams) or Forte servers by Mastodon's standards. Which, by the way, not only clash with the culture on these servers, but even with the technology on these servers. Friendica works a whole lot differently from Mastodon Hubzilla, (streams) and Forte even more so.
Oh, and especially Hubzilla, (streams) and Forte don't even have the concept of moderators. I'm absolutely serious here. They don't have Mastodon's concept of reports. Why not Because they're geared towards self-moderation. Everyone is given the power to moderate their own channels. Unimaginable on Mastodon, also because this involves technologies and features that are unimaginable on Mastodon such as the most advanced permissions systems in the whole Fediverse. Mastodon's culture is about being pampered and coddled. The culture on these three is about self-defence.
Also: You can't force Mastodon-style Mastodon moderation upon a (streams) server. You can try. But you won't succeed. The server admin won't let you. Again, I'm dead-serious here.
Unlike on Mastodon, a (streams) admin has various counter-measures available to get rid of your Mastodon mod.

Stuff like this, by the way, Mastodon forcing its culture upon the non-Mastodon Fediverse, is the very reason why (streams) and Forte have built-in ways to defend themselves against Mastodon. And this is one reason why Hubzilla sticks to ActivityPub being optional on each channel.
Back to the Mastodon mods. They'll probably only know Mastodon. More importantly, they probably won't know anything about groups. They'll probably think the Fediverse doesn't even have groups. They'll only know users following other users.
And then they'll have to moderate on Lemmy. They'll have to moderate a group. Something they didn't even expect to exist. In a place where users can't follow other users, only subscribe to groups, because it's essentially a Reddit clone.
Worse yet, they'll have to moderate a Lemmy community with 10,000 members. All of whom are former Redditors. All of whom live by a culture that's directly derived from Reddit with no influence from Twitter or Mastodon at all. None of whom have ever been on Twitter or Mastodon. Almost none of whom even know that Mastodon exists. And many of whom have their experiences with power-tripping Lemmy moderators, so if you think they're easy to rein in with a culture that isn't theirs, you're very wrong.
(Greetings from Hubzilla.)
I guess that, more often than not, the only new developments that are widely welcome are those that happen on Mastodon, that still don't make Mastodon feel different, and that don't introduce features to Mastodon that are (considered) bad on .
This alone is the reason why many Mastodon admins hold on to older Mastodon versions for their dear lives: They want to boycott new Mastodon features which they don't like, but they don't have what it takes to soft-fork or even only hard-fork Mastodon and remove the new features.
Now, when it comes to developments in the Fediverse outside of Mastodon, they tend to be even more nerve-grating for Mastodon users because they often aren't in line with Mastodon and its culture at all. That is, many Mastodon users don't even notice that these features exist unless these features directly hit their timeline. But once they do, they're considered bad new developments even though they've actually been around for much longer than Mastodon itself.
For example, quote-posts and full-text search. Mastodon users tend to be staunchly against both because they're used to harass and dogpile minorities on . If at all, they're only okay with these if they come with an opt-in, and/or if server admins can turn them off entirely.
If only they knew that Friendica has had both since May, 2010, five years and eight months longer than Mastodon has even existed. That Friendica has been search-indexing and able to quote-post any public Mastodon toot since Mastodon's very launch. I guess they'd demand the immediate destruction of Friendica or at least its complete and permanent defederation.

Great evening here in atlanta hitting a few long irons

DSC8760 by samjstone

New post: The Standing Order

-Term-Care -Home

Amour Profond et Vritable (Liu Guo)

    Amour Profond et VritableAmour profond, sentiments vritables,Sourcils longs, tempes dun noir profond.Dans le petit pavillon, sous la lune claire, elle joue du luth,voquant quelques notes de vent printanier.Je pense toi, je me souviens de toi,Mon me tenlace, mes rves tenserrent.Lcran de jade, o se dissipent les parfums,Ne peut supporter mon rveil aprs livresse.***

NYX (Catherine Pozzi)

Illustration: Gustave Moreau    NYX Louise aussi de Lyon et dItalie vous mes nuits, noires attendues pays fier, secrets obstins longs regards, foudroyantes nues vol permis outre les cieux ferms. grand dsir, surprise pandue beau parcours de lesprit enchant pire mal, grce descendue porte ouverte o nul navait passJe ne sais pas pourquoi je meurs et noieAvant dentrer lternel sjour.Je ne sais pas

Visi danced and pranced around, doing an old routine she did back in high school. It turned out, even after several years ago now, she could still remember and DO all the moves! All those stretches really kept her limber!



Sam Barlow is back at live-action horror

Long before Netflix jumped into interactive movies, this indie dev was already crafting unique experiences with real actors, breaking the fourth wall, and giving players actual agency.

And now he looks ready to drop another masterpiece. Stay tuned

Maybe I haven't told you this yet, but:
Explanations do not belong into the alt-text!
Alt-text must never contain exclusive information that's neither in the post text nor visible to sighted users in the image.
That's because, just like there are people who cannot see the image, there are people who cannot access alt-text. Be it because of physical disabilities (they don't have at least one sufficiently working hand which is a hard requirement for accessing alt-text), be it because of technical limitations (*nix window managers like i3 or ratpoison don't support pointing devices of any kind, so there's no mouse cursor that could hover over an image).
Any explanations or other information that's only in the alt-text is inaccessible to these people.
Therefore, explanations, creator credits, license information and other extra information always go into the message text!
Reference link if you don't believe me: by
Reference posts from someone who actually can't access alt-texts:
RE:
RE:
RE:
RE:
RE:

Lydia Ko really drives the head low and long through the impact zone.

Long

Longnose Butterflyfish, aka Lauwiliwili nukunuku oi oi, at an . Your

Prints available - DM me.

I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The and the # became part of the link (, , for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#Hashtag()", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue Especially Forte that has actually started pandering to Mastodon as of late
I've noticed that Hubzilla 11.4 handles mentions and hashtags (closer to) the Twitter way instead of the Identi.ca way now. The and the # became part of the link (, , for example).
I wouldn't cry out "pandering to Mastodon" now. I don't think this happened in the same vein as Forte giving the choice between starting an enclosed conversation and starting a microblogging-style loose thread. After all, it's vanilla Mastodon out of all microblogging applications that handles the old Identi.ca way quite gracefully. And even what didn't work as intended didn't cause a big mess instead either.
Other Fediverse applications are way less prepared for this. From the Mastodon fork Glitch to all the *keys and, I think, the *omas, not only can't they handle the Identi.ca way, but they tend to fail rather ungracefully because they don't even expect anything else than the Twitter way. Especially on Misskey, this has been recognised as a bug in 2024 already, and nothing much has happened in terms of fixing it. Of course, all the Forkeys have inherited the bug, and I think none of them has fixed it instead of waiting for upstream Misskey to fix it. I'm not even sure if Iceshrimp.NET, a complete rewrite in C#, hasn't re-implemented it.
I mean, if lots of Fediverse server applications render Hubzilla's old "#" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#Hashtag()", and people keep complaining, then someone has to step in and put an end to this mess. And lots of fingers were pointing at Hubzilla. While tens of thousands of Mastodon accounts blocked Hubzilla channels for their long posts, hundreds of *key accounts blocked Hubzilla channels for how completely messed up their hashtags came out.
Also, unless I'm completely wrong, the first Fediverse server application that handled mentions and hashtags the Twitter way rather than the Identi.ca way wasn't Mastodon either it was GNU social, itself a fork of StatusNet, the software that used to power Identi.ca before its switch to pump.io.
So this wasn't a case of Hubzilla acting up on Mastodon. It was a case of Hubzilla acting up across at least half the Fediverse, Mastodon actually largely excluded.
That is, it may still worry you that Hubzilla whose foundation was laid in May, 2012, based on Friendica which is another two years older, adapted to software which came later instead of playing the "we were here first" card. A whole lot of software which came later and which was largely created independently from Mastodon (although both Mastodon and Pleroma started their lives as something akin to alternative frontends for GNU social), but still.
By the way, don't Friendica, (streams) and Forte still cause the same issue Especially Forte that has actually started pandering to Mastodon as of late

Quebec clamping down on refunds for empties from Ontario
The organization that manages Quebec's bottle deposit program says long lineups at its depots are forcing it to make changes, including one that could make it more difficult for Ontarians to cash in some of their empties.

ODE TACTILE (Paul Valry)

    ODE TACTILEUn doigt plus doux que plume sur la harpeSe joue fuir sur la fleur de ta chairEt cette main souple comme une charpeFlatte et polit ce qu'elle a de plus cher.Je vous caresse, raisons d'existence,Parages purs, bords suaves qui sontMa terre tide et d'exquise substanceTerre promise aux fleuves du frissonTerre sensible o frmit ce grand ArbreDe l'me offerte au tendre enchanementDu long baiser sur tes plages de marbreQui suit le fil de

Django LTS

Beau Hosslers Pre-Shot Routine: Is He Taking Too Long

Since you're on Mastodon, you most likely haven't read this comment of mine. So here it is again:
RE:
Having the informative part both in the alt-text and in the message text is redundant. Besides, having the informative part in the alt-text just inflates the alt-text.
I think there are three reasons why Mastodon users stuff all kinds of information into the alt-text. One is that they sincerely believe that any and all information about the image must go into the alt-text because it's image-related. Some are actually being told exactly this.
Another one is that most of them have only got 500 characters for the toot, minus hashtags, minus mentions, minus even the CW. But they've got 1,500 characters per image that they don't have to share with anything else.
Lastly, all they know about accessibility, they know from fully sighted laypeople who actually don't know anything about accessibility themselves. They don't even have the foggiest idea just how exactly alt-texts help blind or visually-impaired users. They know nothing about screen readers, they know nothing about Braille displays, they don't even know that either exist, because neither do those who have told them about alt-text.
Sorry to say, but the accessibility that's so firmly engrained into Mastodon's culture which is being forced upon the rest of the Fediverse often isn't even really accessible.
But you have to look at it from the perspective of screen reader users: They actually have a big problem with long alt-texts. Screen readers can navigate the message text, e.g. jump back a few words or sentences to some point in the middle of the text. But they can't do that with alt-texts.
If you give them a 1,200-character alt-text because you felt like you had to squeeze tons of information in, and they get distracted around the 1,100-character mark, they can't just jump back a sentence. They can only jump back to the beginning of the alt-text and have the whole alt-text read out to them once again.
Unlike what's being falsely taught on Mastodon, alt-text is meant to be a drop-in replacement for the image. It is only for a visual description of the image. It is not meant to be informative.
In general, explanations and other additional information that aren't immediately available in the image to sighted people do not belong into the alt-text.
That's because the assumption that everyone can access alt-text is just as false as the assumption that everyone can see the image.
Just like not everyone has two working eyes, not everyone has two working hands which are a hard requirement for opening an alt-text unless they use a screen reader.
Any additional information must always go into the message text.
CC:
I have a problem with this. But I probably only have this problem because whenever I post an image, it's about an extremely obscure niche topic. (Don't go looking for my recent images on this channel I post my images elsewhere and even there only recently.)
When you're describing an image to a friend, first of all, you're describing the image to only one person. You probably already know that person. You can at least estimate what they know about the image you're going to describe. If not, you can ask them what they know, what they don't know, what they need to know, what they want to know.
And then you can tailor your description to the individual wants and needs of that one specific person. And you can add the explanations which this person needs and omit the explanations which this person doesn't need.
In case they don't understand something, or if they want to know more details, they can interrupt you mid-describing and ask you.
But when you're describing an image for the Fediverse, you're describing it for potentionally everyone in the Fediverse (and everyone on the Web, unless you restrict the permission to view your post). You don't know all these people, there's no way you can.
You simply can't go around and ask millions of Fediverse users and billions of Web users, one by one, what they know about the topic of your image, what they don't know etc. Neither can you predict who exactly will receive your post and then only go and ask these people in advance.
Even if you could, you can't tailor your image description and accompanying explanations to the individual needs of many people. Especially not if you're going to post that image only once for everyone all the same.
Worse yet, they can't interrupt you mid-describing and ask you for explanations either. They'll get the entire description plus your explanations all at once.
Thus, you have to describe and explain your image for everyone all the same with no regards for individual needs. You have to cover everyone's potential needs right away.
Let's take (link CW: eye contact, meme, non-Mastodon Fediverse meta) , for example. I've actually used it in a Fediverse meme post.
If I were to describe it to one friend, I'd ask the friend if they're familiar with the "One Does Not Simply Walk Into Mordor" meme template, and if they're familiar with FEP-ef61 "Portable Objects". Honestly, I expect hardly anyone to know both.
If they aren't familiar with FEP-ef61, and they most likely aren't, I'd ask them if they know nomadic identity, and if they know the streams repository, because knowing both is required for my explanation of FEP-ef61. They probably don't know either, so I'd explain the streams repository to them, including rattling down the whole 16-year history of the software family from Mistpark/Friendica to Forte. When I reach the rewriting of Red in 2012, I'd explain the concept of nomadic identity because it was then when it was first implemented. And even that I could only do if they knew the Fediverse. If not, I'd go start with the Fediverse.
If they aren't familiar with "One Does Not Simply Walk Into Mordor", I'd ask them if I could send them a link to the KnowYourMeme page, or if they need it described by me. If the latter, I'd ask them if they're familiar with the concepts of snowclones and image macros. And so forth. Whatever they aren't familiar with, I'd explain it to them.
As for the visuals, I'd ask them if they need a visual description of what Boromir looks like, regardless of whether or not this matters in the context. I'd also ask them how familiar they are with The Lord of the Rings and specifically the Peter Jackson films. For this may require even more explanations.
How am I supposed to do any of this with an audience of many Right, I can't.
And so I have to deliver all necessary explanations in the message text, right beneath the image itself, just in case someone needs them. And let's face it, most people will need them. The explanation of the image macro itself plus another eight explanations in order for people to understand the main explanation. Over 25,000 characters if they consider links to external explanations bad.
# # # # # # # # # # # # # # # I've been working on an entire wiki about image descriptions and alt-texts for the Fediverse for quite a while now. It's far from finished, not even half of the over 50 pages planned right now are written.
As of now, it'll have 32 rules and guidelines on what to do, how to do it and what not to do. The huge majority of these are completely unknown in the Fediverse otherwise.
# # # # # # # # # # # # # # # I've read somewhere that some blind people prefer LLM-generated image descriptions to human-written image descriptions because they're more entertaining. LLM-generated image descriptions often add some whimsy whereas human-written image descriptions just dryly rattle down what's in the image. Basically, through the screen reader, humans sound more like machines than actual machines.
They usually are aware that LLMs tend to be hallucinating and essentially telling them non-sense. But I've read from one blind user that they don't care whether or not the LLM-generated description is accurate as long as the accuracy isn't a matter of life and death.
In a certain way, it is understandable. The only people who'd criticise an image description for being inaccurate are fully sighted and therefore capable of comparing the image with its description.
Blind people won't notice unless the image description describes something so outlandish to them that they have the impression of an utterly surrealist image where there shouldn't be a surrealist image.
On the other hand, there are also blind people who demand image descriptions be accurate. They simply don't want to be told non-sense, especially not without knowing that they're being told non-sense.
But even on the sighted side, there's the "human versus AI" debate.
Some sighted people are fully convinced that LLMs can describe absolutely every image perfectly in absolutely every situation, no matter how obscure the contents of the image are. They're fully convinced that a generic LLM like ChatGPT can write circles around even human experts at any given time.
Some are simply AI fanbois or fangurls. Others say so in order to convince themselves that what they're doing is the best way: They use image-describing LLMs or even general-purpose LLMs as fire-and-forget tools. They have image descriptions generated, they copy-paste these image descriptions into the alt-texts, they send their posts, and they never take a look at these image descriptions at any point in the process. It's more convenient this way.
And then they wonder why they're under attack from sighted alt-text activists who call them out for their painfully inaccurate and blatantly obvious AI slop.
LLM proponents, both sighted and non-sighted, have in common that they never compare the image and the description. Non-sighted LLM proponents simply can't see the image. Sighted LLM proponents put so much faith into LLMs that they can't be bothered to read the description and cross-check it with the image.
# # # # # # # # # # # # # # # #

Friendica und Hubzilla bieten mehr als 16 Millionen Zeichen, (streams) und Forte bieten mehr als 24 Millionen Zeichen.
Alle vier knnen die volle Bandbreite der Textformatierung erzeugen, die von HTML untersttzt wird, weit mehr, als was Mastodon auch nur anzeigen kann.
Bei allen vieren knnen Bilder direkt in den Text eingebettet werden, also mit Text ber und unter dem Bild, und zwar beliebig viele Bilder. Etwas, was Mastodon berhaupt nicht anzeigen kann.
Friendica generiert standardmig ein sogenanntes "Article-Type Object", das Mastodon darstellt mit Titel, Zusammenfassung und einem Link zum Original, wenn man einem Post einen Titel gibt. (streams) und Forte tun das optional, wenn ein Post mehrere Zeilen hat. (Beide tun das nicht bei Kommentaren, nur bei Posts. Bei allen vieren gilt brigens eine Antwort nicht als Post, sondern als Kommentar.)
Hubzilla hat ein optionales Feature namens "Artikel": Damit kann man lange Texte verfassen, ohne sie ins Fediverse zu posten. Die kann man dann z. B. hndisch in einen Post verlinken und von da aus kommentieren. Es gibt auch noch "Karten", das hnlich ist wie "Artikel", aber noch mchtiger.
Aber: Friendica hat fr jemanden, der allgemein nur Twitter und Mastodon kennt, eine ziemliche Lernkurve, weil es ziemlich anders funktioniert. (streams) und Forte haben aufgrund ihrer Struktur, wo das Konto nicht die Identitt ist, und aufgrund ihres Berechtigungssystems eine noch steilere Lernkurve und auerdem kaum bis gar keine ffentlichen Server. Hubzilla hat die steilste Lernkurve von allen und kann mit Standardeinstellungen am wenigsten gut genutzt werden. Dedizierte Smartphone-Apps gibt's nur fr Friendica und nur fr Android in allen anderen Fllen ist man aufs Webinterface angewiesen.
# # # # # # # # # # # # # # # #

Une frappe de drone a fait au moins 35 morts dans le village de , dans ltat du du Nord, selon . Lattaque a vis un tribunal coutumier alors que des civils assistaient des audiences portant sur des litiges locaux.

BTW I had account on identi.ca, which was StatusNet powered (I believe).

It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.
Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)

This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
BTW I had account on identi.ca, which was StatusNet powered (I believe).

It was. At least until Evan and Erin could no longer justify it running on that janky OStatus protocol. The result was the ActivityPump protocol, the pump.io software and Identi.ca's switch to pump.io with all hands on board.
Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)

This reminds me of how the Fediverse is all over the place in terms of programming languages. Everyone has their own Holy Grail.
Friendica and its descendants are written in PHP. They may not be the fastest (even though what bogged down early Friendica were its heavyweight federation connectors to everywhere, especially the one for Facebook that came in 2011). Mike either discarded or rewrote these when he rewrote Red. But they happily run on a run-of-the-mill LAMP stack.
Mastodon is written in Ruby on Rails. Hubzilla runs circles around it in terms of performance per account/channel, and that has to say something. The only thing that managed to top this was early diaspora*, written in Ruby on Rails for Mac with MongoDB as the database system.
The *omas are built in Elixir. Granted, they're utter featherweights, especially considering their features. They're legendary for their low server impact. Then again, Pleroma apparently is spaghetti code straight from hell. Its own devs often don't have a clue where to go look for bugs, much less how to fix them. (Miraculously, the Akkoma devs do manage to get ride of quite a number of them.)
The *keys are built in TypeScript and Vue.js. I guess one reason why Misskey is infamous for having so many forks and forks of forks is because there are tons of people who can code in JavaScript, the primary mobile programming language.
Iceshrimp.NET is a still very incomplete "rewrite" of old Iceshrimp in C#. It was largely tackled to get rid of all those nasty bugs inherited from Misskey that even Misskey doesn't manage to get rid of. I've heard quite some outcry: Iceshrimp.NET is a sell-out to Microsoft. I guess whoever uttered that didn't go check who owns TypeScript.
PieFed is a dead giveaway: Python. And PieFed makes more headlines in the Threadiverse for server politics than for its underlying technology, except that Lemmy pales in comparison.
GoToSocial is a dead giveaway, too: Go. And it was one of the first Fediverse server applications to not come with a Web UI. Those who use it for a single-user server often don't even bother installing one and use some Mastodon app or other instead. Besides, why drag around a Web UI if there are much better third-party Web UIs than whatever you could whip up
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
I believe there was always the best interest of Mastodon developers to enable their users to engage with content like PeerTube videos, WordPress blog posts, and so on.

WordPress has always been the tricky one out of these.
On the one hand, there was the promise to be able to follow WordPress blogs from Mastodon without resorting to RSS or Atom. And there was the promise to WordPress users to increase their subscribers by the folks in the Fediverse.
On the other hand, there was Mastodon's refusal to render Article-type objects such as those that WordPress sent. And I'm not even talking about rendering them without utterly defacing them. AFAIR, Automattic wasn't really pleased to see Mastodon only linking to WordPress blog posts. (By the way, the *omas and *keys show WordPress blog posts with no problems, even though they consider themselves microblogging apps, too.)
You also mention, that Hubzilla was first application ready to deliberately block other platforms... and then accuse Mastodon of doing the same

Not Hubzilla. (streams) and Forte were the first to have the User Agent Filter and even that not before September, 2024. FedUp, which locks out everything that's incompatible with enclosed conversations, wasn't there before 2025. Neither of these two was backported to Hubzilla.
All that Hubzilla has is ActivityPub being optional. And even that comes from ActivityPub still being an add-on plus the potential desire of Hubzilla users to have a 100% nomadic channel with nothing non-nomadic interfering. Mario and Harald do see it as a potential drawbridge. But it's mostly a historical relic from the times when Mike dreamt of the Grid. In fact, Hubzilla still has Friendica's "federate with everything that moves" attitude deep inside its DNA.
Also, if anyone is interested in blocking the non-Mastodon Fediverse, or large parts of it, from Mastodon, it's individual Mastodon users who have never gotten over their first message from Calckey or Friendica or whatever. The Mastodon devs, well, probably not so much. They want to make the non-Mastodon Fediverse look as bad as they can get away with, but they can't afford locking it out entirely.
I mean, I've actually taken into consideration submitting a feature request in Mastodon's GitHub repository for one or various means of excluding the non-Mastodon Fediverse from individual accounts or even entire servers, if only to see the comments. But I don't think the devs would even only take building that option into consideration, also because it might anger certain other actors like Ghost, Flipboard, Automattic...
But there is no reason to block entire platforms.

Mike Macgirvin will disagree with you.
In fact, almost everyone will disagree with you if you tell them that one of the platforms that can be blocked is Threads.
Myself, I would like to learn Rust and perhaps join some ActivityPub project in Rust, which would not be so strictly focused on being Xitter clone and would support more media options, would display more than 4 image attachments, would be very user configurable, be aware of status size limits of platforms of mentioned users, etc.

Plume is written in Rust. As it so happens, its development is, let's say, dormant. I mean, it outclasses WriteFreely in a whole bunch of ways, be it because it has its own built-in image file space, be it because it supports likes and comments, be it because its Web UI is more straight-forward than WriteFreely's. But its devs don't have any time for it, they won't have any for the foreseeable future, and they recommend everyone who is interested in Plume to join WriteFreely instead.
Maybe they can use an additional main dev who can forward the project (along their plans anyway), merge 3rd-party pull requests and such. It'd be a shame to see it go to waste.
# # # # # # # # # # # # # # #
I believe there was always the best interest of Mastodon developers to enable their users to engage with content like PeerTube videos, WordPress blog posts, and so on.

WordPress has always been the tricky one out of these.
On the one hand, there was the promise to be able to follow WordPress blogs from Mastodon without resorting to RSS or Atom. And there was the promise to WordPress users to increase their subscribers by the folks in the Fediverse.
On the other hand, there was Mastodon's refusal to render Article-type objects such as those that WordPress sent. And I'm not even talking about rendering them without utterly defacing them. AFAIR, Automattic wasn't really pleased to see Mastodon only linking to WordPress blog posts. (By the way, the *omas and *keys show WordPress blog posts with no problems, even though they consider themselves microblogging apps, too.)
You also mention, that Hubzilla was first application ready to deliberately block other platforms... and then accuse Mastodon of doing the same

Not Hubzilla. (streams) and Forte were the first to have the User Agent Filter and even that not before September, 2024. FedUp, which locks out everything that's incompatible with enclosed conversations, wasn't there before 2025. Neither of these two was backported to Hubzilla.
All that Hubzilla has is ActivityPub being optional. And even that comes from ActivityPub still being an add-on plus the potential desire of Hubzilla users to have a 100% nomadic channel with nothing non-nomadic interfering. Mario and Harald do see it as a potential drawbridge. But it's mostly a historical relic from the times when Mike dreamt of the Grid. In fact, Hubzilla still has Friendica's "federate with everything that moves" attitude deep inside its DNA.
Also, if anyone is interested in blocking the non-Mastodon Fediverse, or large parts of it, from Mastodon, it's individual Mastodon users who have never gotten over their first message from Calckey or Friendica or whatever. The Mastodon devs, well, probably not so much. They want to make the non-Mastodon Fediverse look as bad as they can get away with, but they can't afford locking it out entirely.
I mean, I've actually taken into consideration submitting a feature request in Mastodon's GitHub repository for one or various means of excluding the non-Mastodon Fediverse from individual accounts or even entire servers, if only to see the comments. But I don't think the devs would even only take building that option into consideration, also because it might anger certain other actors like Ghost, Flipboard, Automattic...
But there is no reason to block entire platforms.

Mike Macgirvin will disagree with you.
In fact, almost everyone will disagree with you if you tell them that one of the platforms that can be blocked is Threads.
Myself, I would like to learn Rust and perhaps join some ActivityPub project in Rust, which would not be so strictly focused on being Xitter clone and would support more media options, would display more than 4 image attachments, would be very user configurable, be aware of status size limits of platforms of mentioned users, etc.

Plume is written in Rust. As it so happens, its development is, let's say, dormant. I mean, it outclasses WriteFreely in a whole bunch of ways, be it because it has its own built-in image file space, be it because it supports likes and comments, be it because its Web UI is more straight-forward than WriteFreely's. But its devs don't have any time for it, they won't have any for the foreseeable future, and they recommend everyone who is interested in Plume to join WriteFreely instead.
Maybe they can use an additional main dev who can forward the project (along their plans anyway), merge 3rd-party pull requests and such. It'd be a shame to see it go to waste.
# # # # # # # # # # # # # # #
The wiki reveals even different timeline:

"The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...
To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

Gargron simply was lucky.
I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.
Anyway, Mastodon got media coverage, and nothing else did.
In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.
From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.
I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.
I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010).

In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.
By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.
Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.
I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.
I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

Well, they say that ActivityPub is glorified RSS with a rubbery spec.
# # # # # # # # # # # # # # # # # #
The wiki reveals even different timeline:

"The wiki" sounds funny to someone who has three wikis of his own on his Hubzilla channel. Anyway...
To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

Gargron simply was lucky.
I think it was in 2016 already that German tech media got interested in decentralised alternatives to corporate silos. Mastodon caught their interest, being developed in Germany and all. Pleroma didn't, in spite of being developed in Germany, too, not to mention more feature-rich than Mastodon. Friendica was developed in Germany back then already, too, but it seemed like either tech media weren't interested in alternatives to something that needed alternatives much more than Twitter, or Friendica managed to continue to fly under the radar even then.
Anyway, Mastodon got media coverage, and nothing else did.
In 2017, right-wingers started attacking furries and queers on Twitter. They had to escape somewhere. Tumblr wasn't it, having been pretty much killed by being bought out and G-rated. But someone happened to know Mastodon due to the media coverage whereas nobody happened to know Pleroma due to no media coverage at all. So those furries and queers escaped to Mastodon. "Awoo" was briefly part of Mastodon's culture in the late 2010s due to the high furry-to-non-furry rate.
From then on, Mastodon had the two advantages of past media coverage and more users. The rest was like a snowball, essentially. The more users something has, the more users something gains by inviting them.
I guess Friendica and Hubzilla, both of which already existed back then, suffered from the same choice of mindsets: "If you build it, they will come," "We'll first need to get this and that fixed before we're ready for prime time," "Can't someone else take care of that I'm bad at advertising stuff!" Plus, of course, people who really were bad at advertising stuff to anyone who's neither a developer nor a server admin.
I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010).

In 2009, there already was StatusNet. Granted, it was so obscure that vastly more people knew the "lighthouse server" Identi.ca than StatusNet itself. StatusNet supported the Twitter client API, but there were vastly more mobile apps that were hard-coded to Identi.ca than such where you could choose a StatusNet server because the huge majority of those who knew Identi.ca didn't even know it was part of a network. Identi.ca held some 90% of all StatusNet users.
By the way, what killed StatusNet was when Identi.ca changed its backend from StatusNet to pump.io and its protocol from OStatus to ActivityPump, thus becoming incompatible with the rest of StatusNet. What remained was largely unable to stand alone. What kind of helped Identi.ca (OStatus as a profile sucked so badly that Evan and Erin themselves had to whip up ActivityPump) did the opposite to StatusNet. A bit later, the FSF scooped it up, forked it to GNU social and eventually merged what was left of StatusNet into GNU social. It got ActivityPub support later on, but it's gone now, too.
Also, in 2010, Mistpark was around, and so was diaspora* (or what already existed of it at that time). diaspora* had tons of advance publicity due to its crowdfunding stunt, but then the four devs didn't manage to deliver before public interest had faded away, even with Mike's help on the protocol (not even kidding here). And speaking of Mike, he built Mistpark, but almost nobody came because he did nothing in terms of advertising. Even though Mistpark of May, 2010 was more powerful than diaspora* is today. Even though Mistpark took two months for a public alpha and four for a stable point release whereas it took diaspora* years to go beyond alpha, not to mention the entire development team being replaced.
I guess you would have been a prime Friendica user candidate. Particularly, you would have been one of those who were happy on a Friendica node without the performance-hogging Facebook connector in times when everyone was seeking out and piling onto the nodes with that connector, just to see them close registration at not even 150 accounts.
I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

Well, they say that ActivityPub is glorified RSS with a rubbery spec.
# # # # # # # # # # # # # # # # # #
Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.
I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.
As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.
I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
# # # # # # # # # # # # # # # # # # # # # # # # # # #
Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.
I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.
As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.
I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
# # # # # # # # # # # # # # # # # # # # # # # # # # #

Two drugs, two trials, two definitions of success against long COVID

If this matters to you, share it.


Last updated: 2026-08-18






How far is it to Solwezi North Western