I envision actors having public keys as their IDs, possibly with some system for updates/revocations. When actor references are passed, they're sent together with the current (or last known) network location of the actor. Each server keeps a directory mapping IDs to locations. Actors can transparently move between instances, by sending a Move notification about their new location. Anyone who misses the notification can query friends/others who did get it.
@pere
> public keys as ID's
> directory mapping ID's to current location
#Hubzilla does this in its #Nomad protocol. In its #Streams incarnation, it seems to present #ActivityPub posts as a public stream and native Nomad posts as a fine-grain-permissioned stream.
In actor-model programming, it's possible for each actor to have its own separate database, which makes it trivial to move actors by copying their data! Of course this would be done securely, encrypting the data with the actor's own key
Once we have such a system, we can play with network systems that manually/automatically move actors between servers, changing the shape of the network, without any impact on the application layer
For example, an algorithm that balances the network by moving actors from busy/slow/large instances to smaller ones?
And of course people manually moving for social/privacy/ToS/etc. reasons
@pere
> Actors can transparently move between instances, by sending a Move notification about their new location
The biggest concern I've seen come up in discussions about nomadic identity, is how it could impact the moderation model of the fediverse. Anything that breaks instance-level moderation is not going to be universally welcomed.
Add comment