• 0 Posts
  • 541 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • The difference between the 65+ bracket and the 50-64 bracket in the original data is larger than the gap between 50-64 and 30-49 on every chart I’ve examined so far (where they’re broken out by age), so the real break is at retirement. Which makes sense: retirees are less likely to be forced into proximity with LLMs whether they want to be or not. (Interestingly, the older demographics are also less likely to think they have enough control over interactions with “AI”.)


  • they should be forced to build their own infrastructure to support it (no idea what that looks like for delivery robots)

    Tunnels, at least in heavily populated areas. They already make pipes that should be big enough. It might require a slight redesign of the bots so that they can “climb the wall” a short distance to pass each other, and maybe extend/retract some bits depending on whether they’re inside or out, but my heart would not exactly bleed over the money spent. And they’d be out of sight, out of mind most of the time for the rest of us.







  • the next step is to debate what is AI and what’s not.

    Unnecessary, in my view. If you use a tool to produce something, and that something breaks a law, then you are liable, not the tool. Doesn’t matter whether it’s a hammer or an AI. If a human employed by Google had written the incorrect summary on Google’s behalf, then Google would still be liable (the difference is that the human writer might also be individually liable, depending on local law).

    Search engines received various kinds of legal immunity in many jurisdictions because they were only presenting information written by third parties outside their control. These summaries are not third-party content, and if they are libelous, the responsibility falls squarely on Google.






  • The overall hardware package is in the same ballpark as an Arduino (25% less storage, but better processor and RAM), and people put servers on those . . . well, I won’t say “all the time”, but it isn’t an uncommon project, either.

    I wonder if anyone’s ever bootstrapped Forth on one of these vapes—given that there are implementations <512b for other arches, it should fit—and then you could program on it directly rather than flashing machine code compiled elsewhere.

    (The issue with 10-year-old phones on Google is that Google isn’t designed for low-end hardware anymore. It’s overloaded with scripts, styles, and other things that aren’t necessary for doing its job. Present a ten-year-old phone with a page with no client-side script and restrained styling, and I’d bet it would do fine.)