Joep Meindertsma
Joep Meindertsma
I'd like users to be able to validate JSON-AD in their browsers. It should not be too hard to build this, but it would be useful to have this and...
There is overlap between how the Decentralized Identifiers spec and Atomic Data should work. Both emphasize self-sovereign identity management powered by cryptography. Currently, Atomic Data Agents have HTTP(S) identifiers. This...
There are many [use cases](https://w3c.github.io/vc-use-cases/) for verifiable credentials. One of the core features of Atomic Data is the Commit model, which makes data highly _traceable_. However, making sure that one...
One of the core concepts of Atomic Data is that users _sign_ their changes using their identity. This allows for fully traceable, verifiable information, which is one of the core...
Users need to store their agent's secret (which includes the private key) someplace safe, such as a password manager. However, this is still not optimal: - The secret is entered...
First I felt like Agent was a bit more fitting, as it would also entail non-human actors. However, Agent feels unconventional and unfamiliarm compared to 'user', even though it is...
I'm currently using Ed25519 for signing Commits and requests, because: - It's fast, and we need to sign often client-side - [Doesn't break](https://security.stackexchange.com/a/41509/5701) with a broken number generator, such as...
Currently, there is no difference between a Commit that _updates_ a resource and one that _creates a new one_. This can easily lead to accidental overwrites. Approaches: ## Adding `initial`...
This weekend I was implementing [`previousCommit`](#62) in Atomic Server and Atomic Data Browser. This means that Commits need to have an explicit `previousCommit` in order to be accepted by a...
Creating Atomic Data is easy to do if you use the tools I've built, but if you want to implement (part of) the spec yourself theres quite a bit of...