ubertaco

Snopes (like anywhere) is only as reliable as its track record of collecting firsthand sources and accurately reporting on their contents.

Which is to say: pretty good so far, in their case. For the future? Who knows. But they've done well up to now, at least.

This is the exact reason we switched my wife from iPhone to Android – because her iPhone couldn't sync reliably for our shared password vault or for Immich.

You let them write code that runs in prod, which is the same thing with extra steps.

Unless you review that code carefully, and then we're back to the point about it not saving you any cognitive overhead.

....as opposed to the political spoutings off of your brand-new account named "throwaway48965"?

Maybe you're just (ironically) in the minority, and mad that you don't feel like your opinions are sufficiently included.

In my experience, generally Salesforce takes a little while before they notice that they bought you and start imposing uniformity and forcibly regressing you to their mean.

This was a(n internally-)famously hard and lengthy process for them with ExactTarget (read: Marketing Cloud) because ExactTarget employees identified strongly with "ExactTarget orange" culture rather than "Salesforce blue", which mostly meant being appalled at the technical and process swamp that Salesforce represented and pushing hard to keep their own tech stack and their own culture and standards as long as possible.

Heroku had an interesting arc, as they were the bright spot people would point at internally as where actually good engineering somehow happene even at Salesforce. There was a whole effort to let Heroku be the business unit that paved the path to AWS and PaaS for the entire company (which was at the time operating datacenters themselves), and so Heroku got a bunch of investment and freedom for a bit.

Then there was some weird power struggle, and the executives inexplicably decided not only to take that out of Heroku's hands despite their expertise, but also to basically shove Heroku in a corner to be ignored unless stripmined of its customer base through upsells or its staff through reallocations of headcount.

Yeah, I get this a lot, especially from non-southern in-laws who think it's a hoot that they've "cracked the code" and can "speak southern". Being repeatedpy stereotyped to your face gets old pretty quick.

For folks who don't know, here's the best explanation I can offer from growing up in the Atlanta area (but well outside the perimeter):

"Bless your heart" is most commonly an expression of sympathy.

Sometimes, it's sympathetic towards the hardship someone's going through (e.g. "and right after his grandma passed, bless his heart.")

Sometimes it's sympathetic to the trouble someone went through (e.g. "oh bless your heart, you didn't have to go out of your way to bring extra! Thank you so much!")

And yes, sometimes it's an expression of sympathy for the fact that life must be hard for you because of your ignorance, stubbornness, stupidity, or arrogance (or some other such stunting quality) (e.g. "and he thinks he can graduate from Tech with those grades, bless his heart," or "bless his heart, I just don't think he's ever had anyone tell him no in his entire life.")

It's almost all by the kWh here, but perusing PlugShare I've seen a few level 2 chargers here and there that charge by the minute. Usually that's a sign of a charger that was set up a while ago and is owned by someone who hasn't checked on it since.

Interesting, perhaps the message was too narrowly, directly-focused and was missing necessary social context?

This feels like a koan about the subjectivity of which details are important to include.

>Also, that would imply a never-ending wack-a-mole game for me since people obviously keep doing this. I think I have better things to do in my life.

Uh-huh, and what makes that any different if someone else is doing it?

This feels like someone who discovered package managers for the first time.

I worked at Pardot around the time Salesforce started using this same language in internal announcements about Pardot.

Our Pardot leadership translated for us and provided the necessary context: Pardot is being killed. The plan was to start building the product that would replace it, stop selling new contracts, rename Pardot in the meantime so the change wouldn't be as noticeable, and in a timeline of "by 10 years from now" Pardot wouldn't exist anymore.

This is Salesforce for "last call for the lifeboats, we're gonna capsize the boat."

The text of the second amendment, as written, would seem to indicate that the premise of the second amendment is to arm "a well-regulated militia" (which was relevant to the government that adopted the second amendment, as it had no standing army).

It was basically crowdsourcing the military. We've been running through all the various problems with that idea ever since, including:

- oops, turns out not enough people volunteer and our whole army got nearly wiped out; maybe we need to pay people to be an army for a living (ca. 1791)

- oops, turns out allowing the public to arm themselves and be their own militia can lead people being their own separate militia factions against the government, I guess we don't want that (e.g. Shay's Rebellion, John Brown and various slave rebellions fighting for freedom)

