The trademark infringement claim is interesting. Is there any precedent for a company doing something like "Redis Service" or "Coca Cola Reseller" and getting away with it?
Me too. Was there some regulatory change that makes spraying SMS more difficult? It'd be great to hear from someone that works there or at Vonage which sees to have suffered the same fate.
AlmaLinux is a perfect replacement for scientific agencies. It's got the fastest turnaround time for security patches, an open community, and sustainable funding sources.
Exactly. There was the famous quote from a US presidential candidate who couldn't even remember what the DOE was called, even though he wanted to abolish it[1].
Stealing copper cables from electricity posts is common throughout much of the world. Here's an example[1] robbery. It usually amounts to a gain of a few days' wages for the thief, and a loss of half a day's electricity for the neighborhood.
Less than half the activity before/after according to this non-scientific analysis (my client wasn't always connected and it looks like the logfiles contain topic/names and other output).
At work, we upgrade when there's a compelling reason (structured logging in 1.21 came close; we haven't finished migrating from our old logger yet). Before deploying that version, we typically bump versions in all our Go repos and run the tests in those repos. Having the same version across apps gives some people on our team a bit of comfort (with Go, it's not as important as some other runtimes).
Came here to say the exact same thing. chi has been reallly great for a couple projects--in fact, it's easy to forget it's even here. Moving them into the stdlib means they'll always be maintained and ensure that approach is used in many Go programs.
One technique is to never upgrade clusters. Instead, create a new cluster, apply manifests, then point your DNS or load balancers to the new one.
That technique won't work with every kind of architecture, but it works with those that are designed with the "immutable infrastructure" approach in mind.
There's a good comment in this thread about not having your essential services like vault inside of kubernetes.
The government of Russia, home to the world's largest forest reserves, is trying to subsidize wood-frame buildings. Most modern buildings are made from stone, though, because of fire regulations[1].
> Native Americans routinely burned the landscape—to foster the growth of useful plants, to clear space for farming, and to improve the conditions for hunting.
> ...
> In addition to maintaining parklike conditions, these managed blazes prevented fuel from building up, and so staved off larger, potentially unmanageable conflagrations.
Much of the world still operates like this. Check out the Chiang Mai, Thailand burning season[1].
The US and Canada are some of the only countries where wood is the primary building material. In the rest of the world, stone is used which doesn't catch fire so easily. That might help explain the fear of fires in the US.
The author describes the alerting and notification workflow really well.
We use IRC at work for this purpose. Prometheus alerts flow into channels that anyone is free to join or leave depending on what they're working on at the given moment.
Same here. ZNC on Debian (apt install znc) on an Entrywan instance.
The freenode debacle impacted a handful of my favorite channels. #tcl is noticably quieter and a couple others are still trying to decide whether they're an official channel or not (this affects #channel vs ##channel naming). I'd bet that the number of active users has dropped but I don't have any emperical evidence.
If anyone is considering ZNC, here are a couple suggestions to change to the default config:
1. AllowWeb = false (only enable the web interface if you need it)
2. For each channel, add Buffer = 10000 so that you can have history for more than a day or two (the default is quite small)
1: https://www.theguardian.com/environment/2024/sep/20/three-mi...