#HashtagMeta

2026-01-16
So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

#[Hashtag](https://hub.hubzilla.de/search?tag=Hashtag)

Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

#Hashtag

Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

#Hashtag

Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
2026-01-16
So there's that nasty bug on Sharkey that mangles hashtags in messages from Hubzilla and probably also Friendica, (streams) and Forte. They always look like this:

#[Hashtag](https://hub.netzgemeinde.eu/search?tag=Hashtag)

Basically, Sharkey receives fully standard Rich Text from Hubzilla. It manages to convert this Rich Text into its own Misskey-Flavored Markdown. But then its Markdown parser does not parse it and leaves the Markdown code visible to everyone. It simply doesn't expect there to be a hashtag character in front of an embedded link because, seriously, who'd ever do that and why?!

Friendica would. In fact, Friendica does. It puts the hashtag character in front of the tag, as in outside the tag, as opposed to at the beginning of the tag. It has been doing that since its beginnings in 2010 because it was designed from the get-go to also federate with StatusNet from 2008. And StatusNet does hashtags the same way on its few remaining servers. In fact, so did Identi.ca from 2008, from which StatusNet emerged.

Hubzilla, (streams) and Forte do it, too, because they have inherited it from Friendica.

On StatusNet, Friendica, Hubzilla, (streams) and Forte, a hashtag in a message looks like this:

#Hashtag

