#iceshrimpnet — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #iceshrimpnet, aggregated by home.social.
-
As a reminder: I am offering free Iceshrimp.NET fediverse hosting on OP5+’s. Contact me for details.
-
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
@「 Jürgen 」:fedi_mastodon: @crossgolf_rebel - kostenlose Kwalitätsposts @Don di Dislessia Soweit ich weiß, war es so (man möge mich wiederum korrigieren; kursiv sind die "Forkeys höheren Grades", die nicht von Misskey geforkt wurden):- Misskey
Der Ursprung in Japan. - Calckey
Soft-Fork von Misskey mit einigen Extrafeatures.
Entwickler hatte irgendwann keine Zeit/keinen Bock mehr. - Firefish
Fortführung von Calckey unter neuem Management. Wurde aufgrund einer massiven Werbeaktion eines begeisterten Nutzers mit viel Reichweite so populär, daß der Name "Calckey" irgendwann einfach doof war und das ganze Ding eine neue Identität bekam.
Entwickler verschwand irgendwann sang- und klanglos von der Bildfläche. Nach einem halben Jahr stellte sich raus: Entwickler hatte wegen Abschlußarbeit usw. keine Zeit mehr, nicht mal, sich zu verabschieden.
Wurde unter neuer Führung mit neuem Repository und neuer Leuchtturminstanz weitergeführt, aber ohne neue Website. Wurde wieder eingestellt, weil es für eine einzige Entwicklerin viel zuviel war, die ganzen alten Co-Entwickler von Firefish alle zu Iceshrimp gewechselt waren und keine neuen Mitentwickler angeheuert werden konnten. - Iceshrimp
Fork von Firefish von ehemaligen Firefish-Entwicklern. Rebased nach Misskey, weil es auf Firefish nicht weiterging. Erklärtes Ziel war, Stabilität über Calckeys Featuritis zu stellen.
Weil Misskeys Codebase an sich einiges an grundsätzlichen Macken hatte, wurde beschlossen, es ist einfacher, das ganze Zeugs von Grund auf neu zu schreiben, als zu versuchen, das alles auszubügeln. Und bei der Gelegenheit wollte man von JavaScript (TypeScript und Vue.js) weg. Also hat man angefangen, das ganze Ding in C# neu zu schreiben als Iceshrimp.NET. Ziel ist featuremäßige Deckungsgleichheit mit dem bisherigen Iceshrimp und gleichzeitig Anpassung an Mastodon. Iceshrimp.NET ist noch sehr unfertig.
Bei der Gelegenheit wurde das alte Iceshrimp in Iceshrimp-JS umbenannt und in den Wartungsmodus versetzt = gibt keine Weiterentwicklung und keine neuen Features mehr, nur Sicherheitspatches und evtl. Bugfixes. - Catodon
Soft-Fork von Firefish. Ziel war, ein Forkey zu haben, das sich in der Bedienung wie Mastodon anfühlt. Quasi Mastodon-Fassade mit *key-Struktur dahinter. Also ein Forkey für den möglichst leichten Umstieg von Mastodon nach *key.
Wurde, als Firefish endgültig eingestellt wurde und damit die Basis tot war, nach Iceshrimp rebased.
Nachdem Iceshrimp zu Iceshrimp-JS wurde und in den Wartungsmodus ging, hatte Catodon ein Problem: Man kann nicht einfach von etwas, das in TypeScript und Vue.js geschrieben ist, nach etwas rebasen, das in C# geschrieben ist (Iceshrimp.NET). Und zur Weiterentwicklung wäre ein Rebase nötig gewesen, weil man jetzt wieder eine fast tote Basis hatte. Aber nach Misskey wollte man nicht (siehe Hajkey weiter unten), und Sharkey war einerseits zu mächtig und andererseits zu kapriziös.
Inzwischen gehen Catodon die Instanzen ein. Die meisten dürften geschlossen worden sein. - Sharkey
Soft-Fork von Misskey mit dem Ziel, so ziemlich alles, was je für Forkeys an Features entwickelt worden war, in einen einzigen Forkey zu packen und noch mehr obendrauf.
Quasi das Yang zu Iceshrimps Yin. Machte lange den Eindruck, als gingen Features über Zuverlässigkeit. Sharkeys Implementation der Mastodon Client API war schon regelrecht legendär schlecht, und alle hofften auf den Retter, der daherkommt und die Implementation von Grund auf neu schreibt, weil sie als unrettbar im Eimer galt. Inzwischen soll Sharkey seine Zuverlässigkeit im Griff haben, zumindest insofern, wie auch Misskey zuverlässig ist.
Die Entwickler haben eine zweifelhafte Reputation. Unter anderem haben sie Crowdfunding-Gelder für einen Sharkey-Server gesammelt und von dem Geld einen Minecraft-Server aufgezogen, aber keinen Sharkey-Server. Mitunter wird deshalb zum Boykott von Sharkey aufgerufen. - CherryPick
Südkoreanischer Soft-Fork von Misskey. Tatsächlich älter als Sharkey, mindestens von 2021, aber später wurde wohl einiges von Sharkey nach CherryPick portiert. Das Ziel war, einen stabilen und zuverlässigen Forkey zu haben ohne die Macken von Sharkey und sogar ohne die Macken von Misskey, der aber gleichzeitig gut Features hat. Das ist wohl sogar weitestgehend gelungen.
Vom ästhetischen Stil her so ähnlich, wie Misskey früher mal war, also sehr auf den japanischen bzw. südkoreanischen Geschmack ausgelegt: bunt, grell, poppig, genki, kawaii. Alleine das zeigt, daß CherryPick von Misskey geforkt wurde, bevor Misskey gänzlich an den westlichen Geschmack angepaßt wurde.
Unklar, ob es Entwickler hat, die Englisch verstehen bzw. schreiben können; falls nicht, dann als Soft-Fork-Basis ungeeignet. Wäre ohne die Kommunikationsbarriere vermutlich der ultimative *key.
Mein letzter Stand: Bis auf eine Instanz im Großraum Washington, D.C. gibt es CherryPick-Instanzen nur in den Großräumen Tokyo und Seoul. War deshalb lange Zeit im westlichen Fediverse fast unbekannt. - FoundKey
Wohl der erste Forkey, der in PascalCase geschrieben wurde.
Meines Wissens direkter Soft-Fork von Misskey. Wird tatsächlich (oh Wunder) kleckerweise gepflegt, aber nicht für Instanzen mit mehr als 20 Nutzern empfohlen.
Ein paar andere *keys:- Hajkey
Soft-Fork von Calckey, der meines Wissens erst nach Firefish und dann nach Misskey rebased wurde. Wurde exklusiv nur für eine einzige Instanz entwickelt: transfem.social. Inzwischen eingestellt, weil wohl der Aufwand, so einen Wolpertinger nur für eine Instanz zu pflegen (man rebaset nicht mal eben von Firefish nach Misskey), zu groß war. transfem.social wurde entsprechend auf Sharkey umgestellt und ist da jetzt eine der größten Instanzen. - Neko
Soft-Fork von Misskey mit dem Ziel, es tauglich für Docker zu machen. Laut Repository nur für eine einzige Instanz gebaut. Ist nie released worden, was aber Wurscht ist, wenn es eh nur einen Admin als Zielgruppe hatte.git fetchkönnen Releases nämlich piepegal sein. - Meisskey
Japanischer Soft-Fork von Misskey von 2019 (!), der aber lange Zeit der Weiterentwicklung der Basis hinterherhinkte. Wird tatsächlich immer noch weiterentwickelt. - Leisskey
Wiederum japanischer Soft-Fork von Meisskey. Ist seit mindestens 2021 in Entwicklung, seit Februar 2023 aber eine ewige Beta, weil es seit damals keinen Release mehr gegeben hat. Dürfte zu den letzten noch in Entwicklung befindlichen "Forkeys 2. Grades" gehören. - Tanukey
Weiterer japanischer Soft-Fork von Misskey und daher so obskur im Westen, daß man schon die Websuche anstrengen muß, um das Repository zu finden (ist wohl im letzten Oktober von GitHub nach GitLab umgezogen). Noch ein Beispiel für *keys, bei denen selbst das Wissen über ihre Existenz Ostasien kaum je verlassen hat. - Backspacekey
Noch ein ambitionierter, aber eingeschlafener westlicher Misskey-Soft-Fork.
Siehe übrigens auch die Delightful Fediverse Experience: hier und hier.
Verglichen damit ist die Familie von Mistpark bis Forte schon wieder übersichtlich, vor allem, wenn die anderen mehreren Dutzend toten Forkeys mit dazugeholt werden. Immerhin stammt von Mistpark bis Forte über etwa 15 Jahre alles vom selben Schöpfer, der einfach nur sein eigenes Zeug geforkt hat.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #IceshrimpJS #Iceshrimp.NET #Catodon #Sharkey #CherryPick #FoundKey #Hajkey #Neko #Meisskey #Leisskey #Tanukey #Backspacekey - Misskey
-
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
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 -
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
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 -
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
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 -
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
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 -
CW: Why Sharkey fails to render hashtags from Friendica, Hubzilla & Co. properly, and how long this bug has been known already; CW: long (over 6,600 characters), Fediverse meta, Fediverse-beyond-Mastodon meta
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 -
@tux0r :openbsd: "Forkey" bezeichnet Forks von Misskey, Forks von Forks von Misskey usw.
Iceshrimp.NET fällt da nicht drunter, weil es komplett neu geschrieben wird. Es ist vom Funktionsumfang her noch ziemlich mager. Das Ziel des Rewrite war, soweit ich weiß, zum einen, die Macken loszuwerden, die alle Forkeys von Misskey geerbt hatten, und zum anderen von JavaScript wegzukommen (Misskey und alle Forkeys sind in TypeScript und Vue.js geschrieben).
Aber gut, es gibt auch viele, die sich nicht vorstellen können, daß gute Serversoftware in PHP geschrieben sein kann. Mike Macgirvin entwickelt seit jeher in PHP. Und was er baut, ist nicht nur sehr mächtig und fortschrittlich, sondern auch noch leicht zu installieren und zu administrieren und weniger leistungshungrig als Mastodon.
Relatierter Memepost auf meinem Fediverse-Meme-Kanal.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Forkey #Forkeys #Iceshrimp.NET -
@Herr TurTur @crossgolf_rebel - kostenlose Kwalitätsposts @tux0r :openbsd: Die Idee hinter Sharkey war mal, in einen einzigen Forkey quasi alles auf einmal reinzuschmeißen bis hin zur Küchenspüle. Das fiel vor allem auf, als es noch mehr lebendige Forkeys zur Auswahl gab.
Und in der Zeit hatte Sharkey auch noch gewisse Macken, z. B. eine schon legendär unzuverlässige Implementation der Mastodon Client API, wo es hieß, am besten setzt sich einer hin und schreibt die neu. Wer was Zuverlässiges wollte, setzte damals auf Iceshrimp. Sharkey war für wagemutige Spielkinder, die sich an Hubzilla nicht rantrauten.
Inzwischen ist Calckey tot, Firefish ist tot, Iceshrimp-JS ist im Wartungsmodus (Iceshrimp.NET ist derweil noch meilenweit von "fertig" entfernt), Catodon ist auch schon siech, und das nur für eine Instanz gebaute Hajkey ist schon verwest.
CherryPick hat fast nur Server in den Großräumen Tokyo und Seoul und fühlt sich so auf den ostasiatischen Geschmack ausgelegt an wie vor ein paar Jahren noch Misskey selbst. Vielleicht erinnern sich ein paar noch daran, wie Misskey mal den Charme japanischer Verkaufsautomaten hatte.
Und der ganze noch lebende Rest scheint selbst mit Misskeys Entwicklung nicht mithalten zu können, also im Kern veraltet zu sein.
Derweil ist Sharkey wohl inzwischen ziemlich zuverlässig. So ist es zumindest im Westen zum einzigen noch nennenswerten Forkey avanciert.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #Sharkey #Calckey #Firefish #Iceshrimp #Iceshrimp-JS #Iceshrimp.NET #Catodon #Hajkey #CherryPick -
I really don't know what to do about this server. The development of #Firefish was abandoned last year. If I downgrade to an earlier version, I can then migrate to #IceShrimpJS and eventually #IceShrimpNet. I like this because then I could go back to using @[email protected] on my phone. I'm (reasonably) hesitant to rely on a smaller project again, though. I've got no qualms about setting up and using @[email protected] but starting from scratch would necessitate using a different subdomain.
Why do YOU think I should do? Is there a satisfactory option I've not considered?
#feditips #fedihelp #adviceneeded -
@Ben Pate 🤘🏻 Let's just say the only devs who need full identity portability are silverpill and you, and silverpill is actively working on it.
Then there are Mike, Mario Vavti and Harald Eilertsen who have full identity portability.
All the other devs don't seem to care.
As for the users, however... I guess if Mastodon 4.5 went fully nomadic on Forte's scale, people would kiss Gargron's feet because he'd deliver what they've been craving for for so long. For not exactly few of them, this would be what they've been wishing for for years plus cream and a cherry on top.
And if all the various *keys (at least those that are still maintained) went nomadic on a cross-server-type scale, that'd solve the problem with entire Forkeys going belly-up and leaving its users standing in the rain with unmaintained server software. I mean, I guess we all know how volatile Forkeys tend to be. Not only could people move around from server to server with ease and take everything with them, but they could also try out new Forkeys (this explicitly includes Iceshrimp.NET) and still have clones on longer-lived applications like Sharkey, CherryPick or good old Misskey itself as fallbacks.
In fact, I think one reason for Sharkey's popularity is its import/export capability.
CC: @Marcus Rohrmoser 🌻 @Johannes Ernst @Tim Chambers
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Misskey #Forkey #Forkeys #CherryPick #Sharkey #Iceshrimp #Iceshrimp.NET #NomadicIdentity -
@Chris Alemany🇺🇦🇨🇦🇪🇸 The Mastodon devs are talking as if either the Fediverse is only Mastodon, or the Fediverse as a whole doesn't have quote-posts.
Neither of this is true. The Fediverse has had quote-posts since July 2nd, 2010 when Mistpark (now known as Friendica) was launched. Mastodon toots have been quote-post-able since Mastodon itself was launched, for when Mastodon was launched, it immediately federated with at least two Fediverse server applications that have quote-posts, namely Friendica and Hubzilla, a fork of a fork of Friendica by Friendica's own creator.
Nowadays, at least Pleroma, Akkoma, all other Pleroma forks, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, CherryPick, Sharkey, all other Misskey forks, Mitra, Friendica, Hubzilla, (streams) and Forte can quote-post Mastodon toots with no problem.
And Mastodon won't be able to stop them. No, seriously, it won't. Not with a non-standard, proprietary, home-brew opt-in or opt-out switch that doesn't tie into anything that the other Fediverse server apps have. And whatever switch Mastodon is working on will not tie into anything that already exists.
Let me put it this way: Hubzilla has the second-most advanced and fine-grained permissions system in the Fediverse. It goes well beyond most people's imagination. It works on three levels: for the whole channel (that's similar to a Mastodon account), for individual contacts (that's "followers" in Mastodon lingo, but Hubzilla doesn't distinguish between followers and followed), for individual content. (streams) and Forte are the only ones with an even more advanced and fine-grained permissions system.
But even they don't have a quote-post permission setting. And they have permission settings for just about everything. You want reply control in the Fediverse? Hubzilla has reply control, and (streams) and Forte have reply control on steroids. But what they don't have is a quote-posting permission because that's next to impossible to control across the Fediverse even with the most advanced permissions system.
As @Mike Macgirvin ?️ (professional software developer for almost half a century, designer of two Fediverse protocols, creator of Friendica and Hubzilla, inventor of nomadic identity, creator and maintainer of (streams) and Forte) says: The only way to make your posts un-quote-post-able is by not posting in public and not allowing everyone in the Fediverse full access to your posts. Set your "Who can quote" however you want, I'll always be able to quote-post all your public posts with no problem and with no resistance.
So what chance does Mastodon have then? Mastodon which doesn't even know what permissions are? Developed by Eugen Rochko who actually has a history of head-butting with Mike Macgirvin, and who would never take any step towards anything that Mike has ever developed?
I'm commenting from Hubzilla right now, and I'm also on (streams). And I can tell you: If you make any of your posts "un-quote-post-able", this still won't make my Share buttons on Hubzilla and (streams) disappear.
CC: @Stefan Bohacek @FinchHaven sfba
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Iceshrimp.NET #CherryPick #Sharkey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotePostDebate #QuoteTootDebate -
With this release, Ivory now UNOFFICIALLY supports additional fediverse platforms such as GoToSocial, IceShrimp.NET. I've tried these platforms with mostly success.
The better the Mastodon API support on your platform, the better your experience will be. Obviously, platform specific features like emoji reacts or reply controls aren't going to be available. Still nice!
Edit: SNAC and Hollo work as well now!
-
IceShrimp.NET has a new beta release, and the front end UI is starting to catch up to the back end. Including everyone's favorite, MFM! (Well, maybe not everybody, but between instances with support, it sure is fun in moderation)
-
CW: The Fediverse has quote-posts right now, it can quote-post Mastodon toots with no problems, and no Mastodon switch will change that; CW: long (over 4,500 characters), Fediverse meta, Fediverse beyond Mastodon meta, quote-post meta
One of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts?
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace -
CW: The Fediverse has quote-posts right now, it can quote-post Mastodon toots with no problems, and no Mastodon switch will change that; CW: long (over 4,500 characters), Fediverse meta, Fediverse beyond Mastodon meta, quote-post meta
One of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts?
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace -
CW: The Fediverse has quote-posts right now, it can quote-post Mastodon toots with no problems, and no Mastodon switch will change that; CW: long (over 4,500 characters), Fediverse meta, Fediverse beyond Mastodon meta, quote-post meta
One of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts?
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace -
CW: The Fediverse has quote-posts right now, it can quote-post Mastodon toots with no problems, and no Mastodon switch will change that; CW: long (over 4,500 characters), Fediverse meta, Fediverse beyond Mastodon meta, quote-post meta
One of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts?
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace -
CW: The Fediverse has quote-posts right now, it can quote-post Mastodon toots with no problems, and no Mastodon switch will change that; CW: long (over 4,500 characters), Fediverse meta, Fediverse beyond Mastodon meta, quote-post meta
One of the worst aspects of Mastodon's plans to introduce quote-posts with a switch:
You keep having to tell Mastodon users that the Fediverse is not only Mastodon. That (insert a long list of Fediverse server applications here¹) have had quote-posts from the beginning. That they're all in the Fediverse. That they're all fully federated with Mastodon. That they can all quote-post any Mastodon toot they can possibly receive or import. And that they will be able to quote-post any Mastodon toot they can in the future, regardless of Mastodon account settings.
Up until this point, they were fully, firmly convinced that they're 100% safe from quote-posts on Mastodon. Either because they could not for the lives of them imagine that anything in the Fediverse has them. Or simply because they "knew" up until this point that the Fediverse is Mastodon. And if Mastodon introduces an opt-out or opt-in switch, this switch will mean absolute, 100% water-tight safety from quote-posts.
But for the Fediverse outside of Mastodon, the quote-post switch will be completely useless. Again: These lots of Fediverse server apps have had quote-posts before Mastodon introduced them. They had quote-posts before Mastodon invented the opt-in or opt-out switch. I mean, at least two of them have had quote-posts since before Mastodon even existed! So how are they supposed to support a proprietary, non-standard, Mastodon-specific switch which probably won't be documented anywhere before Mastodon rolls out quote-posts?
I'll tell you what'll happen.
Mastodon users will deactivate quote-posts for their accounts or not activate them in the first place. Non-Mastodon users, not knowing about the status of that switch, will quote-post them regardless with zero resistance. Upon which these Mastodon users will shit brix. And they'll call for either blocking that obviously rogue Mastodon user instance-wide, or blocking that user's instance, or Fediblocking that user's instance.
At this point, someone else who is not on Mastodon either will chime in and tell them: That particular user is, in fact, not on Mastodon. The Fediverse is not only Mastodon. That user is on Friendica. No, Friendica is not a rogue Mastodon instance. Friendica is not Mastodon at all. No, Friendica isn't a Mastodon fork either. Friendica has nothing to do with Mastodon. In fact, Friendica is older than Mastodon. On Friendica, quote-posts are perfectly normal. Friendica has had quote-posts for longer than Mastodon has even existed. And so forth.
Cue the Mastodon user shitting brix again, foaming with anger and calling for a Fediblock of all of Friendica.
In fact, I'm pretty sure that if Mastodon's quote-post feature and the rest of the Fediverse disregarding it leads to more awareness of the non-Mastodon Fediverse and its non-Mastodon features on Mastodon, it will also lead to demands for being able to completely block everything that isn't Mastodon, either on an account level (and then on by default, of course) or on an instance level or both.
Oh, by the way: The ability to completely lock out entire Fediverse projects already exists in the Fediverse right now, too. It's exclusive to two other Fediverse server apps that aren't Mastodon, both of which introduced this feature in September.
¹Here's a probably incomplete list of still-active Fediverse server apps with quote-posts which, yes, can quote-post Mastodon toots right now and will be able to quote-post Mastodon toots regardless of opt-in or opt-out:- Pleroma
- Akkoma
- Misskey
- Firefish
- Sharkey
- Iceshrimp
- Iceshrimp.NET
- CherryPick
- Neko
- Catodon
- Meisskey
- Tanukey
- Metaskey
- Mitra
- Friendica
- Hubzilla
- (streams)
- Forte
(Inb4 both Oliphant and The Bad Space trying hard to catch all instances of the server apps mentioned above to blocklist them all.)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Mastodon #Pleroma #Akkoma #Misskey #Calckey #Firefish #Sharkey #Iceshrimp #Iceshrimp.NET #CherryPick #Neko #Catodon #Meisskey #Tanukey #Metaskey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #Threads #BridgyFed #Bluesky #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #FediblockMeta #Oliphant #TheBadSpace -
Found 49 new servers and 39 servers died off since 7 hours ago.
22,771 servers checked. 16,274,408 Total Users with 1,067,282 Active Users today. Check out the stats!
New #fediverse servers found:
frends-0.kade.jp a #mastodon server from Private
vernissage.photos a #vernissage server from United States
triptych.oxus.net a #ghost server from Private
ohitori.hatachanoima.net a #misskey server from Private
arcano.altervista.org a #wordpress server from Germany
vsh.ngrok.dev a #wellesley server from United States
srnovus.fedired.com a #mastodon server from Private
autist.top a #pleroma server from United States
gotosocial.cloud.claudelup.in a #gotosocial server from France
social.1hz.su a #gotosocial server from Russia
snac2.popolon.org a #snac server from France
fdk.goulag.fr a #gotosocial server from Spain
mastodon.grumpfff.fr a #mastodon server from France
caos.social a #gotosocial server from United States
swag.beazone.net a #mastodon server from France
boubs.xyz a #wordpress server from United States
pupu.cafe a #gotosocial server from Private
collectivepower.net a #wordpress server from The Netherlands
fedivers.marcjestin.me a #wordpress server from France
modlabs.social a #mastodon server from Private
verity.cafe a #akkoma server from United States
masto.badger-tailor.ts.net a #mastodon server from United Kingdom
sora-sns.net a #misskey server from Japan
www.reflab.ch a #wordpress server from Belgium
tube.hapyyr.com a #peertube server from Finland
haunted.locker a #gotosocial server from Private
zacheverson.com a #wordpress server from United States
social.sc-sudo.de a #mastodon server from Germany
otsuka.social a #gotosocial server from United States
toot.now a #gotosocial server from Private
frei.social a #mastodon server from Germany
loops.video a #loops server from Private
schafweide.eu a #mastodon server from Germany
test-production.ghost.io a #ghost server from United States
mastodon.jrvs.cc a #mastodon server from The Netherlands
social.deltayeet.net a #mastodon server from United States
johnson.am a #mastodon server from Portugal
pythag.net a #piefed server from United Kingdom
agenda.rouen-luttes.org a #gancio server from France
free.epic-toolbars.download a #iceshrimpnet server from The Netherlands
live.grat.gay a #owncast server from Germany
fedi.goobleschmert.cc a #akkoma server from Germany
misskey.lilalm.site a #misskey server from Private
cool.epic-toolbars.download a #pleroma server from The Netherlands
pixel.pimmsiki.com a #pixelfed server from United Kingdom
social.id1.in a #gotosocial server from United States
arduino.uno a #mitra server from United States
fedi.pregnant.horse a #akkoma server from Private
social.t2arc.net a #mitra server from JapanHelp others find a home, send them to fediverse.observer
-
Found 45 new servers and 28 servers died off since 7 hours ago.
22,779 servers checked. 16,274,408 Total Users with 1,067,282 Active Users today. Check out the stats!
New #fediverse servers found:
arcano.altervista.org a #wordpress server from Germany
vsh.ngrok.dev a #wellesley server from United States
srnovus.fedired.com a #mastodon server from Private
autist.top a #pleroma server from United States
gotosocial.cloud.claudelup.in a #gotosocial server from France
social.1hz.su a #gotosocial server from Russia
fdk.goulag.fr a #gotosocial server from Spain
snac2.popolon.org a #snac server from France
caos.social a #gotosocial server from United States
swag.beazone.net a #mastodon server from France
mastodon.grumpfff.fr a #mastodon server from France
pupu.cafe a #gotosocial server from Private
boubs.xyz a #wordpress server from United States
collectivepower.net a #wordpress server from The Netherlands
modlabs.social a #mastodon server from Private
fedivers.marcjestin.me a #wordpress server from France
verity.cafe a #akkoma server from United States
masto.badger-tailor.ts.net a #mastodon server from United Kingdom
sora-sns.net a #misskey server from Japan
www.reflab.ch a #wordpress server from Belgium
tube.hapyyr.com a #peertube server from Finland
haunted.locker a #gotosocial server from Private
zacheverson.com a #wordpress server from United States
social.sc-sudo.de a #mastodon server from Germany
otsuka.social a #gotosocial server from United States
toot.now a #gotosocial server from Private
frei.social a #mastodon server from Germany
loops.video a #loops server from Private
schafweide.eu a #mastodon server from Germany
test-production.ghost.io a #ghost server from United States
mastodon.jrvs.cc a #mastodon server from The Netherlands
social.deltayeet.net a #mastodon server from United States
johnson.am a #mastodon server from Portugal
fedi.goobleschmert.cc a #akkoma server from Germany
agenda.rouen-luttes.org a #gancio server from France
live.grat.gay a #owncast server from Germany
pythag.net a #piefed server from United Kingdom
free.epic-toolbars.download a #iceshrimpnet server from The Netherlands
misskey.lilalm.site a #misskey server from Private
pixel.pimmsiki.com a #pixelfed server from United Kingdom
cool.epic-toolbars.download a #pleroma server from The Netherlands
arduino.uno a #mitra server from United States
social.id1.in a #gotosocial server from United States
fedi.pregnant.horse a #akkoma server from Private
social.t2arc.net a #mitra server from JapanHelp others find a home, send them to fediverse.observer
-
Found 26 new servers and 38 servers died off since 7 hours ago.
22,796 servers checked. 14,542,455 Total Users with 1,089,093 Active Users today. Check out the stats!
New #fediverse servers found:
riegai.com a #wordpress server from Private
yellbot.online a #yellbot server from United States
wara.lol a #misskey server from Japan
say.lfh.lat a #gotosocial server from Hong Kong
rusoc.site a #gotosocial server from Russia
fedi.jonatkinson.co.uk a #mastodon server from United Kingdom
labyss.online a #mastodon server from South Korea
friendica.youthweb.net a #friendica server from Germany
tripletwenty.net a #wordpress server from Germany
gts.drowsik.party a #gotosocial server from Germany
rojavainformationcenter.org a #wordpress server from Private
m.wangwenzhi.online a #misskey server from Private
ykaerne-podcast.de a #wordpress server from Germany
nosaltres.cantonada.casa a #mastodon server from Germany
campfire.whereismytribe.net a #microblogpub server from Singapore
mastodon.hdiag.de a #mastodon server from Germany
social.appbakery.ee a #mastodon server from Private
mastodon.voege.net a #mastodon server from United States
kazuskey.kazuiton.com a #misskey server from Private
mky.pns2017.xyz a #misskey server from Private
timtrautmann.online a #mastodon server from Portugal
savvyselections.blog a #wordpress server from United States
misskey.lqhost.com a #misskey server from Japan
sharkey1.testing.synth.download a #sharkey server from Germany
brejo.us a #mastodon server from Canada
beeping.synth.download a #iceshrimpnet server from GermanyHelp others find a home, send them to fediverse.observer
-
Found 23 new servers and 34 servers died off since 7 hours ago.
22,794 servers checked. 14,542,455 Total Users with 1,089,093 Active Users today. Check out the stats!
New #fediverse servers found:
rusoc.site a #gotosocial server from Russia
fedi.jonatkinson.co.uk a #mastodon server from United Kingdom
say.lfh.lat a #gotosocial server from Hong Kong
labyss.online a #mastodon server from South Korea
friendica.youthweb.net a #friendica server from Germany
tripletwenty.net a #wordpress server from Germany
gts.drowsik.party a #gotosocial server from Germany
rojavainformationcenter.org a #wordpress server from Private
m.wangwenzhi.online a #misskey server from Private
ykaerne-podcast.de a #wordpress server from Germany
nosaltres.cantonada.casa a #mastodon server from Germany
campfire.whereismytribe.net a #microblogpub server from Singapore
mastodon.hdiag.de a #mastodon server from Germany
social.appbakery.ee a #mastodon server from Private
mastodon.voege.net a #mastodon server from United States
kazuskey.kazuiton.com a #misskey server from Private
mky.pns2017.xyz a #misskey server from Private
timtrautmann.online a #mastodon server from Portugal
savvyselections.blog a #wordpress server from United States
misskey.lqhost.com a #misskey server from Japan
sharkey1.testing.synth.download a #sharkey server from Germany
brejo.us a #mastodon server from Canada
beeping.synth.download a #iceshrimpnet server from GermanyHelp others find a home, send them to fediverse.observer
-
Found 15 new servers and 20 servers died off since 7 hours ago.
22,802 servers checked. 14,542,455 Total Users with 1,089,093 Active Users today. Check out the stats!
New #fediverse servers found:
m.wangwenzhi.online a #misskey server from Private
ykaerne-podcast.de a #wordpress server from Germany
nosaltres.cantonada.casa a #mastodon server from Germany
mastodon.hdiag.de a #mastodon server from Germany
campfire.whereismytribe.net a #microblogpub server from Singapore
mastodon.voege.net a #mastodon server from United States
social.appbakery.ee a #mastodon server from Private
kazuskey.kazuiton.com a #misskey server from Private
mky.pns2017.xyz a #misskey server from Private
timtrautmann.online a #mastodon server from Portugal
misskey.lqhost.com a #misskey server from Japan
savvyselections.blog a #wordpress server from United States
sharkey1.testing.synth.download a #sharkey server from Germany
brejo.us a #mastodon server from Canada
beeping.synth.download a #iceshrimpnet server from GermanyHelp others find a home, send them to fediverse.observer
-
Found 32 new servers and 22 servers died off since 7 hours ago.
22,870 servers checked. 13,842,518 Total Users with 1,030,274 Active Users today. Check out the stats!
New #fediverse servers found:
try.hamabe.space a #hamabe server from Germany
login.ready.pics a #iceshrimpnet server from United States
shark.datenkastl.de a #sharkey server from Austria
staging.joinsharkey.org a #sharkey server from United States
ahermitforhire.net a #wordpress server from United States
universodosparques.com.br a #wordpress server from Private
simplesocialnetwork.org a #simple social network server from Private
pixelfed.slothlife.xyz a #pixelfed server from United Kingdom
sociale.hapa.cd a #mastodon server from France
peertube.dubwise.dk a #peertube server from Austria
paimian.cn a #misskey server from Singapore
hexanext.tech a #mastodon server from New Zealand
social.tatakaibo.xyz a #mastodon server from United Kingdom
journal.phoenixharbor.net a #mastodon server from Germany
jevans.bio a #writefreely server from United States
bsmw.email a #wordpress server from United States
cha.rlesthom.as a #wordpress server from United States
frexitnow.com a #mastodon server from Germany
masto.plaindrops.de a #mastodon server from United Kingdom
spinelessnews.com a #wordpress server from United Kingdom
blog.classstruggle.tech a #writefreely server from United States
mastodon.benoit.jp.net a #mastodon server from Japan
msftnewsnow.com a #wordpress server from United States
smothesfoto.de a #wordpress server from Germany
gts.burning.homes a #gotosocial server from France
bknovel.icu a #misskey server from United States
mastodon.brycedixon.dev a #mastodon server from United States
mstdn.7snowrin.net a #mastodon server from Japan
ds.2000.moe a #diaspora server from United States
sharkey.scorpios.uk a #sharkey server from Private
stg-don.nzws.me a #mastodon server from Private
dissident.social a #mastodon server from PortugalHelp others find a home, send them to fediverse.observer
-
Found 35 new servers and 25 servers died off since 7 hours ago.
22,863 servers checked. 13,871,560 Total Users with 1,035,081 Active Users today. Check out the stats!
New #fediverse servers found:
masto.snoozetown.org a #mastodon server from United Kingdom
ice.yumeka.xyz a #iceshrimpnet server from Private
login.ready.social a #iceshrimpnet server from United States
social.cthuflu.com a #mastodon server from United States
pleroma.fumo.pictures a #pleroma server from Hungary
pixelfed.abhd.fr a #pixelfed server from France
www.right-hands.com a #wordpress server from Japan
digitalmediacookbook.com a #wordpress server from United States
social.guist.at a #mastodon server from Germany
pixel.tacty.org a #pixelfed server from Germany
fed.mingetinnef.de a #gotosocial server from Germany
kunsthandwerk.social a #mastodon server from Germany
mastodon.laranjeira.fr a #mastodon server from France
bobmcdonaldwrites.com a #wordpress server from United States
glowfriend.club a #pleroma server from United States
whatarethese.xyz a #mastodon server from United States
jamesgiroux.ca a #wordpress server from Private
eme.blog.br a #writefreely server from United States
myoyeon.com a #wordpress server from United States
old.chipsandcheese.com a #wordpress server from Private
jeherve.jurassic.tube a #wordpress server from United States
w.ms.vg a #writefreely server from Germany
www.tojio.com a #drupal server from Germany
lexpostma.me a #wordpress server from Private
mini.log.br a #sharkey server from
m.verbum.cc a #mastodon server from United Kingdom
dllk.de a #mastodon server from Private
jon.henshaw.blog a #wordpress server from United States
fed.gdn a #mastodon server from United States
radio.sutty.nl a #suttydistributedpress server from Canada
iceflower.social a #mastodon server from Portugal
mi.misomayo.info a #misskey server from Japan
jpilier.people.aws.dev a #mastodon server from United States
kiki-velzie-rip.translate.goog a #kiki server from United States
lampy.casa a #microblogpub server from The NetherlandsHelp others find a home, send them to fediverse.observer
-
Found 33 new servers and 15 servers died off since 7 hours ago.
22,871 servers checked. 13,871,560 Total Users with 1,035,081 Active Users today. Check out the stats!
New #fediverse servers found:
login.ready.social a #iceshrimpnet server from United States
social.cthuflu.com a #mastodon server from United States
pleroma.fumo.pictures a #pleroma server from Hungary
pixelfed.abhd.fr a #pixelfed server from France
www.right-hands.com a #wordpress server from Japan
digitalmediacookbook.com a #wordpress server from United States
fed.mingetinnef.de a #gotosocial server from Germany
pixel.tacty.org a #pixelfed server from Germany
social.guist.at a #mastodon server from Germany
bobmcdonaldwrites.com a #wordpress server from United States
mastodon.laranjeira.fr a #mastodon server from France
kunsthandwerk.social a #mastodon server from Germany
whatarethese.xyz a #mastodon server from United States
jamesgiroux.ca a #wordpress server from Private
glowfriend.club a #pleroma server from United States
eme.blog.br a #writefreely server from United States
old.chipsandcheese.com a #wordpress server from Private
myoyeon.com a #wordpress server from United States
jeherve.jurassic.tube a #wordpress server from United States
www.tojio.com a #drupal server from Germany
w.ms.vg a #writefreely server from Germany
lexpostma.me a #wordpress server from Private
mini.log.br a #misskey server from Private
m.verbum.cc a #mastodon server from United Kingdom
fed.gdn a #mastodon server from United States
dllk.de a #mastodon server from Private
radio.sutty.nl a #suttydistributedpress server from United States
jon.henshaw.blog a #wordpress server from United States
iceflower.social a #mastodon server from Portugal
mi.misomayo.info a #misskey server from Japan
jpilier.people.aws.dev a #mastodon server from United States
kiki-velzie-rip.translate.goog a #kiki server from United States
lampy.casa a #microblogpub server from The NetherlandsHelp others find a home, send them to fediverse.observer
-
Found 78 new servers and 27 servers died off since 3 hours ago.
22,872 servers checked. 13,966,128 Total Users with 1,043,098 Active Users today. Check out the stats!
New #fediverse servers found:
social.jtalk.ru a #mastodon server from Russia
gts.flauschbereich.de a #gotosocial server from Germany
books.egalwaat.lu a #bookwyrm server from Luxembourg
tube.garrett.life a #peertube server from United States
fed.interfree.ca a #iceshrimpnet server from Canada
feds.praxor.wtf a #gotosocial server from Russia
pixelfed.librehki.eus a #pixelfed server from France
fedi.neurario.com a #iceshrimp server from Australia
high-school.band a #mastodon server from Private
social.chrisbd.online a #mastodon server from France
social.undersea.org.uk a #mastodon server from France
leszackardises.com a #wordpress server from United States
soc.kazachstan.biz a #pleroma server from The Netherlands
www.dailynewsglobal24.com a #wordpress server from United States
social.particle-summary.pt a #mastodon server from Germany
g2s.jyrgi.de a #gotosocial server from Germany
social.kloen-cafe.de a #mastodon server from France
app.southampton.social a #sharkey server from United States
kiel.collabfc.com a #pleroma server from Private
stpauli.collabfc.com a #pleroma server from Private
bochum.collabfc.com a #pleroma server from Private
mainz.collabfc.com a #pleroma server from Private
hoffenheim.collabfc.com a #pleroma server from Private
gladbach.collabfc.com a #pleroma server from Private
wolfsburg.collabfc.com a #pleroma server from Private
augsburg.collabfc.com a #pleroma server from Private
stuttgart.collabfc.com a #pleroma server from Private
union.collabfc.com a #pleroma server from Private
werder.collabfc.com a #pleroma server from Private
freiburg.collabfc.com a #pleroma server from Private
frankfurt.collabfc.com a #pleroma server from Private
leverkusen.collabfc.com a #pleroma server from Private
heidenheim.collabfc.com a #pleroma server from Private
leipzig.collabfc.com a #pleroma server from Private
dortmund.collabfc.com a #pleroma server from Private
bayern.collabfc.com a #pleroma server from Private
napoli.collabfc.com a #pleroma server from Private
torino.collabfc.com a #pleroma server from Private
fiorentina.collabfc.com a #pleroma server from Private
lazio.collabfc.com a #pleroma server from Private
roma.collabfc.com a #pleroma server from Private
bologna.collabfc.com a #pleroma server from Private
atalanta.collabfc.com a #pleroma server from Private
juventus.collabfc.com a #pleroma server from Private
milan.collabfc.com a #pleroma server from Private
inter.collabfc.com a #pleroma server from Private
girona.collabfc.com a #pleroma server from Private
mallorca.collabfc.com a #pleroma server from Private
osasuna.collabfc.com a #pleroma server from Private
realbetis.collabfc.com a #pleroma server from Private
villarreal.collabfc.com a #pleroma server from Private
realsociedad.collabfc.com a #pleroma server from Private
athleticbilbao.collabfc.com a #pleroma server from Private
atleticomadrid.collabfc.com a #pleroma server from Private
realmadrid.collabfc.com a #pleroma server from Private
barcelona.collabfc.com a #pleroma server from Private
lorient.collabfc.com a #pleroma server from Private
nice.collabfc.com a #pleroma server from Private
clermont.collabfc.com a #pleroma server from Private
lyon.collabfc.com a #pleroma server from Private
monaco.collabfc.com a #pleroma server from Private
lille.collabfc.com a #pleroma server from Private
marseille.collabfc.com a #pleroma server from Private
lens.collabfc.com a #pleroma server from Private
psg.collabfc.com a #pleroma server from Private
vitesse.collabfc.com a #pleroma server from Private
rkc.collabfc.com a #pleroma server from Private
heerenveen.collabfc.com a #pleroma server from Private
utrecht.collabfc.com a #pleroma server from Private
sparta.collabfc.com a #pleroma server from Private
twente.collabfc.com a #pleroma server from Private
az.collabfc.com a #pleroma server from Private
ajax.collabfc.com a #pleroma server from Private
psv.collabfc.com a #pleroma server from Private
feyenoord.collabfc.com a #pleroma server from Private
miuchusen.xsns.jp a #misskey server from Japan
gts.plexwave.org a #gotosocial server from United States
mypod.store a #activitypods server from GermanyHelp others find a home, send them to fediverse.observer
-
Found 39 new servers and 28 servers died off since 3 hours ago.
22,811 servers checked. 13,725,374 Total Users with 1,054,054 Active Users today. Check out the stats!
New #fediverse servers found:
kropotk.in a #snac server from Sweden
video.pizza.ynh.fr a #peertube server from France
peertube.qontinuum.space a #peertube server from Monaco
social.tuluz.fr a #mastodon server from France
is.notfire.cc a #iceshrimp.net server from Private
benihistudio.art a #wordpress server from Japan
incise.app a #incise server from United States
is.phite.ro a #iceshrimp server from Romania
videos.buzzkill.pw a #peertube server from United States
social.tdback.net a #gotosocial server from United States
www.salomoun.cz a #wordpress server from Czechia
paolo.blog a #wordpress server from United States
oarsman.de a #wordpress server from Germany
mastodon.buck5060.tw a #mastodon server from Taiwan
mastodon.iceman.synology.me a #mastodon server from Austria
photos.pepicrft.me a #pixelfed server from Germany
喵喵.testing.meow.enterprises a #gotosocial server from Germany
aribaud.net a #wordpress server from France
bassbook.social a #pleroma server from Germany
snac14.karebu.gay a #snac server from United States
myvideo.express a #wordpress server from United States
snac2.karebu.gay a #snac server from United States
snac16.karebu.gay a #snac server from United States
snac13.karebu.gay a #snac server from United States
snac11.karebu.gay a #snac server from United States
snac4.karebu.gay a #snac server from United States
fediworld.social a #mastodon server from United States
snac5.karebu.gay a #snac server from United States
snac6.karebu.gay a #snac server from United States
snac18.karebu.gay a #snac server from United States
snac3.karebu.gay a #snac server from United States
mastodon.jmsquared.net a #mastodon server from United States
misskey.mumeinosato.com a #misskey server from Private
mk.karebu.gay a #misskey server from United States
fedisocial.xyz a #pleroma server from Private
reforms.org a #hubzilla server from United States
brioco.online a #friendica server from United States
thepeakdream.com a #wordpress server from United States
fedi.fabrykajabo.li a #iceshrimp server from GermanyHelp others find a home, send them to fediverse.observer
-
Found 30 new servers and 27 servers died off since 3 hours ago.
22,803 servers checked. 13,745,090 Total Users with 1,055,813 Active Users today. Check out the stats!
New #fediverse servers found:
chookhouse.au a #friendica server from Australia
social.sudovanilla.org a #iceshrimp server from United States
fullgravity.nylarea.com a #pleroma server from Spain
lemmy.riebe.cloud a #lemmy server from Private
f.azumanga.gay a #iceshrimp.net server from United States
social.poketube.fun a #iceshrimp server from United States
probrewer.com a #wordpress server from United States
www.polotecnologicoimperiese.it a #wordpress server from Italy
asha-varadhi.com a #wordpress server from Germany
nanasina.com a #wordpress server from Japan
social.medienzentrum-hdh.de a #mastodon server from Germany
friend.bugs.se a #friendica server from Germany
woolwich1886.com a #wordpress server from United States
queeruferlos.de a #wordpress server from Germany
solucoesdigitais.mapas.tec.br a #wordpress server from United States
floramacabre.com a #wordpress server from Private
moyu.masto.host a #mastodon server from France
partswithpresley.com a #wordpress server from Canada
drinkinthemovies.com a #wordpress server from United States
misskey.gf4.pw a #misskey server from United States
hz.cats-home.net a #hubzilla server from Russia
pod.truefans.social a #truefans server from Private
kanye.aiwnios.com a #pleroma server from Japan
fedired.com a #mastodon server from Private
m.pizza.ynh.fr a #mastodon server from France
qurquma.it a #misskey server from United States
masto.challener.net a #mastodon server from France
markwrites.io a #writefreely server from United States
www.fabioag.it a #wordpress server from Italy
twt.johnpanos.com a #mastodon server from PrivateHelp others find a home, send them to fediverse.observer
-
@Stefan Bohacek
Also worth mentioning that quote boosts, which have also recently received funding, will include work on privacy and safety features around them, possibly extending to other areas of the online experience.
These "privacy and safety features" are non-sense.
They're proprietary, they're non-standard, they're Mastodon-specific. And they are expected to work only by respecting a proprietary, non-standard, Mastodon-specific quote-post permission flag which probably won't even be documented anywhere except Mastodon's server code.
The opt-out feature will only work within a 100% Mastodon bubble and even that only if no non-Mastodon user finds content from within this bubble by searching mastodon.social for hashtags.
Mastodon is selling its whole quote-post feature as a total revolution, as the very introduction of quote-posts to the Fediverse. And it will work. I've once run a poll on whether the Fediverse has quote-posts. 71% of all voters thought the Fediverse does not have quote-posts right now. And that was in my bubble which, in comparison to Mastodon in general, is fairly Fediverse-savvy and full of non-Mastodon users.
But as a matter of fact, the Fediverse does have quote-posts right now! Almost everything that can do microblogging in a way has quote-posts.
Pleroma has quote-posts.
Akkoma has quote-posts.
Misskey has quote-posts.
Firefish has quote-posts.
Iceshrimp has quote-posts.
Iceshrimp.NET has quote-posts.
Sharkey has quote-posts.
Catodon has quote-posts.
Friendica has quote-posts.
Hubzilla has quote-posts.
(streams) has quote-posts.
And so forth.
They haven't introduced quote-posts to spite Mastodon. Some of them have had quote-posts since before Mastodon even existed. Friendica, for example, was created with quote-posts available, and that was five and a half years before Mastodon was created. For as long as Mastodon has existed, Friendica could quote-post Mastodon toots. And so could Hubzilla, created ten months before Mastodon.
In fact, all of the above can quote-post any Mastodon toot right now, with no problems, with zero resistance.
Guess what'll change when Mastodon introduces quote-posts plus the opt-in switch.
Well, Mastodon will be able to quote-post. Mastodon might be able to display quote-posts from outside properly, but probably not because it's ignoring that the rest of the Fediverse can quote-post.
But the rest of the Fediverse will still be able to quote-post just about all Mastodon toots. With no problems. With zero resistance. Even with the opt-in switched to off.
Because that switch is proprietary, non-standard and Mastodon-specific. Because only Mastodon even supports it.
This switch will cause many many more Mastodon users to learn the hard way that the Fediverse is more than Mastodon. Namely by encountering a post or comment from something that does not behave like Mastodon. And many many more Mastodon users will shit bricks in sheer terror upon this revelation.
If Mastodon really wanted this switch to be 100% waterproof, it would have to implement the feature request in its entirety. That includes defederation from all Fediverse instances that don't respect the opt-in switch.
Mind you, the defederation clause and the entire feature request came from someone in the firm belief that the Fediverse is Mastodon, only Mastodon and nothing but Mastodon. Just like about every other Mastodon user out there. So it was only targetted at rogue Mastodon instances with hacked source code.
In reality, however, it would require entire non-Mastodon Fediverse projects to be Fediblocked because they can quote-post without respecting Mastodon's quote-post opt-in switch.
All instances of Pleroma, of Akkoma, of Misskey, of Firefish, of Iceshrimp including Iceshrimp.NET, of Sharkey, of Catodon, of Friendica, of Hubzilla, of (streams) and so forth would have to be Fediblocked because they can quote-post without respecting Mastodon's quote-post opt-in switch. Every last one of them.
Mastodon's quote-post feature will either cause a rift through the Fediverse if this rule is put into action or even more people to shit bricks in terror and escape to Bluesky if it isn't.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Fedisplaining #CWFedisplaining #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Iceshrimp.NET #Sharkey #Catodon #Friendica #Hubzilla #Streams #(streams) #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #FediblockMeta -
Found 62 new servers and 24 servers died off since 3 hours ago.
22,778 servers checked. 13,720,891 Total Users with 1,051,008 Active Users today. Check out the stats!
New #fediverse servers found:
write.pouet.it a #writefreely server from Germany
santacruz.photos a #pixelfed server from United States
acties.todon.nl a #gancio server from The Netherlands
mastodon.kurau.tokyo a #mastodon server from Germany
gts.foggymtndrifter.com a #gotosocial server from Private
themes.69.mu a #writefreely server from France
rad.talesofmy.life a #iceshrimp server from United States
ice.kugetsu.blog a #iceshrimp.net server from Japan
videa.inspirujici.cz a #peertube server from Germany
herebox.org a #wordpress server from Private
mondary.design a #wordpress server from France
mcschluberson.com a #wordpress server from United States
geniemedius.com a #wordpress server from United States
alexvielmav.com a #wordpress server from United States
social.gwsberlin.de a #mastodon server from Germany
exploreviews.online a #wordpress server from Private
deskinvestor.com a #wordpress server from United States
live.theindiebeat.fm a #owncast server from Finland
destabled.xyz a #mastodon server from Private
jixifox.me a #wordpress server from United States
nerdinfekt.de a #wordpress server from Germany
remimarenco.com a #wordpress server from United States
gatherpress.org a #wordpress server from Private
hikercarl.com a #wordpress server from United States
feminegra.com a #wordpress server from United States
smart7line.net a #wordpress server from United States
arges-stiri.ro a #wordpress server from Romania
thepanvelite.com a #wordpress server from United States
citizenspoint.com a #wordpress server from United States
bobonbooks.com a #wordpress server from United States
cmrosens.com a #wordpress server from United States
coot.vabl.dev a #takahe server from Private
funime.de a #wordpress server from Germany
tldr.pramari.de a #gotosocial server from Germany
svenruppert.com a #wordpress server from United States
trendblogz.com a #wordpress server from United States
christianpure.com a #wordpress server from United States
www.kamikazeanimated.com a #wordpress server from United States
tscnewschannel.com a #wordpress server from United States
samupress.ca a #wordpress server from United States
theandressegovia.com a #wordpress server from United States
rollingstonesdata.com a #wordpress server from United States
mastodon.cixoelectronic.pl a #mastodon server from Poland
blog.igv.com a #wordpress server from Private
greenvillager.com a #wordpress server from United States
ortetesekusoccerinfo.co.uk a #wordpress server from United States
pleasethepalate.com a #wordpress server from United States
dailyazerbaijan.com a #wordpress server from United States
mariaisquixotic.com a #wordpress server from United States
weston.ruter.net a #wordpress server from United States
peopletalky.com a #wordpress server from United States
www.lancescurv.com a #wordpress server from Private
rsoemardja.com a #wordpress server from United States
www.nerdandtie.com a #wordpress server from United States
daviemactile.com a #wordpress server from United States
chipsandcheese.com a #wordpress server from Private
doctor-multiverse.com a #wordpress server from United States
md.ghostnoise.ru a #mastodon server from Russia
events.ijug.eu a #mobilizon server from Germany
speacqua.net a #misskey server from Japan
snowfinch.zone a #mastodon server from Germany
guelph.social a #mastodon server from PortugalHelp others find a home, send them to fediverse.observer
-
Found 60 new servers and 23 servers died off since 3 hours ago.
22,780 servers checked. 13,720,891 Total Users with 1,051,008 Active Users today. Check out the stats!
New #fediverse servers found:
acties.todon.nl a #gancio server from The Netherlands
mastodon.kurau.tokyo a #mastodon server from Germany
gts.foggymtndrifter.com a #gotosocial server from Private
themes.69.mu a #writefreely server from France
rad.talesofmy.life a #iceshrimp server from United States
ice.kugetsu.blog a #iceshrimp.net server from Japan
videa.inspirujici.cz a #peertube server from Germany
herebox.org a #wordpress server from Private
mondary.design a #wordpress server from France
mcschluberson.com a #wordpress server from United States
alexvielmav.com a #wordpress server from United States
geniemedius.com a #wordpress server from United States
social.gwsberlin.de a #mastodon server from Germany
exploreviews.online a #wordpress server from Private
deskinvestor.com a #wordpress server from United States
arges-stiri.ro a #wordpress server from Romania
thepanvelite.com a #wordpress server from United States
smart7line.net a #wordpress server from United States
feminegra.com a #wordpress server from United States
remimarenco.com a #wordpress server from United States
cmrosens.com a #wordpress server from United States
hikercarl.com a #wordpress server from United States
bobonbooks.com a #wordpress server from United States
citizenspoint.com a #wordpress server from United States
destabled.xyz a #mastodon server from Private
nerdinfekt.de a #wordpress server from Germany
live.theindiebeat.fm a #owncast server from Finland
jixifox.me a #wordpress server from United States
funime.de a #wordpress server from Germany
coot.vabl.dev a #takahe server from Private
gatherpress.org a #wordpress server from Private
tldr.pramari.de a #gotosocial server from Germany
svenruppert.com a #wordpress server from United States
theandressegovia.com a #wordpress server from United States
trendblogz.com a #wordpress server from United States
mastodon.cixoelectronic.pl a #mastodon server from Poland
www.kamikazeanimated.com a #wordpress server from United States
tscnewschannel.com a #wordpress server from United States
samupress.ca a #wordpress server from United States
christianpure.com a #wordpress server from United States
blog.igv.com a #wordpress server from Private
rollingstonesdata.com a #wordpress server from United States
pleasethepalate.com a #wordpress server from United States
mariaisquixotic.com a #wordpress server from United States
dailyazerbaijan.com a #wordpress server from United States
daviemactile.com a #wordpress server from United States
ortetesekusoccerinfo.co.uk a #wordpress server from United States
www.lancescurv.com a #wordpress server from Private
www.nerdandtie.com a #wordpress server from United States
weston.ruter.net a #wordpress server from United States
greenvillager.com a #wordpress server from United States
peopletalky.com a #wordpress server from United States
rsoemardja.com a #wordpress server from United States
doctor-multiverse.com a #wordpress server from United States
chipsandcheese.com a #wordpress server from Private
md.ghostnoise.ru a #mastodon server from Russia
events.ijug.eu a #mobilizon server from Germany
speacqua.net a #misskey server from Japan
snowfinch.zone a #mastodon server from Germany
guelph.social a #mastodon server from PortugalHelp others find a home, send them to fediverse.observer
-
@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. OnlyHashtagis 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 -
@D.Hamlin.Music @Lunawawa :neofox_snug: :therian: The problem is most likely that Mistpark, now Friendica, introduced hashtags that do not include the "hashtag character" into the link. All of Friendica's descendants took this behaviour over, including Hubzilla and (streams).
#Hashtag
Twitter/𝕏 has always included the "hashtag character" into the link. All the Twitter replacements, Mastodon, Pleroma, Misskey and their forks, have taken this behaviour over.
#Hashtag
However, they largely expect or used to expect everything in the Fediverse to do that. The way Friendica and its descendants do hashtags is unexpected and highly irritating to them. Vanilla Mastodon has largely fixed their hashtag handling; only the extraction of the hashtags in the last line doesn't work properly yet.
Apparently, this fix was introduced to vanilla Mastodon after the Glitch fork, and Glitch has never taken it over. And the Iceshrimp.NET devs seem not to know about this phenomenon either.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Glitch #GlitchSoc #Glitch_Soc #Iceshrimp #Iceshrimp.NET #Friendica #Hubzilla #Streams #(streams) -
Found 16 new servers and 26 servers died off since 3 hours ago.
21,611 servers checked. 14,313,199 Total Users with 1,042,133 Active Users today. Check out the stats!
New #fediverse servers found:
fedi.velzie.rip a #iceshrimp.net server from Private
pixelfed.somamis.it a #pixelfed server from Private
pixelfed.winscloud.net a #pixelfed server from Private
mastodon.neito.us a #mastodon server from France
social.laia.ar a #mastodon server from France
social.smartexplorate.sbs a #friendica server from Belgium
urgentcodex.com a #mastodon server from Portugal
fursails.com a #mastodon server from Hong Kong
social.context.town a #mastodon server from France
meowverse.catsanctuary.top a #firefish server from United States
2-5.cc a #wxwclub server from Private
ivan.cafe a #bonfire; compatible: mastodon, akkoma server from Germany
1718873947080.kzkr.xyz a #cherrypick server from Private
pixelfed.krebos.nl a #pixelfed server from Germany
kookie.app a #kookie server from Canada
sortius.hopto.org a #firefish server from AustraliaHelp others find a home, send them to fediverse.observer
-
Found 16 new servers and 17 servers died off since 3 hours ago.
21,621 servers checked. 14,313,199 Total Users with 1,042,133 Active Users today. Check out the stats!
New #fediverse servers found:
fedi.velzie.rip a #iceshrimp.net server from Private
pixelfed.winscloud.net a #pixelfed server from Private
pixelfed.somamis.it a #pixelfed server from Private
mastodon.neito.us a #mastodon server from France
social.smartexplorate.sbs a #friendica server from Belgium
urgentcodex.com a #mastodon server from Portugal
social.laia.ar a #mastodon server from France
fursails.com a #mastodon server from Hong Kong
social.context.town a #mastodon server from France
meowverse.catsanctuary.top a #firefish server from United States
2-5.cc a #wxwclub server from Private
ivan.cafe a #bonfire; compatible: mastodon, akkoma server from Germany
1718873947080.kzkr.xyz a #cherrypick server from Private
pixelfed.krebos.nl a #pixelfed server from Germany
kookie.app a #kookie server from Canada
sortius.hopto.org a #firefish server from AustraliaHelp others find a home, send them to fediverse.observer
-
Found 16 new servers and 16 servers died off since 3 hours ago.
21,621 servers checked. 14,313,199 Total Users with 1,042,133 Active Users today. Check out the stats!
New #fediverse servers found:
fedi.velzie.rip a #iceshrimp.net server from Private
pixelfed.winscloud.net a #pixelfed server from Private
pixelfed.somamis.it a #pixelfed server from Private
mastodon.neito.us a #mastodon server from France
urgentcodex.com a #mastodon server from Portugal
social.laia.ar a #mastodon server from France
social.smartexplorate.sbs a #friendica server from Belgium
fursails.com a #mastodon server from Hong Kong
social.context.town a #mastodon server from France
meowverse.catsanctuary.top a #firefish server from United States
2-5.cc a #wxwclub server from Private
ivan.cafe a #bonfire; compatible: mastodon, akkoma server from Germany
1718873947080.kzkr.xyz a #cherrypick server from Private
pixelfed.krebos.nl a #pixelfed server from Germany
kookie.app a #kookie server from Canada
sortius.hopto.org a #firefish server from AustraliaHelp others find a home, send them to fediverse.observer
-
Found 56 new servers and 24 servers died off since 3 hours ago.
22,342 servers checked. 13,565,417 Total Users with 1,520,328 Active Users today. Check out the stats!
New #fediverse servers found:
owncast.britishtechnetwork.com a #owncast server from France
goto.wirespeed.cafe a #gotosocial server from France
christian-lorig.de a #writefreely server from Germany
net.woem.space a #iceshrimp.net server from Germany
sampleg325ps7z3d6oqadfgmokwvuic72lgr3b4um22ekgf3jq6ebaad.onion.monster a #gotosocial server from Canada
liber.eu.org a #writefreely server from Romania
ranslite.de a #lemmy server from Germany
mibl.vannilla.org a #gotosocial server from Bulgaria
juef.net a #gotosocial server from Germany
intersex.social a #iceshrimp server from Finland
lem.sabross.xyz a #lemmy server from United States
comunidad.blasterradio.net a #mastodon server from United States
mastodon.ericmitch.com a #mastodon server from United States
pika.moe a #misskey server from United Kingdom
visegrad24.social a #mastodon server from The Netherlands
homo.1919810.space a #misskey server from Private
social.sssa.africa a #mastodon server from Germany
social.endersonmaia.com.br a #gotosocial server from France
pixel.staging.balamb.fr a #pixelfed server from France
pixel.davidpeach.me a #pixelfed server from United Kingdom
social.dfnt.fr a #gotosocial server from France
pix.hilles.space a #pixelfed server from Germany
fedi.feministwiki.org a #pleroma server from Germany
mastodon.mtrnord.blog a #mastodon server from Finland
the.kittywi.re a #gotosocial server from France
pixel.hurel.me a #pixelfed server from France
gts.lumaeris.com a #gotosocial server from Norway
social.kwanters.club a #mastodon server from United Kingdom
social.wjt.je a #mastodon server from Private
social.adridoesthings.com a #mastodon server from Germany
zakstagram.com a #pixelfed server from United States
pxl.dead.rodeo a #pixelfed server from Finland
sosial.nyheimen.no a #mastodon server from Finland
social.pileus.ch a #mastodon server from Switzerland
pixelfed.becometheteapot.cfd a #pixelfed server from Private
toot.burns.is a #mastodon server from Germany
mastodon.vshn.social a #mastodon server from United Kingdom
activitypub.cryptography.dog a #jugaadu server from United States
mastodon.in-two.com a #mastodon server from Germany
gts.nixgeek.com a #gotosocial server from Private
social.cyconet.org a #gotosocial server from Germany
pixel.markbrouch.com a #pixelfed server from Private
sociall.se a #pleroma server from United States
fedi.walrusz.hu a #mastodon server from United Kingdom
social.redbarrel.net a #mastodon server from United States
pixel.mrrl.me a #pixelfed server from United States
social.nblumhardt.com a #mastodon server from United Kingdom
pixel.afop.social a #pixelfed server from Germany
pixel.simplex-software.ru a #pixelfed server from Russia
lilienthal.pics a #pixelfed server from Private
blog.potata.uk a #microblogpub server from Private
blog.psion.co a #writefreely server from United States
pixel.z4i.ru a #pixelfed server from Russia
nimisskey.xyz a #misskey server from Japan
muji.hirasakain.ninja a #misskey server from Private
mastodon.andrewnoonan.site a #mastodon server from United StatesHelp others find a home, send them to fediverse.observer
-
Found 24 new servers and 31 servers died off since 3 hours ago.
22,889 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
social.interfree.ca a #pleroma server from Canada
tigeskey.tarbin.net a #tanukey server from Private
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
mast.brentnatzle.com a #mastodon server from France
tillsammans.duckdns.org a #pleroma server from Sweden
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 24 new servers and 31 servers died off since 3 hours ago.
22,889 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
social.interfree.ca a #pleroma server from Canada
tigeskey.tarbin.net a #tanukey server from Private
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
mast.brentnatzle.com a #mastodon server from France
tillsammans.duckdns.org a #pleroma server from Sweden
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 24 new servers and 31 servers died off since 3 hours ago.
22,889 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
social.interfree.ca a #pleroma server from Canada
tigeskey.tarbin.net a #tanukey server from Private
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
mast.brentnatzle.com a #mastodon server from France
tillsammans.duckdns.org a #pleroma server from Sweden
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 24 new servers and 31 servers died off since 3 hours ago.
22,889 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
social.interfree.ca a #pleroma server from Canada
tigeskey.tarbin.net a #tanukey server from Private
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
mast.brentnatzle.com a #mastodon server from France
tillsammans.duckdns.org a #pleroma server from Sweden
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 23 new servers and 27 servers died off since 3 hours ago.
22,895 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
tigeskey.tarbin.net a #tanukey server from Private
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
tillsammans.duckdns.org a #pleroma server from Sweden
mast.brentnatzle.com a #mastodon server from France
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 23 new servers and 27 servers died off since 3 hours ago.
22,895 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
tigeskey.tarbin.net a #tanukey server from Private
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
tillsammans.duckdns.org a #pleroma server from Sweden
mast.brentnatzle.com a #mastodon server from France
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer
-
Found 23 new servers and 27 servers died off since 3 hours ago.
22,895 servers checked. 13,961,663 Total Users with 1,597,288 Active Users today. Check out the stats!
New #fediverse servers found:
elbereth.xyz a #mastodon server from Portugal
video.onjase.quebec a #peertube server from Canada
tigeskey.tarbin.net a #tanukey server from Private
mastodon.chanchotec.com a #mastodon server from The Netherlands
social.mbirth.uk a #gotosocial server from United Kingdom
ewpratten.com a #cloudflare workers server from Private
gadget.inpocket.net a #mastodon server from Private
fedi.gebbl.net a #akkoma server from United Kingdom
darksky.social a #mastodon server from Germany
staging.tpaw.social a #mastodon server from United States
social.soraharu.app a #mastodon server from Private
staging.verse.averagedood.xyz a #iceshrimp.net server from Spain
snowhouse.noho.st a #plume server from Italy
firefish.nekoq.top a #firefish server from Private
tillsammans.duckdns.org a #pleroma server from Sweden
mast.brentnatzle.com a #mastodon server from France
fl0.net a #mastodon server from United States
boo.hoopla.dev a #mastodon server from Canada
gts.nano.lgbt a #gotosocial server from United Kingdom
catpost.ing a #gotosocial server from United States
mi.minimarimo3.jp a #misskey server from Japan
yurigasaki.com a #misskey server from Private
biblio.barca.dix.asia a #bookwyrm server from JapanHelp others find a home, send them to fediverse.observer