Mentions and hashtags on Hubzilla are more "normal" in version 11.4, and this probably isn't pandering to Mastodon; CW: long (over 3,200 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, hashtag meta
Artikel ansehen
Zusammenfassung ansehen
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 (
@Jupiter's Fedi-Memes on (streams),
#Hashtag, 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 "#
Hashtag" (with the number sign outside the link, the Identi.ca way) as its Markdown representation, "#[Hashtag](
https://hub.netzgemeinde.eu/search?tag=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?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Hubzilla11 #Hashtags #HashtagMeta #CWHashtagMeta #Mention #Mentions #MentionTag