- oops, turns out part of the army can just decide they're a whole new country's army now, guess we don't want that (the civil war)

- oops, turns out actually everyone having guns means any given individual can just shoot whomever they like (like in hundreds of school shootings and mass shootings)

- oops, turns out we gotta give our police force even bigger guns and tanks and stuff so they won't be scared of random normal people on the street having guns (and look where that's gotten us)

Honestly, the whole thing should've been heavily amended to something more sane back in 1791 when the Legion of the United States (the first standing army) was formed, as they were already punting on the mistaken notion that "a well-regulated militia" was the answer instead of "a professional standing army".

When you've got kids, there's no such thing as "rounding errors" in terms of time costs.

It's an entire chore I never have to do. That time savings is significant when I'm already underwater all the time.

I've had quite a few folks in my semi-rural north Georgia deep-red county (where our congressional rep wins landslide elections while literally saying Trump is like Jesus) who are convinced by my F150 Lightning.

It's not a hard sell: no more oil changes, no more annual emissions-testing bill, no transmission to ever worry about, and a massive chunk of storage under the hood where the gas engine would be – plus a bunch of outlets all over for powering or charging tools. When I then tell them that I spend about $30/month on charging the thing (at home) compared to my former gas budget of ~$150-200/month, it becomes even more of a no-brainer.

And none of this has anything to do with climate change. It's just plain and simple practicality.

They tend to ask about range. I get around 300 miles on a full charge when road-tripping, and Buc-ees has some pretty cheap chargers (still cheaper than gas would be) that get me back on the road in about the time it takes me to use the bathroom, grab and eat some brisket, and change the baby's diaper. I've done some shortish road-trips a few times now, and not had any problems. I've got some longer ones planned this year, now that I know that I can find chargers along the way.

I looked into PHEVs on my last vehicle shopping go-round, since few pure EVs met my cargo size requirements (stroller/baby life is a whole thing).

Ultimately, it was way more worth it to go all the way up to an F150 Lightning than to go with a good PHEV, partly due to up-front cost, but mostly due to ongoing cost: I will need to change the oil on the electric motors maybe every 150,000miles, and I never need an emissions test again. PHEVs require keeping the gas engine up, and getting it emissions-tested.

A whole category of cost just straight-up disappeared, for cheaper than I could get a RAV4 Prime too.

Oof. That's pretty gross: just throw away all typesafety?

A `Result<T, E>` return type is way better.

This feels like it'll be viewed like Java's `Date` class: a mistake to be avoided.

The Bible is too well-known a text that is too represented in training datasets for this _not_ to be skewed towards poorly reproducing existing translations.

Beyond that,

>there are hallucinations and issues

seems like a deal-killer for a religious text. Yes, all translation by humans is an act of interpretation on some level, and so there's lossiness in all translation – but the difference between a human carefully weighing their reasoning for a particular choice of rendering vs. an LLM that is basically weighted dice that might land totally wrong is a categorically-different thing, not a question of degrees.

I had a history professor who would often use a similar preamble phrase. His was "And SO IT IS that we see that..."

It worked to get our attention partly because of the time it took to say all that, and partly because it was so idiosyncratic that it sorta became a running joke.

I remember one session in particular.

This was a summer class, and as such each class session was around 2 hours long. The professor would typically give us (and himself) a 10-minute break in the middle of the class, and generally if you hung around the room, he'd strike up a more casual conversation in the room.

This was also not long after Michael Jackson died. The conversation got onto him and his life and his mixed legacy of scandal, went on for a while, and somehow made its way to one student observing that (and I quote): "he lived the American dream – he started out as a poor black boy and grew up to be a rich white man."

The room sorta hung in uneasy suspense at how the professor would respond.

"...and SO IT IS that we see that the Mongol conquest...", he said, launching noticeably-abruptly (and with a bit of a knowing grin) back into the course material.

He was generally a good-natured dude like that. His voice sounded a little unusual, and I guess some students thought he sounded like Kermit the Frog. He came back into the room after a bathroom break once to find someone had drawn Kermit on the whiteboard behind where he usually stood when speaking. He saw it, stopped, visibly pondered what to do with it, and drew a speech bubble from Kermit saying something like "the Silk Road" (or whatever it was were about to cover; it's been quite a few years and I don't remember the specific topic).

