There are much better ways of device enrollment; at a minimum they could require device activation that doesn't blindly use a token with no further checks.
I'm concerned about publicly accessible devices containing secrets also. These are not physically secure places to store keys, they are mounted on street lights where anyone with a ladder can get the key material out of the device.
* Privacy, civic trust, society if you get a chance!
This is the end product of tech leadership taking fat rips of disruption cocaine for the last 15 years. Flock Safety got VC money so that they could build a panopticon. There is nothing surprising about the fact that they did a hack job with terrible security; the fact that their service names are various types of alcohol is beyond parody.
Oh well, at least Flock Safety's IPO will be a critical cash infusion in the pursuit of building the torture nexus so that's cool.
In this metaphor the police are corrupt, running a protection racket, and might get drunk and shoot you while your dealer is in the mafia. The mafia link might be a problem at some point but the person with the badge and the gun is a problem right now.
Manufacturers could add modems to bypass the need for a wifi or cable connection, like they do in cars. I would expect by now that's a valid question to ask if I were to buy a new TV.
In practice this requires duplicating the upstream build and release pipelines, so now you need yet another agent running in the background (+ periodically going off the rails + eating tokens) which incurs more up front cost and cognitive overhead.
In my experience "throw another agent at it/fork it" consistently creates unsupervised trainwrecks.
Fully agree with this. I did that for pi for a while, maintained it and brought merges from upstream while having my own patches on top but then went on holidays and there was that refactor where the agent pipeline failed... now I'm stuck on the version from april/may (works great but I can't use extensions; and I'm too lazy to debug/fix while everything works great).
off: I'm working on my spare time on a code mode lisp alternative (great opportunity to learn lisp) and might switch to it fully as long as I built some simple evals (I'm concerned about token usage, which is why i forked pi the first time)
Granted fossil fuels are much more ubiquitous than CFCs and comparatively more difficult to replace, but we have prior art for changing industrial practices in the interest of improving climate conditions.
That was an awful lot simpler, int aht we (or rather governments) just had to lean on a small number of manufacturers and tell them to find alternatives for CFCs in their products. Nobody was up in arms saying 'my hairspray isn't the same without CFCs' or whatever. I'll bet the majority of consumers never even noticed the difference.
My memory was that once satellite imagery of the ozone hole became available and it suddenly became something you could actually plot on a map the serious debate suddenly ended and complaining about 'they took our CFCs' became a kook issue. But looking up old media coverage, I see that dissatisfaction entrepreneurs like Rush Limbaugh aggressively milked the issue and then recycled successful tropes in other contexts.
I'm still on opus 4.6 for a healthy chunk on work; the technical competence has lagged behind but the slop-comment generation and misdirected self-initiated actions on newer models ultimately burn more time than a little more babysitting, but I'm optimizing for minimized slop generation over sheer generation speed.
Yeah I'm using 5 for its technical abilities, but I much preferred 4.6's personality. 5 loved to double check everything, including the double-checks, and I have to stop it and tell it "this is irrelevant" or "this is out of scope" all the time, or sometimes I'll go leave it to do a task and come back and it's still verifying the tiniest details of its assumptions before actually doing anything
Have you tried Sol? Just curious. I don’t wanna sound like a shill, just feels like every generation it’s important to reevaluate models and pick the best again.
I do find myself returning to 4.6 for casual conversation - asking it to help explain some science/engineering or news to me.
Show me a fully LLM-generated database with an implement that's clear, documented, and adequately bug free.
Codebases degenerate when the authors do not understand the system in which they operate and make changes that degrade the cohesion of the system as a whole. Humans do this all the time; at my company we had a 10k line lua function (within a 250k loc lua service) that grew through ten thousand point modifications. It's bad and humans caused it. Now, it's 15k lines of code and 10k lines of misleading slop comments.
LLMs do not go through the struggle of understanding and don't experience the distress of "wtf am I reading?" and don't experience the drive to make things less horrible for the next person. That suffering loop is how many codebases halt degradation and in the absence of suffering LLMs will pile bugs and rot endlessly.
I was arguing with a colleague today that we will never have a reason to make our AIs autonomous and sentient. But now I can't stop imagining an AI startup meeting where somebody says "LLMs do not go through the struggle of understanding and don't experience the distress of "wtf am I reading?"" and the next second the technical founders jump in joy "...that's our way in! Let's outcompete the competition by inventing pain for AIs!"
> we had a 10k line lua function that grew through ten thousand point modifications
> It's bad and humans caused it.
LLMs do the same thing. I review the code and interrogate the model about the bandaid fix it applied until the proper architectural solution becomes clear. Then the model implements the correct solution which usually involves some major refactoring.
> LLMs do not go through the struggle of understanding and don't experience the distress of "wtf am I reading?" and don't experience the drive to make things less horrible for the next person.
Of course not. That's the human's job.
And it's not every human either. Way too many humans are actually quite content to ship whatever works then go the hell home. Just a job after all.
> software is robust/rock solid but the code is essentially unreadable
I come across this fairly frequently. I think it's because the code has simply been tested into submission. So it works for that particular set of use cases, but the instant you try to add a feature, it all falls apart.
Virginia has more power infrastructure in place but said infrastructure is already seeing significant DC build out; I know little about power distribution in Louisiana but would be surprised if there was extensive spare capacity in the transmission lines and generation facilities. I'm surprised that the rust belt hasn't seen more uptake since they had all that manufacturing capacity but the backing power generation/distribution may have atrophied in the intervening years.
> I'm surprised that the rust belt hasn't seen more uptake
Oracle's doing something just outside the Milwaukee metro. I'd imagine there are others. Datacenter buildout is wildly unpopular around the Great Lakes, and that's not new. For Wisconsinites specifically, the whole thing has a whiff of Foxconn about it.
Some of the largest proposed data centers in the US are in Pennsylvania, West Virginia, and Ohio. The electricity infrastructure is important so is cheap natural gas from the Marcellus shale, natural gas pipeline infrastructure and relaxed regulations.
reply