![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
What’s the problem with the blink engine?
Multiple implementations is good for everyone.
What’s the problem with the blink engine?
Multiple implementations is good for everyone.
legallyDistinctOpenSUSE
I was handed one of these when I was on a church trip as a teenager. One of many many reasons I became disillusioned, but pretty funny in retrospect.
Fun trip down memory lane. Also, bitchin’ domain name!
Also, when you start hosting more than 2-3 services, keeping them up-to-date might become a hassle which you can forget. For docker-based hosting I’d recommend you setup watchtower, which can keep your servives up-to-date for you.
I would caution against automatic updates! Notifications, yes absolutely. But automatically updating things is a great way to have things break suddenly when you’re not in a good place to troubleshoot.
I would enjoy training a LLM on my aggregated command history and using that for auto completion, or maybe using an open source one trained on a larger set from the community, but I am very uncomfortable sending data about every command (as I’m writing it!) to any company.
This might be a little more than you’re asking for, but I would recommend something like Node-RED with a feedparser. Reason being: it opens up a lot of options and could be a useful tool for things other than this one use case.
I use this as it is currently the best option available, but it really doesn’t compare in terms of speed