My unscalable tools and how I want them to work together with my homelab

So one of the things that I'm really interested in is the idea of having a daily record that I keep for myself.

I've made some versions of a bookmarking site ([All My Favs] or 'amf' for short) and an alternative YouTube video manager, [wytchr], that are tightly connected in the data ecosystem that I'm creating. I then added webhook support to so that [wytchr] sends videos that I mark as a favorite to amf. After that, I also made custom "post to my microblog" support so that I can update my microblog with things like the external url prefilled in my cms (yes for my static website).

(A)I've also been making a lot of raycast extensions which makes it easy to add these items to my wytchr and amf databases.

Building things that don't scale

I mentioned this a long time ago and I think I still stand by it. I LOVE building things that don't scale.

I don't care if you use AMF or wytchr (I mean you can, at your own risk) and I don't think you should make a CMS built on FastAPI that adds information to a database that gets read by render engine and deployed on the web. But I did and now I'm thinking about how I can make all this change how I use the web.

But the reality is that I'm learning about scalable solutions whilst building my unscalable projects. I can't speak on the next step in this but I with all of these databases, my next thought is aggregating this information so that I can do things like have a central datafile that I can connect to an LLM and really ask my past self questions and get recommendations. Furthermore I can do things like connect all of these to my [searxng] and then I'm now searching all my stuff privately.

This is, in my opinion the better digital commonplace notebooking than those goofy mindmap things (which I could also do with some simple queries in duckdb).