One idea on the list was JPEG generation loss. I’d seen a few demos years ago and thought they were fascinating. Claude told me it was a good idea and that I’d see the image decay with each save. That sounded good to me so I asked it to create a script, but it didn’t work. There was no obvious generation loss, even after 1000 saves. However, I remembered seeing demos showing jpegs disintegrating, so rather than dismiss the idea like I had others from the list, I tried making a script by hand, but that also didn’t produce the expected results. Then I tried making a Photoshop plugin (maybe there was something wrong with the libraries I was using?). But that also didn’t work.

Finally, out of frustration, I went back and found and rewatched the old demos that had originally piqued my interest, and I noticed they were randomizing the quality setting between saves. Changing the quality changes the quantization table, so that forces the data to be crunched differently between each save, which is what was causes the generation loss. The other demo I remembered wasn’t doing this, but there was someone in the comments saying that the generation loss shouldn’t occur (jpegs stabilize fairly quickly after repeated saves), which matched up with what I was seeing.

I didn’t find the idea of randomizing the quality to be very interesting (even if the effect was cool), so I decided to just start messing around. One idea that led to really cool results was saving an image as a jpeg, then as a lossy webp, then as a lossy avif, and then just repeating this. The image ended up melting into a magenta soup. Once I saw that, I felt I had something neat enough to be worth sharing. I made a short little video on it, you can see it below if you’re interested.

If you enjoy it, a like helps more than you’d think. And if you want to play with the script yourself, I’ve put it on GitHub: https://github.com/patorjk/image-generation-loss 

* I may talk more about this later. I’m still pretty new to this and am probably behind the curve.

The idea to experiment with the effect came to me back in December, when Loic Cressot (author of a few FIGlet fonts) emailed me with the idea to add a chromostereopsis filter to TAAG. I did so and I think it makes for a neat output, though in practice I’m not sure how useful this will be.

I also thought it could make for a fun youtube video topic. At the time I was working on the Image Glitcher stuff, but figured I would circle back to it. You can check out the video below.

The video isn’t really computer science related and I was worried it might flop with my audience. I was also a little worried about how it would do since it seems like around 30% of people don’t experience this illusion.

It seems to have done fine though. However, the most popular aspect seems to be the game of Lights Out that I created using the effect. I kind of wish I’d lead with that. When constructing the script, I had no idea where to place that part, so I just stuck it at the end.

Anyway, if you like it please give it a like or a hype! It definitely helps with the algorithm.

New video! This one is sort of a follow-up to my last video, though this time I explore breaking PNG files.

This topic proved to be a bit more complex than the last one, and one negative is that the coolest stuff is at the end of the video, which most viewers won’t see. Essentially, you can create “fake” or “custom” filters and see what errors/glitches look like by re-encoding the glitched data back into scan line space and then re-encoding it using a real PNG filter. If what I just said made no sense, well, that’s why it’s near the end of the video. But below I’ll share a few images from my favorite custom filter.

Those don’t even look like images with glitches to me. They look like images that have had paint splatted on them. And the fact that you can create any filter you want and glitch it is really fascinating. It feels like there’s so much that could be explored here.

Another topic near the end of the video is glitched animated PNG files. Most people probably don’t even know that animated PNGs are a thing, but they’ve had full browser support since 2020. They weren’t officially recommended by the W3C until last year though. Apparently the PNG Development Group didn’t want animation to be part of the spec (until recently). However, I think it’s a big win for PNGs to support animation. They’re smaller, support more colors, and have better transparency support. Plus, they look cool when they’re glitched:

Anyway, check out the video if you’re curious as to how all of the works. If you’re interested in my inspiration, see The Art of the PNG Glitch, and if you want to glitch your own images check out my Image Glitcher or this script I created to glitch images (the latter allows for more fine grained control).

2026/02/13 Edit: Pressing the “Hype” button on a video really helps it. If you found this interesting and enjoyed the video, please hype it (the button only appears on mobile)!

It’s a simple tool that combines an image preview with a hex editor that has segment highlighting for jpeg images. In the future I hope to support highlighting for other formats too. The idea is that you can more intelligently make glitches in an image file when you know what you’re editing.

I created a short video about the tool framed around the idea of what happens when you edit a jpeg in a text editor. You can watch the video below.

This video was a lot of fun to research. Weirdly the research phase has consistently been the most fun part of the video making process. Originally I was going to cover all of the main image formats in this video (jpeg, png, bmp, gif), but jpegs wound up being much more complex than I anticipated.

There’s also a lot of weirdness with the file type that I opted not to cover in the video (I wanted to keep things focused). For example, you’ll often hear that jpeg’s use the YCbCr color model (basically luminance + color), but that’s not mandated by the spec. It’s actually color space agnostic. You can actually create a jpeg where it internally stores the data as RGB values (though jpegs usually store the data in YCbCr).

