I can't thank @evan@cosocial.ca and @Gargron@mastodon.social enough for all they have done to foster social media communities outside of big tech. Everything that has happened as a result of their work -- and all the projects and communities that have sprung up since then -- gives me a lot of hope.

#Fediverse #Mastodon #identica #statusnet #pumpio

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

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

@「 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

Whenever someone announces to "bring" something "to the Fediverse", chances are that Friendica has actually had it since 2010, for five and a half years longer than Mastodon has been around.

For example, just about everyone on Mastodon is fully convinced that Eugen Rochko has brought quote-posts to the Fediverse this year. That's because next to nobody on Mastodon knows that Friendica has been able to quote-post practically everything in the Fediverse, including Mastodon toots, for 15 years now.

And if Friendica doesn't have it, chances are still that Hubzilla has it, and that Hubzilla has probably had it for longer than Mastodon has been around, too.

For example, private messages that are actually private. Mastodon doesn't have them because the "privacy" of Mastodon DMs is only "guaranteed" by limiting whom a DM is sent to. Hubzilla does have them and has had them since 2012, since it was still named Red. How? Because Hubzilla also limits who is permitted to see a DM.

Oh, and Hubzilla even offers optional encryption on top of that.

Or how about server-independent identity? Everyone still waiting for Bluesky to finally be the pioneer who invents this and implements it for the first time? LOL! Once again, Hubzilla has had this since 2012. Not a vague concept, not an unstable proof-of-concept, but daily-driven by production-grade channels on production-grade servers. (streams) has it, too, inherited from Hubzilla through a whole number of forks. Forte has it, too, and Forte is the first and, so far, only Fediverse server software that uses ActivityPub for nomadic identity.

Now I'm waiting for someone to announce that something will "bring" actual groups "to the Fediverse". A feature that was actually introduced to the Fediverse by StatusNet in 2008, and that's also available on Friendica, Hubzilla, (streams) and Forte. Not to mention that the very principle of the Threadiverse (Lemmy, the remains of /kbin, Mbin, PieFed) is based on groups.

This is what happens when you think that the feature set of the whole Fediverse is the feature set of Mastodon and maybe Pixelfed because that's all you know.

Speaking of Mastodon: Just because it's being "brought to the Fediverse", doesn't mean it'll be adopted by Mastodon.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonCentrism #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #StatusNet #Threadiverse #Lemmy #/kbin #Mbin #PieFed #Groups #FediGroups #FediverseGroups

Whenever someone announces to "bring" something "to the Fediverse", chances are that Friendica has actually had it since 2010, for five and a half years longer than Mastodon has been around.

For example, just about everyone on Mastodon is fully convinced that Eugen Rochko has brought quote-posts to the Fediverse this year. That's because next to nobody on Mastodon knows that Friendica has been able to quote-post practically everything in the Fediverse, including Mastodon toots, for 15 years now.

And if Friendica doesn't have it, chances are still that Hubzilla has it, and that Hubzilla has probably had it for longer than Mastodon has been around, too.

For example, private messages that are actually private. Mastodon doesn't have them because the "privacy" of Mastodon DMs is only "guaranteed" by limiting whom a DM is sent to. Hubzilla does have them and has had them since 2012, since it was still named Red. How? Because Hubzilla also limits who is permitted to see a DM.

Oh, and Hubzilla even offers optional encryption on top of that.

Or how about server-independent identity? Everyone still waiting for Bluesky to finally be the pioneer who invents this and implements it for the first time? LOL! Once again, Hubzilla has had this since 2012. Not a vague concept, not an unstable proof-of-concept, but daily-driven by production-grade channels on production-grade servers. (streams) has it, too, inherited from Hubzilla through a whole number of forks. Forte has it, too, and Forte is the first and, so far, only Fediverse server software that uses ActivityPub for nomadic identity.

Now I'm waiting for someone to announce that something will "bring" actual groups "to the Fediverse". A feature that was actually introduced to the Fediverse by StatusNet in 2008, and that's also available on Friendica, Hubzilla, (streams) and Forte. Not to mention that the very principle of the Threadiverse (Lemmy, the remains of /kbin, Mbin, PieFed) is based on groups.

This is what happens when you think that the feature set of the whole Fediverse is the feature set of Mastodon and maybe Pixelfed because that's all you know.

Speaking of Mastodon: Just because it's being "brought to the Fediverse", doesn't mean it'll be adopted by Mastodon.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonCentrism #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #StatusNet #Threadiverse #Lemmy #/kbin #Mbin #PieFed #Groups #FediGroups #FediverseGroups

