The developer pushes out their work without really checking it at all beforehand. I've had trouble with this on different platforms and browsers (claimed to be supported), where the code was so bad it would just crash on launch, or it might work until you actually try to order something. That hasn't happened lately, but the new VH Monitor 4.0 has never worked for me since it was pushed out a few weeks ago. Monitor 3.0 still works fine most of the time, but sometimes disconnects saying there's some sort of contention with another user. (I am only running one instance.)

The error I get on 4.0 is that it cannot connect to the VH websocket. (Only one instance is running.) I've tried 4.0 a few times, and just tried it again after the May 27th update (yesterday), but it still doesn't work at all.

I've noticed that the new IP addresses for the VH server resolve to cloudflare instead of OVH as they previously did. This seems odd for something with an active server on the backend.

AFAIK, 4.0 and 3.0 should be using the same server, so I've got no idea why one would work and the other would not.

My use is casual, and I should probably donate. The tiered features look interesting, but I don't use it enough to pay enough to get them, so motivation to donate is low.