all other parts of the current rule are same (time of pass, doesn’t apply if the player doesn’t impact the play, 2nd to last defender, only on the half of the field, not on certain sets, etc.)
there would always be millimeter decisions, but current line is too silly too often
Offsides should be when either of the following is true about the offensive player:
A) has one foot planted fully behind the defender
B) has at least one foot in the air fully behind the defender AND other foot is off the ground (regardless of position relative to the defender)
A year ago it wasn’t quite this good.
Even 9-10 months ago it couldn’t really park without extra manual steps.
The best time to buy a car with a FSD was somewhere around October 2025 when it was fully completed for point to point.
The 2nd best time is now.
I just bought a Tesla Model Y
Full Self Driving is one of the most impressive pieces of technology I’ve ever experienced.
I now wish I’d got it a year ago.
The purpose of UBI is twofold:
1. efficient implementation of popular welfare programs with lowest possible administrative costs, and
2. reduce labor market distortions: min wage, employer healthcare lock-in, and poor working conditions (telling your boss to f-off if needed)
anyone worried about lazy people mooching off the government should take a look around and wake up. this isn’t more or less a problem with UBI.
UBI is just good economics. literally essential for labor markets to truly benefit from signals the way capital markets already do
Age Verification should be tied to physical devices (like TPM or similar) with ID verified at time of purchase like everything else. OS and browsers and other apps should just faithfully report the device status on outbound web requests as a tri-value: [adult, non-adult, unknown]
@iamgingertrash perhaps something massively distributed that aggregates/democratizes direct actions for betterment of society, while educating new nodes and back propagating feedback. something with self healing and adaptive properties. a memetic safety net for that which makes us human and free
@staysaasy well the Krugman hypothesis on the impact of internet on productivity has mostly been proven correct at this point. this seems a good/obvious extension of it.
"AI can't stop recommending nuclear strikes in war game simulations... leading AIs from OpenAI, Anthropic and Google opted to use nuclear weapons in 95% of cases," per New Scientist
I have a guest essay in @nytimes today about autonomous vehicle safety. I wrote it because I’m tired of seeing children die. Done right, we can eliminate car crashes as a leading cause of death in the United States
@Waymo recently released data covering nearly 100 million driverless miles. I spent weeks analyzing it because the results seemed too good to be true. 91% fewer serious-injury crashes. 92% less pedestrians hit. 96% fewer injury crashes at intersections. The list goes on.
39,000 Americans died in crashes last year. More than homicide, plane crashes, and natural disasters combined. The #2 killer of children and young adults. The #1 cause of spinal cord injury. We’ve accepted this as the price of mobility.
We don’t have to.
In medicine, when a treatment shows this level of benefit, we stop the trial early. Continuing to give patients the placebo becomes unethical. When an intervention works this clearly, you change what you do.
In driving, we’re all the control group.
Cities like DC and Boston are blocking deployment. And cities are not the only forces mobilizing to slow this progress.
It’s time we stop treating this like a tech moonshot and start treating it like a public health intervention that will save lives.
Link to article below.
👀 this video of Waymo cars evading crashes with people and vehicles. I especially note the ones that require it having a 360° view.
My sincere thanks to Alex Ellerbeck and @acsifferlin for their wisdom and sure hand in editing this piece.
- full stopped for a loose dog running in the road to let it cross in front (shocked me and thought it was phantom braking for a second or two till I saw it too)
- pulled cleanly into garage back at home
It also had three interventions needed (2 new), all navigation related. 😅
Had my first ride in FSDs 14.2 this morning.
It did three amazing things I’d never seen before:
- pulled out of my garage into an alleyway, on garbage can day (took about 3 maneuvers more than optimal, and tapped my recycle bin but was the first time I didn’t need to take over)
@wholemars 💯 Just bought my MYLR for the FSD(s) a few months ago after seeing 13.2.9 videos - been watching very closely for it to hit this point since the claims in 2018. It’s finally here.
EV was not a factor. If anything, it slowed my purchase a bit to research maintenance differences.
If you tax something, you will, on margin, get less of the thing you are taxing.
That is why I find vacancy taxes so interesting: it seems obvious that apartments sitting idle and empty longer than necessary is bad.
What are some other tax ideas that discourage inefficiency?
@elonmusk and adjusting the loan details - nothing worked. Tried all support channels and got no response until about 16 hours later after I already cancelled delivery and created a new order.
Problems were complicated because WI rules meant long travel for pickup.
@elonmusk the final paperwork. Eventually learned from staff that I would have received a check for the remaining trade in value but this was not visible or indicated anywhere in the app or paperwork. Tried everything I could in the app, re-adding the trade in, removing the trade in..
Theory: The fewer long-lived environments the better.
I prefer having only one long-lived environment - Production.
Here's my ideal 3 step workflow:
1. Code on my local machine. Spin up the environment via a single command. Each dev has their own DB instance(s), populated via scripts checked into source control, and a simple command to reset the DB to support reliable automated testing. Everything runs local - no internet required.
2. When I create a branch, a "Preview deployment" (also known as an ephemeral environment) is automatically created and deployed to a unique URL. (For example, Vercel does this). Code reviews, demos, QA, and user acceptance tests use the preview URL. This way, code is fully vetted and approved for prod *before* merge. This shifts quality left and encourages frequent inspection and collaboration.
3. If all tests pass on CI, I merge my PR to main and it auto-deploys to prod. I feature flag if I need to limit who sees the new feature.
Notice what I don't need with this approach? No long-lived Dev, Sandbox, QA, UAT, or Staging environments. These environments lead to batching and coordination overhead, and generally fight against continuous delivery.
Often automated preview deployments and prod are all that's needed.