Domen Kožar

Welcome back friends :)

Or just work from home 🥹

And this is why secretspec.dev is getting required prompt confirmations in 0.15

@penberg Yeeess 🤩

Turso 0.7 is now released 🚀 Faster concurrent writes, improved SDKs, and more! turso.tech/blog/turso-0.7…

Devenv absolutely crushes using docker compose, so fucking good

@ryantm @sandydoo He knows

@sandydoo What does Sander know?

If nix is so good, why hasn't it been vibe rewritten in Rust.

@samuellhuber I'm so happy to hear that Samuel :)

@domenkozar using this to thank you for creating devenv! it's such a joy to easily manage complex environments like s3 (rustfs) + k3d with helm in one configuration file that then validates the whole infrastructure before k3d was manually configured -> error prone thank you!

We're extending devenv availability for another week! Happy to see what you build.

@ImLunaHey That's the whole pitch for secretspec.dev

hot take: using .env files for secrets is wrong and we should move away from this.

@avi_press It's weird to me how all these communities always develop into the same way. You're not welcome to create something over a weekend and show it anymore, but everyone is welcome to write their "it's slop" 10 times.

Good discussion on this in various places. So far of all the (expected) hate this got, I am most disappointed by how many people simply did not engage with the technical points at all, instead falling into: - "I dislike AI" and/or "You have AI psychosis, sad". - "Just a CEO espousing business bullshit with no technical merit" If you have absolutely nothing to learn from our experience, than you must be very wise indeed!

@avi_press @hmemcpy It's all over the forums

@hmemcpy Same. AI is a trigger-word over on r/haskell right now it seems.

well, I wanted discussion, I got discussion

@avi_press I'm surprised you didn't pick Rust, must be cultural

For secretspec 0.15, I'm iterating on: a) how secret retrieval would require explicit via GUI prompts b) entering secrets via GUI prompts groundwork in github.com/dsociative/pin…

I just love the way agents dance here #issuecomment-4936888356" target="_blank" rel="nofollow noopener">github.com/dsociative/pin…

@meekaale Sigh @mtasv.net/T/#u" target="_blank" rel="nofollow noopener">lore.kernel.org/git/7c8b4673-3…

@domenkozar i know a guy who could implement that PR in under ten minutes

Who do we have to poke to get worktree create/delete hooks into git?

I had the same thoughts when I saw Anubis the first time, AI turns out to be much better at captcha than humans.

I still think about this a lot

danklinux is out and it's best desktop I've ever used. Feels like android but on linux. danklinux.com/blog/v1-5-rele…

Every provider understands it, from the CLI and from every language SDK. secretspec.dev/blog/secretspe…

The part I like is a design decision: the coordinate is naming only. Which store resolves it is still your provider chain. So the same declaration reads 1Password in prod and a local .env in tests. The secret's identity never moves, only where it gets looked up.

secretspec 0.14 ships ref. You can now declare a secret that points at one you already keep in 1Password, Vault, AWS, or a .env file, using that store's own name for it. No migrating your existing secrets into secretspec's naming first.