You’ll also often read that the two most popular formats of jpeg – JFIF and EXIF – are incompatible with each other. This seemed really confusing to me until I saw the color coded segments in the editor. JFIF is determined by a JFIF APP segment following the SOI marker, and EXIF is determined by an EXIF APP segment following the SOI marker. Jpeg parsers should have little issue differentiating them. Though possibly even stranger, you don’t even need this segment in a jpeg. Wikipedia often strips it out.

Anyway, there’s a lot of random info I left on the cutting room floor. Maybe one day I’ll work it into something else.

I made a new YouTube video! This one is doing better than usual. I think I may have finally found my groove, though I have no idea what I’ll do for my next video. Amusingly this came about kind of quickly and kind of randomly. I wasn’t planning on making a video, I just went down this weird rabbit hole when I noticed this effect, and wound up learning about (spoiler alert) Turing Patterns. There’s a lot more that can be said about reaction-diffusion but I wanted to keep the video high level and light. It’s just a cool effect that has a neat underlying mechanism.

I’ve made available the accompanying web app and video generator I created to make the effects in the video. Had I known people would ask for them I probably would have done them in a different language, as JavaScript is really, really slow for this kind of stuff. However, it’s the language I’m most comfortable in and I was able to bang it out really quickly (you may notice that web app is just a hollowed out version of the Color Palette Generator I showed off a few weeks ago).

The video does a pretty good job going over the new 404 page. I actually wasn’t planning on updating the 404 page. What happened is I wanted to create a “Fire” filter for the TAAG app, and while looking into how to create a pixelated fire texture I stumbled upon the Doom Fire algorithm. It was simple yet produced such a cool result – I felt I had to do something with it, and that’s when the idea of re-doing the 404 page came to mind. I’m now kind of debating even making a separate app just for burning text or other things, as it’s weirdly kind of fun.

Anyway, if you like the video please leave it a like / comment / etc!

Main Page

I’ve created a new main page. If you’re on desktop you’ll see the spotlight effect from my react-halloween library, but otherwise it’s just a simple directory listing of the main content on this site. The previous main page wasn’t bad, but I wanted something cleaner looking that I could expand upon later with fun ideas (like the spotlight effect).

Color Palette Generator

The Color Palette Generator has undergone a makeover. This was one of the oldest apps on the site. It allows you to generate a color palette from an image, which can be useful when designing a website or creating artwork.

I wrote the app in 2008, then updated it in 2010 to add the “Muller Colors” palette option. There are now countless apps on the internet like this, but I was partial towards mine ever since a rug website reached out years ago to get access to the underlying algorithm. Apparently they had tested many palette generators, and my algorithm worked best for their rugs.

The app was in desperate need of a makeover, so I’ve modernized its design. I’m unsure how much more work to put into this since there are now so many similar apps, but I may add some additional palette generation algorithms in the future.

Chain Letter Archive

I’m a collector of things, and in the 90’s I started a chain letter collection. A handful of the funny ones made their way to this website, but their organization was never very clear and their format was unsuitable for mobile devices. So I made a dedicated page that explains what they are and why they’re here. I also reformatted them so they can easily be read on small screens.

The HTML of some of these letters was copied directly from AOL emails, so it was full of mismatched and deprecated tags (like FONT). Clean-up was a daunting task, so for three of the letters I decided to use AI to clean up the HTML and put them in a more responsive format. Surprisingly, the AI didn’t like the content of these emails. In some cases it even refused to translate them, and in others it censored or rewrote the jokes. It was kind of fascinating.

As an aside, I’ve debated removing these letters from the site since they’re a little embarrassing. I was a teen when I collected them, and the humor is pretty juvenile. But chain letters were a part of the early internet—I think they were the first kind of content to go viral—and they’ve basically disappeared from the web. I don’t think the ones I have collected here are available anywhere else. At the very least, they’re an interesting time capsule showing what viral content looked like 30 years ago.

Facebook Like Buttons

I went through a phase 10-15 years ago where I was putting “like” and “share” buttons from third-party sites like Facebook on pieces of content. Kind of hilariously, I discovered that the Facebook Like buttons on this site displayed a like count but no longer worked. Somewhere along the line they became frozen in time, I’m guessing they required a code update or something. Whatever the case, I removed them. I did leave the X/Twitter buttons since they still work and appear to be occasionally used. I may eventually remove those too though, as third-party APIs inevitably break.

What’s Next?

I plan to update some of the older and lesser-viewed sections on this site. There’s definitely content that needs a facelift. I’ll probably avoid updating stuff that gets decent traffic though, since I don’t want to mess with something people are actively using and create unnecessary angst.

If you’ve got suggestions for improvements or notice anything broken, feel free to reach out. In the meantime, check out the updates and let me know what you think!

TAAG was originally written back in 2007, when I was re-learning JavaScript. For the most part, the original app did what it needed to do, and prior to this latest rewrite, it hadn’t undergone any major changes since 2012.

So… if the old app was fine, why rewrite it? Well, there were two underlying reasons:

• I wanted to modernize the code base to make it more maintainable.
• There were a handful of minor features I wanted to add that weren’t really possible with the app’s ancient code base (ex: better Test All page, searchable selects, dark theme). 

