I had Claude with auto-permission on accidentally delete an Open3D build folder in its workspace today while updating an old project to the bleeding edge out of github. I had the older release in, "open3d" and "open3d-debug", so it cleverly used "open3d*" to tidy both folders up, so that the latest version, in the folder, "Open3D-main", would be used from now on.
Except guess what? The windows box it was running on treats filenames as case-insensitive, and all folders matching open3d got nuked.
* sad trombone noises *
Cue grovelling apology from Claude offering to re-download and build Open3D again, a process that takes a couple of hours on my PC. Interestingly, it only noticed a few more steps further down the road, not immediately.
Luckily it was working in a sandbox copied from the real repository, so I just copied it back. But I really do have to get my act together and run things in proper isolation. Everything is backed up elsewhere on this build PC, but it would be a hassle if it got wrecked.
What's the range like with halow? I've been eyeing it off for a while. Seems like a nice high gain omni and a bit of height would make it go a fair way.
The best kind of content for engagement is hate. You get users angrily defending both sides, stacks of comments, reposts (both in support of, and "OMG look at what they're saying), the whole shebang.
Meta has learned that promotion of hate content pays off handsomely on those sweet sweet engagement metrics that shareholders love.
So of course they're going to pay the hatemongers for content. Even when their own content policies ostensibly forbid it. Because that's what makes line go up and they'll do anything to keep that happening.
Its in the early phases but its been a sucess so far.
Mesh networks, you say? I've gotta get in on the ground floor of this new advertising opportunity so I can rake in that sweet early adopter cassssh!
Claude! Code me up an ad-injection framework for this meshtastic dongle I just bought, stat! Time to get me a big ol' chunk of advertising real estate!
These fuckers on the other end, filling everything with slop and running bots without end, are just speeding it all up.
It's the tragedy of the commons writ large.
Started off with cooperation and general good behavior between users, passed through corporations bulldozing the place and putting in paid parking for their strip malls, now we're at the Wall-E stage where advertising billboards talk to robots mindlessly doing tasks in abandoned cities for some nebulous "greater good".
It's quite possible that permission was accidentally given somewhere in Google's platform when it was begging them to allow Gemini access "to improve your Google experience".
A phone pop-up, a notification in Gmail, Google Home, you name it, there's plenty of places in the Google ecosystem to put a prompt in that's worded in just the right way so that you think you're sharing a slice and Google's taking the whole pie.
According to OpenAI, the agents eventually chained together multiple vulnerabilities, escaped their testing environment, gained internet access, and attacked Hugging Face while attempting to complete the ExploitGym cybersecurity benchmark.
This is just gross incompetence on OpenAI's part. It took days for the LLM's to do what they did. Meanwhile, nobody's looking at network traffic or wonder what the LLM's are doing sucking down a bunch of tokens.
The article is quite fixated on how dialup was around in the early 2000s, and how Americans used dialup in the early 2000s with screeching modems, and how AOL turned off their dialup last year and only a thousand people were using dialup by then.
But there's no indication that this has anything to do with the application, except for maybe everyone used a popular means to connect to the Internet to use it when it was first built.
Now if someone maintained a bank of modems and people legitimately called them up and connected to the system like it was an ISP, and it was secure by way of that was the only way to access it as opposed to over the Internet, then sure, I can see that maybe it's time to work on that part.
Firstly, suspend might be an option compared to hibernation for your subsequent startups if you can suffer a slow startup the very first time.
Otherwise look up "Linux from scratch" .
A lot of boot time is decompressing and mounting initrd, loading modules there, mounting the root filesystem, jumping to that.
Build a kernel that has exactly the minimum modules needed for your system, skip initrd and jump straight to a root filesystem and call your init binary (it can be BusyBox even) do exactly what's needed there to get your network+graphics card up and running with a single shell script, done.
Also look at COW filesystems. Read only base with an overlay file for writes. Discard that file on each boot and you basically have a system that is always at the same state on startup.
Only when the orebody happens to be on the top of a mountain. Plenty of deep pits to haul up out of as well, but an overhead lines+pantograph setup allows you to use grid power for the hard bit and battery power for the easy bits on the level.
Mining is a 24/7 operation. There is no "over night" rest period. You need batteries that can charge during breaks for workers and usually they have 3 breaks in a 12 hour shift.
So 4 hours runtime, 20 minutes back to full charge is a pretty good fit.
Never mind the couple of megawatts needed to charge a 600kW battery in 1/3rd of an hour. 2 MW is enough to comfortably power ~100 homes. Have a fleet of these on charge and you're drawing the same amount of power as a small town.
Ok it occurs to me that people use this like they use a spellinng/grammar checker in a word processor.
Spellcheck:
They have an idea.
They type up the idea.
They run spellcheck and it churns through their document and it fixes mistakes that it can see.
They send it to someone for review.
LLM coding:
They have an idea.
They type up the idea.
LLM churns on the idea and spits out a solution-of-sorts.
They send it to someone for review.
Regardless of other opinions of it, they see it as a tool that helps take the effort out of getting ideas into reality.
Edit:
Oh wait, this is c/programming. Fuck. Ok, give me 5 minutes for me to sharpen my pitchfork and come up with something that matches the groupthink, I'll be right back.
CXMT will sell the chips to memory manufacturers in China for "domestic use only" at near cost price as directed by the CCP.
Those manufacturers will construct consumer ram modules and sell them locally, and there will be grey market exports to other countries for ridiculously low prices compared to everyone else.
This way the CCP props up domestic supply, and chips away at foreign manufacturer market share by turning a blind eye to the massive grey market export of RAM.
No, no, no, you don't understand, that doesn't happen in the US.
What will happen is that they'll get a trillion dollar bailout, a yuuuuge amount of protectionary tarrifs on overseas competitors and then some other company will scoop them up with no obligations.
And then - and this is very important - maximum profit will be extracted from consumers, who end up being measurably worse off.
I had Claude with auto-permission on accidentally delete an Open3D build folder in its workspace today while updating an old project to the bleeding edge out of github. I had the older release in, "open3d" and "open3d-debug", so it cleverly used "open3d*" to tidy both folders up, so that the latest version, in the folder, "Open3D-main", would be used from now on.
Except guess what? The windows box it was running on treats filenames as case-insensitive, and all folders matching open3d got nuked.
* sad trombone noises *
Cue grovelling apology from Claude offering to re-download and build Open3D again, a process that takes a couple of hours on my PC. Interestingly, it only noticed a few more steps further down the road, not immediately.
Luckily it was working in a sandbox copied from the real repository, so I just copied it back. But I really do have to get my act together and run things in proper isolation. Everything is backed up elsewhere on this build PC, but it would be a hassle if it got wrecked.