By default, sharing a sudo password between PTY sessions is not allowed by your operating system. This can be a frustration when using Waveterm because every command is treated as a separate PTY session. To get around this, Waveterm will cache your sudo password in local memory (not written to disk) and share it with a session when provided.
Holy crap, no thanks. That’s legit awful.
I use this as it is currently the best option available, but it really doesn’t compare in terms of speed
What’s the problem with the blink engine?
Multiple implementations is good for everyone.
legallyDistinctOpenSUSE
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 last used it seriously like 7 or 8 years ago and it was fine. I put it on par with GitHub at the time. The ability to self host for free without too much trouble also really affected my position on it.
I haven’t really enjoyed the few times I’ve had to use it in the last couple of years, though.
Looks like Kubuntu in the high res image