Blog

Am happily taking advantage of the MIT license NVidia PAIR is released under (releasing this stuff under the same iirc), and given that it's just released v1.0.0? Looking at where it can strengthen the mAIstr0

IISIDSD v0.2.2 has been released - it's working a lot better than it was, the dashboard can be accessed when running as a service, and settings are exposed if you are a local admin and running in admin mode

Given the fact that I now have several pieces of operational software? I think I need to add this activity to the top of my CV The HA1GH Software company DYNDNSD - a TSR daemon that updates a DNS "A" record when required flm-vscode - a VSCode extension that facilitates access to an NPU-compatible local LLM on FastFlowLM's server IISIDSD - an Internet Defense System for IIS (daemon) mAIstr0 - a cluster orchestrator for local LLMs rDeskm - a remote desktop manager* :P *no released version yet

Busy getting ghosted after the second interview for a job I was looking at (both interviews went rather well, or so I thought) Also been doing a lot of work on mAIstr0 and IISIDSD mAIstr0 has ""borrowed"" some of the nicer features from NVIDIA's PAIR, but is a different offering - it's working as a proper orchestrator, splitting tasks into sub-tasks and farming them out to the most appropriate node in the cluster. I need to re-address how the agents/harnesses are interacted with, also need to add support for more agents/harnesses - need to build the ability to vet the most appropriate agent/harness for the task into the orchestrator tldr? It works! not fast - but that's gonna be because of my shitty gear :D, better gear will gain a much better response IISIDSD is also getting some love to - it's not working the way I want to, but it is working Film at 11

Due to me being a total plank, I've had to start over because I tried too much too quickly and broke things (and, like a muppet, I didn't have source control enabled (I do now)) The project itself is looking better than it did when written in C++ (it's now C#), but it is lacking the full functionality of the original It needs some cosmetic changes, changes to how the data is displayed/stored, and it needs to be able to modify the IP DENY lists of the targetted server(s) in a way that does not cause the website or application pool to recycle (I know it can be done, that was part of the functionality that broke :P) 1 step forwards, 3 steps back - but it's a learning experience - make a repo for everything!