Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)PE
Posts
32
Comments
626
Joined
2 yr. ago

  • I'd like to explore Prometheus (I've never used it). Right now I use InfluxDB to store some data (ping times, temperature, servers load, etc.) can Prometheus read those values and react if something is off or should I store everything twice?

  • I use Uptime Kuma too in my VPS and I monitor it with Node Red at home (that is monitored by Uptime Kuma! 😁) So if anything goes down (monitoring tool too) I receive alerts. Both of them send me alerts with NTFY.

  • If lemmy.world is behind Cloudflare protection, how can it be down for DDoS attack? Cloudflare should block them before they reach the server.. If the server admin is around, could he tell us if this downs are still for the DDoS attack? (Maybe he already have stated this somewhere) And if yes, why Cloudflare protection hasn't blocked them? I'll write here again: this is not an attack to the server admin, these are QUESTIONS.

    I didn't get this sentence:

    you are chasing an idea that does not check out — so to speak. What idea?

    By the way, I'm here chasing discussion, confrontation, communication that are things that can enrich people. If all of the people that downvoted me would have wrote down their point of view in a constructive way, I think that we could have had a good chat!

  • but does run the risk of starving new members from joining and risking a shrinkage of content.

    There are plenty of instances, that will not happens, it's not a risk.

    the stability issues drive from repeated DDoS attacks

    Still? In an older post of the Lemmy.world admin I've read that other instances behind Cloudflare don't suffer from this problem.

  • Why don't you close the subscription to Lemmy.world so new people will subscribe to smaller server so that if one has problem, not the majority of the people are affected by it? Isn't this supposed to be one of the main characteristic of the fediverse?

  • For the valve, any garden irrigation valve will do. If you have a DIY shop (sorry, I don't know how're they called, here are Brico) you can buy and ask for suggestions there. If you don't have power at all there well...maybe a latch valve and an EAP32 with deep sleep code can last a few months (I guess, I've never tried that). For the waterproofing, the valve should already be waterproof, for the circuits you can buy an IP 65 electric junction box. Easy? Maybe not, but when it works, it feels good!!! :)

  • I would suggest you to use Node Red as backend and Home Assistant as frontend. With Node Red you have a very robust system that survives years of updates without problem (I've been running for...mmm...maybe 7/8 years and no update have ever broken anything, while I read all over stories of Home Assistant breaking over updates). Node Red has node for about anything, you can make your home automation product/brand independent using MQTT, so Node Red collects all the sensors/actuators and sends to HA what's needed. If tomorrow you'll change a device, all you have to do is connect a couple of nodes and use the same MQTT topic as you did with the previous device (I don't know if I explained myself...sorry!) If tomorrow you'll want to switch from HA to something else, it will be pretty easy with Node Red in the back! All of this, clearly, IMHO!