Because you can't go far without json.
Sunday evening #doauth programming.
My Sunday Feeling
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.
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! 🏃
OMG #doauth has registered its first user!
(It's me. I am the user.)
On the subject of re-writing the same thing over and over again.
I made a `:> Capture ` query on #hackagesearch website and after very very brief exploration, an API capturing something called `SessionToken` caught my eye.
Upon inspection it turned out that they have B64 encoding as well, except significantly less deranged than mine.
Going live with #haskell development in 6 minutes: