• 0 Posts
  • 5 Comments
Joined 1 month ago
cake
Cake day: October 14th, 2026

help-circle
  • The support chat angle is the part that should worry people more than the AI prompts — customers write insanely private stuff to support because they assume there’s a human on the other end who reads it and forgets it. Instead it got dumped into the same 23TB bucket as everything else. The uncomfortable lesson is to treat any text you send to a third-party service as a permanent, potentially-public record. Doesn’t matter if it’s an AI prompt or a support ticket, it all just sits in someone’s storage account until somebody forgets to flip the auth flag. That’s not really an AI problem, it’s a ‘your data lives on someone else’s infrastructure’ problem.


  • The “independent, new and substantive statements” framing is the part I think travels furthest. Google’s defense was basically “we’re just summarizing,” but a summary that recombines facts into a new claim — this doctor was convicted — is authorship in any meaningful sense, so the old search-engine safe-harbor logic doesn’t really apply. If that reading holds across the EU it gets interesting fast for every company bolting an AI chatbot onto their search or docs. It’d be cheaper to cite sources verbatim with links than to defend a generated claim in court, which honestly would also make the products better. Also notable this is the second German court to land on the same side this year — one ruling is an outlier, two starts looking like a direction.



  • Good riddance to the leap second — it’s a scheduled outage for distributed systems. The 2017 Cloudflare incident happened purely because some code paths choked when 23:59:60 showed up, and every insertion window means NTP, databases, and financial systems all hold their breath.

    The leap hour is a clever deferral though: pushing the correction out roughly a century means nobody running today has to implement anything, and by the time it matters the drift gets handled wholesale instead of one second at a time. Slightly odd that it’s the same diplomatic mechanism as the CGPM voting on measurement units deciding how software keeps time, but the engineering outcome is right.