The phrase "it's ok to be white" has implicature (by maxim of relevance) and associations (by how the phrase originated and is used in practice) beyond its literal meaning. You can disagree with making that statement without thinking it's not okay to be white.
What in particular has been debunked, and by what?
> If it was co-opted, then why [...]
I wouldn't say it was "co-opted" - as far as I'm aware it originated as and still mostly is an alt-right slogan.
> [...] then why did 49% of blacks take a neutral to supportive view of the phrase in the poll? Explain that.
Those unaware of the statement's usage, and those who choose to interpret the poll question as asking only about the statement's direct literal meaning, would likely answer supportive of the statement.
A better-designed poll could separate out those two issues, asking about both the statement's literal meaning and what it implies, but instead it's kind of mushed together dependant on how the respondent chose to interpret the question.
> And couldn't that taint the people against the phrase?
In that, you think some people would agree with the phrase when taken with its implicature and connotations, but then object to its far milder literal meaning? Struggling to see what worldview that'd be possible for.
> No. They'd be agnostic of the alleged nefarious meaning just like [...]
It's entirely possible that some interpreted it as only the literal meaning and still disagreed with it.
My point is "You can disagree with making that statement without thinking it's not okay to be white", and that the poll's poor design does not allow us to distinguish the two, which was answering your question ("How is [the poll's results] not a red flag for "hate" against another racial group?").
If a poll asks people whether they identify as "pro-life" and the majority of liberals say no, it's not a sound argument to say that then implies the majority are admitting to being pro-death, or that it's a red flag for them being some kind of death cult. The term "pro-life" has meaning (relating to abortion) beyond its literal reading (and in this case I'd expect far more to pick up on it). Maybe there genuinely are some pro-death misanthropes in the sample answering no, but the poll's design does not allow you to conclude that.
> [...] you're dismissing all those accepting as being unaware.
Those that answer in support may be unaware of its usage, or aware but choosing to interpret the poll as asking about its literal meaning, or even aware and agreeing with the implicature/associations.
> For your view to be true, you're saying the other 49% of blacks polled are clueless [...]
>It's entirely possible that some interpreted it as only the literal meaning and still disagreed with it.
Here you say "some". Nobody would disagree, at least not me.
Your prior comment was dismissive.
>Those unaware of the statement's usage, and those who choose to interpret the poll question as asking only about the statement's direct literal meaning, would likely answer supportive of the statement.
Your new comment is broader.
>Those that answer in support may be unaware of its usage, or aware but choosing to interpret the poll as asking about its literal meaning, or even aware and agreeing with the implicature/associations.
As for
>it's not a sound argument to say that then implies the majority are admitting to being pro-death, or that it's a red flag for them being some kind of death cult.
"Death cult." I don't get it and presume most people wouldn't place that label either. I agree that would be weird.
> Your prior comment was dismissive. [...] Your new comment is broader. [...]
As in the lack of mentioning those "aware and agreeing with the implicature/associations" in my prior comment? Notably my prior comment was replying to your:
> > If it was co-opted, then why did 49% of blacks take a neutral to supportive view of the phrase in the poll? Explain that.
Correct me if I'm wrong, but I understood your point there to be "there wouldn't be enough black people who agree with its supposed alt-right usage to make up to 49%", so I gave two alternate reasons people would agree making with the statement (those unaware of the alt-right usage, and those aware but choosing to interpret the poll as asking about the literal meaning).
I'm not ruling out that some of the black respondents responded "agree" because they're aware of and agree with the statement's implicature/associations, it was just already the context of the prior comment that there wouldn't have been enough of them alone (for the alt-right associations).
> I don't get it and presume most people wouldn't place that label either. I agree that would be weird.
Similar is the idea here - people can/will disagree with a slogan because of its implicature and associations without disagreeing with its literal meaning.
> The issue is that the kid wants to play a game with his friends [...] This is a clear and meaningful distinction and it doesn't sound supported.
Clear how it could restrict to friends-only when connecting directly to another Nintendo Switch user, but a bit murky how it'd make that determination in cases like Minecraft where the client is connecting to a cross-platform user-hosted game server that is not associated with any Nintendo/Microsoft account.
Could work if you have the parents manually whitelist specific server IPs, as they could with router/firewall, though not sure if "could you whitelist 209.216.230.207 please?" would present a meaningful choice in most cases.
The goals (initially "raise as much money for charity as you can", currently "Do random acts of kindness") don't seem ill-intentioned, particularly since it was somewhat successful at the first ($1481 for Helen Keller International and $503 for the Malaria Consortium). To my understanding it also didn't send more than one email per person.
I think "these emails are annoying, stop it sending them" is entirely fair, but a lot of the hate/anger, analogizing what they're doing to rape, etc. seems disproportionate.
Autonomous vehicles should be on the road iff they reduce overall incidents/deaths. Failure to deal with an out-of-distribution scenario would count against this, but may be rare enough to not significantly affect the average.
I don't feel NFTs ever really had much interest among the general public - average reaction just being "I don't get it, that sounds pointless".
Whereas AI seemed to have a pretty good run for around a decade, with lots of positive press around breakthroughs and genuine interest if you showed someone AI Dungeon, DALL-E 2, etc. before it split into polarized topic.
> [...] Finally, most important of all, did you have fun? The answer to all of these questions is "no".
Exploring the possibilities and limitations of a new technology is fun.
Obviously this is just a quick experiment lacking a whole lot you'd expect from a regular game, but there's also a lot to be curious about and different directions it could be taken in. With a harness could it generate a background, sprites, and collision mask so the player/NPCs can walk around in real-time? Could you limit commands from the player to reasonable actions ("I attempt to kick down the door") without the full god-mode world control? Or alternatively, could you allow a player to act as god of the world dictating changes, with NPCs or other players living within it (like as a tool for DnD)?
> why not just play an actual Legend of Zelda game? They exist. They are good.
One of their posts under "Latest" at the bottom is "Things I appreciate about Ocarina of Time", so presumably they have. Playing a game doesn't mean you can't also play around with experiments like this.
> Stripping information from an identifier disconnects a piece of data from the real world which means we no longer can match them. But such connection is the sole purpose of keeping the data in the first place.
The identifier is still connected to the user's data, just through the appropriate other fields in the table as opposed to embedded into the identifier itself.
> So, what happens next is that the real world tries to adjust and the "data-less" identifier becomes a real world artifact. The situation becomes the same but worse (eg. you don't exist if you don't remember your social security id). In extreme cases people are tattooed with their numbers.
Using a random UUID as primary key does not mean users have to memorize that UUID. In fact in most cases I don't think there's much reason for it to even be exposed to the user at all.
You can still look up their data from their current email or phone number, for instance. Indexes are not limited to the primary key.
> The solution is not to come up with yet another artificial identifier but to come up with better means of identification taking into account the fact that things change.
A fully random primary key takes into account that things change - since it's not embedding any real-world information. That said I also don't think there's much issue with embedding creation time in the UUID for performance reasons, as the article is suggesting.
> Using a random UUID as primary key does not mean users have to memorize that UUID. In fact in most cases I don't think there's much reason for it to even be exposed to the user at all.
So what is such an identifier for? Is it only for some technical purposes (like replication etc.)?
Why bother with UUID at all then for internal identifiers? Sequence number should be enough.
"Internal" is a blurry boundary, though - you pick integer sequence numbers and then years on an API gets bolted on to your purely internal database and now your system is vulnerable to enumeration attacks. Does a vendor system where you reference some of your internal data count as "internal"? Is UID 1 the system user that was originally used to provision the system? Better try and attack that one specifically... the list goes on.
UUIDs or other similarly randomized IDs are useful because they don't include any ordering information or imply anything about significance, which is a very safe default despite the performance hits.
There certainly are reasons to avoid them and the article we're commenting on names some good ones, at scale. But I'd argue that if you have those problems you likely have the resources and experience to mitigate the risks, and that true randomly-derived IDs are a safer default for most new systems if you don't have one of the very specific reasons to avoid them.
Internal means "not exposed outside some boundary". For most people, this boundary encompasses something larger than a single database, and this boundary can change.
UUIDs are good for creating entries concurrently where coordinating between distributed systems may be difficult.
May also be that you don't want to leak information like how many orders are being made, as could be inferred from a `/fetch_order?id=123` API with sequential IDs.
Sequential primary keys are still commonly used though - it's a scenario-dependant trade-off.
> > Using a random UUID as primary key does not mean users have to memorize that UUID. [...]
> So what is such an identifier for? [...] Why bother with UUID at all then for internal identifiers?
The context, that you're questioning what they're useful for if not for use by the user, suggests that "internal" means the complement. That is, IDs used by your company and software, and maybe even API calls the website makes, but not anything the user has to know.
Otherwise, if "internal" was intended to mean something stricter (only used by a single non-distributed database, not accessed by any applications using the database, and never will be in the future), then my response is just that many IDs are neither internal in this sense nor intended to be memorized/saved by the user.
> By design, this is all it is capable of doing. Assuming a finite, inanimate computer can produce AGI is [...]
Humans are also made up of a finite number of tiny particles moving around that would, on their own, not be considered living or intelligent.
> [...] we have yet to produce a logical definition of "intelligence". Of all people, programmers should understand that you can't program something that is not defined.
There are multiple definitions of intelligence, some mathematically formalized, usually centered around reasoning and adapting to new challenges.
There are also a variety of definitions for what makes an application "accessible", most not super precise, but that doesn't prevent me improving the application in ways such that it gradually meets more and more people's definitions of accessible.
reply