Well, it's the enterprise software house pipeline... The software architect writes the spec, hands it down to the implementation team, senior leads, junior devs or offshore teams codes it.
I also disagree with the approach, this is cargo-culting the existing ways of working.
Exactly. Sometimes I just need a 3D printed part to finish a DIY project, I don't want to waste hours designing it. I had my fair share of time playing around with SketchUp when I was a teenager, but that's it.
Criminals don't need Astra or Fable. Get a bunch of GPUs, a good enough open weight model and a custom harness. What the model doesn't have in its weights it can research the Internet. How do you think black hat hacking is being done right now?
On bio: while it's easy to order all the raw material, there's the whole process of culturing bacteria/viruses/etc. that isn't trivial, and while a LLM might help in explaining stuff for rookies, there needs to be somebody physically working on it. It's not automatic. Once you get to this level, you'll find that any undergrad biologist or chemist can already make bio/chem weapons, and you don't see it happening. Terrorist groups already employ biologists or chemists that are supporters of their cause, no need for LLMs.
On cyber: aside of the question of why critical infrastructure is on the Internet on the first place (ah yes, lowest bidders, people not caring enough, business not giving IT/OT budget, S in IoT standing for security etc), if the available models can't handle cyber tasks, how can you defend yourself? See the HF "attack" that HF had to use GLM-5.2 to investigate what happened. This is the best argument for open models. Unless of course, you are the AI model creator or somebody they authorized to use their sanctioned model/harness and want to create a moat for their business.
Uh, actively trying to hack an embedded device that runs Linux over the network, specifically an IP security camera, could be considered red teaming, no?
You never mentioned which exact activities you were getting flagged on and getting refused.
> Uh, actively trying to hack an embedded device that runs Linux over the network, specifically an IP security camera, could be considered red teaming, no?
No. Vendors (and their model guardrails) do, indeed, treat those as separate from pentesting non-embedded infrastructure, and that is because they are very different activities.
And, if you actually read my comment, it says "red team my own computers". That's categorically different from pentesting an IP camera.
> You never mentioned which exact activities you were getting flagged on and getting refused.
Because further details than those I've provided aren't relevant, and it's clearly different from what you're doing.
For my own stuff I simply don't care if Z.ai is learning straight from me or from my GitHub repo a few days later when I push the code.
When I use it for reverse engineering, same thing, the code is already out there, but in binary form, which is becoming trivial for these LLMs to work on.
I even bought some shares from them and got some money out of it!
Why do you assume $20k as the cost to run the fiber?
The cost is the contractor's hours to get up a ladder on each electricity pole from the closest PON splitter to the customer's home, plus the fiber itself which is peanuts at volume.
Everything else (permits, pole rent, etc) is accounting money that can be negotiated. If there's a strategic national program to fiber up the whole country, this could be exempted on a pen's stroke, or depreciated in many decades.
The last emerge conflict I had was handled 100% by an agent.
I'm not wasting my weekend on stupid sysadmin tasks anymore.
reply