And honestly that's for a reason. GLM5.3 on max has in my experience far less hallucinations than any other open weights model and it feels it has some intuition to bring in the right information when it's in principle out of context but relevant to the topic. Like its goal is more to bring value and assist you than just solving the given task with the least token spent.
The funny thing about Revolut is, that they send you from the same "no-reply" address your payment receipts and a ton of spam. There is no link in the spam do stop it and no obvious scheme in the header which would allow to filter the spam from the relevant mails. Good luck recognizing this breach notification as an important one...
I'm somewhat confused. Its an interesting posting but I'm not sure if I understood exactly where he was going with his "policy as code". He concludes "policy-as-code produce enterprise coherence with no central architecture function" to which I would agree but argue that he misses that today there is a lack of infrastructure / company as code. At least if you want to have an agent being able to solve or at least aware of the problems he begun with. Like the policies define the boundaries of our working environment but doesnt the work itself. This "know how" is mostly implicit for people but invisible to llms and limits the context frame in which the agent operates to its given prompt (and maybe restrained by the policies if they're in the context).
Like if I take his example:
"Front-line staff may be skipping mandatory fields because the process adds fifteen minutes of friction to every customer interaction."
First it's unclear whats the policy for those fields are when they are mandatory and also can be skipped. Then why are those mandatory if skipping them seems only lower friction with no other consequences? How should a model decide if it should enforce the policy for those fields, code an automation or just make them voluntary?
But those people who doesn't slop their app them self seem to let their llms install appslop from github en masse. At least that's what I conclude after looking at some recent 50k+ star repositories.
At least they seem still provide results for my searxng instance. I mean sure, they are horrible but duckduckgo just blocks most queries (and I'm the only person using the ip / seraxng instance)...
Next i'll do is to implement tavilly, exa, tinyfish etc. as search engines for searxng. No agents, no mcp, just their search api endpoint.
In my opinion the biggest advantage of podman is that it uses pods with basically the same config and behavior as kubernetes does. As long as you just use podman pods instead (or possibly via) compose files you likely just notice that only the pod has one (and not any more) veth interface, that you reach other containers inside a pod via localhost:$port (instead of $service-name:$port) but when you switch later on to kubernetes you are already familiar with some basics.
I don't see much hope since I last explored some github repositories. There was a time when a successful repo had about 10 - 20k stars and usually those older repos stay around this level. But now there is a ton of vibe coded slop 50k + stars. Most of them have a "nice look", maybe even extensive docs but are usually build with no security considerations at all. One recommended to provide a "google app password" to the agent which has the same permissions as your regular login. Another was a browser plugin with permissions to read all cookies, inject js, open background tabs etc. You would probably assume the chrome store would at least put some visible warnings on the app store page or force the user to actively confirm those permissions. But because they are already stated in the manifest there is only a small footnote and it's even "recommended by google".
It's a good time to reduce the reliance on technology.
Throw out the IoT and "smart" stuff from your home. Remove apps from your phone and leave the absolute basics. Go through the password manager and close accounts for sites you are no longer using. Start migrating off Google. Print out your most precious photos on paper. And so on :-)
A dead giveaway that I think it's AI-made (not necessarily a con) is the complexity of the UI and redundant information. Things like the green dot paired with "interface is up". It looks polished though.
It's not hand coded. I've built it because I've needed for my own purposes.
I've tried wg-easy, but I didn't like the docker approach because it implied to dramatically alter my setup. I just wanted something to manage my already existing setup, something simple and effective. And the coding agent was good enough to built quickly what I needed.
That's maybe the case if you always use the most popular framework and restrict your environment to a basic setup. But as soon as you e.g. build a website with SolidJS, Bulma and vite++ (vp), at least the models I tried are all the time somewhat confused, want to steer your project in a certain direction and build strange workaround so it works the way they are trained on.
Same with mcp. I want them to use the jsdelivr cdn instead of them scraping github against the rate limit. etc. But if I dont explicitly state to strictly use the $%!$@@! mcp for searching in repositories they simply ignore the mcp and even if clearly instructed, they still often fall back to gh.
Putting every detailed instruction in the AGENTS.md would just unnecessarily bloat the context and it works well enough to just instruct them in the AGENTS.md when to use which skill. Yet I agree that Skills are not some voodoo magic to provide your model super capabilities.
I must have spent several days answering design decisions via /grilling in putting it together, so if there's a specific aspect of it you think is unsound, it's probably one I made myself, and I'd love to hear it!