As an American, a sizable number of Americans are lining up to join ICE under the promise of money.

And also, our whole military recruitment strategy here outside of drafts has been "the GI bill" – paid tuition in exchange for lining up to go to war.

I don't know that the gap in morals is as wide as you think.

Somewhat relevant Cautionary Tales episode, wherein a slight variation on your same point is made from history and survey data: https://www.pushkin.fm/podcasts/cautionary-tales/a-deadly-da...

Because dealerships are the automakers' real customers, at least right now.

You don't buy a vehicle from Ford; your local Ford dealership buys a large number of vehicles from Ford, and then you buy one of those.

Yes, an argument could be made that eliminating the dealership keeps the same customer base while eliminating the middleman (see also: Carvana), but now you have a lot more cost and logistics (shipping individual cars to individuals' homes, for example, rather than shipping truckloads to a single well-known spot) and unless you're willing to do the Carvana/CarMax thing of offering a 7-day return window (which adds even more cost and logistics and risk), the average American customer won't feel as comfortable buying a vehicle sight-unseen from across the country as they would if they could sit in the thing while a salesperson pitches it to them.

That means you're taking on whole new category of cost and risk, while assuming that you won't lose any of your incoming revenue.

That's kinda a big assumption, and the major established/legacy/whatever-you-call-them automakers aren't known for having a high risk appetite.

I've never entirely understood "don't speak ill of the dead"; it seems like a vastly-scoped rule with far too many exceptions (and that can prevent learning any lessons from the life of the deceased). Forgive the Godwin's law, but: did that rule apply to Hitler? If not, then there's a line somewhere where it stops being a good rule (if it ever was one to begin with) – and I'd feel confident saying that there's no real consensus about where that "cutover" occurs.

To me, comments like "the entire arc of Scott Adams is a cautionary tale" rings less of vitriol and more of a kind of mourning for who the man became, and the loss of his life (and thus the loss of any chance to grow beyond who he became).

That rings empathetic and sorrowful to me, which seems pretty decent in my book.

Does this even work if you're incredulous enough???

I bet we could vibe-post a bunch of them, even! Blogging is dead!

And that's great, as long as you're totally cool with access to _any_ of your accounts _anywhere_ being completely controlled by either Apple or Google.

I'm struggling to figure out how you really believe this.

Even if you didn't bother to actually read reporting or see images from the ground of children being shot in their mothers' arms by the IDF and such real horrors perpetrated against civilians who are obviously and visibly non-combatants, it's puzzling how nothing in the hyperbolic, propagandic tone of the alleged quote leads you to question its veracity (or even makes you look twice at taking Russia Today TV as a trustworthy source).

Yeah, this and syncthing for keeping our shared password vault file in sync together were 2 of the 3 major reasons my wife's last phone upgrade was a swap from iOS to Android (went with a Pixel 8, which was new at the time).

Since then, Immich and Syncthing+Keepass have worked as well as or better than their proprietary equivalents for my decidedly-non-technical wife.

I did initial setup, and she never has to think about it again. It just works, which is more than I can say for paid cloud subscriptions and their constant nags over exceeded storage space.

Is there anything preventing use of something like Keepass vaults as your 2FA solution?

A little pedantic, but: this will tell you if a poem is shaped like the common English conception of a haiku, but it won't tell you if this is a haiku, because a haiku is more than just counting syllables.

Aside from the fact that "syllables" is not exactly the unit being counted in haiku, there are also considerations of theme, tone, and a sort of "open-ended-ness" – among other considerations.

This article served as my introduction to the actual complexities of haiku: https://forgottenpoets.substack.com/p/haiku-thursdays-one-pl...

Very cool that the author was able to use a profiler without source code and even add debug symbols, but...the actual conclusion (a third-party script using a third-party scripting system the author had installed but never mentioned until the end was the culprit) was so obvious of a first thing to check that it made the post feel a bit contrived.

It's like if someone wrote up a post detailing a step-by-step teardown of their vehicle's engine to determine why they were suddenly getting worse gas mileage, only to end with "oh, you know what, it's probably the giant always-open drag parachute I installed right before I started getting bad gas mileage. Let me try removing that now that I've ruled out every accessible part of the engine."

Classic Safari. If their traditional pattern holds, they'll re-add it in a year or so, but it'll be unusably broken.