Jons Mostovojs @jonn@social.doma.dev

With the tech I have developed with #doauth, I figured, it would make sense to build something like a FOSS about.me that is geared towards geeks, with a cup-of-coffe-per-month hosting.

What key features would you like to see in such a product?

Boosts are welcome.

```
Wed Jun 16 16:22:06:471171601 sweater@rethink ~
λ pass doma/maja.doma.dev
"slip": {
"ops": 4,
"mem": 40960,
"saltSize": 16,
"salt": "5A7ZuPZv8yrOdbU0CTZ0mQ=="
}

*redacted*
```

Feels great to have #doauth password and KDF slip stored in my password manager!

Sneak peek:

https://maja.doma.dev/demo.html

One step closer to integrating #doauth and #mastodon!

As of today we have browser-issued #verifiablecredentials.

I made so many accounts with #doauth already, omg.

https://asciinema.org/a/419081

So, @pola and I have signed up an account through a <textarea> designated for verifiable credential.

I'm finishing up with namespacing for #doauth and we're gonna integrate tomorrow, fingers crossed.

It will mean that we have a VC / DID authentication for #mastodon.

You can already deploy #doauth to your server in dev mode and start registering users. If you do, share your server's PK with me so that I can add it to my server!

https://git.sr.ht/~doma/do-auth/commit/d6703343e9c437a51a1133335d5fd421126818cb

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

Invites work! #doauth

Managed to write a count-based invite system full implementation with #doauth as a library takes 111 LoC.

Going to write tests tomorrow and start looking into integration with mastodon 🎉

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!

Ok well anyway, test your code, kids.

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

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.

Finally, #doauth is sending stuff over HTTP!

A pretty big day.

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

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

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

Logic for #doauth's #tofu is implemented, tomorrow: #phoenix endpoint and maybe deployment to aaa.doma.dev for memes?

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

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

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

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

Here's how to insert a credential / claim in #doauth: https://git.sr.ht/~doma/do-auth/commit/d2a28de2e48dfd3c739b40633b280c4ab4814826#test/db_test.exs-1-4