I got your point. The project structure remains from the initial phase of building the tool. I think I'll eventually remove it or put it on the wiki or somewhere else. My excessive attachment to copyright probably stems from the fact that years ago, when I wrote my own websites and articles, people often simply copied them and signed them as their own. The Linux Foundation website has attribution instructions that ask for the use of the ® symbol; I simply followed this instruction, but I agree that it's probably an exaggeration on my part. Considering what this tool does, I personally think it's lightweight in terms of both binary size, execution times, and dashboard performance. But I agree that's debatable.

I like having tons of docs in the README, vertical screen space is cheap.

The README was AI generated, that's why.

Honestly the sentence from the readme just sounds like a recommendation an LLM would make.

Oh rrdtool is still relevant today. Multiple (if not most of) monioring tools like Cacti, Observium, Munin still use it.

I still use it. A few months ago I whipped up a project to monitor my Unraid NAS. Rrdtool is very useful still.

rrdtool conbined with graphite was powerful back then when metrics and logging was selfhosted.

At some point, writing these files became a hassle and I felt it was too chaotic, so I gave up on it. Regarding licenses, given that LLMs are using other people's work without their consent anyway, and most of the code produced rn is AI, these licenses are to me really just suggestions. I would treat them as an expression of intent, not a strictly legal document.

I think netdata or Grafana with a chosen backend is right for you then. My goal was different, but I'll consider implementing such functionality in the long run. Thank you for your feedback.

Yes, netdata was an inspiration, as I'd been using it for several years. Unfortunately, it stopped being what it initially was, and recently I was so disappointed that I decided to write my own tool. It's also true that I use AI models for coding, but I wouldn't exactly call it vibe coding, as I actively analyze what the models are doing and don't just blindly accept everything. I also try to thoroughly test my code, implement as many security-enhancing features as possible, and have multiple models review my code to catch as many bugs as possible.

netdata is pretty heavy on resources, especially disk writes. I'd appreciate improvement over it, but I won't try out this thing without indication that it improves anything. Especially with such useful features as space invaders built in…

Temperatures monitoring will be added. Initially, I implemented too many metrics, so during development I limited them to a reasonable level to make them manageable, but I'll be adding more as the project matures. Thanks for the feedback!

Well, it was easy since my native language is Polish and I often use "kula szpiegula" term, which translates to something like a "spying crystal ball" in relation to things that allow monitoring or collecting information. In Polish, "kula" can refer to many things, e.g. a sphere or a globe.

I'm not currently collecting metrics for containers. Though I might add this feature later on.

Nice little panel. Although a bit too kawaii for my taste!

I think that once I get most of the core functions stable, I will also want to add options for exporting metrics.

> Why the nonfree AGPL?

By no reasonable definition is AGPL nonfree. It isn't a permissive license, but it's libre, gratis, and open source.

> given that anyone else could vibe code another one in a few hours?

If that's true, then who cares?

To be honest, I didn't think about it for too long. I choose licenses based on intuition. I put a lot of work into this tool, I knew it would require a lot of effort, and besides, I created it precisely because someone else turned a similar project into a money-making machine, completely abandoning the original ideals. Therefore, I felt that AGPL, which requires code disclosure and non-profit use, is the way to go.

1. Why do you ask? Do you intend forking and making money out of it?

2. Why are you lying about AGPL being nonfree? As far as I'm concerned, it is free as in free speech for me as a user. This was the initial goal of the GPL. The freedom of the end user is the main value of the GPL family of licenses. So serious question: why are you lying? Is it intentional, or due to your lack of understanding?