Jons Mostovojs @jonn@social.doma.dev

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

Basically dependent types, amirite? #elixir #myelixirstatus

Eco-aware motorsport fans MUST watch

https://www.extreme-e.com/en/watch-live

and tell your friends. Spec cars, legendary drivers.

Initiatives like these are bringing a little bit of hope.

Work slack has some interesting guests today.

#!/usr/bin/env bash

set -xeuo pipefail

find . -maxdepth 2 -mindepth 1 -type d | grep -e '\/.*\/.*' | cut -d\. -f2 | cut -d\/ -f2- | tee -a .rsyncignore
cat .rsyncignore | sort | uniq | tee .rsyncignore.new
mv -v .rsyncignore.new .rsyncignore

ssh -NCL 9969:localhost:22 remote.host &
sleep 2

rsync --exclude-from=.rsyncignore -Pave 'ssh -p 9969' "localhost:/mnt/e/*" .

#backup #cheatsheet #bash #ssh

Tunnel to #RDP:

ssh -N -vvv -C -L 9999:localhost:3389 remote.host

#cheatsheet

Of course, libsodium23 is the name of the package containing libsodium 1.0.18.

Why wouldn't it be.

Sometimes I miss #nix and #nixos.

I used to overengineer, now I overpolish.

Should learn how to stop at "good enough".

#doauth #chappy

#TIL that #Elixir/#Phoenix is even better than I thought in terms of observability:

https://hexdocs.pm/phoenix_live_dashboard/Phoenix.LiveDashboard.html

Wrote a post about parser combinators together with @pola!

https://doma.dev/blog/parsing-stuff-in-rust/

Give it a read and tell us what you think.

#rust #rustlang

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

Hot take: calling protocols like CHAP "authentication" protocols just because they prevent MITM (frontrunning) and replays, is misleading and yields a ton of vulnerable software.

People at best think of authentication as something to do with identity, not as of a way to validate integrity of an API request.

I'm currently making a CHAP-inspired implementation, and I think, I'm managing to document it well enough without claiming that it's an "authentication" solution.