Jons Mostovojs @jonn@social.doma.dev

Today #doauth has verified its first credential.

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

#myelixirstatus

Today #doauth has issued its first credential in testing...

Big things are coming!

#myelixirstatus #ecto #elixir

Because you can't go far without json.

#doauth

Sunday evening #doauth programming.

My Sunday Feeling

#doauth

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

#doauth #myelixirstatus

A huge milestone for #doauth.

The architecture and data flow spec is encoded in #SQL.

While thinking about a way for #doauth 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.

#doauth

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

Our colleagues from other companies that are working on modern identity-related products are already investigating usage of #ZKP 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 #elixir 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.

#myelixirstatus #elixir #doauth

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

#doauth #did

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 #doauth file storage is straight up sufficient, but I'm too afraid to not use #postrgresql with #ecto, because I'll be laughed at or something.

Asked my first question on W3 IRC!

#doauth #did #vc

I used to overengineer, now I overpolish.

Should learn how to stop at "good enough".

#doauth #chappy

Holy shit am I productive with #elixir and #phoenix.

#Haskell is for thinking and making sure that you're building the right it, #elixir is for doing and making sure you're building it right.

Welcome #chappy, y'all, your friendly hardener for our #DID / #VC implementation called #doauth.

https://asciinema.org/a/zCy4Ro5vPRPShgLiDv0gQ3Hbe

OMG #doauth has registered its first user!

(It's me. I am the user.)

We probably should set up monitoring, @pola ?

I have log aggregates set up for mail server, but I feel like that's not enough too...

Something for me to figure out after #doauth? :)

Bit by bit, bit by bit. #doauth #haskell

On the subject of re-writing the same thing over and over again.

For #doauth I need to capture detached signatures[1] in #API.

I made a `:> Capture ` query on #hackagesearch website[2] and after very very brief exploration, an API capturing something called `SessionToken`[3] caught my eye.

Upon inspection it turned out that they have B64 encoding as well, except significantly less deranged than mine.

[1]: https://hackage-search.serokell.io/?q=%3A%3E+Capture+
[2]: https://hackage-search.serokell.io/viewfile/battleplace-0.1.0.10/BattlePlace/WebApi.hs#line-44

#battleplace #serokell

Going live with #haskell development in 6 minutes:

Implementing #doauth, an #aaa system that just works (for the people).

https://watch.doma.dev/videos/watch/ea6a5813-3803-4bd3-945b-5150edde8004