timg

efore memorizing", and while this is in some ways true, in other ways it is not. I literally had to memorize crap knowledge in order to pass some exams. Some of it was simply boring to no ends, other things were too complicated, but in BOTH cases, being able to memorize it, helped. I may not always understand everything, but being able to connect at the least some parts, did help, just like a spider web that is built up slowly. With that I could lateron learn more, connect more and so forth. So, while I do agree that understanding is better, sometimes you can not, perhaps you lack time. Even in ALL these cases I had over the years, it still was better to be able to memorize even trivial facts. Of course eventually you have to be picky as to what knowledge you want to store in the brain, since I think it can not store infinite knowledge really (just about everyone forgets stuff eventually), but if your goal is to e. g. pass some exams quickly, then being able to quickly memorize even trivial crap, can be useful. There are a few other things I disagree with too, but for the most part I think this is a very useful blog entry. I am curious what people use else, e. g. other than anki and so forth. Or they may have other learning tricks. I always try to re-align my knowledge when it is for an important topic I care about; topics I once learned but never need again I kind of put into a "storage" preservation mode, e. g. if I ever need it again, I can look it up, but other than that I focus on what seems to be more important to me.

ick supports, like webp compression or posterization or dithering, and print out any parameters of the image, like size, along with the image itself. > With the web version I can snap a screenshot with CleanShot X and then drag that screenshot straight onto the web page. I instantly see the different images, pick one that looks good to me, download that and then drag it into my S3 uploading software (Transmit). In my workflow, I edit in Showfoto or Darktable, resize (or, in my case, more often dither and resize) as demonstrated, and then `cp` the appropriate selected image into my blog's main image folder. Hardly more difficult, and while you might not enjoy it, that's exactly my point - we can both make things we like, but you're asserting that LLMs massively changed the landscape overall, while I'm not using them at all. I also have a script, which took about one minute to write, that cleans up the extra temporary images, so that's not much of a concern either.

e sufficient space for 128-bits or 256-bits to "crawl" around? ----------- Take a very-low quality JPEG compression, but be inspired from the JPEG matrix for discrete cosine transforms for how many "bits" to spend. It seems like JPEG is a 16x16 macroblock (256 pixels). 4-macroblocks would make a 32x32 image. If we're working with a huge hash (ex: 512-bit SHA3), that's 128-bits of data we'll need to differentiate per 16x16 macroblock. That seems usable?? Converting the JPEG into ASCII art though would be the hardest part though! But I feel like that part has been solved already by weird Linux programs (play Doom on a Linux console and whatnot) EDIT: https://github.com/hzeller/timg Seems like modern consoles can view very crude low-resolution images. Something like a 32x32 picture is probably usable on modern consoles. ------- JPEGs have that whole "discrete fourier cosine transform" thing that grossly complicates the algorithm though. PNGs are simpler: largely run-length encoding based off of zlib compression. The idea of a "white" block being copied for "0 to 15" pixels (4-bits given to the runlength-encoder, 4-bits selected for the "color") might be an easier "artification" step with more obvious differences in display. 512-bits / 8 (4-bit color + 4-bit runlength) == 64 runs. A 32x32 square has 1024 pixels, so your 64-runs of average length 7.5 will average 480-pixels long (well within the 1024-pixels of a 32x32 square == 1024 pixel square).

idea that U+2580 is two square pixels, one atop the other. But this is not true even for 9x15 fonts, which yield a slight distortion with all of these programs, let alone for yet squarer fonts. Barack Obama looks very odd indeed when U+2580 is actually a 16x16 or 32x32 square, as it sometimes is. (http://fileformat.info/info/unicode/char/2580/fontsupport.ht... shows several square appearances, and it is square in one of the fonts that I use here.) tv, with the way that it already works, is probably best placed to incorporate user-supplied information about the font's character cell aspect ratio. pxl could probably be extended fairly simply, too. The others including timg, I suspect would be harder. Interestingly, M. Zeller has had an open issue about this for timg since 2016. * https://github.com/hzeller/timg/issues/4

uses an ncurses-style double-buffer mechanism to optimize re-drawing.