Find the latitude of any place.  

Failed U.S. Military Effort in Africa

Failed U.S. Military Effort in Africa is on the Chopping Block

The U.S. attack on Venezuela and abduction of its president Nicols Maduro was proof that after months of
:ArticlePost :Sunday :English :Article :Factiva :SmartNews :SocialFlow :NationalSecurity :World :11.00 :1000-1999

Why does someone call one single Fediverse server, one single website "-verse"
Because they're probably stuck at freshly-switched-from-the--iPhone-app-to-the-Mastodon-iPhone-app level of Fediverse knowledge. They probably don't simply believe that the Fediverse is only Mastodon. No, they must believe that the Fediverse is only one server, one website, namely mastodon.social. They might be unable to imagine that multiple Twitter-like websites that run the same code can communicate with each other. After all, they haven't heard of anything like this having happened before.
Which also means that the guys behind the Forkiverse think that their Forkiverse is every but as much a centralised, single-website walled garden silo as they think the Fediverse, i.e. mastodon.social, is. And that there are exactly two websites running Mastodon code now, namely mastodon.social, for which the Mastodon code was probably developed, and the Forkiverse.
If that's so, they're probably going to go completely insane once they discover that people on mastodon.social start leaving content in their Forkiverse. Or people from wholly different Mastodon servers, something they might not even expect to exist.
And that says nothing about how they'll react upon the first comment on a Forkiverse post from something that's very much, very obviously, very blatantly not Mastodon. Like Friendica or Hubzilla or (streams) or Forte. Something that does everything differently from Mastodon, from 33,000 times more characters to text formatting to bullet-point lists to headlines to very different-looking hashtags and mentions.
I mean, I know that Mastodon users who got used to a Mastodon-only Fediverse frequently lose their minds when they come across the first message that's obviously not from Mastodon, and whose author states and proves that this is not a Mastodon toot. And I've seen at least one tech journalist insist in Mastodon being an enclosed network itself and himself being right because he, very much unlike those filthy amateurs that drivel about Calckey and Friendica and Hubzilla and whatnot, is a journalist and therefore a professional.
But imagine you know next to nothing about Mastodon, other than that mastodon.social is a website that's an alternative to , and that it's running on an open-source server application that's also named Mastodon. And then you set up your own website with the same code. And you think it's every bit a walled garden as and as mastodon.social straight out of the box. And then you, as one of the admins and site owners, receive a comment on one of your posts that so very much blatantly not even a Mastodon toot.
Brix will be shat. This will hurt horribly.
# # # # # # # # # # # # # #Why does someone call one single Fediverse server, one single website "-verse"
Because they're probably stuck at freshly-switched-from-the--iPhone-app-to-the-Mastodon-iPhone-app level of Fediverse knowledge. They probably don't simply believe that the Fediverse is only Mastodon. No, they must believe that the Fediverse is only one server, one website, namely mastodon.social. They might be unable to imagine that multiple Twitter-like websites that run the same code can communicate with each other. After all, they haven't heard of anything like this having happened before.
Which also means that the guys behind the Forkiverse think that their Forkiverse is every but as much a centralised, single-website walled garden silo as they think the Fediverse, i.e. mastodon.social, is. And that there are exactly two websites running Mastodon code now, namely mastodon.social, for which the Mastodon code was probably developed, and the Forkiverse.
If that's so, they're probably going to go completely insane once they discover that people on mastodon.social start leaving content in their Forkiverse. Or people from wholly different Mastodon servers, something they might not even expect to exist.
And that says nothing about how they'll react upon the first comment on a Forkiverse post from something that's very much, very obviously, very blatantly not Mastodon. Like Friendica or Hubzilla or (streams) or Forte. Something that does everything differently from Mastodon, from 33,000 times more characters to text formatting to bullet-point lists to headlines to very different-looking hashtags and mentions.
I mean, I know that Mastodon users who got used to a Mastodon-only Fediverse frequently lose their minds when they come across the first message that's obviously not from Mastodon, and whose author states and proves that this is not a Mastodon toot. And I've seen at least one tech journalist insist in Mastodon being an enclosed network itself and himself being right because he, very much unlike those filthy amateurs that drivel about Calckey and Friendica and Hubzilla and whatnot, is a journalist and therefore a professional.
But imagine you know next to nothing about Mastodon, other than that mastodon.social is a website that's an alternative to , and that it's running on an open-source server application that's also named Mastodon. And then you set up your own website with the same code. And you think it's every bit a walled garden as and as mastodon.social straight out of the box. And then you, as one of the admins and site owners, receive a comment on one of your posts that so very much blatantly not even a Mastodon toot.
Brix will be shat. This will hurt horribly.
# # # # # # # # # # # # # #


SNOT Has Completed Five Songs With New Singer ANDY KNAPP Long-Awaited Album Information Coming 'Soon'

Eine grafische Web-Benutzeroberflche als Ersatz fr Pleromas offizielle Benutzeroberflche Pleroma-FE und fr Akkomas offizielle Benutzeroberflche Akkoma-FE. Wenn es da installiert ist, steht Pleroma-FE bzw. Akkoma-FE nicht mehr zur Verfgung, nur noch Mangane.
Als Nutzer kann man es aber nicht installieren, sondern nur als Serveradmin und dann wie schon angedeutet nur fr alle Nutzer gleichermaen.
Es funktioniert auch mit Mastodon.

# # # # # # # # # # # # # # # #

Once again, long nose = long cock

cock, nose = long cock,

The point is that if someone wants to connect to you from Hubzilla, they might have a very detailed profile, maybe even several profiles (this is possible on Hubzilla), but they only give permission to access their profile to their contacts or to certain contacts and not to the general public. So while there is a profile, you are not allowed to access it. Unlike Friendica, Hubzilla's Web UI doesn't even tell you up-front that you aren't allowed to access the profile. And, of course, neither does Mastodon's Web UI, and neither do any Mastodon apps.
At the same time, they could actually be very active posters. But for privacy and security reasons, they don't post in public. All their posts have restricted permissions. Alternatively, they do post in public, but they only grant permission to see their stream of posts on their channel to their contacts or even only to certain contacts. Either way, you as a non-contact are not allowed to access their posts.
Imagine you, on Mastodon, could allow only your followers and followed to read your profile. And you could allow only your followers and followed to access the timeline on your profile page. Both is absolutely possible on Hubzilla. Or you only ever post to "followers only" and never in public, so your posts don't show up in your timeline.
Either way, there's a profile, and there are posts, but you are not allowed to access them. So to you, it appears like a blank and inactive account.
Still, Hubzilla does little to nothing in terms of accessibility. In its software family that spans a decade and a half, it's the only server application that requires coding to add alt-texts.
Friendica may have introduced a Mastodon-like entry field. (streams) and Forte allow for alt-texts to be stored with images in the built-in filespace so they're automatically added when an image is embedded into a post or a comment. On Hubzilla, the alt-text must still be manually grafted into the image-embedding BBcode. Even that information was only spread via hearsay until it was added to the official documentation last year or so.
So the reason why there's hardly ever any alt-text coming from Hubzilla is not because Hubzilla staunchly refuses to replace its own culture with Mastodon's (which it does, by the way, and for very good reasons). It's partly because adding alt-texts is so tedious and requires what amounts to "programming". And it's partly because since Hubzilla's post and comment editors have no UI elements for alt-texts, and neither do the file and image uploaders, hardly anyone on Hubzilla even knows about alt-texts and that it's possible to add them on Hubzilla in the first place.
Hubzilla's entire UI/UX is mostly stuck in 2012 with parts of it dating back to 2010. That was when accessibility didn't matter for hobbyist projects. And it was developed by someone who's much more of a protocol developer than a UI expert. There hasn't changed that much about it since back then except for new features having their UI elements glued on in sometimes seemingly random places.
# # # # # # # #

After cumming

