I am a fan of John McWhorter. I've recently gotten into his podcast Lexicon Valley and I recommend it highly if you are interested in language and how we use it.
> Note all dates and time in this blog post are in Pacific Standard Time (PST).
But the incident was during PDT. Just use UTC or colloquial "Pacific time" or equiv and never be wrong!
My heart goes out to these people. I can imagine how much sustained terror they were feeling, stare hard and harder at your terminals and still nothing makes sense.
Apple is well regarded for their strategy. I don't find it very credible that Apple is reacting here, it seems apparent that they would anticipate substantial negative reception.
So this delay is preordained in the strat, right?
But Apple is only human and has had its share of monumental wtf, so this is just a huge gaffe? The spyware team didn't know about iphone 13 launch? This seems incredible.
There is some n-dimensional chess at play here. I feel like a popcorn munching audience member who is actually a pawn in another dimension.
I have had good results with the decrapifier script by CSAND on spiceworks [0]. It's been getting maintained for a while now and it's on spiceworks so while I'm not a windows nerd enough to judge it, I'm pretty sure it's good if not great. I used this tutorial [1] when installing a new machine, you run it in "audit" mode before the out of box experience. I used -appaccess and -xbox. In my case I'm giving this PC to a friend so she'll get the new PC experience without the start menu garbage.
^^ this is not a good contribution to HN, not much substance. (edit)
Many people who use Grafana will see this news and will stop planning on using Grafana and start planning on doing something else. That has nothing to do with Grafana, that is a common reaction to AGPL.
In theory, AGPL is fine under circumstances blahblahblah. In common practice in commercial settings (in my experience), GPL is poison and AGPL is radioactive poison.
Unless they were making money based on their proprietary modifications to Grafana, Loki, or Tempo, they aren't affected much beyond being required to publish links to the source code.
If, however, they _were_ making money off of proprietary modifications, and they wanted to keep such modifications proprietary, they now have the choice to fork Grafana (and Loki and Tempo respectively) as of a pre-AGPL version.
CGNAT block is popular in private k8s as overlay network address space because often the enterprise network already claims rfc1918 blocks. I'm not sure how close to the line that kind of usage is but I suspect it is SHOULD NOT. Speaking of, I probably should not even post this comment as it will now be indexed and served in search results, further contributing to the corruption. Alas, it works.
Many projects don't even need cluster state, they could have just used a Makefile and some sed templating [0] (get off my lawn). Thankfully in these cases you can use helm offline to render the templates then just apply them but it's not great.
Thus I'm sour on Helm, I'm rooting for Kustomize. [1]
kustomize only covers some simple (but common) use cases. If you can use it, you should since its modifications are semantic. Generally I find it is good for handling known differences between a few environments like local and production.
But it isn't capable of replacing helm.
This has happened to me with Firefox. Thankfully there is Waterfox.
Recently this came up in discussion with a software developer who was overly concerned with openssl certificate minutiae. I advised the only durable solution for his concerns is a method to change the entire implementation, not only the certs.
https://lexiconvalley.substack.com/