Show more

I'm very shy about the structure and understandability of my code, but now I'm workign with ruby codebase and I feel better.

Working hard on being privacy-preserving. API first, backend later.

Another milestone for !

Invite functionality is implemented, now it's basically .

Getting sleepy...

I wonder if I'll manage to implement limked lists for verifiable credentials as seen in , thus implementing everything needed for the quantity-bound invite protocol.

Another milestone in 's history: JS client verified its first credential!

Dont @-me, I'm just following verifiable credentials spec, which kindly tells me to figure out how to attach proofs and what to cover with proofs myself, while imposing JSON schema on me.

Honestly, sometimes I'm apalled by JSON world. It's better than XML, but still doesn't address any of its issues. If we only had better editors for binary formats, we would have lived in a much better worlds. Now I really do understand why architects when I was in my early twenties were so eager to use protobufs...

Ok well anyway, test your code, kids.

Here's a screenshot of sodium.js producing the same key as server.

Show thread

We are getting places with cryptography in browser.
Can't wait to polish the second prototype and start integrating it with services, looking at OIDC compliance, etc.

With . it's really easy to make and validate claims, embedded into

We're trying to prioritise for people who want to use our software (as well as, when the time shall come to make frontends, for the end users).

Show more
Doma Social

Mastodon server of https://doma.dev.