I just started using tap earlier today and was doing exactly this with my identity events. Thank you in advance.

If anyone stumbles into this and also runs piper, here’s the commit. Adds ALLOWED_DIDS to the .env file as a space separated list of dids.

I just had to rescue a project that bundled all of os.environ into kwargs as a way to pass “config” around the codebase. No documentation anywhere on what had to be in kwargs for the program to work. Fun.

ux* actually

Very cool!

I’ve been skeptical of vibe coding outside of throwaway code, but forcing more rigor onto the process through a spec doc seems to work well from my early experience.

Definitely would be interested to know what that RFD looked like. (I saw you already mentioned it was a WIP)

Agreed. I like the mini dopamine hits from writing clean code and learning the language/library/tool. Actually finishing a project isn’t as big of a hit for me for some reason.

I still can’t disagree with the benefits though, so I’m finding ways to integrate it more into my work.

audio isn't identical, but I don't think people understand how compute intensive signal processing was at the time (and still is in some ways). llms are trending in a similar direction, albeit with their own problems (e.g., memory).

~25 years ago, playing audio on CPUs w/o using separate hardware could grind them to a halt. Intel/AMD introduced new CPU instructions that later became the SSE extensions. About a decade of innovation later, now no one thinks about how audio is played on a computer.

the technology isn't going to disappear. decades of progress in software/hardware have shown that valuable compute intensive tools only get more efficient and easier to harness.

open models exist and work well enough. if investment disappeared overnight, progress would still continue.

yep sounds about right. I’m at the “your manager asks why you aren’t using your copilot license” stage of mandatory roll out.