[–] 10 points 1 month ago (1 child)

This sounds exactly like the "Expert Systems" - ie, an interactive flowchart, we had in the 80s. I do wish people would stop labelling everything AI.

  • source
  • [–] 29 points 3 months ago (1 child)

    Lots of respectable EU hosting companies, and also aparently OVH, if they think there's a chance you're taking the piss will ask for a ID so they can ban you. It's not just anti-spam, it's anti-abuse and for preventing non-payment. They think there was a risk involved in accepting your business (whatever that may be, obviously companies don't dilvulge their criteria here), and if you go elsewhere they're not upset about it for that reason.

  • source
  • parent
  • context
  • [–] 11 points 5 months ago (5 children)

    Second person into my polling station this morning. Looked at the odds at 0630 and voted as tactically as I could. I am now going to be in a constant state of clenching until the results are announced.

  • source
  • [–] 2 points 6 months ago

    If you saw the keynote at FOSDEM 2025 from Mozilla, you'd almost think their entire senior management are entirely untechnical and have got through their career by repeating buzzwords they heard in other meetings. Totally vacuous, AI trend-filled, and nothing tangible at all. It does not surprise me that it has continued.

    I really hope they fix their direction or one of the new browsers in development can become useful enough and different enough to use and be used - having the open web be accessible using only one family of products would be a difficult-to-undo disaster.

  • source
  • [–] 2 points 6 months ago

    No, I'm saying that JPEG XL can perfectly represent old JPEG/JFIF data, so on the server side you can store all your image data once and more efficiently, and still support old clients without any lossy cascade or the CPU load of having to re-encode. That is what is meant about it offering backwards compatibility.

  • source
  • parent
  • context
  • [–] 8 points 6 months ago (2 children)

    So now it will be an intentionally ineffective unintentional waste of money, rather than an unintentionally ineffective unintentional waste of money.

    I'm not sure that's actually any improvement at all.

  • source
  • [–] 37 points 6 months ago (6 children)

    It's "compatible" in that it can represent old JPEG/JFIF data more efficiently and in less space, and the transformation to JPEG XL and back to JPEG/JFIF is lossless (in that you don't lose any /more/ quality, you can get the same bits back out) and quick enough to be doable on-demand. You could, for example, re-encode all your old photos on your CDN as JPEG XL without loss of quality but save a bunch of disc space and bandwidth when serving to modern browsers, and translate dynamically back to the old format for older browers, all with no loss of quality.

  • source
  • parent
  • context
  • view more: next ›