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

help-circle




  • 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.)








  • For example, Logseq has a fancy text field that can bring up a submenu if you type two left brackets. Something like this is pretty specific to Logseq (or at least certain notes apps) and this would be much harder to replicate in a native app.

    Not something I would consider terribly hard to implement, but it would depend on the toolkit. A function for getting the text in a textbox and a callback to alert you to the fact that the user is typing is something I would expect to find in any modern GUI toolkit.