@just small circles ๐ We were just talking about a hybrid approach to nomadic identity, where someone could have their identity on their device or on a server or both at the same time.
For those who are not familiar with the concept, nomadic identity is when your identity is not tied to a specific device or server and can be moved around freely. It is similar to portable identity but takes it two steps further: you can have your identity on more than one server or device at the same time, and your content (such as posts) sync between devices and/or servers. If one goes down, you can use the other, making each location of your identity an independent backup. It also makes it easy to migrate to a new server or device since your content moves over too, not just your identity.
If you want full control, you can self-host both the server, or you can use a provider for the server who handles the tech for you. This gets synced with your device which you own, creating two copies of your identity and content in two locations.
It is currently implemented on a server-server basis on several platforms, both other Zot protocol and ActivityPub protocol, but there is no reason why this couldn't be extended to the device level or client application.
For those who are not familiar with the concept, nomadic identity is when your identity is not tied to a specific device or server and can be moved around freely. It is similar to portable identity but takes it two steps further: you can have your identity on more than one server or device at the same time, and your content (such as posts) sync between devices and/or servers. If one goes down, you can use the other, making each location of your identity an independent backup. It also makes it easy to migrate to a new server or device since your content moves over too, not just your identity.
If you want full control, you can self-host both the server, or you can use a provider for the server who handles the tech for you. This gets synced with your device which you own, creating two copies of your identity and content in two locations.
It is currently implemented on a server-server basis on several platforms, both other Zot protocol and ActivityPub protocol, but there is no reason why this couldn't be extended to the device level or client application.