u/ballpark-chisel325

>Backstory: I dropped my 3yo Cateye front light and it just stopped working. It's okay given it was a sealed unit and still used micro USB - I ride in the night regularly, so it got used up fairly well. What annoyed me more was that it started to heat up uncontrollably despite the case did not even look scuffed. I put it in a vice and without any special tool with little effort it just popped open without any damage. There was a 18650 lithium battery inside which I cut out - and it still works. Not sure what to think of the quality, made in Japan, they say. People drop their phones daily and they keep working ...

TL; DR Why are we buying lights every 2 years and toss them away like they were iPhones? /s

Even though it's 2026 and there's huge selection of lights, so many (all?) seem to get it (somewhere crucial) wrong. The "traditional brands" seem to have got stuck in the '10s design, anything with replacable battery is '90s design and sports terrible LEDs. Mounts are like a hitparade of stupidity. We moved slooowly to USB C, but do not support fast charging, everything is heavy, lots of plastic, poor anti-dazzle lenses effort, some lights refuse to charge while in use, they have dozens of modes but single button to control it, remote control is Bluetooth LE and has a lag to it, I could keep going ...

Do I really ask for too much when I think of:

- aluminium body that doubles as an actual working heatsink;

- USB C charging while in use or external pack with non-proprietary connector (barrel kind is fine);

- simple way to switch between "off-road" and "street-legal" mode where the latter actually has a proper beam cutoff and not just drops to 50 lumen;

- normal mount, e.g. GoPro or Garmin twist kind;

- and then a battery pack that I can actually replace with 18650s (or 21700) batteries anytime I want?

While at that, anyone actually seen some well-designed external power pack, like something that actually does not scream it was an afterthought? I thought it can't be that hard to put a dew cells into a sleeve, and shove them up the steerer tube. I tried to find anything like that (integrated) and no results.

First of all, I gave up on ZFS for this very reason. I explored a few couple of threads on this topic - one linked. Home use here, so it is what it is, I am not investing in datacenter grade SSDs.

This older discussion on Reddit talks about just disabling HA services:

https://www.reddit.com/r/Proxmox/comments/1j4ehgq/comment/mg82crh/

But I do not want to do that, so I looked further. Found this 3 years old repository with little traction ever since:

https://github.com/isasmendiagus/pmxcfs-ram

From there, I found a more recent project which also should prevent log data writing wear, but it seems to have been stuck with PVE8:

https://github.com/free-pmx/free-pmx-no-shred

Is there some all-rounder out there I missed or is it all more like YMMV?

This project has been featured in a few blogs by now, it definitely comes across way nicer than the stock Datacenter Manager by Proxmox, even the normal web UI.

I would like to ask for your feedback - if you have been using it or reviewed it on lower level (as a programmer) and found out any operational negatives.

Please do not tell just state it has been AI-assisted development as that is stated in the README and that alone means nothing. Unless genuinely you have informed insight why some of the code is badly put together or outright security vulnerability waiting to happen.

Thanks!

Today I found this web:

https://preview.redd.it/kfaz9d25vizg1.png?width=2672&format=png&auto=webp&s=2e3ff609979afed79b1537cbb734ebc893b36a6e

What's going on? How is this - what's the word - not a trademark violation?

Anyone has similar experience with consumer SSDs and glusterfs being a better fit?

A little known (to me) setup is possible with "external vote support" for the cluster:

https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support

I noticed, that after setting this up, if new nodes are later added, they do not seem to know about each other (the device about them and them about the device). I believe it's then potentially risky situation. I figured that when I undo the whole device setup and redo it again, it's correct again. Because it does not help just waiting. And there's no warning for this.

Is this common? I mean, both - having a quorum device and the procedure to disable and re-enable it every time a node is added. Do I have to do it also when node is removed or that's a non-issue?

Thanks.