home.social

#doauth — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #doauth, aggregated by home.social.

fetched live
  1. Posted a couple of little videos: "The Code of Escape": tubedu.org/w/cUVPfyAKNyBCLXRT8 where we learn the least stupid way to set terminal titles.

    And "HTTP Client in JavaScript": tubedu.org/w/vHgkBkJmTDExVFKkF where I demonstrate how to make a #doauth registration form from scratch while making a minimal wrapper around fetch API in order to write denser code.

    If you like my bits, subscribe with RSS to my tubedu channel! tubedu.org/feeds/videos.xml?vi

  2. Going live with ambient sounds (outdoor cafe[1] + cyberboard typing[2]).

    Main goal for today is adding a #doauth authentication to #duex (an #elixir file upload demo with upload capabilities as rich as Google Drive's, i.e. multi-file upload and *directory* upload!).

    Secondary: start closing UX tickets related to accounting (as in AAA) from #megalith for #zerohr.

    Tune in! behold.memorici.de

    --
    [1]: youtube.com/watch?v=Xxs5X8RYCx
    [2]: youtube.com/watch?v=OQpWL_dEJm

  3. Dropping #ecto in favour of using a #genserver with a simple async persistence only for the things that need to be persisted made a credential verification from a 50+ms ordeal into 1-ms ordeal. x50 speedup makes me hopeful about #doauth 0.4 demo making a user account in sub-100ms, compared to sub 1.5s which 0.3 shows.

  4. github.com/doma-engineering/cl

    Making #elixir reasonable with deep functional programming.

    If I had Uptight.{Text, Binary, Base} while coding #doauth v0.2 and 0.3, I would have done it so much faster.

  5. I know this demo is kinda trashy, but it's a good introduction into how a "registration" works with #doauth and #verifiablecredentials.

    youtube.com/watch?v=22zbm2qNhS

    If you have any feature requests for a next-gen federated authentication and authorisation system, hit me up or make an issue: github.com/doma-engineering/do

    You can also contribute stuff like biometrics support via react-native (to eliminate the password) and more fun protocols! We also need replication via federation for high availability.

    If anyone is excited about #AAA system that anyone can set up in under half an hour (as opposed to #keycloak) and that uses VC/DID by default, and doesn't use blockchain to store data, let's chat too!

  6. Day job done for today, it means, it's time to write some code for #doauth. Tune in to my no comments stream. I reply in chat though.

    twitch.tv/0x101

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

  8. ```
    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:

    maja.doma.dev/demo.html

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

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

    git.sr.ht/~doma/do-auth/commit

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

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

  13. Another milestone for #doauth!

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

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

  15. Another milestone in #doauth's history: JS client verified its first credential!

  16. Ok well anyway, test your code, kids.

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

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

  18. Finally, #doauth is sending stuff over HTTP!

    A pretty big day.

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

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

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

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

  23. 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: git.sr.ht/~doma/do-auth/commit

  24. Today #doauth has verified its first credential.

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

    #myelixirstatus

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

    Big things are coming!

    #myelixirstatus #ecto #elixir