The @mastodon handle on X isn’t the Mastodon network—it’s just a user! The real social network’s account is @joinmastodon. Lucky snag for whoever got that username early.
Folge einfach mal ein paar Menschen um Content (evt. Diskussionen) zu erreichen. Mensch kann jeder Zeit ja wieder ergänzen und/oder wechseln was Thematisch interessiert und austauscht ☺️
Für eine kleine Einführung wie Mensch spannenden Themen mitverfolgt, habe ich schon mal für #neuHier notiert (falls erwünscht) 👇
19.08.2025 09:57 p (@p@pixelfed.social) 🌳 The enchanting Crooked Forest, where nature bends to its own rules. 🌳
This photograph captures the mystical beauty of the Crooked Forest, much like our eco-friendly adventure apparel. Crafted from 100% organic cotton, our hoodies and t-shirts are perfect for those seeking comfort and style in nature.
As we celebrate the beauty of the Crooked Forest, we also celebrate the importance of sustainable fashion. Every piece in our collection is a testament to ethical living and adventure-inspired designs.
Where’s your next adventure taking you? 🗺️ Let us know in the comments!
Another issue is that I don’t see a mechanism for actually *syncing* the content from one server to another.. so that still has to be addressed by some other spec (LOLA, for instance, if I could figure out how THAT works)
But.. once we have a “sync” in place, I’m definitely up for trying to tie an actor or a piece of content to some sort of DID.
It's all being figured out by Mike and silverpill by and by.
On the one hand, silverpill is converting Mitra from your typical non-nomadic, account-equals-identity, built-against-Mastodon-first-and-foremost ActivityPub software into something that's every bit as nomadic as what Mike has made since 2012. Basically, part of what silverpill does is figure out and document what has to be done to achieve this so that other Fediverse server software developers can follow suit. This is the hard part.
At the same time, silverpill casts everything he develops into FEPs so that everything he does is covered by a standard of sorts.
On the other hand, Mike has already had nomadic server software since July, 2012. In fact, he was lucky: Instead of having to build nomadic identity into existing software, he forked his own Friendica, threw the entire backend away and wrote an entirely new one from scratch, this time against Zot rather than DFRN. (On a sidenote, this may explain why Hubzilla is significantly faster than Friendica.) Everything else was evolution ever since.
And he has had nomadic ActivityPub-only server software since July, 2023, which came to exist by taking software based on Nomad and also supporting ActivityPub, ripping the Nomad parts out and basing it entirely on ActivityPub.
So what Mike has is a "nomadic reference". This is where silverpill must head. And (streams) (the one based on Nomad) and Forte (the one based entirely on ActivityPub) are sparrings partners for Mitra's nomadic development branch. As new FEPs emerge, (streams) and Forte are adapted to them by and by. In only very few cases, FEPs are developed on Mitra as well as on (streams) and Forte; FEP-ef61 was one such thing.
However, Mike doesn't have to document just how exactly stuff works on (streams) and Forte. You may argue that it'd be important to know for those who want to develop Nomad-based server software. But you don't make your own Nomad-based software by sitting down behind your computer and writing it from scratch. You make it by forking (streams) which was released into the public domain and with no name and no brand identity for this very reason. The streams repository was literally made to be forked.
Now, silverpill still has a long way to go. The nomadic Mitra development branch does understand (streams)' and Forte's portable objects and nomadic identities. But I'm not sure if it's actually nomadic itself yet.
The first step most likely has to be detaching the identity from an account and putting it into a container, the sort that Hubzilla, (streams) and Forte refer to as a "channel". I'm pretty sure that before Mitra goes nomadic, it will support multiple fully independent identities on one login.
The second step most likely has to be identity management between instances of the same container on different servers.
It isn't before then that we can talk about implementing actual data transfer and syncing it.
And it isn't before then that we can talk about standardising and documenting it in a way that helps those who want to go from non-nomadic to nomadic, or who want to build nomadic ActivityPub software from scratch.
Mike can't help much here. Mike sees the Fediverse and nomadic identity through the eyes of someone who has done nomadic things since years before ActivityPub was even made, and who had to switch his already existing concept of nomadic identity to a protocol which is not made for nomadic identity. One could say that Mike is based and Nomad-pilled.
silverpill, on the other hand, comes from non-nomadic ActivityPub, and that's what he knows, what he's used to. Just like every dev in the Fediverse who isn't Mike or one of his contributors or one of the two guys who took over Hubzilla in 2018. He basically has to re-invent the implementation of nomadic identity from scratch. And it's his experience that's required to know how the bits and pieces of nomadic identity can be implemented in both existing and new ActivityPub software and to cast it all into FEPs.
19.08.2025 09:37 item (@item@libera.site) #Plume #Statistics 2025-08-19 09:00 CEST Number of active instances: 32 Number of users: 23 882 Number of posts: 25 281 Number of comments: 117 903 Number of users last 4h: 0 Number of posts last 4h: 1 Number of comments last 4h: 4