Find the latitude of any place.  

Phi Long Chin thn i lnh

2) None of the solutions feel very approachable. Documentation is thin, and examples are hard to find. Beyond the text of FEP-ef61, where should I go if I want to start building support into my own apps

There isn't much documentation because everything is still very new and also due to the nature of what has already been made with nomadic identity via ActivityPub on which base and which level of stability.
Yes, there's Forte. Yes, it uses ActivityPub for nomadic identity. Yes, it has a stable release.
But: It has never been an ActivityPub project that went nomadic.
It evolved from the Red Matrix (2012)
to Hubzilla (2015)
to some intermediate stuff (2018-2021)
to the streams repository (2021)
to Forte (2024)

So Forte looks back at 13 years of multiple identities per account and nomadic identity. When Hubzilla became the first Fediverse server application to adopt ActivityPub in 2017, the family had already had nomadic identity for over four years.
Implementing nomadic identity via ActivityPub meant switching the whole thing away from a protocol that was built around nomadic identity and over to ActivityPub while keeping nomadic identity.
What you seem interested in is what is working on on Mitra. And that's to take a non-nomadic, ActivityPub-only, account-equals-identity server application and make it nomadic.
AFAIK, this is still highly experimental. It's done in a development branch of Mitra. I know that Mitra understands Forte's nomadic identity, but I can't even say whether that dev branch of Mitra is actually nomadic, as in whether you can clone an identity on one server running the dev branch to another such server and have them sync back and forth.
If anything, this would be what ActivityPub devs looking at nomadic identity should check out. "Would" because it's still in such an early and experimental state that I think there isn't anything worth looking at yet other than how to make your software recognise Forte's nomadic channels as nomadic.
By the way, silverpill is publishing FEP after FEP in which Forte or Mitra, (streams) and Forte are mentioned as implementations at most. So he doesn't just code stuff together, he also tries hard to make it "official" by casting it into FEPs. So I guess he's still figuring out the basics and documenting them rather than getting actual nomadicity to work out of thin air.
You've basically got two options if you want to turn non-nomadic, ActivityPub-only, account-equals-identity software into something that's every bit as nomadic as Hubzilla, (streams) or Forte.
Either you wait until silverpill rolls out the first stable release of Mitra with full-blown nomadic identity of its own. And then there should be quite some documentation on how it was done.
Or you make an experimental nomadic branch of Bandwagon and join silverpill and in getting nomadic identity via ActivityPub going.
# # # # # # # # # # # # # # #

Phi Long Chin thn i lnh tr v thy c nh tan ntcha

Phi Long Chin thn i lnh tr v thy c nh tan nt cha Tnn Phim: Chin thn Hi Sinh, Cn Qut Thin H Siu Phm n tng to v chng n Xin VUA PHIM TNG HP PHIM ... Your browser does not support HTML video. Phi Long Chin thn i lnh tr v thy c nh tan nt cha xin cho

Ideally, they'd flip Mastodon two birds at once and move to somewhere in the Fediverse that not only is not Mastodon, but that's very much not Mastodon. (This is where I really wish there was a native and fully featured iPhone, iPad and Android app for (streams) and/or Forte.)
The problem, however, is that the density of people who think "Fediverse" refers to only Mastodon is very high on mastodon.social, home of newbies, n00bs and those who basically want Twitter without Musk.
# # # # # # # # # # # # # # # # # Allow me to take a look at this from a Hubzilla/(streams)/Forte point of view.

The Sin of Overwhelming Complexity: Instance Selection Paralysis


The only way to really combat this effectively is by hiding the whole concept of servers/instances at first, railroading everyone to a server and only letting them know about decentralisation and servers/instances after the fact.
In theory, this could be doable with Hubzilla, (streams) and Forte, and even better than with Mastodon with its themed servers. It wouldn't make sense to offer Hubzilla, (streams) or Forte servers for certain topics or target audiences, seeing as the whole thing would become moot the very moment when you make your first clone on another server. Simply build a kind of "automatic on-boarder" that sends everyone to the geographically closest open-registration server.
In practice, that'd be a bad idea, but for a different reason than on Mastodon. And that's how these servers tend to be very different. Not in topic. Not in target audiences. Not in rules. But in features. Hubzilla is modular, (streams) is modular, Forte is modular, and each admin decides differently on which "apps" to activate. Then you want to join Hubzilla for one cool feature, but the on-boarder railroads you to a server where that very feature isn't even activated.
Sure, the on-boarder could include the option to select certain features that you absolutely must have in your new home and then pick a server that has them. But that'd be extra hassle and extra confusing.
Besides, where'd you put that on-boarder On the official Hubzilla website Haha, no can do. It's all just dumb old static HTML with a CSS. If it's even HTML and not Markdown or BBcode, that is. You couldn't add scripts to it if you tried.
Oh, and (streams) and Forte don't even have official websites. And (streams) will never have one, seeing as it's officially and intentionally nameless, brandless and totally not even a project. Their "websites" are readme files in their code repositories on Codeberg.

The Sin of Inconsistent Navigation: Timeline Turmoil


The streams on Hubzilla, (streams) and Forte are quite a bit different from Mastodon timelines.
First of all, what you usually don't have on public servers is the counterpart to Mastodon's local timeline and Mastodon's federated timeline. On all three, this would be only one stream, the "public stream" or "pubstream". It can be switched by the admin to either what'd be local or what'd be federated. However, public servers usually have it off entirely. Unavailable even to local users. That's because the admins don't want to be held liable for what's happening on the pubstream.
Technically speaking, you only have one stream on a public server, and that's your channel stream. It's much more efficient than a Mastodon timeline because it always shows entire conversations by default instead of detached single-message piecemeal, and because it has a counter for unread messages which even lists these unread messages for you to directly go to the corresponding conversation. But that's another story.
However, your channel stream can be viewed on your channel page, conversation by conversation, or it can be viewed on the stream page as an actual stream with all conversations shown in a feed/timeline-like fashion, one upon another, and with its own set of built-in filters such as "only my own messages" or "only conversations started by members of one particular privacy group/access list" or "only conversations from one particular group actor". It's actually much more convenient than any Mastodon timeline, but for those who want a Twitter clone for dumb-dumbs, it can be very overwhelming.
Yes, Hubzilla, (streams) and Forte are much more complex in handling than, say, snac2. But they're also much more complex in features than snac2. That power is their USP. And that power must be harnessed somehow.

The Sin of Remote Interaction Purgatory: Federation Gymnastics