Notice how the hashtag character has the same colour as the rest of the post text. And not the same colour as the rest of the hashtag. This means that the hashtag character is not part of the link. (To Mastodon users who don't know this: If something in a "toot" has a different colour from the rest of the "toot", it's a link. Even if it doesn't show a URL in plain sight.)

On 𝕏, Mastodon, Pleroma, Akkoma, Misskey, the various Forkeys and a whole lot of other Fediverse software, a hashtag in a message looks like this:

#Hashtag

Notice how now the hashtag character has the same colour as the rest of the hashtag. This means that the hashtag character is part of the link.

But why did Identi.ca do hashtags differently from Twitter? Because Identi.ca did hashtags before Twitter. AFAIK, when Identi.ca was launched, it had support for hashtags right away. About one year before Twitter.

The hashtag itself had already been invented by the Twitter community. Chris Messina had already codified it in 2007. But it wasn't until 2009 that Twitter actually introduced a technological implementation to support it.

Again, Identi.ca must have had hashtags as early as 2008, and there was no way that Identi.ca creator Evan Prodromou could possibly predict what Twitter would do the following year. So he did what he thought was right and what actually made sense to him.

But nowadays, everybody "knows" that Twitter had the world's very first hashtag implementation ever because nobody, even in the Fediverse, has ever heard of Identi.ca. I mean, the majority of Fediverse users "know" that the Fediverse started with Mastodon.

You know, just like Officer James Barrett "knew" that there is no intelligent life outside Earth only a few minutes before he became Agent J of the Men In Black.

This is also why just about all Fediverse software that does hashtags the Twitter way expects everything to do hashtags the Twitter way. It does not expect hashtags to be done differently. And when a message comes in from Friendica, Hubzilla, (streams) or Forte with hashtags in it, it fails at varying degrees of ungracefully.

Hashtags with the hashtag character outside the link are older than hashtags with the hashtag character inside that they're not only completely unexpected, that they cause software to malfunction, but the same software often can't even handle that malfunction. It's a miracle that the Friendica/Hubzilla family doesn't cause Fediverse servers to crash or even server databases to go corrupt by simply sending hashtags.

Mastodon used to be an exception of sorts, but only because, before version 4.0 from October, 2022, its HTML "sanitiser" actually ripped out any and all rich text code from incoming messages and left nothing but plain text behind. And then it didn't recognise hashtags in messages from outside Mastodon as hashtags at all.

When Mastodon 4.0 came and supported some rich text, including embedded links, it went haywire, of course. But then someone from Friendica and Hubzilla went in and complained about this malfunction and explained what happened, why it happened and why it was not Friendica and Hubzilla that did things wrong. Besides, if something utterly defaces "toots", then Mastodon developers do step in to stop it. After all, Mastodon has a few more of them at hand, paid, full-time professionals even. You have to give it that.

Which takes us back to Sharkey. Sharkey is developed by a small handful of individuals in their spare time. Granted, it's a soft fork of Misskey, so a lot of development work is done by the Misskey devs and taken over by the Sharkey devs, but they still have to weave the code changes coming from Misskey in and make them work with what's different on Sharkey.

So it turned out that (Link content warning: eye contact) this bug has already been filed to the Sharkey devs in October, 2024. All that has happened since then until today was that Hazelnoot added two labels. But the bug report came with no explanations. In fact, it misattributed one of my Hubzilla posts as a Friendica post.

And in fact, it turned out that this is actually (Link content warning: Microsoft GitHub link, eye contact) a Misskey bug which has been filed in January, 2024, two years ago. The bug report is a bit more elaborate, but the reporter still knew precious little about what's going on. So I wrote a comment in which I explained the bug from a Friendica/Hubzilla POV as well as what's going on on the technical side, and why the error has to be on Misskey's side.

I hope this will finally help get the bug fixed. Unfortunately, this fix would come too late for Iceshrimp. Iceshrimp-JS is a true Forkey, but in maintenance mode, so I guess only security patches and critical bugfixes will be merged from Misskey, if anything. And Iceshrimp.NET is a complete rewrite of a pre-this-fix Misskey fork, so the Iceshrimp devs probably don't know about this issue either. If it fails ungracefully upon receiving hashtags with the hashtag character outside, it will require its own bug report.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Twitter #𝕏 #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Sharkey #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Identi.ca #Laconi.ca #StatusNet #Friendica #Hubzilla #Streams #(streams) #Forte
2026-01-14
@「 Jürgen 」:fedi_mastodon:
Irgendwie ist das doch nicht die „übliche“ Verwendung von Hashtags in Beiträgen. Was ist der Hintergrund bei Hubzilla, dass das so gehandhabt wird?

Das hat Hubzilla geerbt von Friendica, weil es umgebaut wurde aus einem Fork eines Forks von Friendica. Und Friendica hat es übernommen von StatusNet, weil es von vornherein mit StatusNet föderieren sollte. Und StatusNet hat es geerbt von Identi.ca.

Sie alle handhab(t)en Hashtags intern als Schlüsselwörter, die keine Raute enthalten. Und sie stellen die Raute außerhalb des Link vor den Link, um zu signalisieren: Das hier ist ein Hashtag. Wenn man einen Post, einen Kommentar oder eine DM verschickt, wird aus dem Hashtag automatisch ein entsprechendes Konstrukt aus ungelinkter Raute plus Link aufs Schlüsselwort generiert.

Das ist wie bei Namen: Auf allen war bzw. ist das @ kein Teil irgendeines Namen, nicht des Kurznamen, nicht des Langnamen. Der Kurzname, der Teil des Profil-Link ist, hat auch kein @. Guck dir mal deine Erwähnung an: Das @ ist nicht Teil des Link, sondern steht vorm Link, und dein Langname ist erwähnt.

Warum "die" das anders gemacht haben als auf Twitter und Mastodon? Ganz einfach: Weil "die" das vor Mastodon gemacht haben. Eigentlich sogar noch vor Twitter.

Identi.ca und StatusNet waren von 2008. Etwa acht Jahre vor Mastodon. Das war der eigentliche Urknall des Fediverse. Und StatusNet hatte meines Wissens damals schon offizielle Unterstützung für Hashtags.

Warum hat es das nun anders gemacht als Twitter? Weil es das vor Twitter gemacht hat.

Es war nämlich erst 2009, daß Chris Messina offiziell Unterstützung für Hashtags bei Twitter eingeführt hat. Evan Prodromou, der Erfinder von Identi.ca, StatusNet und dem Fediverse, konnte unmöglich etwa ein Jahr im voraus ahnen, wie Twitter mal Hashtags implementieren wird. Und die Twitter-Entwickler dürften damals überhaupt nicht gewußt haben, daß auch nur Identi.ca existiert, geschweige denn, wie es Hashtags handhabt.

Friendica ging im Mai 2010 an den Start, etwa fünf Jahre und acht Monate vor Mastodon. Friendica basierte zwar auf einem eigenen Protokoll, war aber von vornherein in der Lage, sich mit StatusNet über dessen eigenes OStatus-Protokoll zu verbinden. Praktischerweise hat der Friendica-Erfinder Mike Macgirvin gleich Identi.cas und StatusNets Handhabung von Hashtags übernommen. Zu diesem Zeitpunkt hatte Twitter Hashtags erst seit gut zehn Monaten.

Ende 2011 hat Mike Macgirvin Friendica geforkt, dann den Fork geforkt und diesen Fork namens Red (später Red Matrix) dann ab 2012 komplett umgeschrieben. Zu diesem Zeitpunkt handhabte alles im Fediverse Hashtags noch auf dieselbe Art.

Um diese Zeit wurde StatusNet nach GNU social hardgeforkt, das wohl versuchte, mehr wie Twitter zu sein. Daher wurden auch die Hashtags wie auf Twitter ausgeführt: mit der Raute als Teil des Schlüsselworts und als Teil des Link. StatusNet verlor dann nach der 2012er Umstellung von Identi.ca auf pump.io seine Entwicklungsgrundlage und wurde 2013 kurzerhand nach GNU social gemerget, ohne aber die Hashtags wieder auf die alte Form umzustellen.

Im März 2015 wurde erstmals Hubzilla veröffentlicht, das entstanden war, indem die Red Matrix umbenannt und massiv erweitert worden war.

Erst im Januar 2016 kam dann Mastodon, Pleroma kurze Zeit später. Weil beide ursprünglich alternative Frontends für GNU social sein sollten, übernahmen sie von GNU social die Twitter-Hashtags.

Zu diesem Zeitpunkt sahen weder die neuen Entwickler, die Friendica seit Ende 2011 hatte, noch Mike Macgirvin es ein, warum sie ihre Software unbedingt an Mastodon anpassen sollten. Mike, der inzwischen zwei Nachfahren von Hubzilla betreut, sieht es bis heute nicht ein. Eher baut er serverseitige Gegenmittel gegen Mastodon in seine Software ein.

Misskey landete meines Wissens erst 2018 im Fediverse, nachdem es ActivityPub adoptiert hatte. Das hatte übrigens Hubzilla als erstes, seit Juli 2017, und Mastodon als zweites, seit September.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #Laconi.ca #StatusNet #GNUsocial #Friendica #Hubzilla #Mastodon #Pleroma #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2026-01-07
@kontrollierterWahnwitz
Es gibt keine falsche Nutzung von Hashtags.

Mach das denen klar, die sich immer darüber aufregen, wenn ich mehr als 4 Hashtags verwende. Und das tue ich fast immer.

Aber da sind eben auch technologische und kulturelle Unterschiede innerhalb des Fediverse im Spiel.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #FediverseKultur
2025-12-30
@Lena Riess 📚💚🤍 @tinderness Und da wundern sich dann die Leute, warum ich teilweise 10, 15, 20 Hashtags oder mehr unter einem einzelnen Beitrag habe.

Die dienen mindestens zur Hälfte dazu, meine Beiträge zu filtern. Ich schreibe ja sehr viel Zeugs, was vielleicht nicht unbedingt jeder lesen will.

Beispielsweise schreibe ich häufig übers Fediverse, das heißt dann aber nicht, daß ich nur über Mastodon und dann auch noch positiv darüber schreibe. Wenn, dann schreibe ich entweder über Sachen, die nicht Mastodon und deshalb ziemlich obskur sind, oder über Mastodon eher negativ oder beides.

Generell schreibe ich häufig sehr lang. Da, wo ich bin (Hubzilla), gibt es weder ein 500-Zeichen-Limit noch irgendein definiertes Zeichenlimit noch eine Kultur, alles schön kurz zu halten. Das stößt aber vielen Mastodon-Nutzern sauer auf, die der felsenfesten Überzeugung sind, Eugen Rochko habe das Fediverse als Mikrobloggingdienst erfunden (hat er nicht). Also gibt's auch hier wieder Hashtags zum Filtern.

Was hier aber schon sehr viel länger Teil der Kultur ist, als es Mastodon überhaupt gibt, ist, sich individuelle CWs mittels Wortfilter vollautomatisch generieren zu lassen, statt daß sie im Zusammenfassungsfeld allen gleichermaßen aufgezwungen werden. Deswegen dopple ich viele Hashtags mit "CW" am Anfang, um klarzumachen, daß sie genau dafür sind. Diejenigen, die sich ihre eigenen CWs generieren lassen, können dann meine Hashtags dafür nehmen.

Dann kommt noch dazu, daß es für viele Sachverhalte einfach irre viele Hashtags gibt und ich nicht vorher wissen kann, wer jetzt welches dieser Hashtags filtert. Das führt zu noch mehr Hashtags zum Auslösen von Filtern.

Alleine, um einen Beitrag mit mehr als 500 Zeichen zu markieren, brauche ich vier Hashtags und noch einmal zwei dazu, wenn er auf Deutsch ist. Wenn ich generell über das Fediverse schreibe, brauche ich noch einmal vier. Und so weiter.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
2025-10-20
@flo Die Darstellung als Markdown im Klartext ist ein eindeutiger Bug in Iceshrimp. Ganz offensichtlich kennt Iceshrimp keine Hashtags, wie sie Friendica schon seit mehr als 15 Jahren produziert, also, wo die Raute nicht Zeichen des Link ist. Also wandelt Iceshrimp die Hashtags in Markdown um, rendert sie dann hinterher aber nicht entsprechend.

Hubzilla selbst verwendet überhaupt kein Markdown. Hubzilla wandelt Hashtags intern in BBcode um. Beim Versenden wird der BBcode in den RTF-Standard umgewandelt. Iceshrimp wiederum wandelt RTF in Misskey-Flavored Markdown um. Aber wie es aussieht, kommt Iceshrimp nicht mit der Konstellation klar, wenn vor einem Link ein Rautenzeichen steht. Daran kann Hubzilla nichts machen.

Viele der Hashtags, die ich verwende, dienen dazu, Filter auszulösen, weil ich immer davon ausgehen muß, daß das, was ich hier so gerade übers Fediverse schreibe, so einige Leute stört. "Oh mein Gott, jetzt schreibt der Rowland wieder irgend so einen Mist über das Fediverse/Quote-Posts/CWs/Alt-Texte/Bildbeschreibungen/..." So können sie diese Inhalte gezielt rausfiltern. Oder sie können sie hinter individuellen, nur für sie automatisch leserseitig generierten CWs verstecken lassen (geht auf Mastodon seit 2022 und auf Mikes Schöpfungen schon immer); deswegen die vielen Hashtags mit "CW" am Anfang.

Beispiele:

#FediMeta und #FediverseMeta heißen: "Der Rowland labert schon wieder übers Fediverse."

#CWFediMeta und #CWFediverseMeta heißen: "CW: Der Rowland labert schon wieder übers Fediverse."

Hashtags sind es deshalb, weil die sich noch am unauffälligsten als Schlüsselwörter in jeden Post, jeden Kommentar und jede Antwort einbauen lassen.

Und es sind deswegen soviele, weil ich ja nicht wissen kann, ob jetzt jemand "QuotePost" oder "QuoteTweet" oder "QuoteToot" oder "QuoteTröt" oder "QuoteBoost" oder den jeweiligen Plural filtert. Die meisten dürften davon genau eins filtern, aber ich weiß eben nicht welches.

Wenn ich damit jetzt aufhören würde, weil das einige Leute stört, würde ich andere Leute stören, die genau diese Hashtags filtern.

Warum nicht "einfach" CWs wie auf Mastodon?

Weil Mastodons CW-Feld hier ein Zusammenfassungsfeld ist. Und zwar auf Hubzilla seit Frühjahr 2015, auf Red bzw. der Red Matrix (quasi Proto-Hubzilla) seit 2012 und auf Friendica seit 2010. Länger, als es Mastodon überhaupt gibt.

Zwei Dinge sind bombenfest in den Kulturen von Friendica und Hubzilla einzementiert.

Zum einen: Das Zusammenfassungsfeld ist für Zusammenfassungen.

Zum anderen: CWs läßt sich jeder automatisch und nur für sich individuell mittels eines Filters namens "NSFW" generieren. Und das ist tausendmal besser, als dieselben CWs allen Leuten über das Zusammenfassungsfeld aufzuzwingen, ob sie diese CWs brauchen oder nicht.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
The Very I of Night :startrek:kcdc@universeodon.com
2025-10-01

Reservoir Dogs: Canines in Film

#DogPodCasts
#HashtagMeta

2025-09-30
@Stefan Bohacek
And what about non-English text?

During all my researches about alt-text and image descriptions, I haven't found any steadfast and definite rule for how to transcribe non-English text in an image. On the one hand, you must transcribe any and all text in an image 100% verbatim. On the other hand, you must use the same language throughout your entire image description, also because no screen reader can switch language mid-reading process, much less mid-alt-text.

Just like the existence of non-readable text in an image has never been taken into consideration, neither has the existence of non-English text in an image.

I mean, I've run into this very issue a few times myself, so I know what I'm talking about from first-hand experience.

This is also why this part of my "how to transcribe text" entry in my alt-text/image description wiki will not have a definite method for transcribing foreign-language text anytime soon.

- check if you CapitalizeYourHashtags properly

This could easily go haywire on my two (streams) channels where I can and do use multiple-word hashtags with mid-hashtag blank spaces. Where Mastodon only supports #⁠MultipleWordHashtag, I can and do use #⁠Multiple-word hashtag.

I could do that here as well, but then I'd have two versions of some of my hashtags, and I'd still have to supply the PascalCased versions for those who filter any of my hashtags.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2025-06-11
Are you referring to my mentions being @Erik :heart_agender: and @Roknrol rather than what you're used to, namely @⁠bright_helpings and @⁠roknrol? Using the long name rather than the short name and keeping the @ outside the link rather than making it part of the link? Likewise, the # being outside the hashtag link rather than being part of it?

This is because I'm not on Mastodon. The Fediverse is not only Mastodon. It has never been. So this is not a toot.

No, really. This is what I post from: https://hub.netzgemeinde.eu/channel/jupiter_rowland, https://hub.netzgemeinde.eu/profile/jupiter_rowland. I ask you: Does this look like Mastodon? Have you ever seen Mastodon look like this?

Where I am, this style of mentions and hashtags is hard-coded. And it has been since long before Mastodon was even an idea.

I'm on something named Hubzilla. Hubzilla is not a Mastodon instance. Hubzilla is not a Mastodon fork either. Hubzilla has got absolutely nothing to do with Mastodon at all.

It is its very own project, fully independent from Mastodon (https://hubzilla.org, https://framagit.org/hubzilla, https://joinfediverse.wiki/Hubzilla).

Hubzilla has not intruded into "the Mastodon Fediverse" either. The Fediverse is older than Mastodon. And Hubzilla was there before Mastodon.

Hubzilla was launched by @Mike Macgirvin ?️ in March, 2015, eight months before Mastodon, by renaming and redesigning his own Red Matrix from 2012, almost four years before Mastodon. And the Red Matrix was a fork of a fork of his own Friendica, which was launched on July 2nd, 2010, 15 years ago, five and a half years before Mastodon. (https://en.wikipedia.org/Friendica, https://friendi.ca, https://github.com/friendica, https://joinfediverse.wiki/Friendica)

Friendica was there before Mastodon, too.

Here's the official Friendica/Hubzilla timeline on Hubzilla's official website to show you that I'm not making anything up: https://hubzilla.org/page/info/timeline. Scroll all the way down and notice all the features that you may right now know for a fact that the Fediverse doesn't have, but that Friendica has introduced to the Fediverse 15 years ago, five and a half years before Mastodon was launched.

Again, Mastodon has never been its own network. The Fediverse has never been only Mastodon. When Mastodon was launched in January, 2016, it immediately federated with

Friendica has been formatting mentions and hashtags the way I just did for 15 years now. When Mastodon was launched, Friendica has been formatting them that way for five and a half years already, and Hubzilla has done so for ten months. It is hard-coded there. It is not a user option.

That's because not everything in the Fediverse is a Twitter clone or Twitter alternative. [b]Friendica was designed as a Facebook alternative with full-blown long-form blogging capability. And Hubzilla adds even more stuff to this. This is why Friendica and Hubzilla don't mimic Twitter.

Another shocking fact: As you can clearly see here, Friendica and Hubzilla don't have Mastodon's 500-character limit. Friendica's character limit is 200,000. Hubzilla's character limit is 16,777,215, the maximum length of the database field. And it's deeply engrained in their culture, which is many years older than Mastodon's culture, to not worry about the length of a post exceeding 500 characters.

One more shocking fact: Friendica has had quote-posts since its very beginning. So has Hubzilla. Both have always been able to quote-post any public Mastodon toot, and they will forever remain able to quote-post any public Mastodon toot. And Mastodon will never be able to do anything against it. (By the way: In 15 years of Friendica, nobody has ever used quote-posts for dogpiling or harassment purposes. Neither Friendica nor Hubzilla is Twitter.)

You find this disturbing? You think none of this should exist in the Fediverse, even though all this has been in the Fediverse for longer than Mastodon?

Then go ahead and block all instances of Friendica and Hubzilla as well as all instances of Mike's later creations, (streams) (https://codeberg.org/streams/streams) from 2021 and Forte (https://codeberg.org/fortified/forte) from 2024.

Or you could go ask @Seirdy / DM me the word "bread" and @Garden Fence Blocklist as well as @Mad Villain of @The Bad Space to add every last instance on any of these lists to their blocklists for being "rampantly and unabashedly ableist and xenophobic by design" due to not being and acting and working like Mastodon and just as rampantly and unabashedly refusing to fully adopt and adapt to the Mastodon-centric "Fediverse culture" as defined by fresh Twitter refugees on Mastodon in mid-2022 as well as refusing to abandon their own culture which is disturbingly incompatible with Mastodon's. Essentially try and have four entire Fediverse server applications Fediblocked once and for all because they're so disturbing from a "Fediverse equals Mastodon" point of view.

Or you could go to Mastodon's GitHub repository (https://github.com/mastodon/mastodon), submit a feature request for defederating Mastodon from everything that isn't Mastodon by design and then go lobbying for support for your feature request.

As for why I have so many hashtags below my comments, here is what they mean. Many of them are meant to trigger filters, including such that automatically hide posts behind content warning buttons, a feature that Mastodon has had since October, 2022, that Friendica has had since July, 2010, and that Hubzilla has had since March, 2015.

  • #Long, #LongPost = This post is over 500 characters long. Create a filter for either or both of these hashtags if you don't want to see my or anyone else's long posts.
  • #CWLong, #CWLongPost = CW: long post (over 500 characters long). Create a filter for either or both of these hashtags if you don't want to see my or anyone else's long posts.
  • #FediMeta, #FediverseMeta = This post talks about the Fediverse. Create a filter for either or both of these hashtags if you don't want to see me or anyone talk about the Fediverse.
  • #CWFediMeta, #CWFediverseMeta = CW: Fediverse meta. Or: CW: Fediverse meta, Fediverse-beyond-Mastodon meta. Or: CW: Fediverse meta, non-Mastodon Fediverse meta. Create a filter for either or both of these hashtags if you don't want to see me or anyone talk about the Fediverse.
  • #NotOnlyMastodon, #FediverseIsNotMastodon, #MastodonIsNotTheFediverse: This post talks about the Fediverse not only being Mastodon. Create a filter for either or multiple or all of these hashtags if you don't want to see me or anyone else talk about the Fediverse being more than Mastodon. Otherwise, click or tap any of these hashtags to read more about it in your Fediverse app.
  • #Friendica: This post talks about the Facebook alternative in the Fediverse named Friendica. Create a filter for it if you don't want to see me or anyone else talk about Friendica. Otherwise, click or tap it to read more about it in your Fediverse app. It is also meant for post discovery.
  • #Hubzilla: This post talks about the Swiss army knif of the Fediverse named Hubzilla. Create a filter for it if you don't want to see me or anyone else talk about Hubzilla. Otherwise, click or tap it to read more about it in your Fediverse app. It is also meant for post discovery.
  • #Streams, #(streams): This post talks about the Facebook alternative in the Fediverse commonly referred to as (streams). Create a filter for either or both of them if you don't want to see me or anyone else talk about Friendica. Otherwise, click or tap either of them to read more about it in your Fediverse app. It is also meant for post discovery.
  • #Forte: This post talks about the Facebook alternative in the Fediverse named Forte. Create a filter for it if you don't want to see me or anyone else talk about Forte. Otherwise, click or tap it to read more about it in your Fediverse app. It is also meant for post discovery.
  • #AltText = This post talks about alt-text and/or contains an image with alt-text. It is primarily meant for post discovery.
  • #AltTextMeta = This post talks about alt-text. Create a filter for this hashtag if you don't want to see me or anyone else talk about alt-text.
  • #CWAltTextMeta = CW: alt-text meta. Create a filter for this hashtag if you don't want to see me or anyone else talk about alt-text.
  • #ImageDescription = This post talks about image descriptions and/or contains an image with an image description. It is primarily meant for post discovery.
  • #ImageDescriptions, #ImageDescriptionMeta = This post talks about image descriptions. Create a filter for either of these hashtags if you don't want to see me or anyone else talk about image descriptions.
  • #CWImageDescriptionMeta = CW: image description meta. Create a filter for this hashtag if you don't want to see me or anyone else talk about image descriptions.
  • #Hashtag, #Hashtags, #HashtagMeta = This post talks about hashtags. Create a filter for either of these hashtags if you don't want to see me or anyone else talk about hashtags.
  • #CWHashtagMeta = CW: hashtag meta. Create a filter for this hashtag if you don't want to see me or anyone else talk about hashtags.
  • #CharacterLimit, #CharacterLimits = This post is talking about character limits. It is primarily meant for post discovery. But if you don't want to see me or anyone else talk about character limits, create a filter for any of these hashtags.
  • #QuotePost, #QuoteTweet, #QuoteToot, #QuoteBoost = This post talks about quote-posts and/or contains a quote-post. If this disturbs you, create a filter for any of these hashtags.
  • #QuotePosts, #QuoteTweets, #QuoteToots, #QuoteBoosts, #QuotedShares = This post talks about quote-posts. Create a filter for either of these hashtags if you don't want to see me or anyone else talk about quote-posts.
  • #QuotePostDebate, #QuoteTootDebate = This post talks about quote-posts. Create a filter for either of these hashtags if you don't want to see me or anyone else talk about quote-posts.
  • #FediblockMeta = This post is talking about fediblocks. It is primarily meant for post discovery.

Lastly: Having all hashtags in one line at the very end of a post that only contains hashtags is the preferred way in the Fediverse. For one, hashtags in their own line at the end of the post irritate screen reader users much less than hashtags in the middle of the text. It's actually hashtags in the middle of the text that are ableist. Besides, Mastodon is explicitly designed to have a separate hashtag line at the end of the post.
2025-05-04
@Regezi Ich setze Hashtags locker zur Hälfte ein, um Leuten das Filtern zu erleichtern und auch das automatisierte, individuelle leserseitige Verstecken von Posts hinter CWs, wie es auf Friendica und Hubzilla schon der Standard war, bevor es Mastodon überhaupt gab. (Deswegen die Hashtags, die mit "CW" anfangen.)

Ich nehme dafür aus zwei Gründen Hashtags statt Schlüsselwörtern. Zum einen sieht eine Zeile aus nackten Schlüsselwörtern bekloppt aus. Zum anderen habe ich durchaus auch Überschneidungen, also Hashtags, die sowohl dem Auffinden als auch dem Filterauslösen dienen.

Eigentlich müßte ich, um mich vollends an Mastodons Kultur und Regeln zu halten, meine Kommentare alle hinter Zusammenfassungen verstecken, die Mastodon dann als CWs versteht. Aber Hubzilla hat keinerlei wie auch immer geartete Unterstützung dafür, weil eine Zusammenfassung für etwas, was im Prinzip so etwas wie ein Blogkommentar ist, keinen Sinn ergibt. Es gibt in den Eingabebereichen für Kommentare kein Zusammenfassungsfeld, und [summary][/summary] funktioniert in Kommentaren auch nicht richtig, wenn sie über ActivityPub rausgehen.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #MastodonKultur
2025-04-01
@Jorge Candeias That's true. And it's on the verge of rendering certain hashtags (#Fediverse, #Mastodon) useless because they're misused too much.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2025-04-01
@Jorge Candeias Bad idea. (Hubzilla user here.)

Hashtags are not only for discoverability (and critically so on Mastodon). They're also the preferred way of triggering the automatic generation of individual reader-side content warnings.

Content warnings that are automatically generated for each user individually based on keyword lists have a long tradition in the Fediverse. Friendica has had them long before Mastodon even existed, much less before Mastodon hijacked the summary field for content warnings. Hubzilla has had them since its own inception which was before Mastodon, too. (streams) has them, Forte has them.

On all four, automated reader-side content warnings are an integral part of their culture. And users of all four (those who are not recent Mastodon converts at least, i.e. those who entered the Fediverse by joining Friendica in the early 2010s) insist in automated reader-side content warnings being vastly better than Mastodon's poster-side content warnings that are forced upon everyone all the same.

Oh, and by the way, Mastodon has this feature, too. It has only introduced it in October, 2022, and since the re-definition of Mastodon's culture in mid-2022 pre-dates it, it is not part of Mastodon's culture. But Mastodon has this feature.

However, in order for these content warnings to be generated, there needs to be a trigger. The safest way is by hashtags: If you post content that not everyone may want to see, add corresponding hashtags, enough to cover as many people as possible. If you don't want to see certain content right away, add the corresponding hashtags as keywords to NSFW (Friendica, Hubzilla, (streams), Forte) or a CW-generating filter (Mastodon).

In fact, hashtags can also be used to completely filter out content that you don't want to see at all. And they can be used to trigger such filters. This should work everywhere in the Fediverse.

I myself post stuff that some people don't want to see all the time. Hence, I need a whole lot of hashtags.

Let me explain the "hashtag wall" at the bottom of this comment to you.

  • #Long, #LongPost
    This comment is over 500 characters long. Many Mastodon users don't want to see any content that exceeds 500 characters. They can filter either or both of these hashtags and at least get rid of my content with over 500 characters.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #CWLong, #CWLongPost
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: long (over 8,300 characters)"). Also, filtering these instead of the above has less of a chance of false positives than the above.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #FediMeta, #FediverseMeta
    This comment contains Fediverse meta content. Some people don't want to read anything about the Fediverse, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either or both of these.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #CWFediMeta, #CWFediverseMeta
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: Fediverse meta" or, in this case, "CW: Fediverse meta, Fediverse-beyond-Mastodon meta").
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #Fediverse
    This comment is about the Fediverse. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about the Fediverse find my comment.
  • #Mastodon
    This comment touches Mastodon as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about Mastodon find my comment.
  • #Friendica
    This comment touches Friendica as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Friendica is, but you're curious. Also, the hashtag helps people looking for content about Friendica find my comment.
  • #Hubzilla
    This comment touches Hubzilla as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Hubzilla is, but you're curious. Also, the hashtag helps people looking for content about Hubzilla find my comment.
  • #Streams, #(streams)
    This comment touches (streams) as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell the streams repository is, but you're curious. Also, the hashtag helps people looking for content about (streams) find my comment.
    Why two hashtags if they're the same on Mastodon? Because they are not the same on Friendica, Hubzilla (again, that's where I am), (streams) itself and Forte. If I have to choose between catering to the technologies and cultures of Friendica, Hubzilla, (streams) and Forte and catering to Mastodon's, I will always choose the former.
  • #Forte
    This comment touches Forte as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Forte is, but you're curious. Also, the hashtag helps people looking for content about Forte find my comment.
  • #MastodonCulture
    This comment touches Mastodon culture as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, including critical views upon how Mastodon users try to force Mastodon's 2022 culture upon the users of Fediverse server applications that are very different from Mastodon, and that have had their own culture for much longer. Also, the hashtag helps people looking for content about Mastodon culture find my comment.
  • #Hashtag, #Hashtags
    This comment touches hashtags as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about hashtags and their implications find my comment.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #HashtagMeta
    This comment contains hashtag meta content. Some people don't want to read anything about it, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either it.
  • #CWHashtagMeta
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: hashtag meta").

By the way: Hashtags for triggering filters are even more important on Hubzilla in comments when Mastodon users may see them. That's because Hubzilla cannot add Mastodon-style content warnings to comments (= everything that replies to something else; here on Hubzilla, it's very different from a post that isn't a reply). What's a content warning on Mastodon is still (and justifiedly so) a summary on Hubzilla. But from a traditional blogging point of view (Hubzilla can very much be used for full-fledged long-form blogging with all bells and whistles), a summary for a comment doesn't make sense. Thus, the comment editors have no summary field on Hubzilla. Thus, I can't add Mastodon-style CWs to comments here on Hubzilla.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #MastodonCulture #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2025-02-16
@Laura @Roni Laukkarinen Depends on the effort per post. It's one thing if it takes you no more than two minutes to describe one image, any image.

But my own current standards for myself require me to invest several hours into description and explanation for a meme post based on a standard template. For one of my original images, I would need two days now. I would because I can't properly describe at least some of my old images. They're pictures of the past. What they show is no longer there. This means that I can no longer source all the detail informations necessary for an image description on my current level.

In fact, my current level, my current standard isn't even really defined. I'm working on a new series of image posts, I have been since last year. And I may or may not try something new, namely long image descriptions (not to be confused with the short image descriptions in the alt-texts) in little HTML files linked into the post. As long as I don't know if that's actually better than putting the long descriptions directly into the post, inflating it to a titanic size, I can't touch older posts anyway.

That is, if I added a full set of image descriptions to each one of my oldest images, I would also have to go and upgrade my more recent image descriptions to my current standard. I don't want the quality of my image descriptions to tank at some point two years ago.

While I'm at it, I'd generally have to upgrade all my old posts in several ways. Placement of hashtags. Choice of hashtags, especially filter-triggering hashtags. Mastodon-style content warnings in the summary field, along with summaries, especially for any and all posts and comments that exceed 500 characters.

Trouble is, Mastodon doesn't understand edits from Hubzilla. All posts would go out to my hundreds of Mastodon connections on countless instances once more as brand-new. This would be extra awkward for posts about events that were years ago.

#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Hubzilla #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta
2024-12-15
Der Standard ist eigentlich PascalCase: Erster Buchstabe von jedem Wort ist groß. CamelCase wäre eher "camelCase", also erster Buchstabe des ersten Wortes klein, erster Buchstabe von allen anderen Wörtern groß. Aber das ist für die, die zu faul sind, Großbuchstaben zu schreiben.

Am elegantesten sieht natürlich ein Hashtag aus mehreren Wörtern aus. Zumindest auf Hubzilla, (streams) und Forte kann man ihn mit Anführungszeichen generieren: #"The Prodigy". In der Darstellung verschwinden dann die Anführungszeichen, und man sieht einen durchgängig linkenden Hashtag mit mehreren Wörtern. Eventuell geht das auch auf Friendica.

Ich weiß jetzt allerdings nicht, wie gut das in Screenreadern funktioniert. Vorlesen können sie das definitiv, aber das Risiko besteht, daß sie einen Hashtag aus mehreren Wörtern nicht als Hashtag aus mehreren Wörtern erkennen und nur das erste Wort als Teil des Hashtags erkennen.

In der Mastodon-Suche spielt das übrigens keine Rolle. Beim Indizieren von Hashtags schmeißt Mastodon alle Zeichen raus, die auf Mastodon in Hashtags nicht funktionieren. #TheProdigy, #The-Prodigy und #"The Prodigy" (das dann ja zu #The Prodigy wird) sind im Suchindex von Mastodon alle gleichermaßen #TheProdigy.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #ScreenReader #A11y #Accessibility #Barrierefreiheit #FediTips
2024-10-13

5/x
Anm zu 3. in 4/x:
Warum gibt es kein kombiniertes Emoji für 🐰 🕳️ ? Ganz zu schweigen für einen Unicode-Punkt.

An dieser Stelle muss ich wohl beginnen, diesen 🧵 zu verschlagworten mit
#IconicTurn

Anmerkung dazu: @mastodon, bitte zerstört meine Binnenmajuskeln nicht in Eurer #HashtagMeta #autocompletion. Danke!

2024-10-12

Lo dico? Lo dico: gli hashtag legati al nome dell'istanza sono, nel migliore dei casi, la forma peggiore.

(A seguire: quelli basati sul nome di una singola piattaforma.)

L'unico caso in cui dovrebbero essere utilizzati è quando si riferiscono effettivamente a questioni specifiche che riguardano quell'istanza (o quella piattaforma).

#hashtag #hashtagMeta

2024-08-17
@Dodo III. @Samantha Cohen Keep in mind that hashtags can be and are used to trigger filters as well.

And where I am (Hubzilla), we've been using keywords or hashtags to automatically generate CWs since before Mastodon was even made. Depending on how much sensitive or potentially disturbing content there is in a post, it may need a lot of hashtags.

Notice the hashtags at the bottom of this comment that start with "CW".

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2024-08-14
@Michael Vogel
Was anderes aus Interesse: Wieso schickst Du bei allen Posts die gleichen Hashtags mit? Ist das eine Eigenschaft von Hubzilla oder fügst Du die Hashtags immer per Hand hinzu? (und wenn ja, wieso?)

Die schreibe ich per Hand rein.

Teilweise sind die zum leichteren Auffinden auf Mastodon. Hauptsächlich sind sie aber zum Triggern von Wortfiltern. Es gibt kaum etwas, worüber ich schreibe, was nicht irgendjemanden so stören würde, daß sie es nicht rausfiltern würden. Und Hubzilla schickt anscheinend auch meine öffentlichen Kommentare an alle meine Kontakte, also auch quer über Mastodon.

Klar könnte ich jetzt sagen, die meisten Mastodon-Nutzer würden nicht mal Filter benutzen, wenn ich ihnen eine Schritt-für-Schritt-Anleitung mit konkreten Beispielen posten würde. Aber wer auf Mastodon jetzt tatsächlich was filtert, kann ich blöderweise nicht mal aus Zustellungsberichten rauslesen.

Die ersten vier eben, #Long, #LongPost, #CWLong und #CWLongPost, baue ich immer ein, wenn ein Post oder Kommentar die 500 Zeichen überschreitet, um irgendwas zu haben, womit sich Mastodon-User meine "überlangen" Beiträge vom Hals schaffen können.

Ist eben so: Ich habe sehr viel mehr Publikum auf Mastodon als auf Friendica, Hubzilla und (streams) zusammen. Andererseits sind es gerade Nutzer aus unserer Ecke des Fediverse, die ich dabei erwischt habe, das Hauptthema meines Kanals auszufiltern.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
2024-08-14
@The Nexus of Privacy I'm someone who usually follows all advice about good Fediverse behaviour to a tee. That is, as far as Hubzilla lets me, as long as it doesn't require me to abandon Hubzilla's own culture in favour of only Mastodon's culture, and as long as it doesn't require me to abandon a number of Hubzilla's key features because Mastodon doesn't have them.

Some may say I'm overdoing the Mastodon-style content warning thing, at least in posts. Hubzilla doesn't support content warning in comments, and if I reply to something, it's always a comment and never a post. Otherwise you'd get one big honking Mastodon-style content warning here. You do get a huge pile of filter-triggering hashtags, though.

Some may say I'm overdoing the image description thing. My image descriptions in alt-text are among the longest in the Fediverse, and these are my short descriptions. My long descriptions for the same images which go into the posts are the longest, most detailed, most explanatory image descriptions in the Fediverse, full stop. And I keep raising my own standards. I only have one image description which I don't consider outdated, obsolete and sub-standard yet.

So I'd normally love to fulfill everything in your post to a tee by my definition of "a tee". And my definition of "to a tee" is everyone else's definition of "Are you completely insane, man?!" But this time, it's more difficult. Call me racist, but it's more difficult.

(1/7)

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagmeta #Filters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Racist #Racism
2024-08-13
@D.Hamlin.Music Okay, let me demonstrate it this way. I hope Glitch can at least display multiple-line code blocks. If not, I give up, for there's absolutely no way of showing you what I mean.

On Twitter, Mastodon and everything else that "does microblogging", a hashtag includes the hashtag character in the link. In #[zrl=https://hub.netzgemeinde.eu/search?tag=Hashtag]Hashtag[/zrl], everything is part of the link and part of the hashtag.

All this is a link
    |
________
#[zrl=https://hub.netzgemeinde.eu/search?tag=Hashtag]Hashtag[/zrl]

Look at the hashtags that you're used to. The # is always part of the link and part of the hashtag.

This is what Mastodon used to expect. And this is what Glitch (which is where you are) and Iceshrimp.NET (which is where @Lunawawa :neofox_snug: :therian: is) still expect and nothing else.

Friendica, Hubzilla (which is where I am) and (streams) work differently, also because Friendica is five and a half years older than Mastodon, Hubzilla is an indirect Friendica fork, and (streams) is an indirect Mastodon fork.

In #[zrl=https://hub.netzgemeinde.eu/search?tag=Hashtag]Hashtag[/zrl], the # is decoration, not part of the link, not part of the hashtag. Only Hashtag is the link and the actual hashtag.

Neither Glitch nor Iceshrimp.NET can handle this. Their devs have probably never seen any of this. They neither know it exists, nor do they even only expect it to exist.

Result: Glitch "sanitises" the unknown, unexpected, "IDFK what this is" code away, just like Mastodon probably used to do until someone from Friendica or Hubzilla filed a bug on GitHub. And Iceshrimp.NET doesn't know how to handle this unexpected code at all. It fails ungracefully by going completely haywire.

I'm going to file a bug on the Glitch repository now. For Iceshrimp.NET, I'll need an account on its repository.

The following hashtags are only for discovery purposes and for sensible users to filter this comment out.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Glitch #GlitchSoc #Glitch_Soc #Iceshrimp #Iceshrimp.NET #Friendica #Hubzilla #Streams #(streams) #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst