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.
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]
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.
This is what I'm talking about wrt bitching and moaning, in summary you tried to use ES but you didn't rtfm or didn't know about jvm tuning or didn't scale test and found out the weekend is a bad time to come up to speed on those, you had a bad time several times, plus you slashdotted yourself with monitoring; then you did a custom implementation for your vertical use case which didn't have the rtfm problem because you wrote it, but also only satisfied your case as opposed to the wide applicability of ES. Ultimately cool story bro because ES is freely available for anyone to use (many people do this) and modify (some people do this too) and your alternative is unknown.
What are the fundamental flaws of ES and what alternatives avoid those flaws, or how do you propose ES could address those flaws?
For example:
- "Algolia is so much better because it is a managed service." (hey whatsup ycombi)
- "Solr is also lucene but necessarily requires significant customization to the workload which avoids the common ES problem of it appearing to work so well out of the box that people neglect the details until it becomes an incident."
- "ES fundamental flaw is that zen disco mcast nonsense, people please stop being clever using mcast it never works in practice because igmp snoop". (hey whatsup we out here using ES since a while now)
If someone would say that on HackerNews then they would expect to hear "citation needed".
Anecdotally what I hear is a bunch of bitching and moaning about ES yet it clearly does work and has generally all of the difficulties of any CAP problem. This indicates to me that ES is addressing a Hard Problem and to the extent that it is long lived and quite popular, it's likely not substantially worse than any reasonable alternative.
Please tell us what you view as ElasticSearch fundamental flaws and give some proposed alternatives either as revisions to ES or entire other solution components.
AboveNet built out a datacenter in a mostly derelict mall in the middle of downtown San Jose. At the time the irony of ecommerce servers in an abandoned mall was fresh and surreal.
There was a street seller who was so distressed by the economic conditions and especially the petty corruption that he publicly set himself on fire.
Almost a decade later, possibly the cops on the beat shakedown situation has improved but general man on the street economic conditions are not improved in Tunisia. It is not apparently (yet) a success story.
ha I was gonna comment this sounds like a book I read recently (since I didn't read TFA because who even does that).
I'm unsatisfied with the cassava and acorn stuff. I get that metabolism is externalized and I get that once it is a cultural practice then that's just how it is. I struggle with envisioning the part in between where the processing is newish and becoming a practice, especially in regards to something like the cassava toxin that doesn't happen until decades later. How does a processing strategy sustain in those early iterations? Versus the animal husbandry practices, they have more immediate results that seem less vulnerable to biases making false causation. I think I struggle with the making sense part of it, what I got from the book is that considering cause is a luxury won by doing it "because I said so".
What are the obvious reasons? I'll presume you are referring to disclosure of the card number.
I had this discussion recently about 'security' with regard to X-Header versus ?query=param. Either it's http all plaintext on the network or it's http with tls all cyphertext on the network. Every bit in the http request and response is equivalent - verb, path, headers, body, etc - agree?
You could represent the card number as cyphertext in the request body, that's a good practice regardless of tls, but of course don't roll your own crypto. You could put that cyphertext in the path as well but if the cyphertext isn't stable that makes for a huge mess of paths.
You could make a case for trad 'combined' access logs situation with the path disclosed in log files. I can appreciate keeping uris 'clean' makes it safe to integrate a world of http monitoring tools, I would make this argument. In the case of the card represented in a stable cyphertext it's kinda cool to expose it safely to those tools.
Commonly on windows, build pipeline tools don't work when they don't have a desktop environment even though there's no requirement for human interface (indeed, requirement for no human). The advent of Server Nano motivates a first class headless windows reality but even so, we been out here running xvnc because whatever tool required an X server.
ObPedant: notice in google's status page "...as of Tuesday, 2019-07-02 09:11 US/Pacific." This notation is useful because it's stable year round. I don't recommend 'PDT', instead colloquially 'out here on the left coast' or specifically US/Pacific.
great deep dive into the Amen break. this video is from the yt days of yore, nice to see the yt algo still propping it up.