If you happen to drive east / west through Yakima on a semi-regular basis you've probably noticed the Rattlesnake Ridge slide over the past half a decade:
I'm not sure I understand the mental model you're basing your inferences on, but my model leads to a far different outcome:
If you've got a good enough bot and it's pre-qualified to spend money, then it can use the special "register as a bot" API and provide personal information and whatever else I want to understand that there is a "real human" behind the curtain. A credit card alone is not enough, they can be (trivially) stolen. The way I see it using agentic bots will ultimately require you to provide more personal details than an actual human would.
> you're guaranteed a consistent ser/de experience
Are there that many implementations of protobuf? How many just wrap the C lib and proto compiler? Consistency can be caused by an underlying monoculture, although that's turtles all the way down because protobuf is not YAML is not JSON, etc.
Off in the weeds already, and all because I implemented a pure Python deserializer / dissector simply because there wasn't one.
Focuses on the contiguous US States. It gets more interesting when you're accessing resources not located in North America / Western Europe. It gets even more interesting when neither you or the resources are located there.
I don't quote the following to discount what the article is saying, I think it is what the article is saying:
> This may or may not be OK for your market—"good internet" tends to be in population centers, and population centers tend to contain more businesses and consumers.
and this:
> That said, I'm deliberately not making any moral judgments here. If you think you're in a situation where you can ignore this data, I'm not going to come after you. But if you dismiss it out of hand, you're likely going to be putting your users (and business) in a tough spot.
> If you are dropping packets and losing data, why would it matter if you're making one request or several?
Let's just focus on the second part: why would it matter if you're making one request or several?
Because people make bad assumptions about the order that requests complete in, don't check that previous requests completed successfully, maybe don't know how (or care) because that's all buried in some frontend framework... maybe that's the point!
> Believing that one request maps to one packet is a frequent "gotcha" I have to point out to new network devs.
What is a "network dev"? Unless they're using UDP... maybe you're thinking of DNS? Nah probably not. QUIC? Is that the entire internet for you? Oh. What about encryption? That takes whole handshakes.
Send one packet, recipient always receives one packet, is a "gotcha" I have to point out to experienced network administrators... along with DNS requires TCP as well as UDP these days, what with DNSSEC, attack mitigations, etc.
> This is because standard TCP packets max out at ~65 Kb.
BTW, frags are bad. DNS infra is still kneecapped by what turned out to be an extremely exuberant kicking of the can down the road packaged as "best practice". I think the architectural discussion must have been "100 nameservers for an AD domain, plus AUTHORITY and ADDITIONAL, not to mention DNSSEC..." "Oh UDP is fine. Frags aren't a problem, the routers and smart NICs will handle it fine." "4096 ought to be enough for anybody." "Good. I'll have another Old Fashioned then." And then the clever attacks begin.
Jumbos are great, but the PMTU has to support it. Localhost or a datacenter, maybe a local network. Somewhere between BIND 9.12.3 and BIND 9.18.21 the default for max-udp-size changed from 4096 to 1232. Just sayin....
I don't know. I still use telnet for things, but I can use nc in a pinch. I would be more inclined to wish for expect.
What I don't get is all the SSL kids never mention s_client, as in "...use s_client instead". Granted, most of the time ssl will work for, you know SSH (port 22). Are you really going to negotiate the cypher by hand, mate? I get it, how many of them can identify what "\x16\x03\x01" is?
I don't know that this is a particularly good article, but it touches on two elements of games based on incomplete / imperfect information.
One of these elements he refers to as "leverage" and I think he does an ok job explaining what it is, although maybe not how / why it works.
The other one, contrasting doctors and contractors, I think he does poorly. Full disclosure: I've had really crappy luck with doctors (it's not just luck). Doctors aren't used to getting "not to exceed" demands, things like that. On the other hand my father was a psychiatrist, a specialist, and that gives me insight into the "practice" of medicine; and I've worked for a number of biotechs and I have some insight into the evolution of medical practice. Combined, I have a pretty good sense of when the doctors are "practicing" versus forming a hypothesis (ask for one!).
During one of my burnouts I took a "vacation" working (what started as part time) for a high-end flooring contractor. Although the owner and I had different backgrounds and beliefs we had mutual respect for each other (and we had great conversations). But what the public calls (and in public we called) an "estimate" we called internally an "interview"; and we wanted to take the temperature of the "pain in the ass" factor: Does the prospect truly understand the work? Does the prospect have irrelevant concerns? (I'm doing a poor job here, although I'm pretty sure successful contractors will understand what I'm talking about.) Our bids could vary as much as 300% (upwards) from our baseline model / estimate for the job... before we said "no" outright or came up with good excuse for them to fire us before receiving our bid.
There were some rather "zen" aspects of the process (my father had a zen question: how do you feel? I have a zen question: what do you measure?), such as an insistence that all special instructions had to fit, legibly handwritten, in about 1/3 of an 8x11 piece of paper. (We did $10000 floors on a one page contract, not including non-negotiable required boilerplate; why can't we do that in IT? Can we? Yes, yes I say we can.)
But distilling this down: some contractors would rather deal with the masssages and fish tank cleaning (at 3x the $$$) than do floors... whereas for us flooring was a religious calling or something. You'll find this both in doctors and in contractors; and you'll also find people out there who expect to pay that 300% markup to have the contractor walk their dog.
https://www.heraldnet.com/northwest/landslide-near-yakima-mi...
https://www.yakimaherald.com/news/local/lower_valley/rattles...
reply