c-hendricks
There's lots of solutions, I also find compose hits the sweet spot for integration into my homelab
Using settings on the indexer isn't great since with Prowlarr the user doesn't actually interact with the indexer portion of Sonarr.
Doing it in release profiles by bumping down their score is a cute workaround but then the torrents will just stop saying ".exe" in their title.
Really it's a thing Sonarr have to do, as evidenced by the multiple PRs they have to try and finally do it.
I see people talking about this being new in v2 everywhere but it's not the case. What's new is that it's the default (and also not really since `opencode service` and `opencode serve` start two different things). But in v1 it was very possible to run one opencode instance and have multiple clients connect to it (like Openchamber and neovim).
Paseo is a layer on top of various harnesses (aka you get to use a Claude subscription), and keeps its own database of sessions, etc.
I use Openchamber (and another client in neovim), but Paseo does have one convenient advantage where you can connect to other paseo servers
Your info might be like decades out of date, since windows 10 it's just been an overlay and locking out some appearance customizations (you can still set them via other means though).
I've tried a couple of times but just gave up because zigbee/zwave work well enough and I'm not sure I'll like where thread/matter end up in a decade.
MCP in some harnesses bloats context. MCP in some harnesses doesn't bloat context.
Definitely helps that the home assistant api is documented online most likely in the training data.
The ideation of features, their requirements, getting code for features written, testing the features, seeing how they fit in with the rest of the landscape, and maintaining those features. Same as before. Do those go away in your future? Even with the aid of AI agents, do you really think billions of people will want to go through that process every time they want a device to do something? Do you really think the younger generations who are being told AI will replace them will also embrace AI?
Similar to how even your hypothetical devices of the future still very much have an operating system (a kernel, libraries for software to interface with hardware, a standard suite of apps and tools, an environment for the user to kick things off)
> You might as well just say "I think you're overestimating the general public's interest in using computers"
I might, because I think the general public doesn't much like to "use the computer". It's what they need to use for work, or school, or how to listen to music or watch what they want to watch.
We're only just starting the general public's introduction to agentic AI with Siri and some Android devices. I'm betting there will eventually be some horror stories.
Just with the bit I quoted above, that seemed like a big misread of the market and the implications of everyone writing their own apps.
In this future, are people paying the API pricing of traffic providers? In this future, who's supplying the traffic data if no one is using their mapping apps?
> Is there a meeting happening anywhere right this minute that I’m supposed to be in?
> You can go on and on like this. These all sound trivial. That’s the point. They’re normal-life problems nobody would have built serious programs around, because the audience sounds too small.
Waze and Calendars. Both have huge audiences.