However, I didn’t want to make any drastic changes. I wanted to maintain the same feel as the old version. For the most part I think I was successful, though I did receive one email bemoaning the changes since they really liked the retro feel of the old version. However, I think the more polished version will be better for the site in the long term. 

Modernization: TypeScript?

I don’t think I’ve discussed my thoughts on JavaScript vs TypeScript publicly before, but I used to be hugely pro-JavaScript. I loved the freedom it gave you, I loved how I could quickly create prototypes, and I loved how versatile it was. However, over the past few years I’ve had a change of heart. Navigating gigantic JavaScript code bases (100k+ lines) can make you lose your mind. I have a pretty high pain tolerance when it comes to crazy JavaScript code, but in recent years even I have reached my limits. 

After giving TypeScript another try (I used it years ago and it caused me more problems than it solved), I’ve found it to be hugely beneficial. It helps catch mistakes that would have gone unnoticed and it makes code easier to understand. I’ve slowly introduced it at my work, and it’s now starting to make its way into some of my personal projects. 

In Conclusion

There’s something satisfying about taking an 18-year-old app and giving it new life. Hopefully it works the same and feels familiar while being more solid under the hood. I have plans for additional features and improvements, but I wanted to get something out there because I get distracted easily.  I hope you like the updated app. If you have any suggestions just let me know in the comments.

For one, all the files were encoded in Windows-1251, which is what Windows used prior to moving to unicode. This encoding used a single byte for each character and had a different character mapping. Additionally, sometime between Windows XP and now, Windows changed how it rendered the Arial font, so now many of the pieces looked a little messed up (I think this change was to make it more in-line with how other OSes render Arial).

Rather than let the gallery stay by the wayside, I decided to give it a major face-lift. I wrote a script to convert the Windows-1251 encoding to UTF-8, and then spent a minute or two on each piece, fixing any obvious errors. The old gallery still rendered properly on Windows 98, so I used a VM of the site there as a reference to any edits I made.

I also decided to over haul the UX. The old gallery required over 500 clicks to see everything, so for the new gallery I decided to put everything on one page. And to ensure good performance, I used virtualization. However, virtualization kind of messes up the browser’s Ctrl+F find feature, so I decided to write a custom search feature to allow users to search through the art.

This is where things got a little hairy though. I thought maybe I could use AI to generate tags for all of the art (my plan was to use IntelliJ’s AI assistant to comb through the files), but it turns out ASCII art is the kryptonite of LLMs. They have no idea what they’re looking at and will just hallucinate a response that makes no sense. So I had to settle for a feature that looks at the filename and file contents. However, I thought the hallucinations were kind of interesting and decided to make a short video on the topic:

Anyway, if you’re interested in checking it out you can find a link to the new gallery here:
Arial ASCII Art Gallery

I never got a cease and desist for Mosaicer 2.0, but I didn’t want to bring any extra attention to myself in the off chance I would come onto the patent holder’s radar. At the time I remember reading through the patent and finding it overly broad, and looking at it again today, I feel the same way. I don’t see any way to create photo mosaic software without violating Claim 1 in this patent. And the guy who filed the patent wasn’t even the first person to make a photo mosaic. The whole thing just seems absurd.

But the past is the past. The patent expired in 2017. I could have released a version 3.0 then, but I had moved on by that time and was busy doing other things.

I had always wanted to revisit the app though, and a few weeks ago I remembered an idea I had for a photo mosaic app that used an FFT block matching algorithm. I had read about it in grad school and always thought it would be a good fit for a photo mosaic program. So I got to work and wrote a new photo mosaic app in Java – Mosaicer 3.0.

However, when I got to the part on writing a tile matcher that used the FFT algorithm I came to the sad realization that it was a poor fit. It did way more calculations than necessary and was more expensive than the standard sum-of-squared-differences calculation. Coming to this realization was a huge bummer, though since I was 90% done at this point, I decided to carry on and just finish up the app.

Mosaicer 3.0 isn’t really anything special – with the patent having been expired for 8 years now there are a lot of free and commercial options out there. However, one more free photo mosaic app can’t hurt, and one thing I thought I could provide that seemed to be missing was some good info on how to get images. That’s actually the hardest part about making a photo mosaic. So I put together a short list of resources and datasets that one can use when creating mosaics.

The albums dataset is especially cool. You can make album covers out of album covers. I made a Flickr Gallery of some of my favorites. Below you can see one of Metallica’s Master of Puppets.

Another idea I had was making YouTube thumbnails out of YouTube thumbnails. The yt-dlp app allows one to easily get thumbnails, and I was able to make some VSauce thumbnails entirely out of other VSauce thumbnails (example below). The only problem with this idea is that photo mosaics require a lot of images, and most channels don’t have enough videos.

I’m not sure if I’ll continue development on this app, but it’s been kind of fun to play around with.

Lastly, I made a short video on photo mosaics. If you’re interested you can watch it below.