axytol

I'm using VictoriaMetrics (VM) to store basic weather data, like temperature and humidity. My initial setup was based on Prometheus however it seemed very hard to set a high data retention value, default was something like 15 days if I recall correctly.

Since I would actually like to store all recorded values permanently, I could partially achieve this with VM which let me set a higher threshold, like 100 years. Still not 'forever' as I would have liked, but I guess me and my flimsy weather data setup will have other things than the retention threshold to worry about in 100 years.

Would be nice to learn the reason why an infinite threshold is not allowed.

3 dB would be halving/doubling. With 10 dB, you would get a ratio of 10x.

As a fellow alternative Ubuntu user, one additional difference is the LTS support schedule which is shorter for Ubuntu alternatives. For example, Xubuntu 24.04 is supported until 2027, while Ubuntu 24.04 is supported until 2029.

Interestingly, as I understood it, when a release such as Xubuntu goes out of support it does not stop getting updates that are not specific to that respective flavor, so in a way you still have some indirect support, but feels a bit like a gamble.

One nice benefit for optical media is that it's hard read only by default. This makes it easy to ensure the install media does not get corrupted by overwrites or malware.

They mention Zen 2 and 3, any info on Zen 1? Would it simply apply as well?

For some cars, getting to reverse requires to press down the shifter and then shift to the same position as 1st. I think this scheme would not work in such cases.

That's a good list of reasons, however it seems the biggest concern is if you run a dedicated DNS service on your network.

For a simple home network setup, as long as naming conflicts can be managed, it looks like mDNS is quite handy.

On a side note, I find .local to be best suited for the purpose, since from the language perspective it's easier on international users than .localhost

The newly proposed .internal comes close, but .local still looks more semantically flexible or maybe this is a cognitive bias of mine.

They list under hardware requirements "a powerful graphics card with at least 6 GB VRAM is recommended. Otherwise generating images will take very long"

Does anyone have any idea what would very long mean on a 4GB VRAM card?

After more than 15 years of average default Ubuntu user, I also had to move, in my case I went to OpenSuse Tumbleweed (TW).

While there were a lot of Ubuntu changes over the years, that I managed to adapt to, this time I realised it was too much work on my side as a user:

- for snaps, since I have data spread across different mounts, I had to apply some bindfs cludge to address the hardcoded paths that snaps get access to.

- for Gnome I got tired of having to install all kinds of 3rd party extensions for basic UI features like right click actions.

Debian or derivative would have been my initial choice too, I went with OpenSuse because it's got a strong developer backing and very responsive update schedule, it's a rolling release which means that it has quite new packages but also if updates break it, you can quickly revert it with snapper. Some downsides to consider are that this is not a Debian derivate so, while most guides on the Internet can be 'ported' to OpenSuse it's a bit more involving. That said they also feature quite some good docs, so many common scenarios are covered.

PS I know you can get the same Gnome on OpenSuse, but the upside is that one has access to more recent alternative DEs, which can replace Gnome on rolling releases.

I've been doing just that with a Raspberry Pi Zero W and a USB ethernet adapter. The eth adapter is set to dhcp, and the wifi sets a hotspot. The wireguard adapter is routed/from to wifi with firewall rules. I even tested the Pi plugged to a powerbank and it still works.

Not OP and certainly not in the anti-IPv6 camp.

I'm wondering though: could you build a case that under IPv4, a misconfigured NAT would only result in lost connectivity for nodes behind the router, while for IPv6 a misconfigured firewall and worse triggered through a vulnerability, would then result in protected nodes being exposed?

I know NAT-PMP (port mapping) vulnerabilities exist, allowing external actors to set port mappings to hosts behind NAT, but this seems a bit harder to exploit than a bypassed firewall.