News for hackers. Stuff that matters.
Re:Tracking SQLite Database Changes in Git by upon_drumhead on Thursday November 02, 2023 @05:07AM (#38110780)
That’s a really cool trick! I’m going to have to see if I can apply it to other things at work as well. Maybe a image to ascii and then a diff would be useful…
Re:Tracking SQLite Database Changes in Git by klabb3 on Thursday November 02, 2023 @05:19AM (#38110888)
Here’s an idea for the AI folks: ask it to explain the differences. Imagine something like like:

“The same screenshot of an iOS app, but the Subscribe button is clear blue and more prominent”

(Although it wouldn’t work directly, since it looks like git runs “text dump” on both independently and then compares the text naively).

Re:Tracking SQLite Database Changes in Git by TikolaNesla on Thursday November 02, 2023 @05:35AM (#38111019)
""""AI""""
Re:Tracking SQLite Database Changes in Git by bambax on Thursday November 02, 2023 @06:19AM (#38111354)
If the process of image generation / description was fully reversible we could store image descriptions instead of a list of pixels...

But if one feeds an image description from chatGPT to Dall-e and back in a loop, how many steps does it take to revert to pure noise? (surely this has been tried? but I couldn't find it)

Re:Tracking SQLite Database Changes in Git by klabb3 on Thursday November 02, 2023 @11:05AM (#38114498)
I mean there are billions of perceptually distinct images that map to the same “text description”. So text would generally be both lossy and inefficient.

> instead of a list of pixels

We don’t store lists of pixels. Not even lossless formats like PNG does that. Good ole JPEG has 1:10 - 1:20 compression ratio, ballpark.