British aristocracy has been pronouncing their own surnames wrong for centuries on purpose. Cholmondeley is "Chumley" Featherstonehaugh is "Fanshaw." If you read it phonetically you mark yourself as an outsider. The misstake is the membership card. (Heck, even in Portland we locals hear about misprouncing Couch St probably every year in local press as some bar for membership to our own locals only vibe.)
I don't really see that as the same thing as what the article was pointing out. Those are shibboleths that only an insider would know. You have to get the pronunciation of Cholmondeley or Couch "right" to pass for an insider.
The random misspellings, missing spaces, sloppy grammar, etc in the examples in the article seem different to me. Misspelling "en route" as "enriewu" doesn't show, "look, I know the secret country club spelling for en route". It simply shows that you don't have to care about your mistakes. You write something that approximates what you mean, and you're too important to spend time revising. The mistake could be "enrout" or "n route" or on any other word. But you're not going to be a try-hard who edits and frets over their messages, you're blessing someone with 10 seconds of your attention and they're lucky to receive your correspondence, typos and all.
Or its a simple signifier that the author was human, and that a real person is trying to convince you of something. I've experimented with putting minor grammar mistakes into my work of the sort that would be frowned upon, but are not strictly invalid. The existence of any kind of mistake makes the work sound "human".
Don't know about that as a general rule, since spam messages have had typos and mistakes in them since forever, and its precisely what marks them as not trustworthy.
More like signaling that a specific human wrote it themselves instead of one of their human assistants. The article is mostly about emails from the Epstein files so non-human authorship wasn't really a possibility at the time they were written.
I don't necessarily think it's that... it's just a matter of a rush to respond/send quickly and not take a lot of time. It's pretty easy to either fat-finger when typing on a keyboard, or gesture input on a phone to get the wrong word and you hit send before realizing.
Sometimes I'll notice right after, delete and re-reply (social media) other times I'll just let it be... It's pedantic busy bodies that will single you out for a typo as opposed to discussing the idea at hand.
The "enriewu" thing wasn't a misspelling of "en route", it was someone's name who had arrived in Miami with Jean-Luc and Peggy. It's probably a misspelling of Henry pronounced in French.
We’ve known since Socrates that writing instead of speaking eroded thinking. We seriously need to stop putting packaging, especially writing, on a pedestal. Instead we should put what little lifetime we have in sum towards focusing on what’s actually important: the ideas and concepts themselves.
That's great. What's also amusing is how you felt it necessary to provide the diacritical pronunciation guide for "Vaughan"... because I think to most native English speakers we can't imagine any other pronunciation!
I think native English speaker who had never heard of Vaughan (sure we can find some of those) would likely to pronounce it like "Vog-un" - /ˈvɒɡən/ or "Vog-han" - /ˈvɑːɡən/
This sent me down a mental rabbit hole, I think it's one of those interesting nuances that are rules that native speakers follow without being able to name it, or know it.
I'm a native speaker, and also thought `vawn` was the most obvious pronounciation.
I'm guessing it's because `augh` is perceived as a recognizable vowel cluster where `gh` tends to be silent (daughter, caught, naught, taught). The interesting twist for me is that `laugh` is in obvious counter example, until I realized that gh in final position (laugh, rough, enough) is almost always \f\. And further, in words like laughter, roughness, we immediately distinguish a modified root word from the lexical position.
Maybe there's also an interesting thread to pull on in that the pattern may be more pronounced for names (e.g. Hughes). Just ruminating here though, I don't have a source for any of this.
There are a handful of neighborhood and street names used in Toronto (not necessarily from Toronto) that have unusual pronunciations. Here I'll give some triples of (English spelling, actual pronunciation (IPA), a naive pronunciation (IPA)):
Definitely heard "Alana" in the South. On the West cost right now, got a buddy from West Virginia, and even after 20-30-some-odd-years in California, he still says it like that. Among other things he boomhauers.
In case you're wondering, Couch St. in Portland, Oregon, USA is pronounced "Cooch." It's named for 19th century ship captain and early businessman John H. Couch. It's the "C" street in the so-called Alphabet District north of Burnside, which is the "B" street. There are, or were, other landmarks named after Capt. Couch, but I'm not sure if any still exist.
Note that you only pronounce Couch that way in Portland when talking about the street. You wouldn’t maintain the pronunciation when saying eg “Sorry for spilling wine on your couch”
Sometimes I wonder about the aristocrats who towns and roads in the UK were named after, like Lord Penistone of South Yorkshire, or Lady Sluts Hole of Norfolk.
Featherstonehaugh pronounced Fanshaw is apparently something made up by P.G. Wodehouse for one of his characters. It's just Featherston-haw for everyone in reality.
The character Beauchamp ("BEE-jum") Day in Armistead Maupin’s Tales of the City is a softening of the English aristocratic way ("Bee-chum") of the French spelling Beauchamp ("boh-SHON" as the French would say).
But he's less a British aristocrat than a brittle prep-school martinet in a cheap tie who rants at a secretary over three typos like a duke defending the realm, sneers about Kelly girls and office decor as if guarding the Social Register, treats sleeping with his own employee as proof of authority, and then sneaks off to bathhouses while running his typing pool with equal parts class anxiety, closet panic, and a middle manager's superiority complex.
In New Orleans, protesters against outsiders acquiring and developing real estate hold up signs that read "Say Tchoupitoulas" (/ˌtʃɑp ə ˈtuː ləs/). I give my wife lots of hassle about the pronunciations of Louisiana place names like Tchoupitoulas, Natchitoches (/ˈnæk ə ˌdɪʃ/, really!), etc. especially when she complains about northeastern place names like "Leominster".
Did they? The article[1] seem to be in contradiction to the claim. For centuries it was rather easy to distinguish aristocracy without lingustic conspiracies. I'm really not an expert in British surnames however I know for sure that pop history is full of invented "fun facts" which are not true but persist cause they sound cool.
There's also the British penchant for deliberately mispronouncing French words. I have heard "renaissance" pronounced "reh-NAY-sance", "fillet" pronounced "fill-it", "valet" as "val-it" and so on. I think it's a national point of pride to pronounce the words of their neighbor incorrectly.
I'm always amused by some mispronunciations that stray farther away from the original than necessary.
My favorite is probably crepe, which Americans pronounce like an almost diphthong-y craype (or crape like grape I guess) when crep (like step) would do just fine and be closer to the original.
But as a native French and basically-native American speaker, I also couldn't really care less about it, or about things like Americans pronouncing the t in croissant, or French people being unable to say the.
I notice the variance in british and american pronunciation of especially romance + greek words, correct or otherwise and I'm willing to give credit where it's due, I'm also happy to celebrate the differences rather than mock or correct them, I just won't accept the slander!
I’ve always said that one key difference between British English and American English is that a British speaker will intentionally mispronounce a foreign word, while an American will attempt to pronounce it correctly but get it wrong anyway.
It's much deeper than that probably because the kludge of english is in large part french.
But I also completely disagree, I don't think americans are attempting to pronounce croissant correctly for example, whereas brits will be much closer with no attempt at intentional mispronunciation, it just happens that brits are much closer on some and further on others, and vice versa re americans.
and I don't think there is any malice, in fact it became common among the british aspirational middle-class in the 70s to adopt french words in an attempt to appear cultured and upper, ironically now a clear marker of non-u.
"Valet" and "cadet" is an interesting pair: they rhyme in French (/va.lɛ/ and /ka.dɛ/), but rhyming them in English would be ... unusual.
If there were just French words pronounced in a French way and English words which came from French and are now pronounced in an English way that would be bad enough but in fact we have a whole spectrum of bastardisation.
Those are the standard British pronunciations, if you meant 'I have heard' as though it might be a niche or occasional occurrence. ('fill-ay' et al. are AmE pronunciations.)
It's not always that way though, consider 'niche': it's AmE that decided it's 'nitch'!
Yep. And try "lieutenant" or "herb" on for size. (Edit: I guess "herb" is a bit of a complex one... originally from Latin's "herba" where the H was pronounced, but from UK it came most immediately from French's "herbe" with no H sound. So UK did somehow shortcut back to a more original sound.)
So this isn't the British being deliberate obtuse, foreigners pronounce English words wrong all the time and we don't accuse them of doing it on purpose. They do it because that's how they would pronounce those words in their language.
Fillet/valet are mis-pronounced because of mallet, pallet, etc. Renaissance? Nail, snail, tail, etc.
It really is that simple, we're just pronouncing them as if they were an English word.
not entirely, IOMMU is a thing, that is IIRC how Amazon and other hyperscalers can promise you virtual machines whose memory cannot be touched even in the case the host is compromised (and, by extension, also if the feds arrive to v& your server).
>how Amazon and other hyperscalers can promise you virtual machines whose memory cannot be touched even in the case the host is compromised (and, by extension, also if the feds arrive to v& your server).
Even if we take those promises at face value, it practically doesn't mean much because every server still needs to handle reboots, which is when they can inject their evil code.
This is excellent. The ability to trick remote servers into believing our computers are "trusted" despite the fact we are in control will be a key capability in the future. We need stuff like this to maintain control over our computers.
Well, it kind of is actually. The previous iteration of the design didn't have that vulnerability but it was slower because managing IVs within the given constraints adds an additional layer of complexity. This is the pragmatic compromise so to speak.
Does it count as a conceptual problem when technical challenges without an acceptable solution block your goal?
Hosting tor outbound server at home is stupid idea.
Your home is gonna be raided by Police and you will wait months or year to get your shit back and then if nothing, gonna be charged for having pirated windows and Photoshop lol
These days, every American's threat model should include being v& by the feds, and here in Germany, the situation isn't much better, you can get v& for saying the Minister of Interior is a dick [1].
Yes, this was later on ruled unconstitutional, but it doesn't change the facts, and, worse, Germany doesn't have a "fruit of the forbidden tree" rule.
But the point here is that userspace can use this to bypass kernel protections that would otherwise prevent it from mutating R^X pages for example, not that the kernel can bypass its own.
Those protections are mainly about preventing well intentioned people from accidentally shooting themselves in the foot though, right? So it's not really a big deal that there is a way around it.
No, page table write access allows arbitrary memory access because I can map any PFN I want. It's certainly a vector to execute arbitrary code in ring 0.
Not really, of the security measures on Windows, is exactly to control how kernel can access secure process memory, as possible mitigation to attacks by rogue drivers.
Naturally it is the kind of stuff that requires Windows 11 vlatest with the nice Pluton security CPU, as part of CoPilot+ PCs design.
I'm in my 50s and when I was early 20s I crossed from US to Canada for a business meeting. "Why are you coming to Canada?" "To work." "Where's your work permit?" "Huh, I don't have one." That simple "wrong word" slip STILL gets me flagged and cordoned off into hours-long border diversions whenever I go to Canada.
Just imagine how it'll be now... for decades you'll be fending off some hidden receipts from an IG comment you made.
Back in around 2012 or so, some friends and I decided to book a canal house in Amsterdam to all pitch in together and live there for about 2 months. Celebrating a few coinciding life achievements before moving onto the next phase of adult life sort of thing.
I worked remotely, so planned to simply do work for half the time I was there. As such, I brought a proper monitor, keyboard, etc. with me.
As I have my 20" boxed up LCD panel in my arms in the immigration/customs line at Schipol, a Dutch immigration officer comes up and asks me what the monitor is for. I of course like an idiot said "staying here for a couple months for a vacation, but I plan to work some while I'm here!". I got infinitely lucky with the officer in question - she very quickly told me I was incorrect and that the monitor was to play video games and that's what I was going to tell the immigration officer at the passport desk.
One of those early lessons learned that I'm sure looking young, naive, and stupid helped me in a way that I could not get away with in my mid-40's these days.
I worked for a small company that did work for a cross-border manufacturer. Coming from Canada, we were told explicitly that "meetings" was a perfectly good reason for a day trip, and we were never there "to work". US customs has been historically as humourless a bunch as ever existed, and the factory on the other side was unionised, so meetings it is.
What cracked me up was driving back late one evening, arriving back at the Canadian side. The agent asked where I'd been, and I mentioned the town just behind me.
Not your fault but another lesson here is lying to border guards is ok if they say it is.
Which proves how much theater there is in security and that laws are not there to be blindly followed, but to enable the state to pursue its perceived enemies
Had a similar experience: over a decade ago our firm opened an office in Canada and being scrappy and startup-like I had to cross into Canada with some networking equipment to help set up the new office. The amount of scrutiny was insane: thankfully it never stuck and I was eventually let on to do the work and return
Of the seventeen countries (including China, Saudi, Thailand, USA, etc.) I have visited over the last four decades the only time I have been taken out of the queue at passport control to be interviewed was at Toronto flying in from Europe. Actually the tone of voice was more suited to interrogation than polite inquiry. It was very odd, and quite at odds with both my impression of and experience of Canadians themselves.
Ah ok so only lawyers get to use AI hallucinations! (Actually, CA has a bill pending that AFAIR requires lawyers to manually verify AI citations... which is a lot narrower and better than what NY is trying here.)
This is not directionally good because NY already has laws against unauthorized professional practice and deceptive conduct, and S7263 mainly replaces regulator-led enforcement with a vague, fee-shifting private cause of action that is likely to drive serial plaintiff litigation while chilling useful consumer guidance.
Whats at least somewhat humorous is the disclaimer requirement that "[t]he text of the notice shall [be] no smaller than the largest font size of other text appearing on the website on which the chatbot is utilized."
H1 hero font size here we come for disclaimers! (Which don't do anything, per the bill, anyway.) But also is the fancy thought that chatbots only appear on websites.
reply