@Maxi 11x 💉

Das Fediverse wird immer mehr zu Facebook und ich hab da wenig Lust drauf.

Das Fediverse war Facebook, bevor es von Millionen von ahnungslosen Mastodon-Newbies zu Twitter gemacht wurde.

Mehr als die Hälfte der Mastodon-Nutzer glaubt, das Fediverse sei nur Mastodon. Der weit überwiegende Teil derer, die eines Besseren belehrt wurden, glauben immer noch, das Fediverse sei

• (frühestens) 2016
• von Eugen Rochko
• als reine Microblogging-Plattform und Twitter-Klon
• mit einem Zeichenlimit von 500 Zeichen

erfunden worden. Und alles, was davon abweicht und nicht "offensichtlich (wie PeerTube & Co.) als Extra an Mastodon drangeklebt" worden ist, wird aufgefaßt als lästige Eindringlinge im Mastodon-Fediverse, die sich nicht an die Regeln des Mastodon-Fediverse halten und sich auch nicht an die Kultur des Mastodon-Fediverse anpassen.

Um das mal zurechtzurücken:

Im Januar 2016 ging Mastodon an den Start.

Im Juli 2010, fünfeinhalb Jahre vor Mastodon, startete Friendica (https://de.wikipedia.org/wiki/Friendica, https://friendi.ca) als Facebook-Alternative.

• Ohne Zeichenbegrenzung (tatsächlich 16.777.215 Zeichen).
• Mit allem, was eine gute Bloggingplattform an Textformatierung hergibt.
• Mit Inhaltswarnungen, die jeder für sich selbst automatisch generieren lassen kann mittels einer Liste von Schlüsselwörtern.
• Mit Titeln und Zusammenfassungen, und die Zusammenfassungen waren schon immer in dem Datenfeld, das Mastodon seit 2017 für CWs verwendet.
• Mit der Fähigkeit, andere Posts als Komplettzitate zu teilen. Und nicht ein einziges Mal ist das mißbräuchlich verwendet worden.

Jetzt regen sich Mastodon-Nutzer darüber auf, daß Friendica auf so infame und rücksichtslose Art und Weise ins Mastodon-Fediverse eingedrungen ist und seine Nutzer

• sich nicht ans 500-Zeichen-Limit halten
• alle mit ihren Textformatierungen nerven
• keine CWs schreiben
• dafür das CW-Feld mißbrauchen mit "Titeln oder was weiß ich, was das ist"

Daß Friendica schon seit über 15 Jahren quote-posten kann, weiß zum Glück beinahe niemand auf Mastodon.

Fakt ist aber: Friendica gab es nicht nur schon fünfeinhalb Jahre, als Mastodon startete, sondern es war auch schon fünfeinhalb Jahre im Fediverse, als Mastodon startete. Und es hatte auch schon gut fünf Jahre lang seine eigene Kultur, als Mastodon startete.

In dem Augenblick, wo Mastodon startete, verband es sich sofort mit StatusNet (von 2008, wofür Mastodon ursprünglich nur eine Alternativoberfläche war; heute GNU social, https://de.wikipedia.org/wiki/GNU_Social, https://gnusocial.rocks/), Friendica und Hubzilla (von 2015, basiert auf einem Fork eines Forks von Friendica von 2012; https://de.wikipedia.org/wiki/Hubzilla, https://hubzilla.org). Und nicht umgekehrt.

Wir waren zuerst hier. Findet euch damit ab.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #MastodonZentrizität #MastodonNormativität #StatusNet #GNUsocial #Friendica #Hubzilla #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Zeichenlimit #Zeichenlimits #ZeichenlimitMeta #CWZeichenlimitMeta #500Zeichen #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteTröt #QuoteTröts #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebatte #QuoteTrötDebatte

@Mirko Schenk

wenn ich das recht mitbekam, war z.B. die "Content Warning" im Protokoll eigentlich als Überschrift gedacht, wurde dann für "Spoiler" genutzt, die dann zu den CWs wurde.

Ursprünglich war das die Zusammenfassung von StatusNet von 2008.

Überschriften im Sinne von Post-Titeln kamen im Fediverse 2010 mit Mistpark (heute Friendica) an, und zwar zusätzlich zu Zusammenfassungen. Aber die spielen auf Mastodon nur eine Rolle bei Article-Type Objects, wo Mastodon den Titel zeigt und dann aufs Original verlinkt.

2017 kam dann ein Bastler aus der Demoszene und reichte auf Mastodon einen Pull Request ein, mit dem auf Mastodon die Unterstützung des Zusammenfassungsfelds eingebaut wurde. Aber nicht als Zusammenfassung, weil das bei nur 500 Zeichen Quatsch wäre, sondern als Inhaltswarnung.

Seitdem glauben alle auf Mastodon, das Feld wäre von vornherein für CWs und nur für CWs erfunden worden.

Quoted Posts werden jetzt nach etlichen Jahren langsam eingeführt

Auf Mastodon. Fast das ganze übrige Fediverse hat sie schon. Friendica hat sie auch schon seit Anbeginn (2010). Und so können Friendica und Hubzilla Mastodon-Tröts quote-posten, seit es Mastodon überhaupt gibt. Und das werden sie weiterhin können, egal, wer auf Mastodon was wie einstellt.

Andererseits muss man Mastodon halt zugestehen, dass es den Einstieg vergleichsweise einfach macht. Also abgesehen davon, dass dieses Instanzen-Zeug für Monopol-gewohnte User anscheinend generell nicht so einfach ist.

Och, 2022/2023 sind auch Unmengen an Japanern nach misskey.io gerailroadet worden.

Mastodon ist nur so groß, weil es praktisch allen westlichen Twitter-Flüchtlingen als die einzige Twitter-Alternative angepriesen wurde. Wohlgemerkt, überwiegend von Leuten, die selbst glaubten, das Fediverse sei nur Mastodon.

Und die meisten Alternativen skalieren auch schlecht auf sehr viele User.

Wobei Mastodon eigentlich pro Identität absurd viele Server-Ressourcen braucht. Möglicherweise kommt das notorische Fliegengewicht Akkoma mit noch mehr Identitäten pro Server klar.

Selbst die Friendica-Familie ist dank PHP leichtwiegiger als Mastodon, auch Friendica selbst, das um 2012 geradezu absurd viel Leistung pro Nase brauchte, und sogar das Featuremonster Hubzilla. Weil die aber ziemlich obskur sind und auf (streams) geschätzt 90% aller Nutzer und auf Forte praktisch jeder auf einem eigenen Server ist, ist überhaupt nicht bekannt, wie die skalieren. Also, mal abgesehen vom Schluckauf, den die bestehenden bekannteren Nodes Anfang des Jahres hatten, als haufenweise Leute aus Facebook umgestiegen sind.

GoToSocial dürfte auch eine Riesenkapazität haben auf entsprechend leistungsfähigen Maschinen, gerade auch, weil es kein Web-Frontend hat. Da ist es nur eben so, daß eine Fediverse-Serveranwendung ohne Web-Frontend jetzt nicht unbedingt so attraktiv ist, auch wenn alle Welt mit Smartphone-Apps unterwegs ist.

CC: @Michael Blume

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #StatusNet #GNUsocial #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Akkoma #GoToSocial #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta

@crossgolf_rebel - kostenlose Kwalitätsposts Interessant ist der Punkt, wo Laconi.ca, also der Quellcode von Identi.ca, zu StatusNet wurde: Haufenweise Leute wollten ihre eigenen Microblogging-Server mit dieser Software fahren, stellten dann aber fest, daß sie damit völlig isoliert waren, weil die Server ja nicht miteinander kommunizierten. Das war der eigentliche Startschuß der Föderation, weil Evan an der Stelle erstmals ein Protokoll schrieb, mit dem solche Server miteinander interagieren konnten.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Identi.ca #Laconi.ca #StatusNet

The bang (!) version originated from Laconica later renamed to StatusNet and later became GNUsocial. It was the very first and original Fediverse software, way back in 2008. It was always meant for groups.

Mastodon® software is planning on adding groups too, and they probably will use bang (!) as well. Besides, it's the only logical reason.

The sharp/pound/hashtag (#) is for hashtags ever since hashtags were invented. While the atsam (@) is for user accounts that has been around since the 90s (afaik).

What looks like an "email" is called WebFinger. It is actually a webstandard (see: https://en.m.wikipedia.org/wiki/WebFinger ). Aside from email addresses and OpenID, the first social network [software] that used it was Laconica/StatusNet/GNUsocial in 2008 (the birth of the Fediverse).

Since Threadiverse software like Lemmy, Kbin, and Mbin were built for the Fediverse network, they're following the standards and established practices, instead of reinventing the wheel. If they were joining the Matrix network, they no doubt would follow the standards and practices in the Matrix network.

That's the answer to "why".

#Laconica #StatusNet #GNUsocial #Fediverse #Mastodon #WebFinger #Threadiverse #Lemmy #Kbin #Mbin