This was actually a pretty straightforward fix, but has theoretical massive impact. The dev tools preferences were uncomfortable to look at, since it was white text on a white backgrounds. I dug into their design system and found they had the right CSS variables, just weren't being applied on the options.

As above.

...As above.

This hasn't been merged yet. I'm not sure if I make changes in line with the maintainers' intentions, but... there was a TODO comment in the codebase for 2 months about cleaning up redirect handling. I refactored it to use direct dispatch methods instead of the public API instance. There's some other work that could be done in that file as well, but I want to see how their test runner works before I go further. Well, I already have, but I want to verify my theoretical changes won't break anything..

This is still open. Next.js inherently does a lot on its own, and processing pages for static export can cause large sites to hit the JavaScript's call stack limit. I traced through the export pipeline, found the build calls, and implemented a warning system that catches this as builds fail. I think it might be decent to elucidate on design principles in the warning, but who knows; Vercel might decide to suddenly pivot/support big SSG.

I tried my hand a bit at engaging in some discussions/commenting on issues, but... wow, it's a lot to keep up with.

I think it's quite a nice idea, and I want to continue working on it, but we got derailed due to wondering how we'd get user configs nice and ergonomic when they're setting up their GitHub urls and whatnot, and I just got kinda bored and didn't want to implement the API caching... which, IMO, is absolutely necessary. So it's at version 0.0.1 right now, because I also found other things that were more interesting. But this is still interesting! There're just a lot of competiting priorities.

The blog part is it. We're still working on trying out different designs/libraries, but I personally just prefer dense information and non-functional art. So... everything and nothing.

Vercel's database pricing was getting expensive as the project grew. Migrated everything to Supabase using pg_dump to ensure 100% data integrity. The migration went smoothly and now I get way more database features for a fraction of the cost.

The original setup was doing way too many database round trips. I added proper indexing on frequently queried columns, restructured some of the more complex queries, and implemented aggressive caching with TanStack Query. The 50ms response time made the whole app feel snappy.

This was probably the most technically challenging part of the whole project. Most infinite scroll libraries break native browser behavior - you lose things like browser back/forward, scroll restoration, etc. I needed bidirectional scrolling (up and down infinitely) while preserving all that native functionality. Had to do custom DOM manipulation and careful event handling to make it work seamlessly.

This is in the App portion. It was really, really hard to achieve even half of the Discord-level usability, because there is just so much state management.

This is me thinking of justifiable ways to work with distributed systems. By offloading image processing to a dedicated microservice, I was able to decouple the image processing logic from the main application, making it easier to scale and maintain. Further notes are in the Potato Image Compressor section itself.

This is pretty basic. I used Drizzle, too. Like, it's just adding more types and stuff..

I turned this off for now, but it was nice when I tried it a while ago. Rather than making users manually tag everything, I integrated Claude's API to analyze content and suggest relevant tags. It's surprisingly good at understanding context and suggesting useful categorization that actually improves search and organization.

This was just to prove that I could. I want to disable it, but... idk.

This was also just to prove that I could. It isn't on, because I don't really have anything that necessitates it.

I asked my mom to look at my previous versions. I also tried really hard to match up to Discord's design system earlier on, but I realized that I have my own tastes, and I want to try out a bunch of new animation and 3D libraries.

We don't really have a use for this, but we did it to prove that we could.

This was a fun project. I wanted to learn Go, and I thought it would be a good idea to build an image processing pipeline. It was simpler when I initially added it a few months into the Scrapbook project, and it was a couple months later that I really thought to dig deep and make this bigger and better and faster and flashier. I used goroutines with worker pools and sync primitives (both semaphores and mutexes) to make it concurrent and efficient. Oh, and I wanted to try out gRPC too. It's not the most complex thing, but it was a good exercise in Go.

I wanted to use k6 because it seemed like some sort of industry standard, but I ended up doing the bulk of the testing with shell scripts... which seems like what k6 kinda does anyway, at least for my case here. Anyway, the baseline was also this supremely naive, sequential little thing. Which I don't think I even had? Like, I'm pretty sure it was already async/await (in go terms) from the start..

This was a fun challenge. I wanted to make the image processing pipeline more flexible and extensible, so I designed it with a modular architecture in mind. This way, I could easily swap out different compression strategies (like libvips) without having to rewrite a lot of code. It was a good exercise in software design principles.

This was another interesting challenge. I wanted to make the image processing pipeline accessible over the network, so I used the Adapter Pattern to expose its functionality via HTTP and gRPC. I also set up monitoring and metrics tracking using Prometheus and Grafana, along with some shell tooling to make it easier to work with. It was a good way to learn about distributed systems and observability.

This was a fun little project. I saw a StackOverflow question that had been open for 1000 days about how to fold single-line comments in VS Code. I thought it was a neat idea, so I built an extension that does just that. It's simple but effective, and it's nice to see other developers finding it useful.