#fedimeta — Public Fediverse posts

• AI-generated Mastodon code
• on an AI-generated Web server
• with an AI-generated database driver
• on an AI-generated operating system kernel

• AI-generated Mastodon code
• on an AI-generated Web server
• with an AI-generated database driver
• on an AI-generated operating system kernel

• AI-generated Mastodon code
• on an AI-generated Web server
• with an AI-generated database driver
• on an AI-generated operating system kernel

• AI-generated Mastodon code
• on an AI-generated Web server
• with an AI-generated database driver
• on an AI-generated operating system kernel

• AI-generated Mastodon code
• on an AI-generated Web server
• with an AI-generated database driver
• on an AI-generated operating system kernel

People can follow hashtags

People can follow hashtags

People can follow hashtags

People can follow hashtags

People can follow hashtags

*winkt allen @nrw.social aufmunternd zu*

https://status.nrw.social/status/main

#nrwSocial #fedimeta

*winkt allen @nrw.social aufmunternd zu*

https://status.nrw.social/status/main

#nrwSocial #fedimeta

• It's the only wiki about alt-texts and image descriptions. Few writers have even only written multiple pages or articles on this subject.
• It's the only guide that takes the existence of the Fediverse outside of Mastodon into consideration. This means that it's also the only guide that doesn't assume that Fediverse equals always having only 500 characters for the message text. It actually recommends an additional, longer image description in the message text in certain situations, regardless of whether or not vanilla Mastodon users can do that.
• It's the only guide that, instead of regurgitating the alt-text rules for webpages and blogs and assuming that they apply to the Fediverse just the same, talks about the peculiarities of posting images into the Fediverse, how Mastodon's alt-text quality criteria are different from the W3C WAI and WCAG alt-text quality criteria, and why it's critically important to know and fulfill Mastodon's requirements for good alt-texts.
• It's probably the only guide that doesn't assume that you can always precisely target a certain audience for your content and make sure that only those receive it who understand it right off the bat.
• It is the only guide that lists over 60 references, including your blog post, but also including university webpages as well as over two dozen guides from Veronica Lewis a.k.a. Veronica with Four Eyes.

• entirely running on its own protocol, Zot6
• with nomadic identity that makes it possible to clone your channel across multiple servers and making it resilient against server outage
• with multiple channel (identities, like complete Friendica accounts, but without separate logins) on one account/login, and you can switch between them without logging out and back in again (all with multiple profiles like on Friendica)
• without Bluesky integration
• with less pandering to Mastodon
• with an even better permissions system
• with full (client-side and server-side) OpenWebAuth support
• with polls
• with WebDAV access to your file space
• with a built-in CalDAV calendar server
• with an optional built-in CardDAV addressbook server
• with optional articles, planning cards, wikis and webpages
• with a very extensive, detailed and well-written built-in help system
• with the ability to integrate git repositories with 3rd-party add-ons and themes that can even be upgraded with shell scripts as easily as the whole hub
• with 3rd-party themes available that change the entire UI and UX instead of reskinning the existing UI, especially the Utsukta themes by @Saiwal

