As a Black American, I find the author's idea extremely interesting and naturally began to wonder -- what might this idea (in code?) look like for us?
Owing to history and whatnot, the role "Black American English" might play is of course very much a moving target, but it's interesting to think about.
The more I think about it, the more difficult it seems. Not that it shouldn't be done, but wow.
The non-prestige dialects of a language don't usually attract official interest, not least because officially the people who understand that dialect could also understand a prestige variant. Scousers may not talk like King Charles among themselves, but if he speaks they're not confused about what the King is saying even if they wouldn't use those words or say them that way.
This might get sketchier for Chinese topolects where the official government policy is that China has a single language, "Standard Chinese" but, those topolects sure do seem like different languages if you didn't know about the policy. However AAV is nowhere close to that, I can't imagine that anybody who uses AAV normally watches "Last Week Tonight" and goes "That guy is speaking a completely unrecognisable language, are there subtitles?".
This means that AAV is culturally important, but there's not necessarily the same sense of "this is a separate language" that there is with Scots, even though in many ways it has all the same claims of being one.
It would be exceedingly difficult to strongly distinguish it from "Gen Whatever Slang" or "US Slang" or a lot of "LGTBQ Slang" etc etc. The list goes on.
Linguists would tell you that Scots is a sibling to English rather than just a dialect of English, having both descended from Middle English and that the dialect of English people in Scotland speak is instead "Scottish English". In practice of course humans don't language tag their speech (indeed they rarely even language tag written text) so it's murky. Maybe one word in ten that a Scottish bloke just said to confuse a tourist was technically Scots not Scottish English and perhaps some of it was even Gaelic. The important thing was that they confused the tourist as desired, for which frankly even an inside joke would work.
Sociolects are fun. In one of my friend circles the word "fish" is understood to mean the controller for a video game, I don't know why exactly, but if you said to one of us "Pass the fish" they'd hand you a controller without even seeming puzzled, that's just obviously what you'd call it. But in another circle it means nothing and you'd be greeted with confusion.
>That guy is speaking a completely unrecognisable language, are there subtitles?
Interestingly enough, I remember reading somewhere that you could be legally entitled to an interpreter in a court setting (take that with a grain of salt, I forget where I read it)
That is how it often manifests, the bits the Brits get to choose is in their own language and spelling.
The other thing I find interesting is that formal English has eschewed the double negative as an intensifier while most (all?) other Indo-European languages employ it. Compare Spanish “No veo nadie” (literally ”I don’t see nobody“ which is the informal English formulation) to English “I don’t see anybody.”
There is a constant American assumption that their language and culture is the norm and we should all adjust our language to fit their definitions and culture. I intend to keep eating faggots, having a master branch in git, etc.
This is now far more than an American assumption. I have seen younger continental Europeans bristle at UK English because they grew up in a world of social media that is converging on usage that is closer to US English.
4.3 Limited Use Nonce Values
The Digest scheme uses a server-specified nonce to seed the
generation of the request-digest value (as specified in section
3.2.2.1 above). As shown in the example nonce in section 3.2.1, the
server is free to construct the nonce such that it may only be used
from a particular client, for a particular resource, for a limited
period of time or number of uses, or any other restrictions. Doing
so strengthens the protection provided against, for example, replay
attacks (see 4.5). However, it should be noted that the method
chosen for generating and checking the nonce also has performance and
resource implications. For example, a server may choose to allow
each nonce value to be used only once by maintaining a record of
whether or not each recently issued nonce has been returned and
sending a next-nonce directive in the Authentication-Info header
field of every response. This protects against even an immediate
replay attack, but has a high cost checking nonce values, and perhaps
more important will cause authentication failures for any pipelined
requests (presumably returning a stale nonce indication). Similarly,
incorporating a request-specific element such as the Etag value for a
resource limits the use of the nonce to that version of the resource
and also defeats pipelining. Thus it may be useful to do so for
methods with side effects but have unacceptable performance for those
that do not.
Presumably the etymology was in place before it took on its present meaning, but it is not a word I would use in a professional context.
My comment was oblique, but not sarcastic. Partly because I didn't want to use the word directly, and partly in keeping with the tone of the original blog post!
Wait, isn't that a cigarette? Why would you eat it?
edit: nevermind, it's actually meatballs, the short version is for cigarettes
> There is a constant American assumption that their language and culture is the norm
> having a master branch in git