Is there a NixOS tool that can retroactively record what I did and translate the changes into the config file or do I have to write down each and every change manually again and again?
It’s generally best to make the change in your configuration.nix or flake.nix rather than with the imperative tools. Then you just version control that file (or files if you break it up)
Temperatures monitoring will be added. Initially, I implemented too many metrics, so during development I limited them to a reasonable level to make them manageable, but I'll be adding more as the project matures. Thanks for the feedback!
If you have a moment, I would be grateful if you could create an issue on github. I will then be able to let you know when it's ready and ask you to try it out. Please also let me know which temperatures you'd like to primarily monitor. I assume I'll have to gradually introduce the supported ones, as not all of them can be detected at once.
Sure thing. In my experiences based on using LibreHardwareMonitor [1] on Windows, and Dunnart [2] on Linux, dealing with temperature monitoring is not trivial. But it's not impossible either. For example, in Linux, looking at /sys folder for CPU temperatures, I can often find several entries, of which, some are dead, some are way off, and some are correct, but it is always a hit and miss endeavour. So, reliably monitoring temperatures requires a bit of an algorithm to detect the right source.
Yeah, that's a pain. Every time I boot up new hardware, I wonder how many readings I'll be able to get this time, and if it's even possible. On one computer, I have practically all the temperatures, voltages, and fan speeds, while on another, I can barely read the CPU temperature alone. Not to mention the need to sometimes compile sketchy drivers from github...
Fair question! NOVA is built on a different structural foundation. We operate as a terminal native execution layer designed to interact with your codebase and file system through a proprietary approach. It is really a difference in engineering philosophy because we focus on autonomous system level changes rather than standard session based history management.
both do if you can run python in WSL. I'm running both server and agent on a windows test machine, but I admit I'm not a windows user... also pro is free until May, so don't worry about costs. You can always hit me up for a free key after that though, I'm pretty loose about it.
Hi, this looks like a dream come true IF it can work correctly. So I started testing it today and I hit a make or break corner case: as long as the radio stations themselves are strong (in network sense), the AI is recognizing speech correctly and shifting the radio stations. But, if a station network connection is weak and the packets are being dropped, the listener is left hanging with silence. So, I believe you need to make the player resilient to these problems and to treat network disruption same as speech. Thanks.
Some use cases are better served by a system-wide process, I agree, but when I think source code, I think VSCodium. It is about configuration and starting/stopping. I don't mind the browser based web UI, but I do mind having to babysit one more (albeit super useful) tool. I'd rather have it as a VSCodium extension that would AUTOMATICALLY start when I load a workspace, configure the watched directory from that workspace, and stop when I close the workspace. So instead of me spending my attention on babysitting UNF, through VSCodium, UNF would just follow me wherever I go with zero configuration needed.
Well, if I have 10 different projects across 10 different drives, then, yes, I would need to babysit it. Furthermore, I wouldn't want it run it 24/7, but only when the files are actually going to be changed.
Thanks for the feedback. Didn't really consider folks may want a transient mode which shuts off after session completion, e.g. no edits in X timeframe. Interesting idea.
Very interesting, thanks. I would like to contribute to make it usable on windows (spare time permitting). I've noticed that the design proposes Windows OCR for recognition purposes. Judging by my decade long use of Microsoft PowerToys which does have a built-in screen-snip-OCR tool which also uses Windows OCR under the hood, that's barely usable. More times than not, I get maybe 50% accuracy which I then need to fix up using my own eyes and brain. So, from a get-go I would say Windows OCR is a no-go for this purpose.
Fascinating. This is exactly what democracy needs. The only way to keep the ruling class accountable is by demanding total transparency. We need this on all levels of government. Thank you and keep up the good work.
reply