• Mastodon
• Friendica
• Hubzilla (rebuilt from a fork of a fork of Friendica by Friendica's creator)
• (streams) (fork of a fork of three forks of a fork (of a fork?) of Hubzilla by the same creator)
• Forte (fork of the streams repository by still the same creator

• Mastodon:
  500 characters; requires source code modifications to get more
  Friendica:
  16,777,215 characters
• Friendica:
  Can render and create the full gamut of HTML text formatting
  Mastodon:
  Can only create plain text; can only render a small subset of HTML text formatting
• Friendica:
  Have as many images pro post as you want
  Embed them within the text
  Mastodon:
  Limited to 4 images
  Images can only be file attachments
• Friendica:
  Shows you all content in the Fediverse just like the author intended it
  Mastodon:
  "Sanitises" away half the formatting, all embedded images and all images except for the first four, just for the sake of purist microblogging
• Mastodon:
  Timeline consists of single messages with no context
  Friendica:
  Timeline consists of complete conversations, all the way back to the start post, with all branches (ignores and blocks notwithstanding)
• Mastodon:
  Conversations consist of toots and more toots, loosely strung together with mentions
  Replies only reach those who are visibly mentioned
  Friendica:
  Conversations consist of exactly one post and otherwise comments
  Replies go from the replier to the thread starter and from there to all participants in the conversation without having to mention anyone
• Friendica:
  Has groups built in (groups are accounts with special settings)
  Mastodon:
  Has no support for groups whatsoever, much less its own groups
  Most Mastodon users don't even know that the Fediverse has groups
• Friendica:
  Lets you federate with the whole Fediverse
  Lets you federate with diaspora*
  Lets you include and remote-control a Bluesky account
  At least used to be able to do the same with a Tumblr account or a Twitter account
  Lets you crosspost to Dreamwidth, Libertree, LiveJournal and XML-RPC-based blogs like WordPress
  Mastodon:
  Just barely so federates with the Fediverse
  Tries to make everything that isn't Mastodon look broken
  Would love for the Fediverse to be only Mastodon
• Mastodon:
  Makes the whole Fediverse look like Mastodon
  Friendica:
  Shows you which server software a message came from

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

Yes, and it should not be implemented in Ruby or PHP or something like that. I have seen one online discussion forum being rewritten from PHP to Rust few years ago, and the improvement in responsiveness of the web platform was amazing. (I do C, not Rust, but C is too oldschool now, and the performance penalty of Rust is minor, probably not noticeable at all)

I believe there was always the best interest of Mastodon developers to enable their users to engage with content like PeerTube videos, WordPress blog posts, and so on.

You also mention, that Hubzilla was first application ready to deliberately block other platforms... and then accuse Mastodon of doing the same

But there is no reason to block entire platforms.

Myself, I would like to learn Rust and perhaps join some ActivityPub project in Rust, which would not be so strictly focused on being Xitter clone and would support more media options, would display more than 4 image attachments, would be very user configurable, be aware of status size limits of platforms of mentioned users, etc.

The wiki reveals even different timeline:

To me, it seems, that Gargon simply was not as colossal nerd, as others, and somehow managed to create cult following of sufficient number of users, which were not really techies.

I was thinking about need for decentralized social media since at least 2009, as I was watching the old web to slowly loose any relevance. (My Facebook account was canceled without any explanations as soon as perhaps sometimes like 2010?).

I was thinking about basing it on bunch of combined RSS feeds, the publicly compatible vs. the activity stream, which is not so different from from like ActivityPub is made today, except that signing of content with public keys is more advanced concept, that what I was able to imagine.

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

Also, ALT text translates with the rest of the post, which can be helpful for images which contain only foreign language text.

Hubzilla is the most incompatible ActivityPub software in Fediverse. You do just lot of things wrong, to put it mildly.

yes, the Hubzilla author is writing Streams, with nomadic identity, but it also means, that he understands, that Hubzilla approach is kind of dead-end.

while nomadic identitity would be cool thing, currently it does not exist

People know, that there are alternatives, and explore them.

I think it can replace also Facebook and Instagram.

Digital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery. A more detailed description including explanations and text transcripts can be found in the post.

Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin, brown eyes and black hair which is styled as a neck-long bob. She is wearing a black tank top with the logo of the 17th birthday of OSgrid on it, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace with the OSgrid logo. The OSgrid logo is made up from five identical parallelograms arranged in a circular, star-like pattern. It is also part of the birthday logo which is mostly two tones of yellowish orange. The writing on the birthday logo reads, from top to bottom, “OSgrid”, “The Open Source Metaverse” and “17th Birthday”. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.

Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin and black hair which is styled as a neck-long bob. She is wearing a black tank top, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace. She is looking at the cover of the Leonard Cohen album Recent Songs on a white easel. The cover is a painting of the musician's face. He is shown to be a middle-aged man with light skin, green eyes and black hair in a black shirt. A hummingbird is drawn hovering above his shoulder to the left. The background is medium blue. Cohen's name and the album title are written in the top corners. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, “CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact”, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.

Image macro, based on a screen capture from the Disney and Pixar animated film Finding Nemo. At the top, there is a white space with a two-line caption: “OSgrid: offline for weeks to come,” and “Owners of other grids, looking at OSgrid residents:”. In the screen capture below, ten seagulls are perched on two mooring lines in the background. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”

Image macro, based on a screen capture from the animated film Finding Nemo. At the top, there is a white space with a two-line caption: “Fediverse admin: announces the end of their instance and asks their users to migrate to other instances,” and “Admins of other instances:”. In the screen capture below, ten seagulls are perched on two mooring lines. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, “Mine?”

3 Uhr nachts und ich denke darüber nach, dass wir KI-Systemen beibringen, "ethisch" zu handeln, während wir selbst nicht mal einigen können, ob man Pizza mit Ananas essen darf. 🍕

Vielleicht ist das eigentliche Problem nicht, dass Maschinen keine Moral haben – sondern dass wir versuchen, eine universelle Ethik in Code zu gießen, die wir als Menschheit nie ausverhandelt haben.

Gute Nacht, Maschinenraum.

#KI #Ethik #Nachtgedanken #FediMeta

• 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.

• 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 fetch kö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.

We love it so much that every time we check the FediGroups Directory, cool new groups have sprung up!

(We keep hoping that someone will create an education-themed group. Fingers crossed!)

If you haven't checked it out in a while, go take a look.

https://about.fedigroups.social/directory

#FediMeta #MastodonMeta #FediGroups #Education

I went to block an account tonight and accidentally blocked the instance instead...

...but it was mastodon.social. hahahaha

I have thus messed up a bunch of follows and followers.

Is there an easy/elegant way to fix this?

*I'm not worried, I think it's funny on my end, I just don't want to slight or confuse people, and so from that perspective would like to get it fixed asap.

#FediMeta #MastodonMeta