! Falls du Hubzilla mal in Aktion sehen willst:
Zunchst einmal, das hier ist mein Kanal:
Das hier ist mein ffentliches Profil:
Das Farbschema nebst Hintergrundbild ist brigens von mir. Das ist alles einstellbar. Das Layout und die Navigation habe ich auch ein bichen frisiert.
Es gibt einen ungefhr monatlich stattfindenden deutschsprachigen Hubzilla-Workshop. Der findet statt auf BigBlueButton, du brauchst also nur einen Webbrowser, ein Mikro und eine Abhre. Er hat einen eigenen Hubzilla-Kanal: . Dem kann man meines Wissens auch von Mastodon aus folgen. Alternativ kann man der Organisatorin folgen (Mastodon: Hubzilla: Friendica: ).
Folgenswert ist auch der schreibt fters mal ber Hubzilla. Er hat auch das komplette Hilfesystem fr Hubzilla auf Deutsch und Englisch neu geschrieben (), und er betreibt die Hubzilla KnowledgeDB () und ein deutschsprachiges Supportforum ().
Auf dem zweiten Workshop im Oktober 2025 hat Pepe zunchst einmal einen Vortrag gehalten ber den Einstieg in Hubzilla. Hier ist das Video:
Auf demselben Workshop habe ich einen Vortrag gehalten ber Privacy-Gruppen (= Mastodon-Listen auf Steroiden und Koks) und Kontaktrollen (gibt's auf Mastodon so nicht mal ansatzweise). Hier ist das Video:
Auf dem dritten Workshop im November ging es darum, wie auf Hubzilla gepostet wird. Das ist an sich schon ein gewaltig viel greres Thema als das "Trten" auf Mastodon. Da hat Pepe auch einen Vortrag generell ber das Posten gehalten (Videos scheint es nicht zu geben Prsentation: ) und ich einen ber die Unterschiede beim Posten zwischen Hubzilla und vor allem Mastodon (wieder kein Video Prsentation: ).
Der erste Workshop im September war eigentlich nur ein Testballon, knnte aber trotzdem interessant gewesen sein. Da ging es um verschiedene Einstellungen, um Hubzillas mchtige Filter und um verschiedene Tips & Tricks. Hier ist das Video:
Die nchsten zwei Workshops sind am Mittwoch, dem 28. Januar, und am Mittwoch, dem 11. Februar, jeweils um 19.30 Uhr. In beiden geht es um Hubzillas mchtiges und hochkomplexes Berechtigungssystem. Das ist so ein groes Thema, da wir beschlossen haben, es auf zwei Workshops auszudehnen. Das heit, den am 11. Februar verstehst du wahrscheinlich nur, wenn du am 28. Januar schon da warst.
# # # # # # # # # # #

Permissions meet groups


It gets really interesting when the permissions system is applied to groups. As the owner of a Hubzilla forum, you have the following options:

(streams) and Forte have four different types of group channels instead:
Whether or not a group is visible in the directory is a separate switch.
As I've already said, you can grant individual permissions to your contacts on your personal channel. But you can grant individual permissions to forum users on a forum channel just the same. You can have regular users. You can have users with certain extra privileges. You can use the permissions system to silence users without kicking and blocking them.
And you can use the permissions system to appoint extra forum admins/mods. You can grant contacts permission to administer your forum. Now, this requires for your channel to recognise visitors and their identities to see what permissions they shall have and to grant them these permissions. And this requires OpenWebAuth. So right now, you can only make forum members from Hubzilla, (streams), Forte, Friendica, Mitra and Tootik additional admins/mods. But you can.
(9/9)
# # # # # # # # # # # # # # # # # # # # #

Permissions, part 3: At post level


As I've already said, whenever you write a post to start a new thread, you also define the permissions of this post. Of this post and of all replies.
Let's translate this to Mastodon again.
You know the toot visibility button, I guess. Let's assume it looks and works somewhat different. Especially the visibility options.
"Public" still exists. It does what it says on the button: It makes your toot public. Oh, and now, it also makes all replies public. There's no replying to your toot with a DM.
The other three don't exist.
Instead, as the second option, you have "Only me".
Right below, all your lists are listed up. You can pick one of them. You can send your toot to everyone on one specific list of yours and to only those on that list, all without having to mention them. Better yet: Only those on that list are permitted to see your toot. And only those on that list are permitted to see any reply to your toot. Killer feature: They can see each other's replies, and they can reply to each other.
Below that, all groups that you follow are listed up. Again, you can pick one of them. This will have the effect that your toot will go to the group, and it will be forwarded by the group to all its members, but it will not go to your followers unless they're also in that group.
Below that, there's "Custom selection". This opens another window with each one of your lists and each one of your followed accounts, each with a green "Allow" button and a red "Don't allow" button. Here, you can put together a choice of lists and single accounts whom to send your toot to and a choice of lists and single accounts whom not to send your toot to. Again, only those who receive the toot are also permitted to see it, and only them are permitted to see any of the replies, and no-one can ever change these permissions.
What sense this makes
Imagine you have a list with a certain group of friends in it. One of them will soon celebrate their birthday, and you want to organise a birthday surprise for them. So you send a toot to that list with everyone in it, but without that person who'll soon celebrate their birthday so you won't ruin the surprise for them.
Or: Imagine you have lists according to which languages people speak. Like, you have a German list, and you have an English list. Then you can put together an audience for a German toot from lists and single followed users, but exclude the English list so that those who don't understand German anyway won't receive that toot.
By the way: This also covers DMs. And this means that DMs are actually private.
As Mastodon is right now, you can DM Alice, you can have a conversation with Alice, but Alice could mention Bob and pull him into the conversation. This also gives Bob the opportunity to read the whole thread because he has access to it now. Mastodon only defines to whom a message is sent, but not who is allowed to see it.
In this version of Mastodon, when you DM Alice, you only grant Alice permission to see your toot and everything else in the thread. Now, Alice can mention Bob all she wants, but she can't pull him into the thread. Bob won't even receive the toot with his mention in it. He is not permitted to see it. You have not granted him permission to see the start toot, and thus, you have not granted him permission to see any of the replies, including the one in which Alice mentions him. Alice cannot change any permissions in the thread. Neither can you, by the way. The moment you send the start toot, all permissions are permanently set in stone for the whole thread.
This also makes dogpiling by extra mentions in DMs impossible.
Also, this provides for very effective quote-post control. It isn't allowed to boost posts that aren't public, including replies. It isn't allowed either to Mastodon-style-quote, as in quote-post, posts that aren't public, including replies.
These DMs have another advantage of DMs on Mastodon-as-it-is-now: If you send a DM to Alice and Bob, Bob receives Alice's replies, and Alice receives Bob's replies, and the two can reply to one another.
Oh, by the way, there's another nifty button. A speech bubble. With this button, you can allow or disallow replies to your post. Mind you, again, this only works when you start a thread. You cannot allow or disallow replies to a reply that you post.
Now, how does Mastodon-as-it-is-now handle DMs from Hubzilla, (streams) and Forte It sees them as Mastodon DMs, and it treats them like Mastodon DMs. The downside is, if I send a restricted-permission post to Alice on Mastodon and Bob on Mastodon, both perceive it as a Mastodon DM. Both can only reply to and converse with me. They can't see each other's replies, and they can't reply to each other.
(8/9)
# # # # # # # # # # # # # # # # # #

Permissions, part 3: At contact level


Let's go one level further down. The second level of Hubzilla's permission system is per contact. On Mastodon, that'd be those whom you follow.
If Mastodon was like Hubzilla, you'd have the possibility to create permission templates which you can then assign to those whom you follow. (Hubzilla calls them "contact roles", by the way.)
Like, you could make one template for those whom you really trust. You grant all permissions in that template.
Then you could make one that's more privacy-oriented. You only grant permission to send you toots, fave and reply to your toots and send you DMs.
In theory, you could also make one for those whom you absolutely must follow, but whose toots you don't want. In this one, you only grant permission to fave and reply to your toots and send you DMs. This, however, only makes sense on something that works like Facebook, something like Hubzilla, where you can only confirm follow requests by also following back because connections are always mutual by default.
Then you could go to your list of followed accounts. And you could edit and configure them, one by one. You could choose which of these permission templates is assigned to them and thereby what you allow them to do. While you're already there, you could also, for example, add them to lists or remove them from lists.
There's one catch, though: If you grant a permission for your whole account, you automatically grant it to everyone whom you follow. You cannot forbid one of your followed something your account generally allows. So if you want to be able to choose whether someone is allowed to do something or not, you must not allow it for your whole account, and instead, you must allow it followed by followed.
(streams) and Forte make things a great deal easier than Hubzilla, by the way: They don't require such templates anymore. Instead, when you go edit a contact, you'll see one on-off switch for each permission, and you can turn each permission on or off right there, right then (provided it isn't inherited from the channel). You still have such templates, but they only serve to grant the same set of permissions to a whole lot of contacts without having to click single permissions on or off for all of them.
(7/9)
# # # # # # # # # # # # # # # # # Add your location to a Google Map

Permissions, part 2: At channel level


The top level of Hubzilla's permissions system is the whole channel. On Mastodon, that'd be your account and everything that happens on it.
Translated to Mastodon again, for each of the above permissions, your account would have seven or eight choices whom to grant the corresponding permission:

*It's unclear what exactly this option means. See, Hubzilla is not based on ActivityPub. It is based on its own protocol, Zot. When it was created, it was the only server software that used Zot, so limiting permissions to Hubzilla and limiting permissions to whatever uses Zot had the same effect, seeing as Hubzilla could and still can also connect to a whole lot of other things using a whole lot of other protocols. So nowadays, "Anybody in this network" may mean anybody using Zot which means anybody on Hubzilla or (streams), or it may mean anybody on Hubzilla which means just that, excluding (streams).
**This translates to Mastodon badly. Basically, Friendica, Hubzilla, (streams) and Forte know three states of connection. Either a Mastodon follow request, that's a "contact". Or a mutual follower, that's a "confirmed contact" because it's listed on your connections page, and you have control over that connection. Or only you follow someone, that's a "confirmed contact", too, because, again, because it's listed on your connections page, and you have control over that connection. The concept of confirmed follower doesn't exist because confirming a connection request will automatically make it a mutual connection. Remember we aren't talking about Twitter followers and Twitter followed, but about Faceboook friends.
The choices on (streams) and Forte, translated to Mastodon, are:

To stick with Mastodon equivalents, there are a few more settings on Hubzilla (as for (streams) and Forte, I've covered them in the previous comment already).
I guess you already know the switch that hides your account from Google and other search engines and the switch that makes your account automatically accept follow requests.
You know that you can mention anyone out of the blue on Mastodon, regardless of whether they follow you or you follow them or not, and they're always notified Imagine this being notified is optional. And off by default. On Hubzilla, both is the case.
Okay, so, next, you don't allow anyone on the internet to reply to your toots. But there's an option that "half-allows" this: Anyone on the internet can send replies to your toots, even if they don't have any Fediverse account at all. Now it comes: You have to approve these replies. You have a green button that you can click, and the reply becomes visible, and it's added to the thread to which it belongs. Before then, nobody can see the reply but you. You also have a red button, and when you click it, the reply is rejected and deleted.
There are two clear use-cases for this. One is when you want absolute control over who replies what to you. Then you don't allow anyone to reply to your toots, but you activate this option. When someone does reply, you can choose whether to let the reply through or delete it.
The other one is a use-case that doesn't work on Mastodon, namely when you want to run a Hubzilla channel as a fully public long-form blog with a target audience that isn't limited to the Fediverse, and you want everyone to be able to comment on your posts, even without having some Fediverse account and following you first, but you want to keep spam out.
Lastly, there's the option that if you don't allow everyone to see your images and other media at , these images and other media can still be seen attached to toots by those who are allowed to see the toots that they're attached to.
(6/9)
# # # # # # # # # # # # # # # # # #

Permissions, part 1: Introduction


Now allow me to explain Hubzilla's permissions system to you. From a Mastodon point of view again.
Hubzilla's permission system works on three levels. In Mastospeak, the first level is your entire account.
The second level is everyone whom you follow, individually. Like, you can go to your list of followed accounts and click on them and configure them. Among other things, you can assign to them a set of permissions that, usually, you'll first define. You'll probably have multiple such sets of permissions.
(Yes, this completely leaves out those who only follow you, and whom you don't follow back. Such a thing does not exist on Friendica, Hubzilla, (streams) and Forte. That is, it does, but you don't have a list of these, and you can't configure these, because they can't do much anyway as long as you don't follow them.)
And the third level is each toot that is not a reply, and then that toot forces its own permissions hard upon all toots that reply to it. If you reply to someone else's toot, your toot will have the same permissions as the start toot with no way for you to change them.
Translated to Mastodon, Hubzilla offers the following permissions:

In addition, there are more permissions that don't translate to Mastodon because they cover features that Mastodon doesn't have:

Translated to Mastodon again, (streams) and Forte offer the following permission settings, some of which are yes/no switches, some are numbers or text fields:

Again, there are permissions that don't translate well to Mastodon:
list
  • Manually allow toots from those who request to follow you
    (Doesn't make sense on Mastodon because if someone wants to follow you, you do not have to follow them back on (streams) and Forte, confirming a follow request does make you follow them back)
  • Show links to all clones of your account in your profile
    (Mastodon doesn't have nomadic identity)
  • Don't show whether you're online
    (Mastodon doesn't show whether you're online anyway, it doesn't even have this feature)/list
    That said, some of these permissions don't make sense from a Mastodon point of view, namely those that handle what people can see when visiting your profile at . There would have be some way to identify them to grant them the permissions you've given them.
    Hubzilla has such a way, as do (streams) and Forte. It's OpenWebAuth, a "magic sign-on" system created by the creator of these four for a Hubzilla fork that was backported to Hubzilla and inherited by (streams) and Forte. These three can recognise logins to grant guest permissions, and their logins can be recognised. There are a few more Fediverse applications whose logins can be recognised. This was actually also developed for Mastodon and ready to be merged in, but the patch was actually silently rejected.
    (5/9)
    # # # # # # # # # # # # # # # # # #

    • Events


    Friendica, Hubzilla, (streams) and Forte have the option to announce events in new posts. Mastodon can receive and show these posts.
    However, Mastodon has no way to handle the actual event part. Like, you can't confirm your participation in an event on Mastodon. Mastodon doesn't know events. Mastodon has no buttons or other UI elements for interacting with events. And Mastodon doesn't have an event calendar either which you'd add the event to when confirming your participation.
    There are also events with no announcement post. For example, birthdays. Friendica, Hubzilla, (streams) and Forte have a dedicated birthday field in their profiles, much unlike Mastodon. For example, I have a "birthday" in my public profile. When someone on Friendica, Hubzilla, (streams) or Forte connects to me, and I confirm that connection, my "birthday" will be added to their event calendar, and they will be notified about my "birthday" every year. This might also work for users on PieFed which has an event calendar, too, although I'm not sure if PieFed understands these birthday fields.
    (4/9)
    # # # # # # # # # # # # # # #

    Groups, part 3: Replying to a thread, and how conversations work


    If you want to reply, just reply. It's good manners to mention whomever you're directly replying to, and even that only if you're replying to a reply. But you don't have to mention anyone to reach anyone. Even then, your reply will be boosted to everyone who has received the top post.
    Even if you reply to Carol who has replied to Bob who has replied to Alice who has started a thread in the group.
    Within Mastodon, you'd have to mention Carol so she receives and sees your reply, you'd have to mention Bob so he receives and sees your reply, you'd have to mention Alice so she receives and sees your reply.
    Conversations on Friendica, Hubzilla, (streams) and Forte work much more like on Facebook: Your reply will go past Carol. Past Bob. Past Alice. Straight to the group account/channel. From there to Alice because she has started the conversation. And to Bob and Carol because they have received the quote-post of Alice's post. And to everyone else who has received the quote-post of Alice's post.
    Now, how does everyone see your reply
    At this point, it's important to say that a Friendica feed or a Hubzilla or (streams) or Forte stream looks vastly different from a Twitter feed or a Mastodon timeline and much more like a Facebook feed. Again, that's because Friendica was a Facebook alternative long before Twitter clones became the default. And Hubzilla, (streams) and Forte are direct descendants of Friendica with largely the same purpose. So no mimicking Twitter's behaviour here.
    What does your Mastodon timeline look like Single posts with no context. And more single posts with no context. You receive a new post, it immediately shows up at the top of your timeline as a single post with no context. You have no idea how many unread messages you have. You want to see the context of a post, you have to click and click and click.
    Facebook doesn't show you single-post-with-no-context piecemeal. Neither do Friendica, Hubzilla, (streams) and Forte. They always show you entire conversations with the top post and with all comments.
    Imagine your Mastodon timeline. But instead of single posts with no context, you always see entire conversations with the top post and all replies that is, you actually only see the last three replies, but you can easily unfold the thread view and see everything.
    Imagine whenever someone replies to a post that you already have in your timeline, you automatically receive that reply.
    Imagine that you have a little counter of unread messages somewhere. When you receive a new post, the counter goes up by one. When you receive a new reply, the counter goes up by one. But neither that new post nor that new reply is automatically added to the top of your timeline.
    Now you click the counter of unread messages. Out comes a list of unread messages. Not the messages proper. A list, including who sent them and, if that's the case, whom they reply to (not as in whom they directly reply to, as in Carol in the above example, but who wrote the top post, as in Alice in the above example).
    You can click on any item in the list. Imagine you do. You will leave the timeline view. You will be shown only that one conversation with the top post and the comments. And the view will focus on the new comment and flag it as seen, and the counter of unread messages will go down by one. You can scroll through the conversation and see the entire context in which that reply was posted.
    This is what Friendica groups, Hubzilla forums, (streams) groups and Forte groups are geared towards. They aren't group add-ons to Mastodon, and they aren't geared towards integrating perfectly into Mastodon. Remember that Friendica groups are almost six years older than Mastodon itself.
    I'm not sure how exactly Mastodon users receive replies from Friendica groups, Hubzilla forums, (streams) groups or Forte groups. One thing is certain: They will not visibly mention you. Another thing is certain: They will send you replies regardless.
    I can only guess what happens: You do get replies. But you get them as new posts in your timeline. And you have to scroll down your timeline until you stumble upon them. If you really want to participate in groups, if you really want to see everything that happens there, you'll have to scroll, scroll, scroll, scroll, scroll down your timeline until you hit posts which you know you've seen before. You probably won't be notified about these replies.
    (3/9)
    # # # # # # # # # # # # # # # # # # #

    Groups, part 2: Starting a thread


    Okay, here comes the twist. Here is where the group magic happens.
    If you want to start a new thread in that group, you have to be a member of the group account. Connected to the group account. In Mastospeak, mutually follow the group account.
    Then, if you send a new post that mentions the group account, and it is not a reply to another post, then the group account will automatically quote your post and send the quote-post with your post in it to all its connections (followers).
    You know quotes Quote-posts Like, quote-tweets What half of Mastodon is so afraid of because it's used on Twitter only to harass and dogpile people That's what I'm talking about. Friendica has had these quote-posts for almost 16 years, and never have they been used for harassment and dogpiling, for never has anyone used Friendica as a drop-in replacement for Twitter. Friendica calls them "shares". And Friendica has used these quote-posts in groups for almost 16 years.
    That is, within Friendica (and its descendants), one thing is a wee bit different: If you're on Friendica or Hubzilla or (streams) or Forte, you have to send a DM with a special mention (!group instead of group on Friendica, !group on Hubzilla, (streams) and Forte) to the group account for this to happen. This automatically activates what's "mentioned only" on Mastodon and makes your post a DM.
    But from Mastodon accounts and the like, it accepts public posts with group mentions. That's because Mastodon & Co. don't know !group and !group mentions.
    (2/9)
    # # # # # # # # # # # # # # # # # # # # # # # # # # # # Okay, I guess here's some explanation necessary from a Mastodon point of view.

    Groups, part 1: Membership


    As for a Friendica group, you can think of it as a Mastodon account, but with a little twist. In order to join that group, you follow it. And if you have your own group, you have one Mastodon account that's your personal account and another Mastodon account that's the group.
    However, Friendica is not a Twitter clone. It's a Facebook replacement, and it has been one long before cloning Twitter was considered the one thing the Fediverse does.
    Now, Twitter has followers and followed. As does Mastodon because Mastodon is a Twitter clone.
    But Facebook doesn't have followers and followed. It has "friends" which in Twitterspeak and Mastospeak are mutual followers. Thus, it's the same on Friendica.
    Friendica doesn't have followers and followed as two fully separate things and mutuals as the state when you follow someone and they follow you back. It has connections which are always mutual.
    So in order to really join a Friendica group, you must connect to it (Mastodon: follow it), and the group account must confirm the connection (Mastodon: follow you back).
    It's basically the same on Hubzilla, (streams) and Forte. Only that on these three, much unlike on Mastodon and Friendica, the account, the login and the identity are not tied together into one thing. Imagine you could have as many Mastodon-accounts-as-in-identities on one Mastodon-account-as-in-login. Imagine you could switch back and forth between fully independent identities on the same server without having to log out and back in again. Only that Hubzilla, (streams) and Forte refer to a Mastodon-account-as-in-identity as a "channel" and to a Mastodon-account-as-in-login as an "account".
    This means that on Hubzilla, (streams) and Forte, a group (Hubzilla: forum) is a channel with special settings. As a group owner, you have one account/login, and on that one account/login, you have your personal channel, and you have your group/forum channel, and you can switch between them while staying logged in.
    (1/9)
    # # # # # # # # # # # # # # # # #
    I'd like to see more of that in the fediverse features like events, groups, moderation, different roles, permissions etc. complemented by secure communication!

    The Fediverse has literally got just about of this right now. Mastodon doesn't. But the Fediverse does because there's stuff in the Fediverse, as in federated with Mastodon, that has it. And it has had all of this for longer than Mastodon has even existed.

    Friendica


    Friendica has

    Friendica is from May, 2010, over five and a half years older than Mastodon.
    It was made as an alternative for Facebook right away. It was not meant to be a Facebook clone, though, but better than Facebook while also covering all long-form blogging features.
    And Friendica is fully federated with Mastodon. You can follow Friendica accounts from Mastodon, and Friendica users can connect to your Mastodon account from Friendica.

    Hubzilla


    Hubzilla has

    Hubzilla is from March, 2016, ten months older than Mastodon. It was created by Friendica's creator by rebuilding and repurposing a fork of a fork of Friendica.
    It is considered a "decentralised social content management system" that can be just about anything you want it to be because it's so modular. Basically, what's incomplete and unstable at best and an unfulfilled promise at worst on Bonfire has been readily available and rock-solid stable for over 10 years on Hubzilla. And even more on top of that.
    Red, the Hubzilla precursor, was the first software to establish nomadic identity, something that Bluesky claims to be in the process of inventing from scratch. And that was as early as 2012.
    Hubzilla was the very first software to implement ActivityPub. And unlike Mastodon, Hubzilla implemented ActivityPub by the book and largely still does so.
    And Hubzilla is optionally fully federated with Mastodon. In fact, this comment that you're reading right now comes from Hubzilla. Like, you're directly speaking with someone on something that has absolutely everything you wish for the Fediverse to have, and that has had all of it for longer than Mastodon has existed.

    (streams), Forte


    (streams) and Forte have

    (streams) is from October, 2021. It was created by Friendica's creator as a fork of a fork of three forks of a fork (of a fork) of Hubzilla.
    Forte is from August, 2024. It was created by Friendica's creator as a fork of (streams).
    Forte was the first software to establish nomadic identity via ActivityPub.
    And both are fully federated with Mastodon (streams) optionally so, but it is by default.
    I've made a document with a series of tables which directly compare the features of Mastodon, Friendica, Hubzilla, (streams) and Forte:

    In fact, this document is on the very same Hubzilla channel that I'm commenting from right now.
    # # # # # # # # # # # # # # # # # # # # # # # # #
    Aber im Fediverse ist es sooo schlimm, weil man "belehrt" wird, dass es nicht nur Mastodon gibt. Ich kann's wirklich nicht mehr hren.

    Die Leute auf Mastodon haben sich einfach gewhnt an ihr schnes, liebes, nettes, kuscheliges, flauschiges, einheitliches Mastodon-Fediverse, das Gargron 2016 (oder 2022) als in sich geschlossenes Netzwerk erfunden haben soll. Oder sie gewhnen sich gerade daran. Genau so wollen sie es also haben.
    Erstens haben sie zuerst den Begriff "Mastodon" gelernt und mssen sich jetzt nicht nur die Mhe machen, auch "Fediverse" zu lernen, sondern dann auch noch zu lernen, da diese Begriffe nicht gleichbedeutend sind.
    Zweitens empfinden sie alles im Fediverse, was nicht Mastodon ist, als strend. berhaupt, der Gedanke, ihr schnes flauschiges Mastodon-Fediverse mit irgendwas teilen zu mssen, was nicht das schne flauschige Mastodon ist, ist zutiefst verstrend. Das wollen sie nicht. Das soll wieder weg. (Wobei "wieder" Quatsch ist: Friendica und Hubzilla, zwei der "schlimmsten Strenfriede", waren vor Mastodon im Fediverse.)
    Na ja, und drittens empfinden sie jede Erklrung, nach der sie nicht ausdrcklich gefragt haben, als bergriffig und Fedisplaining und Reply-Guying oder gar Mansplaining. Aber buchstblich niemand von ihnen wrde je auf die Idee kommen zu hinterfragen, ob das Fediverse wirklich nur aus Mastodon besteht. Das steht fr sie auer Frage, bis sie das Gegenteil erfahren.
    brigens gilt man auf Mastodon vielfach schon als Reply-Guy, wenn man jemandem antwortet, der einen nicht vorher erwhnt hat und mit dem man auch nicht beidseitig verbunden ist. Wohlgemerkt, auf Friendica und hier auf Hubzilla, wo Konversationen vllig anders funktionieren und Kommentare vllig anders verteilt werden als auf Mastodon, ist das ein ganz normaler Vorgang.
    # # # # # # # # # # # # # # # # # #

    My

    I do take alt-text and image descriptions more seriously than anyone else in the Fediverse. I'm even working on a wiki about them. But it doesn't make a difference whether I actually describe my images or not, not in terms of repeats (that's what we call boosts here). At least not on my two (streams) channels which I use to post pictures. I no longer post pictures here on Hubzilla because most pictures I'd post are sensitive in some way. (streams) can make Mastodon blank out sensitive images Hubzilla can't.
    One of my (streams) channels is jup . It specialises in 3-D virtual worlds, so that's very niche. It has 43 connections. Two are PeerTube channels. One is a podcast on Castopod. Two are groups. 13 are only inbound. Another two are my own Hubzilla channels. The rest isn't enough for me to get a significant number of repeats for any of my image posts, especially since my images probably aren't interesting for that many people to begin with.
    The other one is jup . It specialises in Fediverse memes, and as these memes are never Mastodon-centric and often not about Mastodon at all, it's very niche again. It has only 12 connections. Two are FediBuzz relays and only inbound. One is a Lemmy community, and I'm not even sure if that connection works properly I don't post to it anyway. One is a Bonfire test account that ought to be dead now. So I'm down to 8 working outbound connections at most.
    In fact, this Hubzilla channel that I'm commenting from right now must have well over 700 outbound connections, maybe over 800 by now. I could completely go out of my way describing images like in . But as you can see, not a single repeat, not even a single like. I've looked through my image posts. I couldn't find a single one with even only one measly repeat.
    Either my reach is minimal in spite of these figures. Or the topics of my image posts are so niche and obscure that they simply aren't interesting for anyone. Or there are fewer Fediverse users who appreciate my posts and my image descriptions than there are Mastodon users who mute or block me for posting more than 500 characters at once. The latter means that a proper pair of descriptions for an in-world image costs me more reach than it grants me.
    So I can't confirm that alt-text will give me more boosts.
    Still, I'll continue to refuse to post any images without what I consider sufficient image descriptions and explanations. So don't worry about that. (But no, I won't go back and add image descriptions by my current standards to my old undescribed images, nor will I go back and upgrade older, outdated image descriptions that are substandard now.)
    # # # # # # # # # # # # # # #
    People, especially those in recovery, need to have safe spaces and CWs allow for self moderation (giving the person on the receiving end control over what they allow into their space).

    Ironically, Mastodon isn't even particularly good at that. Not by overall Fediverse standards.

    How Mastodon does it


    Mastodon handles CWs by having them put into a text field that was invented on identi.ca in 2008 as a summary field. Thus, CWs have to come from the poster. And the poster has no other choice but to force the same CWs upon absolutely everyone else, regardless of whether they need that particular CW or not, regardless of what other CWs someone may need. Your posts will be over-CW'd for some and under-CW'd for others.
    What's even worse is that this and only this is deeply engrained in Mastodon's culture. From a Mastodon POV, it's completely unimaginable that it could possibly be any different. It's actually being enforced upon the whole Fediverse by Mastodon users.
    CWs would be better if they didn't come from the poster. If they were automatically generated on the reader's side, individually for each reader and their needs, based on text filtering.
    Mastodon can do that actually. But it's cumbersome. It's as cumbersome as Mastodon's filters altogether: Each keyword needs its own filter defined and adjusted. Next to no-one knows that Mastodon can do that, also because Twitter can't, and who expects Mastodon to have features that Twitter doesn't Lastly, it was introduced in October, 2022, with Mastodon 4.0, too late for it to become part of Mastodon's culture.

    How Hubzilla does it: Filters


    Now let's look at Hubzilla. (Friendica, which Hubzilla was indirectly derived from by its own creator, may be similar, but not quite as advanced can probably say more about it as a part-time Friendica user.)
    For what Mastodon's filters could do before 4.0, Hubzilla only needs one blocklist. Adding a new keyword is as easy as adding a new line to the blocklist. For reader-side CW generation which Mastodon's filters learned in October, 2022, Hubzilla has an optional extra filter list named "NSFW". It has had it from its very beginnings, and it has inherited it from Friendica. Just about everyone in the whole software family agrees: Having your own CWs generated only for you is better than having the same CWs forced upon you as upon everyone else while misusing the summary/abstract field for it.
    Hubzilla also has an allowlist for the whole channel. It optionally has one blocklist and one allowlist per contact so you can filter certain things coming from certain contacts and not coming from all the others. It supports regular expressions. And it has a very advanced filter syntax for the blocklists and allowlists that, for example, allows you to filter by whether a message is a repeat (Mastodon: boost), whether it's public or restricted, whether it's a top post or a comment, from whom it came etc. etc.

    How Hubzilla does it: Permissions


    But self-moderation doesn't stop at filters on Hubzilla. There's also the permissions system, the second-most advanced one in the Fediverse, second only to Hubzilla's own descendants, (streams) and Forte, again created by the same developer. Hubzilla's permissions system works on up to three levels: for the whole channel (Mastodon: account), for each individual contact (Mastodon: follower/followed) and often also for individual content (posts/threads, images/media/other files etc.).
    Some examples of you can do with the permissions system:
    Also, conversations on Hubzilla aren't bunches of posts loosely tied together by mentions. They're enclosed objects with exactly one post at the top and otherwise comments. All comments always have the same permissions as the top post, and this cannot be changed. This means you cannot reply to a public post with a DM. This also means that, very much unlike on Mastodon, you cannot pull someone else into a DM conversation just by mentioning them. That someone else simply isn't permitted to see anything in the conversation.
    There's even more: You don't only own your own posts. You also own all comments on your posts. You and not whoever wrote them. This means you can moderate your own conversations by deleting comments from it. (That is, if someone on Mastodon comments on your post, and you remove it, you do not delete their Mastodon toot from their Mastodon account. You only remove it from your conversation.)
    This is real serious self-moderation power.
    Hubzilla is entirely built around moderating your own channel and your own stream yourself and, if it is activated, the public stream (Mastodon: local or federated timeline, depending on the admin configuration) along with it. Mastodon's filters work by deleting stuff from your inbox, but letting it onto and keeping it on the local or federated timeline regardless. Hubzilla's filters and permissions work by rejecting it altogether. Content that you reject, and that nobody else on your hub allows in, doesn't enter the hub at all and thus doesn't show up on the pubstream either.
    By the way, this also works with forums (groups): You can make a forum private by only allowing its contacts to see its profile. You can make its membership private by only allowing its contacts to see its other contacts. You can hide it from directories. You can make its conversations private by limiting reading permission to only contacts.

    How (streams) and Forte do it


    As I've said, (streams) and Forte go another bit further.
    They don't rely mostly on templates called "roles" to define the permissions of your channel and of your contacts. You can switch individual permissions on and off anytime.
    They have an extra switch to let repeats in or not. Hubzilla needs a filter syntax line for that.
    And they have the option to make reply control even more advanced: Next to entirely allowing and entirely disallowing comments, you can allow only your own contacts to comment on a certain post. You can generally allow comments on your posts for a certain period of time. And you can allow comments on a certain post only until a certain point in the future.
    # # # # # # # # # # # # # # # # # # # # # # # # Den ewigen September haben wir lngst. Nur ist das hier der ewige November, und zwar seit November 2022. Ein bestndiger Zustrom von Newbies, die ber das Fediverse nix wissen, vor allem nicht, da es mehr ist als nur Mastodon und auch nicht auf Mastodon basiert, und von denen viele komplett lernresistent sind.
    Die Leidtragenden sind dann die, die selbst nicht auf Mastodon sind, die aber von genau diesen Leuten behandelt werden, als wren sie auf Mastodon. Oder bekmpft, weil es sie im Mastodon-Fediverse doch eigentlich gar nicht geben darf. Die sich herumrgern mssen mit Sachen, die von solchen Leuten "frs Fediverse", aber hart nur gegen Mastodon gebaut worden und zu nichts anderem kompatibel sind.
    CC:
    # # # # # # # # # # # # Das ist in der Tat eine gute Frage.
    Bei Leuten, die von Windows nach Linux umsteigen wollen, ist ja traditionell ein Problem, da sie sich nicht vorstellen knnen, da ein Betriebssystem anders funktionieren und sich folglich auch anders bedienen kann als Windows. Also erwarten sie von Linux ein kostenloses Windows ohne Onlinekontenzwang und ohne Spionage, aber ansonsten haargenau mit der UX von Windows.
    Und dann sind sie schon berfordert mit der Paketverwaltung und mit der vllig anderen Struktur des Dateisystems (oder auch nur, da sie sich jetzt mit dem Dateisystem auseinandersetzen mssen). Wenn man ihnen dann auch noch mit "diesem doofen MS-DOS-Fenster", also der Konsole, kommt, statt ihnen fr alles Klickibunti-Lsungen zu prsentieren, dann sind sie endgltig vergrault. Ach ja, und mit Quellcode und Lizenzen braucht man ihnen auch nicht kommen.
    Bei Leuten, die von wegwollen, ist es doch nicht anders. Das haben uns doch die letzten knapp vier Jahre gezeigt.
    Mastodon sieht nicht haargenau aus wie und bedient sich auch nicht so Und tsch! Ab nach Bluesky, das sieht wirklich aus wie Twitter, als Twitter noch gut war. Da mu man nicht umdenken und fast nichts neu lernen.
    Bei Mastodon "mu" man eine "Instanz" whlen Viel zu kompliziert! Bluesky stellt sich technischen Laien dagegen einfach nur als Handy-App dar, wo man sich so einfach registrieren kann wie damals auf Twitter. Ungeachtet der Tatsache, da sowohl die offizielle Mastodon-App als auch die offizielle Bluesky-App beide eine Instanzauswahl bieten, die auch noch auf beiden optional ist, weil sie eine Instanz (mastodon.social, bsky.social) voreingestellt hat.
    Auf Mastodon hat man die 800.000 Follower, die sich in 12 Jahren auf Twitter angesammelt haben, nicht innerhalb einer Stunde Da ist doch "keiner", da hat man voll keine Reichweite und keinen Fame, das lohnt sich nicht. Sieht man ja schon daran, da der Feed, h, die Timeline nicht sofort nach dem ersten Login rappelvoll mit Tweets, h, Trts ist.
    Diejenigen, die geblieben sind, sind unter entsprechend hohem Leidensdruck geblieben. Oder ihnen war und ist auch Bluesky suspekt. Oder als Bluesky aufkam, hatten sie schon mehr Interaktion, als sie auf Twitter je hatten.
    Wer also "literarisch Twitter ohne Musk" sucht und partout seinen Denkkasten nicht benutzen und sich nicht umgewhnen will, wird enttuscht werden.
    Umgekehrt kann es aber auch Leute geben, die von der Kultur auf komplett wegkommen wollen und etwas ganz anderes suchen. Die werden auf Mastodon auch nicht unbedingt glcklich werden. Gerade auf Mastodon und da vor allem auf den typischen "Anfngerservern" wie mastodon.social gibt es viele, die sich tatschlich nicht umgewhnen knnen oder wollen. Die benutzen Mastodon genau, wie sie benutzt haben. Und die verhalten sich auch wie auf . Fr die ist Mastodon "literarisch Twitter ohne Musk", nur da es eben anders aussieht.
    Vielleicht wren diese Leute auf z. B. Sharkey besser aufgehoben. Klar, Sharkey ist mit Mastodon fderiert, so da man mglicherweise auf dieselben Nasen stoen wird. Aber man ist nicht sofort von genau diesen Nasen umgeben, weil es die auf dem eigenen Server nicht gibt. Und wenn man auf diese Leute stt, hat man dann schon ein Umfeld, das einem hilft, sich gegen diese Leute zu verteidigen.
    Das Schne am Fediverse auerhalb von Mastodon ist doch: Die Leute, die einfach mit geringstmglichem Widerstand den nchstbesten -Klon haben wollen, bleiben allesamt auf Mastodon hngen. Viele von denen wissen nicht mal, da das Fediverse mehr ist als nur Mastodon. Das wollen die auch nicht hren, das berfordert sie nur. Einige drften sogar glauben, das Fediverse bestnde nur aus mastodon.social.
    Jenseits von Mastodon trifft man nur die Fortgeschrittenen an, die Ambitionierten, die wirklich etwas anderes als suchen. Die verhalten sich dann auch nicht, als wren sie noch auf . Die verhalten sich nicht mal, als wren sie auf Mastodon.
    Ich bin berhaupt dafr, mehr Leute von direkt nach etwas im Fediverse zu holen, das nicht Mastodon ist. Umgewhnen werden mssen sie sich so oder so. Aber dann gewhnen sie sich nicht an ein reines Mastodon-Fediverse, zumal etwa Misskey und die Forkeys ihnen anzeigen, von welcher Serveranwendung ein Beitrag kommt. Dann gewhnen sie sich nicht an ein Fediverse, das nur Mastodons Features hat. Dann gewhnen sie sich von vornherein an Features, die nicht hat, die Mastodon nicht hat, wo sie sich dann aber fragen, wie sie so lange ohne diese Features auskommen konnten.
    Und wenn sie irgendwann selbst Leute ins Fediverse holen, dann werden sie denen auch nicht vorgaukeln, das Fediverse sei nur Mastodon.
    CC:
    # # # # # # # # # # # # # # # # # # # # # Nein, das ist einfach nur der krasse Unterschied in Technologie und Kultur zwischen Mastodon und Hubzilla.
    Auf Mastodon wollen viele am liebsten ein reines Mastodon-Fediverse haben. Auch weil sie glauben, sie htten das mal gehabt.
    Die Hubzilla-Community dagegen stammt von der Friendica-Community ab und hat von ihr zu einem groen Teil die Attitde geerbt, sich mit allen mglichen und unmglichen anderen Netzen verbinden zu wollen.
    Viele Mastodon-Nutzer wrden am liebsten sogar alle Mastodon-Server aus ihrer Timeline verbannen, die ber 500 Zeichen erlauben. Alles, was nicht Mastodon ist, schon mal erst recht.
    Hubzilla-Nutzer schalten im krassen Gegensatz dazu ActivityPub an, um sich dann kreuz und quer ber das ganze Fediverse zu verbinden. Und dann schalten sie auch noch diaspora* an, um sich damit auch noch zu verbinden. Sie bewegen sich in drei Netzwerken mit drei Protokollen gleichzeitig (Grid mit Zot6, diaspora*, Fediverse mit ActivityPub) ohne Berhrungsngste. In vier Netzwerken mit vier Protokollen, wenn die OStatus-basierte Federation nicht im ActivityPub-basierten Fediverse aufgegangen wre. Und dann abonnieren sie RSS- und Atom-Feeds.
    Dem Mastodon-Nutzer geht der Hut hoch, wenn irgendwas in seiner Timeline von den Mastodon-Standards abweicht.
    Dem Hubzilla-Nutzer geht das Herz auf, wenn seine Autovervollstndigung Akteure mit drei verschiedenen Protokollen gleichzeitig anzeigt.
    CC:
    # # # # # # # # # # # # # # #
    Die Regeln sind nicht bei den Diensten anders, sondern generell bei jeder Instanz (unabhngig was darauf fr eine Software luft, das hat damit nichts zu tun).

    Sowohl als auch.
    Auf der einen Seite hat natrlich jeder Server seine eigenen Regeln.
    Auf der anderen Seite ist aber z. B. Friendica oder Hubzilla technologisch und konzeptionell vllig anders als Mastodon. Daher haben die beiden eine vllig andere Kultur als Mastodon. Daher wiederum haben sie auf ihren Servern vllig andere Regeln als Mastodon.
    Auf vielen Mastodon-Server besteht z. B. Alt-Text-Pflicht. Wenn man nicht alle seine Bilder mit hinreichend guten Alt-Texten versieht, wird man dafr sanktioniert.
    Auf Hubzilla wird dir das nicht passieren. Allein deshalb schon nicht, weil Hubzilla keine schicken Eingabefelder fr Alt-Texte hat, sondern man Alt-Texte hndisch in den Einbettungs-Markup-Code fr die Bilder "reinprogrammieren" mu. Bis letztes Jahr gab es nicht mal irgendeine Dokumentation, wie das geht.
    Oder CWs. Auf vielen Mastodon-Servern sind die auch Pflicht.
    Auf Hubzilla ist Mastodons CW-Feld immer noch ein Zusammenfassungsfeld. Das ist es schon lnger, als es Mastodon berhaupt gibt. Und wenn man nicht nur 500 Zeichen hat, sondern ber 16,7 Millionen, dann ergibt ein Zusammenfassungsfeld auch einen Sinn.
    CWs handhabt Hubzilla statt dessen, wie sein Vorfahr Friendica es schon seit 2010 tut: Man kann sich optional einen Textfilter aktivieren, der einem ganz individuell vollautomatisch genau die CWs erzeugt, die man selbst braucht.
    Zum einen ist man damit nicht davon abhngig, da alle immer schn brav die richtigen CWs eintragen. Sie mssen nur irgendwo im Post die richtigen Schlsselwrter haben, was sehr viel wahrscheinlicher ist. Zum anderen bekommt man auch keine CWs aufgezwungen, die man gar nicht braucht, und zwingt anderen auch keine CWs auf, die sie gar nicht brauchen.
    Das geht auch auf Mastodon, aber erst seit Oktober 2022, und von kennt man das auch nicht, also ist es nie in Mastodons Kultur angekommen. Auerdem gehrt das zu den Sachen, die auf Friendica und Hubzilla sehr einfach gehen, wo man sich aber auf Mastodon dabei einen abbricht. Wie brigens Filter im allgemeinen.
    Gerade Hubzilla hat es generell nicht so mit Regeln. Auf Mastodon hast du eigentlich nur "stummschalten", "blockieren" und "melden". Hubzilla hat ein sehr mchtiges, feingliedriges Berechtigungssystem und ist darauf ausgelegt, da man seinen Stream selbst moderiert (und damit, falls vorhanden, den Public Stream gleich mit). Die mchtigen, aber einfach zu handhabenden Filter helfen auch mit.
    CC:
    # # # # # # # # # # # # # # # # # # # # # # # Wenn man selbst nur Mastodon nutzt, fhlt es sich piepschnurzegal an. Dann nimmt man eh das ganze Fediverse als nur Mastodon wahr und die Unterschiede zwischen Mastodon und Nicht-Mastodon fast berhaupt nicht.
    Wenn man selbst aber etwas ganz anderes im Fediverse nutzt als Mastodon, dann ist es immens wichtig.
    Ich selbst bin nicht auf Mastodon. Ich bin auf Hubzilla (, , ). Das funktioniert vllig anders als Mastodon, das hat ein vllig anderes Konzept als Mastodon, das wird von Mastodon vllig unabhngig entwickelt. Es hat Features, die auf Mastodon unvorstellbar sind. Noch dazu ist es zehn Monate lter als Mastodon. Es geht sogar zurck auf Friendica, das mehr als fnfeinhalb Jahre lter ist als Mastodon.
    Aber wie du mit eigenen Augen sehen kannst, kann ich Mastodon-Trts nicht nur empfangen, sondern auch von Hubzilla aus kommentieren.
    Wenn jemand das komplette Fediverse meint, es aber "Mastodon" nennt, dann meint er mich zwar damit, spricht mich aber nicht an. Ich bin ja nicht auf Mastodon.
    Wenn jemand einen meiner Posts oder Kommentare als "Trt" bezeichnet in der Annahme, ich sei auch auf Mastodon, dann ist beides sachlich falsch.
    Wenn jemand sich wnscht, "das Fediverse" mge endlich ein bestimmtes Feature einfhren, nur weil Mastodon es nicht hat, dann kann ich mir nur vor den Kopf schlagen. In den allermeisten Fllen hat Hubzilla genau dieses Feature schon zehn Monate lnger, als es Mastodon berhaupt gibt. Sehr hufig hat Friendica dieses Feature schon etliche Jahre lnger, als es Mastodon berhaupt gibt. Das Fediverse hat dieses Feature also. Mastodon hat es nicht, aber das Fediverse hat es.
    Wenn jemand dagegen ist, da "das Fediverse" ein bestimmtes Feature einfhrt, dem sei gesagt: Hchstwahrscheinlich hat das Fediverse dieses Feature schon. Mastodon nicht, aber das Fediverse. Denn hchstwahrscheinlich hatten Friendica und Hubzilla es schon immer, also auch wieder lnger, als es Mastodon berhaupt gibt.
    Am besten war noch der Widerstand gegen Quote-Posts. "Das Fediverse" sollte die auf gar keinen Fall einfhren, sagten einige. Der Witz: Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, GoToSocial, Mitra, Friendica, Hubzilla, (streams), Forte usw., sie alle haben Quote-Posts. Und zwar schon lnger, als es diese Debatte auf Mastodon berhaupt gibt. Und sie alle (auer GoToSocial) knnen widerstandslos jeden, aber auch wirklich jeden Mastodon-Trt quote-posten.
    Oder damals der Widerstand gegen Volltextsuche. Auf gar keinen Fall sollte "das Fediverse" Volltextsuche haben. Nur hatte das Fediverse schon lngst Volltextsuche: Friendica war schon im Mai 2010 mit eingebauter Volltextsuche an den Start gegangen.
    Ach ja: Zeichenlimits. Wer "Mastodon" und "Fediverse" gleichsetzt, fr den hat auch das Fediverse ein festgelegtes Limit von 500 Zeichen. Friendica und Hubzilla hatten aber nie wirklich Zeichenlimits. In deren Kultur kommen auch keine Zeichenlimits vor. Aktuell haben sie brigens ein "Limit" von ber 16,7 Millionen Zeichen. Bis auf Threads hat alles im Fediverse ein sehr viel hheres Zeichenlimit als Mastodon. Entsprechend kriegen Nicht-Mastodon-Nutzer stndig auf den Deckel, wenn sie das angeblich von Gargron fr das ganze Fediverse festgeschriebene Limit von 500 Zeichen berschreiten.
    Also: Das Fediverse ist nicht nur Mastodon. Das Fediverse war auch nie nur Mastodon. Das Fediverse ist nicht nur ein Twitter-Klon. Das Fediverse hat sehr viel mehr Features als Mastodon. Und das Fediverse hat auch nicht berall dieselbe Kultur und wird sie auch nie haben.
    CC:
    # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
    ich werbe ins Fediverse zu kommen und sage klar das erstmal als Alternative zu FB,Insta, X etc zu nutzen und das Andere nach und nach auszufaden.

    Das Fediverse: ja.
    Aber komm nicht auf die Idee, Mastodon und nur Mastodon als alleinige Alternative zu und Facebook und Instagram zu verkaufen.
    Mastodon ist eine Alternative zu . Nicht die einzige. Eine von vielen. Pleroma, Akkoma, Misskey, Sharkey usw., sie sind auch alle Alternativen zu und besser als Mastodon. In mancher Hinsicht sind brigens Misskey und seine Forks sogar dichter an dran als Mastodon.
    Mastodon ist keine Alternative zu Instagram. Die hauptschliche Alternative zu Instagram ist Pixelfed. Man kann sogar sein komplettes Instagram-Konto mitsamt allen Bildern direkt nach Pixelfed importieren.
    Mastodon ist auch keine Alternative zu Facebook. Nein, wirklich nicht. Die populrste Alternative zu Facebook ist Friendica, das 2010 vorn vornherein als Alternative zu Facebook entwickelt wurde. Es ist also sehr viel dichter an Facebook dran als Mastodon. Wer mehr Features will und/oder mehr Sicherheit und/oder mehr Resilienz gegen Serverausfall, kann sich auch Hubzilla angucken.
    Was die Themen Synthesizer und Musikproduktion angeht: einfach mal aufhren, mit Hashtags in den ther zu rufen und zu hoffen, da die richtigen Leute anbeien. Statt dessen sich einfach mal da umzugucken, wo es ein Killerfeature gibt, auf das Mastodon nicht mal vorbereitet ist: Gruppen.
    Beispiel: Lemmy. Die primre Alternative zu Reddit im Fediverse.

    Beispiel: Friendica.

    Und falls dir das nicht bekannt sein sollte: Alles, was ich hier jetzt erwhnt habe, ist nicht nur im Fediverse, sondern das heit, es ist auch mit Mastodon verbunden. Und miteinander.
    Gru von Hubzilla brigens.
    CC:
    # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
    Wenn aber Leute, die schon lange hier sind, manche Dinge ber das FediVerse und seine Dienste tatschlich grob fehlerhaft darstellen, dann darf man das schon mal richtigstellen, finde ich.

    Und dann wirst du von den fanatischen Mastodon-Sektenanhngern wegen "Mansplaining" und "Fedisplaining" stummgeschaltet oder gleich blockiert.
    Oder es ergeht dir wie : Der hat sich mal mit einem Tech-Journalisten auf Mastodon gezofft, der der felsenfesten berzeugung war, Mastodon sei ein in sich geschlossenes Netzwerk. Crossgolf ist schon lnger auf Calckey, als dieser Journalist auch nur wei, da es Mastodon gibt. Aber der Journalist nahm fr sich die alleinige Kompetenzhoheit in Anspruch, weil er ja Journalist und somit Profi ist und Crossgolf nur Amateur.
    (Falls jetzt irgendjemand sagen sollte: "Wieso, der Journalist hat doch recht": Leute, ihr habt noch sehr viel ber das Fediverse zu lernen. Ob ihr das wollt oder nicht.)
    CC:
    # # # # # # # # # # # # # # # # #
    Das direkt wohl nicht, aber es sind immer mal wieder Leute schnell dabei neuen Leuten sehr deutlich zu beschreiben, dass dass hier nicht Mastodon heit und wie das Fediverse funktioniert und dass es noch zig andere Mglichkeiten zur Interaktion und viele viele andere Dienste gibt usw

    Das ist aber durchaus gerechtfertigt, sie so frh wie mglich darauf hinzuweisen, da das Fediverse nicht nur Mastodon ist. Du als Sharkey-Nutzer solltest das eigentlich aus eigener Erfahrung wissen.
    Klar, jemand, der nur Mastodon kennt und vielleicht noch die "Mastodon-Satelliten" PeerTube und Pixelfed, wird sagen: "Ist doch scheiegal. Lat sie glauben, das Fediverse ist nur Mastodon. Ist doch viel einfacher und sympathischer und weniger nerdy." Auch klar, fr jemanden, der nur Mastodon kennt, sieht in der eigenen Timeline erstmal alles aus wie von Mastodon. Auer vielleicht, wenn es Sachen macht, die Mastodon nicht kann, wie hier z. B. Teilzitate oder Kursivschrift oder auch nur ber 500 Zeichen. Aber auch dann wissen Mastodon-Nutzer nicht, woher es statt dessen kommt. Viele glauben, das kommt alles von irgendwelchen frisierten Mastodon-Servern.
    Diejenigen, die schon lange etwas anderes als Mastodon daily-driven, sehen das alles aber vllig anders. Die wissen aus eigener leidvoller Erfahrung, da solche Leute sich dann ber Monate oder gar Jahre daran gewhnen, da das Fediverse nur Mastodon ist und auch nur die Features von Vanilla-Mastodon hat. Wenn Mastodon-Nutzer nicht von Anfang an wissen und sich nicht von Anfang an daran gewhnen, da das Fediverse nicht nur Mastodon ist und das vllig normal ist, neigen sie dazu, das Nicht-Mastodon-Fediverse zu diskriminieren. Doch, diskriminieren. Nicht selten entwickeln sie sogar eine Feindseligkeit gegenber dem Nicht-Mastodon-Fediverse.
    Dann sehen sie Mastodon als den alleinigen Goldstandard im Fediverse an, an dem sich alles andere zu orientieren hat. Was anders ist als Mastodon, ist schlecht. Und Features, die Mastodon nicht hat (und die sie persnlich nicht unbedingt haben wollen), sind bse.
    Dann versuchen sie mit aller Gewalt, Mastodons Kultur und Mastodons ungeschriebene Regeln allen aufzuzwingen, die irgendwie in ihre Timeline gesplt werden. Es ist ihnen ja nicht klar, da das nicht alles Mastodon ist. Es ist ihnen noch weniger klar, da das nicht mal alles wie Mastodon ist, da das auch mal vllig anders sein kann als Mastodon. Vom Konzept her, von den Features her und, ja, auch von der Kultur her.
    Die wissen einfach nicht, da auf Pleroma ist, das ungefhr so alt ist wie Mastodon selbst, und wo mindestens 5000 Zeichen ganz normal sind. Die wissen auch nicht, da du auf Sharkey bist und 3000 Zeichen hast und auch das ganz normal auf Sharkey ist.
    Die wissen auch nicht, da auf Calckey ist mit, soweit ich wei, 3000 Zeichen. Er ist tatschlich schon mal angeschnauzt worden, da er seine Posts auf maximal 500 Zeichen beschrnken oder sich aus dem Fediverse verpissen soll. Glaubt ihr nicht, weil euch das noch nie passiert ist Ist aber passiert. Fragt ihn. Fragt , die ist auch auf Calckey, die wird das besttigen.
    Die wissen auch nicht, da ich auf Hubzilla bin. Da es Hubzilla schon 10 Monate lnger als Mastodon gibt und es einen Stammbaum hat, der zurckgeht bis zu Friendica von Mai 2010, also mehr als fnfeinhalb Jahre (!) vor Mastodon. Und da wir hier nicht nur ber 16,7 Millionen Zeichen haben (doch, wirklich), sondern da Hubzilla genau wie Friendica weder ein Twitter-Klon ist noch eine Immer-alles-schn-kurz-Kultur hat und noch nie hatte. Und da Hubzilla genau wie Friendica schon technologisch nicht zur Mastodon-Kultur pat.
    Auch das kann niemand nachvollziehen, der nur Mastodon kennt.
    Es kommt sogar vor, da Mastodon-Nutzer der felsenfesten berzeugung sind, Gargron habe das Fediverse als in sich geschlossenes reines Mastodon-Netzwerk erfunden. Folglich mu alles, was im Fediverse ist, was aber nicht Mastodon ist, unrechtmig da sein und ein bses Hackertool sein. Der Friendica-Nutzer jakob ist tatschlich genau deshalb mal von einer Mastodon-Nutzerin gesperrt worden, weil sie der Ansicht war, er mu ein bser Hacker sein, der sich illegalerweise mit seinem bsen Hackertool Friendica ins Mastodon-Fediverse reingehackt hat.
    Falls so jemand ein fhiger Programmierer ist, wird er mglicherweise ein Tool oder eine Website fr das Fediverse bauen. Er wird sie aber hart nur gegen Mastodon bauen. Also nicht gegen die Mastodon Client API, sondern direkt und nur gegen Mastodon und gegen Eigenarten, die nur Mastodon hat. Und er wird womglich trotzdem "Fedi" in den Namen einbauen. Wenn man ihn darauf hinweist, da es im Fediverse auch noch andere Sachen gibt, zu denen seine Kreation aber komplett inkompatibel ist, dann kann er nur mit den Schultern zucken, weil sein Werk so, wie es ist, in Stein gemeielt ist und er Untersttzung fr jede einzelne andere Fediverse-Serveranwendung nachtrglich einbauen mte.
    Wenn man Mastodon-Neulingen von vornherein erklrt, da das Fediverse nicht nur Mastodon ist, bevor sie sich an ein reines Mastodon-Fediverse gewhnt haben, dann kann man all das abwenden.
    Wenn man Mastodon-Neulinge glauben lt, das Fediverse sei nur Mastodon, dann passiert aber genau das. Und weil das beinahe alle Mastodon-Neulinge glauben und man sie auch glauben lt, ist das Fediverse ein buchstbliches Minenfeld, wenn man selbst auf etwas anderem als Mastodon ist, aber mit Mastodon kommuniziert.
    So ist Mastodon zu einem Groteil zu einer fanatisierten Sekte geworden, die dem unumstlichen Glauben anhngt, Gargron htte das Fediverse als reines Mastodon-Netzwerk erfunden.
    CC:
    (PS: Irgendjemand hier, der allen Ernstes geglaubt hat, alle erwhnten Personen und ich selbst seien auf Mastodon Seid ehrlich!)
    # # # # # # # # # # # # # # # # # # # # # # #
    Describe it as if you were on the phone and you wanted to fully explain the image to your correspondent.

    I always fully explain my images. My posts are generally about very obscure niche topics, my image posts even more so. This means I always have a whole lot to explain, sometimes on various levels (explanations of explanations of explanations of explanations).
    However, I don't describe and explain my images as if I'm on a phone. If I were on a phone, my correspondent could talk back. I could ask them inhowfar they're familiar with the topic at hand, what they need described, what they need explained and what they don't. Then I could give them a description and explanation tailor-made just for them.
    This doesn't work in the Fediverse. I don't have one correspondent, but potentially millions in the Fediverse and billions on the Web. I can't tailor one description and explanation for all of them all the same. I can't even ask them all what they need and what they want, and even if I could, I'd get lots of different replies that'd contradict each other.
    So what I do instead is write one gigantic info dump right away. It doesn't go into the alt-text, though. For one, explanations must never go into the alt-text. They must always go into the post text where everyone can access them. See also . Besides, Mastodon, Misskey and their forks cut alt-texts with over 1,500 characters off, so I can't really exceed that. But as far as I know, Mastodon allows external posts to have 100,000 characters before it rejects them, and my character limit is over 16.7 million. So I have much more space in the post than in alt-text anyway.
    When I post a meme, the image gets a regular alt-text that also transcribes the relevant bits of text verbatim, and I add an explanation section to the post text that links to whatever I can link to for explanations and explains directly what I don't have external explanations for. I've read that at least some Mastodon users prefer explanations right in the post to links because linked websites don't necessarily have to be accessible. But my experience is that if you give them the choice between one link to KnowYourMeme and seven explanations measuring over 10,000 characters, they'll prefer the link to such a monster post.
    Still, I can't always link to external explanations, so I might still have to inflate meme posts with long explanations.
    Examples:

    My original images are rendering from very obscure 3-D virtual worlds. When I post one of these, I describe it twice.
    For one, I write a full, detailed description of the entire image. I can never know if someone is curious enough to want the whole image described. Besides, more often than not, what matters in the image in the context of the post is not one specific element in the image, but the whole image, the whole scenery. This description also includes transcripts of all text within the borders of the image as long as I can read it in-world, and it includes all explanations necessary to understand the post, the image, the image description as a whole and all elements of the image description.
    The long description goes into the post text.
    As it's a hard requirement to have an accurate, sufficiently detailed image description in the alt-text if your posts reach Mastodon, I distill a shorter image description for the alt-text from the long one. It has to fit into 1,500 characters together with a note where to find the long image description. The alt-text doesn't contain any text transcripts because I can impossibly put 20 or more individual text transcripts into well under 1,500 characters.
    Examples:

    # # # # # # # # # # # # # # # # # # #

    *7 Cat Breeds with the Longest Tails

    7 Cat Breeds With The Longest Tails

    This is exactly the problem.
    I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
    I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
    For example, you can grant or deny permission to

    All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
    Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
    But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
    And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
    Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
    On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
    Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up Just copy-paste them into a text file.
    But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
    Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
    Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
    (streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
    Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
    Unfortunately, next to nobody knows.
    For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
    In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
    # # # # # # # # # # # # # # # # # # # # # # # # # # #

    ** Information Briefing: **

    Second for K-Drama "Can This be "


    Verfgbar in (lang=de)//Available in (lang=en)//Disponible en (lang=fr)

    Netflix Releases Second Long Preview for Romance K-drama Can This Love be Translated with Kim Sun Ho and Go Yoon Jung

    Aus dem Fediverse wird an vorderster Front berall nur Mastodon empfohlen. Sonst nichts. Man wird sich sehr weit durchklicken mssen, um auch nur Pleroma als Zweitalternative fr zu finden.
    Fr Nicht-Mastodon-Nutzer, denen die allgegenwrtige Mastodon-Zentrizitt und Mastodon-Normativitt und das vllige Ignorieren odar gar absichtliche Totschweigen des brigen Fediverse schon lnger gegen den Strich geht, sieht es so aus, als wrde genau das hier wieder passieren. Dabei sind die meisten Microblogging-Serveranwendungen im Fediverse Mastodon haushoch berlegen.
    Natrlich kann man jetzt sagen, da es beim Digital Independence Day darum geht, europische Alternativen zu finden und die meisten anderen Fediverse-Serveranwendungen eben nicht in Europa entwickelt werden.
    Aber: Nicht nur Mastodon wird in Europa entwickelt. Auch nicht nur Mastodon und Pleroma.
    Friendica wurde zwar von einer Privatperson in Australien erfunden, ist aber seit 2011 in deutscher Hand. Einzig die Tatsache, da Friendica weiterhin beharrlich den Code bei GitHub in den USA hostet, knnte zur Disqualifikation reichen. Aber auch Mastodons Code liegt bei GitHub.
    Hubzilla stammt ursprnglich vom selben Australier und aus derselben Softwarefamilie. Aber seit 2018 ist es in den Hnden eines deutschen Chefentwicklers, der als Vize einen Norweger hat. Auerdem liegt der Code bei Framagit in Frankreich.
    Beide sind also sehr wohl europische Projekte. Noch dazu sind beide lter als Mastodon und trotzdem mit Mastodon verbunden. Aber kurioserweise werden sie im Rahmen des Digital Independence Day nirgendwo erwhnt. Direkte Alternativen zu Facebook werden gar berhaupt nicht genannt.
    All dies pat wunderbar zusammen mit der allgemeinen medialen Darstellung und befeuert sie sogar noch weiter: Entweder ist das Fediverse gleich Mastodon. Oder es gibt kein Fediverse, nur Mastodon. So oder so wird Mastodon flschlicherweise dargestellt als a) das einzige seiner Art und b) in sich geschlossenes Netzwerk.
    Ich kenne gengend Leute, die sich genau daran sehr stren und das auch zum Ausdruck bringen.
    Nur daran stren sich dann wiederum diejenigen, die selbst praktisch oder tatschlich nur Mastodon kennen und Mastodon ansehen als Standard, Goldstandard oder tatschlich das ganze Fediverse, die auf jeden Fall aber so Sachen wie Misskey, Pleroma, Friendica und deren jeweilige Nachfahren ansehen als bse, rcksichtslose, kulturlose, unerwnschte Eindringlinge in ihrem kuscheligen Mastodon-Fediverse.
    brigens dient ein Groteil meiner Hashtags dazu, Filter auszulsen inklusive dem automatischen Erzeugen individueller leserseitiger CWs. Gerade letztere sind da, wo ich bin, schon lnger technisch mglich und Teil der Kultur, als es Mastodon berhaupt gibt. Und obwohl Mastodon sie auch hat, sind sie da nie Teil der Kultur geworden, weil sie nicht hat und auch Mastodon sie erst im Oktober 2022 eingefhrt hat.
    CC:
    # # # # # # # # # # # # # # # # # # # # # # # # # No. Very clearly no.
    People keep thinking that AI solves the alt-text problem perfectly. Like, push one button, get a perfect alt-text for your image, send it without having to check it. Or, better yet, don't even push a button, the AI will take care of everything fully automatically.
    However, at best, AI-generated alt-text is better than nothing. Oftentimes, AI-generated alt-text is literally worse than nothing.
    First of all, AI does not know the context in which an image is posted. But an alt-text should always be written for a specific context because it usually depends on the context what needs to be described at all and on which level of detail.
    This means that AI tends to leave out details that may be important while describing details that literally nobody is interested in.
    AI can't take your target audience/your actual audience into consideration either. It can't write an alt-text specifically for that audience, fine-tuned for what that audience knows, what it doesn't know and what it needs and/or wants to know.
    Worse yet, AI tends to hallucinate. It tends to mention stuff in an image that simply isn't there. It tends to describe elements of an image falsely. You could post a photo of a Yorkshire terrier, and the AI may think it's a cat because it can't distinguish it from a cat in that photo.
    Seriously, AI may get even descriptions of simple images of very common things wrong. If you post images with very obscure, very niche content, AI fares even worse because it knows nothing about that very obscure, very niche content.
    If you post a screenshot from social media, AI will not necessarily know that it has to transcribe the text in the screenshot 100% verbatim. And just pushing one button or running AI on full-auto, the thing that so many smartphone users are so much craving for, will not prompt it to do so.
    If you want good, useful, accurate, sufficiently detailed image descriptions that match both the context of your posts and your audience, you will have to write them yourself.
    Trust me. I know from personal experience. I post some of the most obscure niche stuff in the Fediverse. And I've pitted an image-describing AI against my own 100% hand-written image descriptions twice already. The AI failed miserably to even come close to my descriptions in both cases.
    # # # # # # # # # # # # # # Eigentlich bruchten wir mehr Vergleichstabellen und auch Vergleichsvideos: Mastodon vs. andere Fediverse-Anwendungen. Videos vor allem fr diejenigen, die nur Twitter und Mastodon kennen und nicht die Aufmerksamkeitsspanne haben, um mehr als 500 Zeichen lesen zu knnen.
    Die Videos mte es jeweils in zweifacher Ausfhrung geben. Einmal informativ fr diejenigen, die wirklich neugierig sind.
    "Von Mastodon nach Sharkey: So gelingt der Umstieg auf die mchtigste Microblogging-Anwendung des Fediverse"
    Idealerweise wrden hier auch die kommerziellen, zentralistischen Dienste zum Vergleich rangezogen fr diejenigen, die im Kopf immer noch da sind. Z. B. , Mastodon und Sharkey. Oder , Mastodon, Facebook und Friendica, damit die Leute begreifen, da vieles, was auf Friendica anders als auf Mastodon ist, daher kommt, da es Facebook nachgeahmt ist und Facebook wiederum in diesem Punkt anders als ist.
    Auerdem reierisch fr die Mastodon-Fanbois und -Fangurls, die Mastodon als unschlagbar und perfekt ansehen, aber immer aus der Sicht von jemandem, der Mastodon schon kennt und die jeweils andere Anwendung gerade neu entdeckt hat:
    "Mastodon vs. Hubzilla: Der FEDIVERSE-ALLESKNNER, der Mastodon VOLL FETT KRASS HART IN DEN ARSCH FICKT!"
    CC:
    # # # # # # # # # #


    <>


    Last updated: 2026-01-13






    Why you need new friends