363 karma · joined September 9, 2014
I'm not sold on SDD yet, but part of that is because we already have decently detailed tickets and designs.
It looks pretty interesting though, I'll give it a shot
I've wondered if it'd be legal to just chuck a couple into some random trees.
Having a nice tui/plaid sync for plaintextaccounting would be nice.
Also I'm going to complain a little bit about the name: SMTP is for sending (not reading) mail, so asmtp to me at first glance looked like 'async-smtp' which didn't really make sense. And 'agent-smtp' sounds like "let your agents send e-mail" vs an api spec.
_Should_ I give my money to unknown worlds?
I'm hoping local llms start rapidly improving even more though.
Or maybe another option would be to outsource the search part to "site:yourdomain" on google or something similar.
Not op, but one reason I have a speaker in _almost_ every room is for notifications. Simple stuff like "the garage door is still open" or weather alerts, etc. I rarely actually play music on all of them.
My assumption is that they are extremely excited about AI, because they are also extremely excited about being able to reduce their workforce while expecting more output from smaller teams.
Doom emacs and Spacemacs are both good starter kits to give you an idea of what you could do.
I didn't know irssi was still maintained in 2026. There hasn't been a release in a while, but there are at least a few recent-ish commits. Has everyone moved on from irssi to weechat?
You could a) have the app acquire a lock in the db and do its own migrations, or b) create a k8s job that runs the migration tool, but make sure the app waits for the schema to be updated or at least won't do anything bad.
I really appreciate that you didn't include a "curl | bash" command to paste for installing, but at the same time it's what I was expecting when I clicked.
I'm pretty sure I saw a comment on HN where the user wrapped all of their npm/pip/etc commands with bubblewrap. I've been thinking of doing something similar and basically just seeing how many of my daily commands I can sandbox. My hunch is that _most_ of them don't need to operate outside the current directory and don't need internet access.
One example experiment I had was seeing if I could get a llm to build its own knowledge wiki where I would paste a few links and have it go do some research on whatever the subject was, then distill what it finds into specific wiki pages with links to other pages or the source refs. It looked good until you read the actual data.
This was a few years ago though, so maybe it's worth trying again with something like opus 4.7.
(that's one of my biggest hurdles for really adopting any useful assistant type of agent)
But my counter argument is that the generated code can easily balloon in size and then if you ever have to manually figure out how something works, it is much harder. You'll also end up with a lot of dead or duplicated code.