Sure, Hubzilla, (streams) and Forte have some of the best built-in search systems in the whole Fediverse. They can pull almost everything onto your channel stream just by searching for it. And if it has replies, chances are they pull these in as well.
But still, they're geared towards desktop users. They still require copy-paste. Phone users don't copy paste. Most of them don't even know the very concept of copy-paste. For most of those who do, copy-paste is much too fumbly if the input device available to them is a 6" touch screen.
You can't blame them, though. This is next to impossible to do any differently. I mean, you won't see a button magically appear with which you can pull in just that one post or comment you want to pull in.
Rather, the issue is that they can only reel in almost everything. Sometimes the search returns nothing, like a void. Sometimes the search runs indefinitely without any kind of result. This may be because someone has blocked your channel, because someone has blocked your entire server, because the server someone is on has blocked you or your entire server, because Hubzilla/(streams)/Forte doesn't understand the URI pasted into the search field or whatever.
So this is made worse by Hubzilla, (streams) and Forte not knowing what they can search for, what they can't and why not.
Connecting with someone whom you encounter on your channel stream is fairly easy. Connections can be initiated with only two clicks. Either you click their long name, and you're taken to a pretty much distraction-less local "intermediate page" with a striking green button that's labelled "+ Connect". Or if you don't want to leave the channel page, you hover your mouse cursor over their profile picture, click on the little white arrow that appears, and you get a small menu that offers you the "Connect" option as well. Granted, even some veterans don't know the latter trick because it isn't immediately advertised on the channel page.
Also, sure, you don't simply follow them right off the bat with nothing else to do like on Mastodon. You're taken to your Connections page, and you have to configure the connection (you don't have to do that on Mastodon because you can't configure connections on Mastodon).
Following accounts/channels from the directory is a bit easier. The green "+ Connect" button is there right away (unless you're already connected). However, Hubzilla's directory only lists channels based on the Nomad protocol, i.e. Hubzilla and (streams) channels, because ActivityPub is only implemented in an optional, off-by-default-for-new-channels add-on whereas it's in the core and on by default on (streams) and the only available protocol on Forte.
Importing contents or following actors when seeing them locally on other servers without copy-pasting and searching can be done. It requires OpenWebAuth magic single sign-on, however, and it requires it to be implemented on all servers of all Fediverse server applications from Mastodon to WordPress to Ghost to Flipboard. Hubzilla, (streams) and Forte are the only Fediverse server applications with full (client-side and server-side) OpenWebAuth implementations. But that's of little use if the rest of the Fediverse doesn't have server-side implementations, and Mastodon has even silently rejected a mere client-side implementation already developed to a pull request two years ago.

The Sin of DM Disasters Waiting to Happen


I think this is less of an issue on Hubzilla, (streams) and Forte because they handle DMs differently from Mastodon (which "the Fediverse" actually refers to in the article).
On all three, DMs are integrated into their extensive, fine-grained permissions system in which everything is only public if it's really public. The difference between a post and a DM is not just a switch.
If I want to DM you, I can either tag you !benpatemastodon.social rather than url=https://mastodon.social/benpateBen Pate /url. Then you're a) the only one to whom the message is sent (it literally doesn't even go out to any other server than mastodon.social plus my clone on hub.hubzilla.de as can be seen in the delivery report) and b) the only one who is granted permission to view the message.
Or I can use the padlock icon and select you from the opening list as the sole recipient. The very moment that I select certain recipients, the post I'm composing quits being public, and the padlock icon switches from open to closed. This isn't a one-click or two-click toggle. You don't do that casually. It's basically configuration. It requires so many mouse clicks that you do it consciously and intentionally. If you want to post in private, you have to really want to post in private.
Better yet: You can default to posting only to a certain limited target audience. In fact, by default on a brand-new channel, you only post to the members of one privacy group/access list (which is a Mastodon list on coke and 'roids). You have to manually reconfigure your new channel if you want to post to the general public by default.
If you preview your post, you can see whether it's a direct message to one or multiple single connections (envelope icon next to your long name), a limited-permissions message to one or multiple privacy groups/access lists/group actors (closed padlock icon) or actually public (no icon).
Even better yet: Posts to group actors generally aren't public. Posts to at least Friendica groups, Hubzilla forums, (streams) groups and Forte groups are never public. They do not go out to your followers as well unless they're connected to the same group. And this is independent from whether a group is public or private. You can't accidentially post to a group actor in public, and if you do, you don't post to that group actor at all, at least not in a way that makes the group actor forward your post to its other connections.
Granted, what does not happen is your background switching from your background colour or background image (which can be user-configured) to red #800000 or a yellow-and-back chevron pattern when you change visibility and permissions to something that isn't public.

The Sin of Ghost Conversations and Phantom Follower Counts


And again, when says, "the Fediverse", he almost exclusively means Mastodon. He writes as if the entire Fediverse handled conversations as terribly as Mastodon, as if the entire Fediverse was as blissfully unaware of enclosed conversations as Mastodon. Which is not the case.
Hubzilla, (streams) and Forte, as well as their ancestor Friendica, handle conversations in ways that exceed Mastodon users' imaginations and wildest dreams by magnitudes. Unlike Mastodon, they know threaded conversations, and they see them as enclosed objects where only the start post counts as a post, and everything else counts as a comment.
This means that once you've received a post on your stream, you will also receive all comments on that post, regardless of whether or not you follow the commenters, regardless of whether or not they mention you. That's because all four reel in the comments not from the commentors, but from the original poster who is perceived as the owner of the thread. Only blocks or channel-wide filters can prevent comments from coming in.
Beyond that, (streams) was the first to introduce . Forte inherited them from (streams), and when they were defined in , Hubzilla implemented them, too.
Here on Hubzilla, I can see all comments in this thread because my channel has fetched them directly from . And I can actually see them right away because that's the default view here on Hubzilla, rather than Mastodon's piecemeal.
Even if you import a post manually using the search feature (and you better import the actual start post), AFAIK existing comments will eventually be backfilled. Comments that come in after importing will definitely end up on your stream as part of the thread.
So this is not a shortcoming of the Fediverse. The Fediverse has been able to do better for 15 years. It's a shortcoming of Mastodon.
The only "issue" here may be that it sometimes takes some time for a comment to show up for some reasons. But unless there are blocks or filters in play, it eventually will.

The Sin of Invisible Discovery: The Content Mirage


I'm not going to pick on the audacious implication that "Eugen and team" invented the Fediverse.
But Tim writes like literally everyone wants "the Fediverse" (read, actually Mastodon) to be literally Twitter without Musk.
Also:

Oh, and none of them has an explicit opt-in switch to soothe panicking Twitter converts because panicking Twitter converts have never been the primary target audience of either of them.
Instead, on Hubzilla, whether someone can find your content depends on whether they've got permission to view it in the first place ("Can view my channel stream and posts"). If it's public, they have it. Full stop. Public is public is public. Stop whining. You've made it public, now deal with everything being able to see it.
(streams) and Forte behave the same. In addition, they have an extra permission: "Grant search access to your channel stream and posts". This controls who may search your channel stream using your own local search feature while visiting your channel locally. Something that isn't even possible on Mastodon.
As for not having any content on my channel stream before I connect to anyone: I, for one, do not want some algorithm to force content upon me that I'm not interested in. Full. Frigging. Stop. I want to have full and exclusive control over what I see and what I don't.

The Sin of User Discovery Hell


Can it really be that Mastodon's directory is so much worse than Friendica's, Hubzilla's, (streams)' and Forte's directories I guess it is because it really only lists local accounts on that one particular server. A side-effect of Mastodon being a microblogging service and Twitter clone. And not a full-blown, fully-featured social network and Facebook alternative. No, seriously, it isn't that.
Friendica is. It was designed as such. It was designed to take Facebook's place, and not by aping and cloning Facebook, but by being better than Facebook.
The directory on each node is decentralised. It lists all actors known to that node. What's outright unimaginable from a Mastodon point of view: It takes the keywords in the profiles into account. Better even: It ranks suggestions by the number of matching keywords.
Want something centralised instead Try the . Looking for people Looking for news accounts Looking for groups There are specialised tabs for that. Friendica can tell them apart, and so can the Friendica Directory.
Caveat: The Friendica Directory only lists Friendica accounts. Friendica's built-in directory should list everything it knows. I haven't used Friendica in many years, but I guess this even includes diaspora* accounts because why not
Hubzilla has indirectly inherited its directory from Friendica.
Again, it lists local as well as federated channels. You can choose whether to see only local channels ("This Website Only") or federated channels as well. You can choose whether channels flagged NSFW shall be listed or not ("Safe Mode"). You can choose to only have group actors listed that let themselves be listed ("Public Forums Only"). You have a cloud of keywords from the keyword lists in the profiles that you can filter by (Mastodon doesn't even have keyword lists in profiles). You have full-text search for names and keywords. There's even a Facebook-style suggestion mode that proposes connections to you with a ranking based on your keywords and their keywords as well as the number of common connections, and that still has the same filters.
Caveat this time: Hubzilla's directory only supports the one sole protocol built into Hubzilla's core. And that's Zot6. This means that Hubzilla's directory only lists Hubzilla and (streams) channels because Hubzilla and (streams) are the only Fediverse server applications that support Zot6.
(streams) and Forte have inherited their directories again. And they probably have the most powerful decentralised directories in the entire Fediverse. I'd give you a link, but (streams) directories generally aren't public only local channels can access them.
These directories are similar to the ones on Hubzilla. You see local and federated actors, and you can choose to only see local actors ("This Website Only"). You can choose to only see group actors ("Groups Only"). You can choose to not see channels flagged NSFW ("Safe Mode"). What's new: Inactive actors can be kept out, too ("Recently Updated").
Now it comes: (streams) has ActivityPub built into its core, and it's on by default on new channels. Forte is entirely based on ActivityPub.
This means that their directories can list anything from anywhere that uses ActivityPub. "Groups Only" gives you Guppe groups, Lemmy communities, /kbin and Mbin magazines, PieFed communities, Mobilizon groups, Flipboard magazines, Friendica groups, Hubzilla forums, (streams) groups, Forte groups etc., all on one list.
(streams) has a slight edge over Forte here because it also lists Hubzilla and (streams) channels that have ActivityPub off such as the Streams Users Tea Garden where ActivityPub was turned off with the very intention to keep Mastodon out.
If there was a gigantic Forte server, as big as mastodon.social, and its directory was accessible to the public, that directory would be the best directory in the Fediverse for anything really. If it was on (streams), it would list more, but it would confuse some users of e.g. Mastodon who'd try to follow Hubzilla or (streams) channels that have ActivityPub off. Forte simply doesn't list these because it can't find them.
A global directory of everything sounds like a good idea, but it's next to impossible to implement.
Either the directory would go look for actors itself. In order to do that, it would have to know within a split-second not only whenever a new actor is created somewhere so it can index that actor right away, but also whenever a new server is spun up so that the admin actor can be indexed, and that server can be watched. How is it supposed to know all that
Well, or the directory, a single, monolithic, centralised website, would have to be hard-coded into all Fediverse server software. That way, each server could immediately report newly created actors to the central directory upon their creation.
For starters, this would make the whole Fediverse depend on one single centralised website under the control of, if bad comes to worse, one person.
Besides, this would be a privacy nightmare. Let's suppose I create a new (streams) channel that's supposed to be private. Its existence and all its properties would be sent to the central directory before I can set it to private and restrict its permissions. This wouldn't be so bad on Hubzilla because I'd make the channel private before I turn on PubCrawl and make the channel accessible to the directory in the first place because the directory would only understand ActivityPub.
Of course, the directory would mostly be built against Mastodon. It would not understand the permissions systems implemented on Hubzilla, (streams) and Forte, and it might happily siphon off the profiles of channels where access to the profile is restricted and make them publicly accessible. On the other hand, this is likely to mean that the directory couldn't read most of Hubzilla's, (streams)' and Forte's profile text fields anyway because Mastodon doesn't have them.
But such a centralised directory wouldn't make connecting to other users that much easier and more convenient. You'd still have to copy and paste URLs or IDs into your local search and search for them (unless you're on Friendica, Hubzilla, (streams) or Forte where you can connect to URLs directly). At the very least, you should be able to go to the centralised directory and follow anyone just by clicking or tapping them. That, however, would require OpenWebAuth support on both your home server and that directory.
Ideally, that directory would be firmly built into all instances of all Fediverse software from snac2 to Mastodon to Hubzilla, even replacing any existing directory to confuse people less. But that would make the Fediverse even more dependent on one central website and its owner, something which should be avoided at all cost.
Lastly, nothing can ever be built into all instances of all Fediverse software. Remember that there's software with living instances that's barely being developed such as Plume. There's even software with living instances that's been officially pronounced dead such as Calckey, Firefish or /kbin. How are Firefish servers supposed to implement such a feature if nobody maintains Firefish anymore, and even the code repository was deleted
CC:
# # # # # # # # # # # # # # # # # # # # # # # # # #

Hes here in DFW now But he wont be for long

Hahaha.
Tell you what: has decentralised Fediverse identities as early as 2011. He invented nomadic identity (, ) almost five years before Mastodon was made. And he first implemented it in 2012 on what would later become Hubzilla (, ). That was still almost four years before Mastodon was launched.
Oh, and by the way: Hubzilla is very much part of the Fediverse. It is very much (albeit optionally) connected to and federated with Mastodon. I am replying to you right now from a Hubzilla channel which simultaneously and identically resides on two independent servers.
Nomadic identity is reality now. It is being daily-driven right now, and it has been daily-driven since long before Solid was even announced.
Solid is nothing but Hubzilla or (streams) or Forte (both are descendants of Hubzilla by Hubzilla's creator) as ordered from wish.com. A cheap and shoddy knock-off.
CC:
# # # # # # # # # # # # # # You would still need write permission to lemmy.world's local database. For that, a local user account on lemmy.world would be a hard requirement. Local actions saved in a Lemmy database cannot reference a user in a database on a wholly different server running under a wholly different domain.
This would require
A clone before your visit sounds more practical, but it's non-sense. It simply isn't doable. How is your Mastodon instance supposed to know before the fact which Fediverse servers you want to visit and interact with like with a local account
"Drive-by cloning" during your first visit is more doable. But cloning takes time. And I'm talking from personal experience here. I myself have cloned a number of Hubzilla and (streams) channels over the years. It always took quite a bit of time to sync all the contents from one server to the other one. And none of them were even nearly as active as your Mastodon account.
Granted, cloning from Mastodon to Lemmy would be quick because Mastodon and Lemmy have next to nothing in common. Lemmy would have no use for your toots, for your images, for your followers and followed.
But let's suppose I post a (non-federating) , I advertise it in a federating post, and it sounds interesting to you. Then you'll have to come over to hub.netzgemeinde.eu to read it because, again, the actual article doesn't federate to your Mastodon timeline. Upon visiting hub.netzgemeinde.eu, j12t.social would automatically register a local user account on hub.netzgemeinde.eu and then clone your entire Mastodon account into a Hubzilla channel. And I mean pretty much all of it. This would take considerable time.
Also, drive-by cloning would have quite a few other disadvantages.
In particular, it would bog Fediverse instances down. Anyone who visits them would have their account or channel drive-by-cloned. Every Fediverse instance would have a clone of each visitor's account or channel. With all their posts and comments and DMs and all their files on it. And these clones would be sync'd with their main instances all the time.
This would also mean the end of tiny, self-hosted single-user servers like yours. Everyone who even only goes check your Mastodon profile locally on your server (and on some Fediverse server applications, that's the only way, for there's no viewing remote profiles locally) would have their account or channel drive-by-cloned.
If your account is popular enough, you'd end up with maybe tens of thousands of local user accounts with clones of other people's Fediverse identities, with all their posts and comments and DMs, with all their images and other files. And j12t.social would be pelted with nomadic syncs of all these identities all the time.
You want to use any Fediverse server like with a local account, but with your j12t.social identity Then grant everyone else the same wish. And order a big honkin' rack server for your single-user server because it won't stay single-user for long.
# # # # # # # # # # # # # # #
I'm going to dig into FEP-ef61 (which is what I think Forte and Mitra are supporting) to see if I can make it work on my side, too.

Yes, FEP-ef61 is one out of a whole bunch of FEPs brought forward by Mike and silverpill and an important key to nomadic identity via ActivityPub.
Once there's a stable actually nomadic Mitra release, we'll also have a first successful case of a conversion of non-nomadic, ActivityPub-only software to nomadic, i.e. something that other devs could look at to see how it can be done.
# # # # # # # # # # #
So, is Zot the one true way to get this done

No longer as I've pointed out in my first comment.
Created (actually forked*) in August, 2024, there is , the youngest member of 's software family that started in 2010 with what is now known as Friendica. It is also the first and only member of the family that only supports ActivityPub and has done so since its very inception.
Forte is the very first Fediverse software to fully rely on ActivityPub and only ActivityPub for nomadic identity. What Hubzilla and (streams) do via two versions of the Nomad protocol, Forte does entirely via ActivityPub and only ActivityPub. All support for the Nomad protocol has been removed.
In March, 2025, Forte officially had its first stable release. It is no longer experimental. It is now daily-driver-grade software.
This means that a stable point release with a full implementation of nomadic identity via ActivityPub, including cloning, exists.
There is another implementation of nomadic identity via ActivityPub in the making: , creator and maintainer of , was the first to want to use ActivityPub for nomadic identity. This time, the idea was not to take something nomadic and convert it to "ActivityPub only". It was rather to make something non-nomadic nomadic without rebuilding it against the Nomad protocol with ActivityPub as a secondary, non-nomadic protocol.
Currently, only a development version of Mitra really supports nomadic identity via ActivityPub. Inhowfar this version is nomadic itself, i.e. whether it's actually possible to clone Mitra identities across multiple instances running that development version, I don't know. After all, this is also the first attempt at converting something non-nomadic where the account/login equals the identity in the stable version into something nomadic.
See, there are two big hurdles to take from how most of the Fediverse does it to full-blown nomadic identity. Almost everywhere in the Fediverse, your login and your account is your identity. They're fully inseparable. So in order to go fully nomadic, your identity must be uncoupled not only from the server you're on, but also from your account/login.
Hubzilla did it first back in 2012 when it was still named Red. On one account on one server, you can have as many fully independent identities ("channels") as you want. Each one of them is like a full-blown account elsewhere, only that they're all on the same account, and you can switch back and forth between them without logging out and back in. Nobody can even tell that your channels are all on the same account.
Now, nomadic identity goes much further than just moving your identity to another server. Moving is a side-effect of the actual killer feature of nomadic identity: cloning. A clone is a live, hot, near-real-time, bidirectional backup of your channel on another server, but with the exact same identity as the main instance of your channel. And you can even log into your clone and use your clone like you can use the main instance of your channel.
Let's play this through under the assumption that Mastodon is nomadic.
So you're benpatemastodon.social. In this example, Mastodon is like Hubzilla, (streams) and Forte, and it has channels just the same. benpatemastodon.social is not your account. It's a channel on your account on mastodon.social.
Now you create an account on mas.to. You need to have a channel on that account. So you clone your benpatemastodon.social channel. The identity of the clone remains benpatemastodon.social even if it's on mas.to.
Now you toot something on mastodon.social. That toot is automatically sync'd over to mas.to. But it only goes out once.
You change something in the settings on mastodon.social. Those changes are automatically sync'd over to mas.to. The clone is always kept identical to the main instance in near-real-time.
This actually works both ways: You can log into the clone, toot, follow people, change settings, whatever, and it will be sync'd to the main instance.
In fact, if mastodon.social goes offline for a while, you can use your clone on mas.to regardless of the main instance being offline. When mastodon.social comes back online, everything that has happened on your clone on mas.to during the downtime is sync'd over to your main instance on mastodon.social.
Oh, and: You can make one of your clones your new main instance which changes your identity to based on the server with the new main instance (benpatemas.to) and demotes your previous main instance (should it still be online) to a clone.
Moving a channel actually involves cloning it:

So moving using nomadic identity has two advantages over moving the "traditional" way. One, you actually take everything with you. (Only exception on Hubzilla, (streams) and Forte: Which "apps", i.e. optional extra features, are activated is not cloned.) Two, you actually move, as in you don't leave a dead account/identity behind.
*Forte is a fork of the streams repository which is a fork of a fork of three forks of a fork (of a fork) of Hubzilla which, in turn, was renamed and enhanced from a fork of a fork of Friendica.
# # # # # # # # # # # # # # # Long Das klingt so, als wenn ihr einerseits ber jede Kleinigkeit berichten werdet, die Mastodon betrifft.
Aber wenn Mike Macgirvin und silverpill die nchste groe technische Revolution im Fediverse perfekt machen und das nomadische Klonen zwischen Forte und Mitra ermglichen (ist tatschlich eins ihrer nchsten Ziele), dann werdet ihr das komplett ignorieren. Forte Mitra Kennt keiner, nutzt keiner, ist es nicht wert. Erst wenn Mastodon nomadische Identitt und Klonen ber Serverarten hinaus einfhrt (wird es nie, aber mal angenommen), werdet ihr darber berichten und es so aussehen lassen, als htte Mastodon berhaupt erst die nomadische Identitt im Fediverse eingefhrt, weil ihr nicht mal Hubzilla (das nomadische Identitt schon lnger hat, als es Mastodon berhaupt gibt) auch nur in einem Nebensatz erwhnt. Kennt ja keiner, nutzt keiner, interessiert keinen.
Das ist alles andere als ausgewogene Berichterstattung. Das ist Mastodon-Propaganda.
CC:
# # # # # # # # # # # # # # # # # # The first step is already done:
, most recent project from the same family that started with Friendica 15 years ago, is the first and only stable Fediverse server application that uses ActivityPub for . Nomadic identity itself is a concept created by Mike in 2011 and first implemented by himself in 2012 in a very early version of Hubzilla which he called Red back then.
This means that you can have the exact same channel/identity (think Mastodon account, but without its own login) on multiple server instances with one account each. If one server goes down, you still have at least one clone (depending on how many clones you make).
is working on implementing this on . It's still only available in development versions, though. The difference is that Mike had already created a whole bunch of Fediverse server applications with nomadic identity since 2012 he "only" had to port nomadic identity from the Zot or Nomad protocol to ActivityPub. Silverpill, on the other hand, has to implement nomadic identity in something that was built upon ActivityPub with no nomadic identity.
Both recognise each other's nomadic identities. (For comparison: Mastodon doesn't recognise any nomadic identities. It takes the two instances of this Hubzilla channel of mine for two fully separate identities.) But that's all for now.
The next step, and that's way into the future, would be to be able to clone from Forte to Mitra or from Mitra to Forte. This would give you one identity on at least two server instances of two separate Fediverse server applications.
The obvious downside is that you won't be able to take everything with you everywhere when you clone to other server types. For example, if you clone a Forte channel to Mitra, you won't be able to take your permissions settings, your permission roles, your friend zoom settings, the contents of your cloud storage, your CalDAV calendars and your CardDAV addressbook with you over to Mitra. That's simply because Mitra doesn't have any of these features.
What you envision is another step further. And that's the adoption of nomadic identity via ActivityPub and ideally also OpenWebAuth magic single sign-on, another one of Mike's creations, by all Fediverse server applications. And I mean all of them. Including extremely minimalist stuff like snac2 or GoToSocial. Including stuff that isn't actively being worked on like Plume. Including stuff that's dead, but that still has running servers, like Calckey, Firefish or /kbin. And including Mastodon which stubbornly refuses to make itself more compatible with the "competition" in the Fediverse and adopt technologies created by anyone else in the Fediverse, even more so if that someone is Mike Macgirvin.
In other words, this won't happen. Mastodon would rather turn itself into its own federated walled garden by becoming incompatible with all other ActivityPub implementations.
What many Mastodon users who know nothing about decentralisation wish for is another step further. And that's to create one account on one server instance of one Fediverse server software, no matter which, and then to have full-blown user permissions on any instance of any Fediverse server software.
Like, create one account on mastodon.social, go to a Pixelfed instance, post pictures Instagram-style, go to a PeerTube instance, upload videos, go to a WriteFreely instance, blog away, go to a Hubzilla hub, build a webpage, all with only your mastodon.social login.
Of course, this is impossible to do. This would mean that if you create an account on one Fediverse server instance, it would have to be cloned to all 30,000+ servers in the whole Fediverse instantaneously. And if you start your own instance, it would have to trigger 30,000+ servers to clone their tens of millions of accounts and channels over to your instance.
Usually, when I explain this to people who want to use everything with one login, they tell me that they don't want to use every server in the Fediverse. No, but they want to use any server in the Fediverse. Any one of the 30,000+.
And they want to use it immediately. Like, go there, use it with full-blown local user permissions right away, no delay.
Now you may argue that their account or channel could be cloned to that server when they visit it for the first time. Drive-by cloning, so-to-speak. Still, won't happen. Cloning takes time. I myself have cloned enough Hubzilla and (streams) channels over the years to be able to estimate just how long it takes. And none of my channels has ever contained tens of thousands of posts and thousands of pictures.
Besides, drive-by cloning would inflate Fediverse instances senselessly, not to mention bog them down with extra network traffic. Whenever you visit a Fediverse server instance for whichever reason (like, you want to look at a post on Friendica or Hubzilla to see what it looks like without being botched by Mastodon), your account or channel would automagically be cloned to that server instance. Another account (and channel, if necessary) on that server instance, another deluge of posts and files flooding into the database, and that clone would have to be synced with your 600 other previous drive-by clones on the 600 Fediverse server instances you've visited before.
Extra nefarious: Some "websites" that have to do with Hubzilla or a certain aspect of Hubzilla are parts of Hubzilla channels themselves. This includes . If you visited them, you'd create a drive-by clone on the Hubzilla hub which hosts that website.
So if someone set up a single-user Hubzilla hub with their personal channel and a website channel on it, and the website is interesting enough, and 10,000 Fediverse users visit it, it'll end up bigger than the biggest current Hubzilla hub within days. It'll have 10,001 accounts, namely the owner's account with two channels and 10,000 accounts with drive-by clones, automatically created by the 10,000 external visitors.
But this will remain utopic not only because it's technologically pretty much impossible and very much not feasible at all. It also requires a mechanism for one Fediverse server to recognise logins on other Fediverse servers. You know, like OpenWebAuth. You want your Mastodon account to drive-by clone itself, Mastodon will have to implement OpenWebAuth, and I mean fully implement it.
There actually is (= Hubzilla, (streams) and Forte would recognise Mastodon logins). This isn't even about full-support that'd include login recognition on Mastodon's own side. This pull request has been there for two years. It was never merged. And it probably will never be merged.
This means that the Mastodon devs have practically rejected OpenWebAuth as a feature to implement. Won't come. Ever. Not even half of it.
And this should say everything about the chances that Mastodon will ever implement nomadic identity.
CC:
# # # # # # # # # # # # # # # # #

Bumper long weekend wine guide: Best pinot noir for $30 or less

New Zealands production of pinot is exceeding the demand
# #30

Bumper long weekend wine guide: Best pinot noir for $30 or less

New Zealands production of pinot
# #30

Do you absolutely depend on being on Mastodon (as opposed of the rest of the Fediverse)
Because there is Fediverse server software (as in federated with Mastodon, as in you can follow Mastodon users from there, and Mastodon users can follow you when you're there) that offers way more than 500 characters. It may also offer other features which you may want Mastodon to have, or which are even completely unimaginable from the point of view of someone who knows the Fediverse as only Mastodon. Some examples:

CC:
# # # # # # # # # # # # # # # # # # # # # # # #

Du hiu may mn trn lng bntay#shortvideo

Du hiu may mn trn lng bn tay#shortvideo Your browser does not support HTML video. Du hiu may mn trn lng bn tay#shortvideo

DRAFT WATCH #11 With week to go, Brooklyn Nets hold five picks but for how long

Lemmy ist ja eigentlich ein Reddit-Klon, also in erster Linie darauf ausgelegt, da jemand ein Bild, einen Link oder sonstwas postet und darber dann diskutiert wird. So, wie es auf Reddit thematisch spezialisierte Subreddits gibt, gibt's auf Lemmy Communities.
Lemmy ist dabei nicht die einzige Serversoftware im Fediverse, die darauf ausgelegt ist. Es gibt auch noch

Gegenber Lemmy haben sie zwei Vorteile.
Zum einen sind sie besser darin, sich mit etwas anderem als dem "Threadiverse" (Lemmy, /kbin, Mbin, PieFed, hoffentlich bald auch Sublinks) zu verbinden. Lemmy kann eigentlich nur mit Reddit-Klonen richtig fderieren.
Zum anderen haben sie als Entwickler nicht einen knallharten Stalinisten und einen knallharten Maoisten, die beide sowjetische und chinesische Greueltaten relativieren oder gar bestreiten.
Lemmys einziger Vorteil ist, da alle bekannten Lemmy-Communities listet, aber keine /kbin- oder Mbin-Magazine und auch keine PieFed-Communities.
Kulturell ist Lemmy vllig anders als Mastodon. Es ist nicht Mastodon mit thematischen Gruppen. 99% aller "Lemminge" kommen direkt von Reddit und kennen Reddit sehr gut, aber meistens weder Twitter noch Mastodon.
Twitter-Nutzer, die nach Mastodon abgehauen sind, fanden meistens die Twitter-Kultur grausig und vergiftet. Daher haben sie auf Mastodon eine ganz neue Kultur "erfunden", die a) von Twitter inspiriert ist, b) aber freundlicher ist und c) die bis Mitte 2022 bestehende Mastodon-Kultur regelrecht verdrngt hat.
Redditors, die nach Lemmy abgehauen sind, fanden dagegen die Reddit-Kultur nicht scheie. Sie haben im Prinzip die Reddit-Kultur 1:1 nach Lemmy bertragen, wo sie sich nur ein bichen wandelte, weil Lemmy eben kein zentralisierter Monolith ist. Die Lemmy-Kultur hat mit der Mastodon-Kultur nichts, aber auch gar nichts zu tun. Statt dessen ist sie die Reddit-Kultur plus Stnkern gegen andere Lemmy-Instanzen.
Das heit in der Praxis: Wenn du nach Lemmy postest oder kommentierst und dich dabei zu sehr nicht wie ein Redditor verhltst, dann wirst du komisch angeguckt.

Von Mastodon nach Lemmy posten


Ich mchte noch einmal konkretisieren, wie man mit Mastodons beschrnkten Mitteln nach Lemmy postet. Dabei sind zwei Dinge wichtig: Zum einen ist auf Lemmy ein Titel absolut essentiell wichtig, whrend Mastodon kaum wei, was Titel sind. Zum anderen ist unbedingt die Lemmy-Community zu erwhnen.
Wenn du von Mastodon nach Lemmy posten willst, mu das so aussehen:
Titel
(Leerzeile, der bersichtlichkeit halber und evtl. auch aus technischen Grnden empfohlen)
Lemmy-Community
(Leerzeile, der bersichtlichkeit halber und evtl. auch aus technischen Grnden empfohlen)
Post-Text

Wenn du nach Lemmy, Friendica, Hubzilla, (streams), Forte und Guppe crossposten willst, dann geht das so:
Titel
(Leerzeile, der bersichtlichkeit halber und evtl. auch aus technischen Grnden empfohlen)
Lemmy-Community Friendica/Hubzilla/(streams)/Forte-Gruppe1 Friendica/Hubzilla/(streams)/Forte-Gruppe2 Friendica/Hubzilla/(streams)/Forte-Gruppe3 ... Guppe-Gruppe1 Guppe-Gruppe2 Guppe-Gruppe3
(Leerzeile, der bersichtlichkeit halber und evtl. auch aus technischen Grnden empfohlen)
Post-Text

Das heit, du erwhnst:

Auch wichtig: Alle Erwhnungen mssen in einer und derselben Zeile stehen! Du solltest sie also nicht aus irgendeinem Grunde untereinander in jeweils einer eigenen Zeile anordnen.
Auerdem wichtig: Keine Hashtags! Du kannst zwar mit Hashtags nach Lemmy posten. Aber Lemmy kennt keine Hashtags, weil Reddit keine kennt. Zum einen braucht Lemmy keine Hashtags, weil es ja die Communities gibt. Zum anderen, wenn du Hashtags postest, macht das bei den ganzen Redditors auf Lemmy keinen guten Eindruck. Auf Lemmy knnen Posts und Kommentare nmlich auch downgevotet werden (Upvote auf Lemmy = Fave auf Mastodon Downvote = das Gegenteil, das Mastodon gar nicht kennt, Lemmy aber sehr wohl), und ich wage zu behaupten, es gibt einige, die Posts mit Hashtags wegen der Hashtags downvoten.

Von Mastodon nach Lemmy kommentieren


Hier wre auch noch etwas erwhnenswert: Im Gegensatz zu Mastodon kennt Lemmy Konversationen. Und die funktionieren ohne Erwhnungen. Man braucht Lemminge nicht zu erwhnen, damit sie mitbekommen, da man in einem Thread kommentiert hat. Das ist da vllig anders als auf Mastodon.
Das heit auch: Wenn du in einem Lemmy-Thread kommentierst, lsch auf jeden Fall die von Mastodon automatisch generierte Erwhnung raus! Die fllt da genauso negativ auf wie Hashtags. Das macht man da nicht.
Beim Kommentieren sollte auch das Erwhnen der Lemmy-Community berflssig sein. Dein Kommentar kommt auch so an.
# # # # # # # # # # # # # # # # # # # # # # #

The Suns have three paths forward, but only one leads to long-term hope

Lng bit n gip bn thu ht nhiu may mn n

Lng bit n gip bn thu ht nhiu may mn n Your browser does not support HTML video. Lng bit n gip bn thu ht nhiu may mn n

I don't know what they expect. Also, I hardly ever get any feedback for my image descriptions unless I explicitly ask someone for it.
But I've actually asked blind or visually-impaired users a few times, and in the few occasions that they actually answered, they said that this amount of description is okay.
After all, the limitations in navigating alt-text with a screen reader only apply to actual alt-text "underneath" an image. They do not apply to image descriptions in the post which can be navigated like the rest of the post text.
# # # # # # # # # # #
The description you have given is a meter long and frankly (again please forgive my ignorance I know nothing about the blind and how they navigate the web) contains too much details to the point where using a screen reader to listen to this turns into a very boring podcast.

Someone somewhere out there might be interested in all these details.
Allow me to elaborate: My original pictures are renderings from very obscure 3-D virtual worlds. You may find them boring. Many others may find them boring.
But someone somewhere out there might be interested. Intrigued. Excited even.
They've put high hopes into "the metaverse" as in 3-D virtual worlds. All they've read about so far is a) Meta Horizon failing and b) otherwise only announcements, often with AI-generated images as illustrations. Just before they saw my image, they thought that 3-D virtual worlds were dead.
But then they see my image. Not an AI picture, but an actual rendering from inside an actual 3-D virtual world! One that exists right now! It has users! It's alive! I mean, it has to have users because I have to be one to show images from inside these worlds.
They're on the edge of their seat in excitement.
Do you think they only look at what they think is important in the image Do you think they only look what I think is important in the image
Hell, no! They'll go on a journey through a whole new universe! Or at least what little of it they can see through my image. In other words, they take in all the big and small details.
If they're sighted.
Now, here is where accessibility and inclusion comes into play. What do accessibility and inclusion mean They mean that someone who is disabled must have all the same chances to do all the same things and experience all the same things in all the same ways as someone without their disability. Not giving them these chances is ableist.
Okay, so what if that someone is blind In this case, accessibility and inclusion mean that this someone must have the very same opportunity to take in all the big and small details as someone who has perfect eyesight.
But if I only describe my images in 200 characters, they can't do that. Where are they supposed to get the necessary information to experience my image like someone sighted
They can only get this information if I give it to them. If I describe my image in all details.
And that's why I describe my original images in all details.
And stuff like the text not being legible. I don't know how you read that text cause I am unable to read it as well.

