I used to help nonprofits and small businesses build websites. Process always went like 1. buy domain, 2. buy a shared hosting provider that one-click-installs Wordpress, 3. use a theme to begin editing the website. Often, I would also use the email included with that hosting provider for the firm.
ALL of that goes through cpanel, for every shared hosting provider I can ever remember using. Even if the stuff happening on those servers didn't use perl, cpanel itself -- the admin of everything provided for that domain by the hosting provider -- it's a huge surface area.
I don't see it as fetishizing byte count. I think of it as a proxy measure for how complicated or uncomplicated the exploit might be. They could just as well have said "we can do it in 3 lines of python" or "the Shannon entropy of the script implementing the exploit is really small" and I would have interpreted it similarly.
Where do you see this "fetishizing" happening most often? It's a strange thing to counter-fetishize about.
> I think of it as a proxy measure for how complicated or uncomplicated the exploit might be.
From a Busy Beaver, 256-bytes compo, or Dwitter perspective, 732 bytes isn’t really that meaningful.
And the sample exploit is even optimizing the byte size by using zlib compression, which doesn’t make much sense for the purpose. It just emphasizes the byte count fetishization.
Again, I think the point is that compressed size is a reasonable measure of the inherent complexity of a program. I'm a crap mathematician, but I believe that is a fundamental concept in information theory.
They probably won't buy Honda Civics, but they (or their children, more realistically) might buy the electric equivalent of an F150 if the market produces one that can fulfill what they perceive their needs to be.
I just bought a (small, hybrid) truck because I need to do some truck stuff. I 100% would have bought an electric if the market produced one with comparable capability and competitive price, but we're not there yet, and I don't have Rivian money (yet! lol maybe someday).
My point being: there is still a huge demand for trucks from both a capability and culture standpoint, and very little supply of a cost-comparable product that doesn't take gas or diesel. Rivian is around double what most people want to pay, and the F150 Lightning was marketed poorly and had bad towing/hauling range compared to gas/diesel equivalents.
I'm not here to defend "truck culture" but I do believe that if you offer people a better product, they will figure it out and buy it. An electric truck with 400+ miles of towing range, an onboard 2kW+ inverter, 500 ft-lbs of torque, and fast charging for the same price as a comparable gas F150 will sell. Unfortunately the battery energy density and EV supply chain economies of scale aren't there yet in North America.
Have you considered that "very weird writing style" might be due to the fact that a German person is writing in English?
One post a day over the last short period of time does not seem unusual for someone who is suddenly interested in a least a part-time career as an author.
Your random online persona assassination aside, I am curious about the book. The Devil Book kept me occupied for years when I was in university; I'd like to see what I've missed since then.
> “The raw output of ChatGPT’s proof was actually quite poor. So it required an expert to kind of sift through and actually understand what it was trying to say,” Lichtman says.
This is how I feel when I read any mathematics paper.
Tbh, a ton of academic papers are quite poorly written. I'm not a PhD researcher, but I did have to implement quite a few of the, (computer graphics, signals & systems etc), and with most of them, I basically reconstruct the author's tought process from scratch.
The formulas were opaque, notations unique and unconventional, terms appearing out of nowhere, sometimes standard techniques (like 'we did least-squares optimization') are expanded in detail, while other actually complex parts are glossed over.
My short academic career where I did my share of "what the hell are they saying they did" reverse engineering others' papers proved to be an excellent training for when I eventually transitioned to engineering.
reply