My life of working with it got easier when I started just looking at the actual code, using network level tools like nc/tcpdump, making extensive use of the debug exporter, and almost ignoring the docs entirely except as a basic summary of what a thing does.

Seems to indicate a collection cron with a manual query to truncate can fix it. This is fun little things I like to learn. SRE Easter eggs.

Edit:

To be clear still interesting finds. I think with some chaining some of them might be more severe. Like the ovpn one and windows potentially registering vpn app as default open or some protocol opener for a url location like openvpn:// in an I frame and some clever social engineering. Just a random thought

Edit: Obviously you'll be using more tokens but this is the trade off for running a smaller model and running locally. Similar to time memory trade off but in token economics. Sorry I need more coffee

- the cloud was invented and we were told CTOs would be able to just point and click and make infrastructure and apps! What did we actually get? Another layer of abstraction to debug through. Does it have is perks? Yes. Does it have it's own problems? Yes. Is it more expensive than setting up bare metal and having a solid team? Well that depends on what you're doing and the economics of it and the team.

- then document storages came along like and got wildly popular like mongo and people were calling it the end of SQL! And no more complexity or relational nonsense. Everything is JSON and life is great. What actually happened? These companies realized over time their data was getting trashed, adding things and fixing bugs became complex in pure docstore systems. So the initial v1 was easy and looked beautiful but only 4 years in you have a production db with orphan data that's twice as big as it should be. New features take forever to see a clear path in adding it to the model because it's no longer as intuitive to get performance for a feature.

Anyway. I see AI taking both of these roads at the same time. In 5 years I believe the code will be a giant pile of unfixable mess for most vibe coded things. I also don't see it getting rid of programmers but just adding another layer of abstraction to the mix that yes is helpful, but only if you already know what you're doing, much like what came of the clouds.

For the search, some of the local results are wrong but I live in a very small area so it may be more reliable for highly populated areas. Lately I've been checking out Kagi for a few things just to see what the quality is like on competition. The anonymized chat (proxy) for AI is cool but very small context limit. Good for looking up random questions and they typically include references.