Again: I don't look at the image. I look at the real thing. The world itself. Like so:

This gives me superpowers in comparison to those who describe images only by looking at the images. For example, if there's something standing in front of a sign, partially obstructing it, I can look around that obstacle.
Imagine you're outside, taking a photo with your phone, and you want to post it on Mastodon. There's a poster on a wall somewhere in that image with text on it, but it's so small in the image that you can't read it.
Now you can say the text is too small, you can't read it, so you can't transcribe it.
Or, guess what, you can walk up close to that poster and read the text right on the poster itself.
# # # # # # # # # # # #

Michael Campbell reflects on 2005 US Open win, 20 years later #20+ #2005 .

From the point of view of a Hubzilla veteran, Bonfire is Hubzilla as ordered from wish.com. Only with an easier-to-use UI and better advertising, also because it's advertised from Mastodon whereas Hubzilla is entirely advertised from Hubzilla. The latter is one reason why at least three out of four Mastodon users have never even heard or read the name "Hubzilla". This probably includes the Bonfire devs. In fact, I wouldn't be surprised if the Bonfire devs knew nothing about Friendica either.
Bonfire has Mastodon users excited and on the edges of their seats with features which they think Bonfire is the first to introduce to the Fediverse. But Friendica has had quite a few of these features since 15 years ago already. Hubzilla has had others since ten years ago.
Not to mention the features that Hubzilla has that Bonfire hasn't. For example, the second-most advanced permissions system in the Fediverse (the most advanced one can be found on (streams) and Forte, both descendants of Hubzilla from Hubzilla's own creator) with three permission levels: , , . Or . Or a cloud file storage with WebDAV connectivity. Or groupware features like a CalDAV calendar server and a headless CardDAV addressbook server.
Or can you set up entire websites on Bonfire is actually built on a Hubzilla channel.
Or can you use Bonfire as a full-blown long-form blog With post titles, with all kinds of text formatting via markup, with an unlimited number of images embedded within posts, with a tag cloud, with categories and with no character limit worth worrying about (Friendica: 200,000, Hubzilla: 16,777,215, (streams) and Forte: over 24 million) Optionally even for non-federating blog posts
Does Bonfire have a magic single sign-on system like OpenWebAuth implemented Or OpenWebAuth itself Can you even write posts, comments, articles etc. in such a way that different users may see them differently if recognised by OpenWebAuth
How about support for threaded conversations via How about owning your entire discussion yourself and being able to moderate it, all the way to being able to delete individual comments In fact, how about comment control
At best, Bonfire is the VHS to Hubzilla's Betamax. The former is inferior, but with more publicity the latter is better, but so obscure that next to nobody knows it.
# # # # # # # # # # # # # # Yes. As a matter of fact, I've had an AI describe an image after describing it myself twice already. And I've always analysed the AI-generated description of the image from the point of view of someone who a) is very knowledgeable about these worlds in general and that very place in particular, b) has knowledge about the setting in the image which is not available anywhere on the Web because only he has this knowledge and c) can see much much more directly in-world than the AI can see in the scaled-down image.
So here's an example.
. It may not look like it because it clearly isn't on Mastodon (at least I guess it's clear that this is not Mastodon), but it's still in the Fediverse, and it was sent to a whole number of Mastodon instances. Unfortunately, as I don't have any followers on layer8.space and didn't have any when I posted this, the post is not available on layer8.space. So you have to see it at the source in your Web browser rather than in your Mastodon app or otherwise on your Mastodon timeline.
(Caution ahead: By my current standards, the image descriptions are outdated. Also, the explanations are not entirely accurate.)
If you open the link, you'll see a post with a title, a summary and "View article" below. This works like Mastodon CWs because it's the exact same technology. Click or tap "View article" to see the full post. Warning: As the summary/CW indicates, it's very long.
You'll see a bit of introduction post text, then the image with an alt-text that's actually short for my standards (on Mastodon, the image wouldn't be in the post, but below the post as a file attachment), then some more post text with the AI-generated image description and finally an additional long image description which is longer than 50 standard Mastodon toots. I've first used the same image, largely the same alt-text and the same long description in .
Scroll further down, and you'll get to in which I pick the AI description apart and analyse it for accuracy and detail level.
For your convenience, here are some points where the AI failed:

CC:
# # # # # # # # # # # # # # # # # # # LLMs aren't omniscient, and they will never be.
If I make a picture on a sim in an OpenSim-based grid (that's a 3-D virtual world) which has only been started up for the first time 10 minutes ago, and which the WWW knows exactly zilch about, and I feed that picture to an LLM, I do not think the LLM will correctly pinpoint the place where the image was taken. It will not be able to correctly say that the picture was taken at <Place> on <Sim> in <Grid>, and then explain that <Grid> is a 3-D virtual world, a so-called grid, based on the virtual world server software OpenSimulator, and carry on explaining what OpenSim is, why a grid is called a grid, what a region is and what a sim is. But I can do that.
If there's a sign with three lines of text on it somewhere within the borders of the image, but it's so tiny at the resolution of the image that it's only a few dozen pixels altogether, then no LLM will be able to correctly transcribe the three lines of text verbatim. It probably won't even be able to identify the sign as a sign. But I can do that by reading the sign not in the image, but directly in-world.
By the way: All my original images are from within OpenSim grids. I've probably put more thought into describing images from virtual worlds than anyone. And I've pitted my own hand-written image description against an AI-generated image description of the self-same image twice. So I guess I know what I'm writing about.
CC:
# # # # # # # # # # # # # # # #That's probably because threads work differently on Mastodon from Hubzilla. Mastodon doesn't know threaded conversations. And Mastodon users only receive messages
But they do not receive messages that are comments on posts which they've already received.
Let's assume Alice posts something on Mastodon, Bob comments on Mastodon, Carol replies to Bob on Mastodon, Dave replies to Carol on Mastodon and you reply to Dave on Hubzilla.
If this was an all-Hubzilla thread, you'd only mention Dave to show that you're replying to Dave. Your comment goes straight to Alice, and Bob, Carol and Dave pick it up from Alice because they've already got Alice's post on their stream.
But since Alice, Bob, Carol and Dave are on Mastodon, if you only mention Dave, then only Dave will receive and be notified about your reply because you've mentioned Dave. Alice, Bob and Carol will never see your reply because you haven't mentioned them.
So in this constellation, if you want all four to see your reply, you have to mention them all.
Granted, other reasons may be delivery delays on Hubzilla's side, or that enough Mastodon users have muted or blocked you because, from their point of view, you as a Hubzilla user act too disturbingly un-Mastodon-like, and you break Mastodon's unwritten rules left and right.
# # # # # # # # # # # #

Bajando temporalidad

A 70/1 each-way play tops these 4 US Open bets

Cubs 8, Phillies 4: Ian Happs two homers lead a long-ball barrage

In the cases of some Mastodon users, I actually wonder if it's worth telling them a) that the Fediverse is not only Mastodon, b) that I'm on something that's very very much not Mastodon and c) the implications of all this. Especially if they give the impression of wanting the Fediverse to be only Mastodon oh so very much.
Or whether I should simply Superblock them so that they'll never appear on my stream again.
# # # # # # # # # # # # # #Are you referring to my mentions being and rather than what you're used to, namely and Using the long name rather than the short name and keeping the outside the link rather than making it part of the link Likewise, the # being outside the hashtag link rather than being part of it
This is because I'm not on Mastodon. The Fediverse is not only Mastodon. It has never been. So this is not a toot.
No, really. This is what I post from: , . I ask you: Does this look like Mastodon Have you ever seen Mastodon look like this
Where I am, this style of mentions and hashtags is hard-coded. And it has been since long before Mastodon was even an idea.
I'm on something named Hubzilla. Hubzilla is not a Mastodon instance. Hubzilla is not a Mastodon fork either. Hubzilla has got absolutely nothing to do with Mastodon at all.
It is its very own project, fully independent from Mastodon (, , ).
Hubzilla has not intruded into "the Mastodon Fediverse" either. The Fediverse is older than Mastodon. And Hubzilla was there before Mastodon.
Hubzilla was launched by in March, 2015, eight months before Mastodon, by renaming and redesigning his own Red Matrix from 2012, almost four years before Mastodon. And the Red Matrix was a fork of a fork of his own Friendica, which was launched on July 2nd, 2010, 15 years ago, five and a half years before Mastodon. (, , , )
Friendica was there before Mastodon, too.
Here's the official Friendica/Hubzilla timeline on Hubzilla's official website to show you that I'm not making anything up: . Scroll all the way down and notice all the features that you may right now know for a fact that the Fediverse doesn't have, but that Friendica has introduced to the Fediverse 15 years ago, five and a half years before Mastodon was launched.
Again, Mastodon has never been its own network. The Fediverse has never been only Mastodon. When Mastodon was launched in January, 2016, it immediately federated with

Friendica has been formatting mentions and hashtags the way I just did for 15 years now. When Mastodon was launched, Friendica has been formatting them that way for five and a half years already, and Hubzilla has done so for ten months. It is hard-coded there. It is not a user option.
That's because not everything in the Fediverse is a Twitter clone or Twitter alternative. bFriendica was designed as a Facebook alternative with full-blown long-form blogging capability. And Hubzilla adds even more stuff to this. This is why Friendica and Hubzilla don't mimic Twitter.
Another shocking fact: As you can clearly see here, Friendica and Hubzilla don't have Mastodon's 500-character limit. Friendica's character limit is 200,000. Hubzilla's character limit is 16,777,215, the maximum length of the database field. And it's deeply engrained in their culture, which is many years older than Mastodon's culture, to not worry about the length of a post exceeding 500 characters.
One more shocking fact: Friendica has had quote-posts since its very beginning. So has Hubzilla. Both have always been able to quote-post any public Mastodon toot, and they will forever remain able to quote-post any public Mastodon toot. And Mastodon will never be able to do anything against it. (By the way: In 15 years of Friendica, nobody has ever used quote-posts for dogpiling or harassment purposes. Neither Friendica nor Hubzilla is Twitter.)
You find this disturbing You think none of this should exist in the Fediverse, even though all this has been in the Fediverse for longer than Mastodon
Then go ahead and block all instances of Friendica and Hubzilla as well as all instances of Mike's later creations, (streams) () from 2021 and Forte () from 2024.

Or you could go ask and as well as of to add every last instance on any of these lists to their blocklists for being "rampantly and unabashedly ableist and xenophobic by design" due to not being and acting and working like Mastodon and just as rampantly and unabashedly refusing to fully adopt and adapt to the Mastodon-centric "Fediverse culture" as defined by fresh Twitter refugees on Mastodon in mid-2022 as well as refusing to abandon their own culture which is disturbingly incompatible with Mastodon's. Essentially try and have four entire Fediverse server applications Fediblocked once and for all because they're so disturbing from a "Fediverse equals Mastodon" point of view.
Or you could go to Mastodon's GitHub repository (), submit a feature request for defederating Mastodon from everything that isn't Mastodon by design and then go lobbying for support for your feature request.
As for why I have so many hashtags below my comments, here is what they mean. Many of them are meant to trigger filters, including such that automatically hide posts behind content warning buttons, a feature that Mastodon has had since October, 2022, that Friendica has had since July, 2010, and that Hubzilla has had since March, 2015.

Lastly: Having all hashtags in one line at the very end of a post that only contains hashtags is the preferred way in the Fediverse. For one, hashtags in their own line at the end of the post irritate screen reader users much less than hashtags in the middle of the text. It's actually hashtags in the middle of the text that are ableist. Besides, Mastodon is explicitly designed to have a separate hashtag line at the end of the post.

A 66/1 shot leads our US Open Specials

What if I transcribe text within my image (for any definition of "text within my image") in a long image description in the post itself which I write in addition to the actual alt-text And the alt-text explicitly mentions the long description at its end E.g. "A more detailed description including explanations and text transcripts can be found in the post."
I often have so many bits of text to transcribe (in addition to describing where in the image they are) that I can't fit them all into the 1,500-character limit for alt-texts that Mastodon, Misskey and their respective forks impose on the whole Fediverse.
I'm not talking about screenshots from social media or something. I'm talking about renderings from 3-D virtual worlds where there may be 20, 30, 40 or more bits of text strewn across the scenery within the borders of the image. The rule says that all text within an image must be transcribed 100% verbatim, and it doesn't explicitly mention any exception, so I do have to transcribe them all. In addition, if they aren't in English, I must additionally translate them as literally as possible. There's no way I can fit all this plus a sufficiently detailed and accurate visual description into 1,500 characters.
But if you (or others) insist that all text within an image must be transcribed verbatim in the alt-text, and if you sanction image posts that transcribe the texts in the image elsewhere than in the alt-text, then I simply won't be able to post certain images in an appropriate way.
# # # # # # # # # # # # # # # # #

NBA Free Agency: Will the Bucks look to extend Portis long term

At , we are committed to providing to help your pets live , , and lives. From and to services, , and , our experienced team offers personalized plans tailored to your pets unique needs.

To know more:

Don't mix up quotes and quote-posts. They're something very different, not only in technology, but also in use-case and especially in cultural implications.
Whereas on platforms with threaded conversations, quotes are usually used in comments within a thread, and on many platforms, such comments could be removed by the thread owner.

This is a quote. Like in a bulletin-board forum. This is actually only used in comments. For Mastodon users, it's basically unimaginable that this ever happens in social media. Twitter has never had this, so most Mastodon users don't even know the very concept of this. Thus, it is not what they're upset about.
What Mastodon users are so upset about are quote-posts. What they refer to as "quote-posts" or "quote-toots" is what we call "shares" or "shared posts", what Twitter/X calls "quote-tweets", and what is used on Twitter/X for harassment and dogpiling purposes, namely this:
It should be noted that Twitter-style platforms use quote posts in an entirely different way than platforms with threaded conversations.
With Mastodon, someone can quote you, criticize you, and then people dogpile on. Since it is not part of a thread, and is its own top level post, nothing can be done about it.
Whereas on platforms with threaded conversations, quotes are usually used in comments within a thread, and on many platforms, such comments could be removed by the thread owner. Yes, they can create new top level post quoting someone, but that seems to be used less on threaded conversation platforms than on Twitter style platforms.
This creates a different culture surrounding quoting people, since one has potential consequences and one does not.
Plus, I think there is also a cultural difference between people who want to broadcast their thoughts versus people who want to join conversations. People who want to participate in conversations are typically less hostile since they get banned or blocked pretty quickly. People who broadcast their posts just want as many followers to see it as possible and tend to block anyone that disagrees with them. It is a different mindset.
That is why Mastodon has to implement quote controls, but thread conversation platforms do not.
You should see that it's something completely different. This never happens within the same thread. It wouldn't make sense to quote-post/quote-tweet/share a post in a comment on that same post.
This is what Mastodon users what to have control over. This is what they want to prevent. Entirely. They would want a switch that makes Hubzilla hide the Share button under a post of theirs if they knew that a) Hubzilla exists, and b) Hubzilla can share posts/quote-post.
This is what keeps preaching over and over and over that literally the only possible way to keep this from happening is by not posting in public. For this is what neither Hubzilla nor Mike's own (streams) and Forte have a permission setting for because even their highly advanced and fine-grained permissions systems have no way of implementing actually water-tight quote-post control. So what chance does Mastodon have with its total lack of a permission system and no understanding of Hubzilla's, (streams)', Forte's or even only Friendica's permission system
Mastodon doesn't have either implemented, neither quotes nor shares/quote-posts, at least not beyond displaying quotes properly formatted (it is working on displaying quote-posts properly formatted now). Hubzilla has inherited both from Friendica which has had both for 15 years.
CC:
# # # # # # # # # # # # # # # # # # # # # # # # # # #

Our 5 best bets for the US Open at Oakmont

An iconic landmark in Nairobi
.
.
.
.
.
.
.
.
.
.

MLB scores: Mike Yastrzemskis 3 RBI day was long overdue

How long until Aaron Bummer gets an opportunity to close


Last updated: 2025-06-19






Ships and Yachts around Western Australia