Jons Mostovojs @jonn@social.doma.dev

I love #glitchart!

```
{
"@context": [],
"type": [],
"issuer": "did:doma:z9WvHH7JyPek1SehusPElQRTMl8UfxvP9sANUlGZ57U=",
"issuanceDate": "2021-06-16T17:15:05Z",
"credentialSubject": {
"@context": [],
"credentialSubject": {
"capacity": 10,
"holder": "did:doma:c5Cfk0Aw_SYXzIgvDO3QNumrD30E5o-Sd61n8bL4dTw=",
"kind": "invite"
},
"id": "/invites/0LMLz-psbFmVEc2aVr9pXShesbIxfeeg6Kc0YCVYMI0=",
"issuanceDate": "2021-06-08T09:48:15Z",
"issuer": "did:doma:c5Cfk0Aw_SYXzIgvDO3QNumrD30E5o-Sd61n8bL4dTw=",
"proof": {
"created": "2021-06-08T09:48:15Z",
"proofPurpose": "assertionMethod",
"signature": "Tj2bekNqJyj73q64RAUW2GMSuimP4IW2kbApwTFQvVZT8oEe5fzWUO9c_UwgRohQd-0vJ1i5LECjZJyvwov-Cw==",
"type": "libsodium2021",
"verificationMethod": "did:doma:c5Cfk0Aw_SYXzIgvDO3QNumrD30E5o-Sd61n8bL4dTw="
},
"type": []
},
"proof": {
"created": "2021-06-16T17:15:05Z",
"proofPurpose": "assertionMethod",
"signature": "30GoSvC2GxiIP_3Sh9Jd0ebHsDjY5Myo7MXVEpg2nEGWIpcvcomuKjIBj5vebXArZUk4rb7r7yLQOOoaUvgnBw==",
"type": "libsodium2021",
"verificationMethod": "did:doma:z9WvHH7JyPek1SehusPElQRTMl8UfxvP9sANUlGZ57U="
}
}
```

People: tweeting about pandemic ending.
UK:

One step closer to integrating #doauth and #mastodon!

As of today we have browser-issued #verifiablecredentials.

Can't wait to open registration on this instance again!

Fair enough

What's this lock thingie in #tusky ?

Sometimes #ruby trait naming convention gets hilarious.

Everything that is wrong with #MVC in one screenshot.

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

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

Invites work! #doauth

Another milestone for #doauth!

Invite functionality is implemented, now it's basically #clubhouse.

Getting sleepy...

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

Another milestone in #doauth'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 #doauth #Elixir server.

Ah, #JavaScript, I just started to like you.

(Razer sharp languages are so razer sharp).

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

Just Dance is the best thing Ubisoft did ever.