Also peppers and potatoes. It's amazing to me to think about how adaptive people are that "old world" places have so thoroughly integrated these "new world" items into their culinary cultural identities.

Wikipedia gives a decently quick tour of chili's evolution.

I've been spouting about the "chili queens" of old San Antonio as the origin, but it sounds like they were more significant as an early analog to food trucks that drove chili across cultural gaps. The origin of that food sounds like it originated back, at least, to indigenous peoples and does sound like a staple of cowboys/vaqueros long before the Great Depression.

Then there's Cincinnati-style chili, "developed by Macedonian and Greek immigrants, deriving from their own culinary traditions", so that merging of another style under the same name might muddy the water when it comes to talking about the origin of spiced meat bits.

____________________________________________________ gun control ___________________.

💀

That's a big motivation for me, too, but I'd say it's about equally that I want archival of the best stuff for when rights holders pull their catalogs from the services I stream. I used to think that was mainly for the more obscure stuff, like local bands' early albums that I can barely find anymore, but recently I've noticed albums missing from main services (Tidal and Spotify, in my case) for bigger acts, too.

Cleveland clinic says says about coffee's laxative effect:

Researchers found that 29% of coffee drinkers report a desire to poop after drinking coffee. The feeling can come pretty quickly, too. (In as little as four minutes!)

And about lactose intolerance (same article):

An estimated 65% of people have some difficulty digesting lactose, which can lead to restroom runs. Lactose intolerance can cause diarrhea and other gastrointestinal (GI) issues within 30 minutes of consumption.

At least they didn't write "brand's", so there's that.

I'd had this over my front door for however long it took for them to build it. My pest control service said the size of the nest can affect how aggressively defensive they might respond to perceived intruders. I guess maybe I was just lucky we caught this one before it got any more developed.

I gnu y'all would find a way to pun it up.

I thought it was because he’s afraid he sounds like he's saying "lion" instead of "lying", and he doesn't want to risk sounding complimentary.

It is ridiculous, but it's also exactly what is happening with loud combustion engines. Any sound coming from it is just higher-entropy (i.e., unused) energy being produced and promptly lost instead of contributing to power.

I thought, "What's wrong with 'fascist' in a politics forum?"

Data can be beautiful. I just found a similar but maybe clearer example from 2016 with a nice write-up about it.

Teaser from that article:

I think the common term for these is "cartogram".

For me, it's helpful to remember what the underlying reality is.

Skewed for population and colored on a red-blue scale to reflect vote mix.

When those votes are counted, the resulting electoral votes align to those votes, which results in maps like what you showed. When strategists tune their messages to target demographics they can divide (e.g., rural vs. urban), they're playing a game of inches and shades on this map of purple goo, and that's still the reality behind the ultimate electoral vote, even if it doesn't feel like it.

Keep voting, everyone!

edits: So much autocorrect.

1. Granola and plain yogurt
2. An Italian-ish sandwich (ham, salame, lettuce, tomato, cheese, giardiniera, oil+seasonings, and mayo, on wheat) with peperonicini-flavored kettle chips/crisps
3. Pork carnitas "street" tacos with borracho black beans

It blows my mind that centuries-old concepts "let's not jump to hasty conclusions" and "people should be free to protest the government but not break the law" just got called "flaming progressive".

edit: Sorry, now I see what you're saying, that those were some points that pull people from across the aisle.

ah goddammit

Keep in mind, though, so far, we only know it to be a user experience issue.

“Incomplete paper and online applications will not be accepted,” Evans said in the statement. (Parker’s cancellation request would have lacked a driver’s license number.) The Secretary of State’s Office did not respond to individual questions about what testing the portal underwent before launch, the system’s security procedures, what happened to Parker’s cancellation request....

It doesn't matter what the browser says if the end user tampered with the running page to make it say something. It matters if the application might have been processed. They're claiming it wouldn't have been processed since it was incomplete (lacking ID number). We'd need to know how this was handled on the back end to know how risky it really was. It could still have been bad, but this isn't, in itself, proof of an actual problem.

edit: Just to be clear, I'm not saying it shouldn't be investigated. It really should be, as the article claims, an all-hands-on-deck moment. I'm just saying that the article makes the case that it should be investigated to ascertain what would have happened to the incomplete application submission to assess the exposure, not that it definitely was a vulnerability at all.

“Incomplete paper and online applications will not be accepted,” Evans said in the statement. (Parker’s [demonstration] cancellation request would have lacked a driver’s license number.) The Secretary of State’s Office did not respond to individual questions about what testing the portal underwent before launch, the system’s security procedures, what happened to Parker’s cancellation request....

Yeah, that tells us we just don't know if this was a problem after all. Evans's statement basically claims it wasn't a vulnerability. If that's correct, then the worst thing might be if someone's browser tripped on the validation JS and allowed them down a blind alley execution path. If the claim is correct and if the page's JS never shits the bed, then in that case the only negative outcome would be someone dicking with the in-browser source could lead themselves down the blind alley, in which case who cares. The only terrible outcome seems like it would be if the claim is incorrect--i.e. if an incomplete application submission would be processed, thus allowing exploit.

Short of an internal audit, there's no smoking gun here.

This really is the only acceptable comment. Might as well close the thread.