I think you are right, but here it is where my knowledge falls short and why I didn't write @pics@lemmy.world or !pics@lemmy.world. I think those would be user and community respectively.
And for those who have watched all Ben Eater's videos, I highly recommend James Sharman's 8 Bit CPU from scratch playlist. I'ts a bit less step-by-step-tutorial, but it covers more ground than Ben.
Not an expert, those who know more, please correct me.
I think all name disambiguation is made by adding the instance name after. So if someone has the user pics in pixelfed.social, it would be pics@pixelfed.social, while the lemmy.world community would be pics@lemmy.world.
(..) Brecht’s team even taught the rodents to play hide and seek. At the beginning of the game, a rat was enclosed in a box while a researcher hid somewhere in the room. The researcher then opened the box using a remote control, allowing the animal to jump out and begin “seeking.” When the rat successfully found the hidden scientist, it was rewarded with—you guessed it—a tickle. The rats were also given the opportunity to hide while the researchers looked for them, and they proved to be especially good at coming up with creative hiding spots. Their ability to strategize was “almost spooky,” Brecht recalls.
(...) Brecht’s team first made sure the rats were comfortable with their new playground, aka a dimly lit plastic box, as well as their human playmates. The researchers then played games of “chase the hand” and tickled and the animals on their backs and bellies (see video (...) for an example from a previous experiment). In response to the tickling, the rats shimmied in delight and let out endless “giggles.”
If it does, I should be able to post images on the pixelfed app that show my username as @adonis.
It cannot work as stated because there could be another @adonis accounts in other instances and the only way to prevent that would be to centralize all the signups which goes against the whole idea of decentralization. That's why the user must be adonis1@kbinwhatever as it is shown now.
Regarding the OAuth/JWT, again... not an expert, but what I understand is that that kind of integration is much stronger than the current system. AFAIK, it could work as you say, but that would make things much more complex for the servers; you usually provide OAuth authentication for a few services, I don't know how well that scales with ... hundreds / thousands (?) of authentication provders. But, who knows, maybe in the future it's implemented in one way or another.
We should take into account that this technology is fairly new and people are still building on it.
I'm not an expert, those who know more, please correct me.
Regarding logging-in with one account into another instance, I think that's not how it's intended to work. But I'm oot sure I understand what you're asking.
There is a lot of work to do, even outside of ActivityPub. As Dave mentions, we also need a common posting API. The most popular Mastodon client apps do not support either ActivityPub or Micropub. But a lot of progress can be made focusing on interoperability for the server-to-server part of the API. That should be the top priority with Threads set to join the fediverse.
Some communities with different content: