Show more

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).

Good morning! Time to fix some tests I broke while implementing tofu logic.

Logic for 's is implemented, tomorrow: endpoint and maybe deployment to for memes?

Show thread

A road to : servers can almost register themselves, now let's self-sign!

Been a while since I've updated y'all about .

Well, we can insert credentials under transaction with a very nice interface: a keypair and a claim map.

Underneath, it's 99%-compliant with and standards, but on the surface it just gives programmers what they care about!

Here's how to insert a credential / claim in :

Today has verified its first credential.

Going to clean up noisy logging output and push the code tomorrow.

Oh yeah, baby, nice UX to insert stuff into the database.

Important bit is that we just supplied PK as a string and we let Ecto figure out how to fetch it...

I wish there was a cache layer so that I don't have to query stuff every time I make a changeset...

A huge milestone for .

The architecture and data flow spec is encoded in .

Show thread

While thinking about a way for users to control their identity, disclosing nothing by default AND high availability / replication, I came up with the notion of disclosure event logs.

After just a little bit of tinkering with the definition, it turned out that it's getting modelled with existing approach to credentials / claims really well.

I love that immediate positive feedback on design and architecture.

I really like the fact that there is a very high theoretical ceiling for

Our colleagues from other companies that are working on modern identity-related products are already investigating usage of to reduce correlation attack surfaces.

A rare occurrence when being in cryptocurrency business since 2013 pays off — I already understand quite some stuff about zero knowledge cryptographic systems, so it won't be too hard to catch up! 🏃

I'm really bummed out by the fact that doesn't come with a property-based test engine.

Since propex is unstable right now, I write plain stupid unit tests and hate every moment of this bullshit.

URI implementation: one of the few reasons why you might want to have optional values.

Joe Armstrong advocated usage of file system to persist key-value mappings, and databases to store data that we need aggregate queries over.

I feel like for file storage is straight up sufficient, but I'm too afraid to not use with , because I'll be laughed at or something.

Show more
Doma Social

Mastodon server of