In the database there are no conflicts, since everyone is still referred to by hash. The user interface will simply use the same name for both users. In addition to the self-assigned names, a user can also assign names…
Patchwork is a user interface for displaying messages from the distributed database to the user, and to allow the user to add new messages. The underlying protocol supports arbitrary message types, patchwork exposes a…
You can also use the same keypair on multiple devices. This however results in another problem: You could post content from both devices simultaneously. But the underlying protocol requires each message to refer to the…
(Public) information is not only shared between friends, but also between friends of friends. So as long as they have common friends connected to the internet, the data flows without problems. To help with this…
Especially since the implementation details are not set in stone. Once the lower-level protocols start to stabilize, more efficient implementations will probably emerge.
Currently, a user can simply post an `about` message in the stream. Clients will then automatically use this name instead of the key.
In the database there are no conflicts, since everyone is still referred to by hash. The user interface will simply use the same name for both users. In addition to the self-assigned names, a user can also assign names…
Patchwork is a user interface for displaying messages from the distributed database to the user, and to allow the user to add new messages. The underlying protocol supports arbitrary message types, patchwork exposes a…
You can also use the same keypair on multiple devices. This however results in another problem: You could post content from both devices simultaneously. But the underlying protocol requires each message to refer to the…
(Public) information is not only shared between friends, but also between friends of friends. So as long as they have common friends connected to the internet, the data flows without problems. To help with this…
Especially since the implementation details are not set in stone. Once the lower-level protocols start to stabilize, more efficient implementations will probably emerge.
Currently, a user can simply post an `about` message in the stream. Clients will then automatically use this name instead of the key.