The truck won't wait long. That's why its texting ahead. Its giving a tight eta and confirming someone is there. Then it would wait 10-15 minutes tops. If no one shows up, its already got the next stop set up where the recipient states they are home and able to retrieve the package. If they aren't home, they could provide a time window for when they will be and the package can be delivered then. If you are a "no show" too many times, you don't get home delivery. Those people will be directed to a locker or local service facility.

While this sounds cool and futuristic, its a dumb idea for several reason...

1. How could it deliver to anyplace that isn't a wide open yard?
2. What happens when it crashes? Especially if it damages property or injures someone.
3. What happens when kids think its fun/funny to throw things at them?
4. How could it deliver to anyone beyond street level?
5. This would have severe weight restrictions and not be useful for a large % of items.
6. This would have issues delivering in a variety of weather/wind conditions.
7. Thieves would eventually target these for what they carry as well as the drones themselves.
8. Customers don't want their good delivered to the middle of their yard. They want them discretely placed by a door.
9. Urban areas are too dense for these and most rural areas are too far apart.

The real "drone" deliveries will be by USPS/UPS/FedEx via trucks once FSD is available. They will text people to alert they are coming soon. Once confirmed they will arrived and wait a time period for the recipient to collect the package from the truck using a code. Machinery in the truck will place the item in a locker where it can be retrieved from once the code is entered. Meanwhile, the truck is already texting the next recipient or 2 and prepping to deliver the next item. This can run 24/7 without the need for couriers or drivers. All it needs is someone to load the truck. If customers want something hand delivered, they can/will pay an upcharge. If they work 2nd shift and want their item delivered at 2AM, its no issue and no overtime pay will be required. This is the future. The biggest downside is the several million couriers/drivers whose jobs won't exist in 20 years.

Nowadays, university students chant ... "support Hamas"

Who is your favorite Corey? Corey Hamas or Corey Feldman?

https://en.wikipedia.org/wiki/...

Are they "less committed" or "less desperate"?

Does anyone trust Musk enough to have full access to a spy satellite system like this?

It seems extra risky to "rock the boat" messing with customers who you already have in a subscription model. Many will pay forever, UNTIL you make a change that causes them to reevaluate the situation. I'd try at all costs to NOT entice my customers to reevaluate the value of my product to them and whether they should continue using it.

So they tried super hard to kill sharing of accounts which forced some people to go ahead and get their own accounts and have a surge in new subscribers. The real trick will be if they can hold on to all those accounts. I can imagine a scenario where those "new" accounts last a few months before they realize why they never bothered to pay for the service. They either don't use it frequently enough or there isn't enough content that interests them. Additionally, those who already had accounts and were sharing with others may have felt compelled to keep the accounts active before since they believed those they were sharing with valued the access. But once they aren't sharing anymore, they have no reason to resist cancelling if they themselves no longer felt the value warrants the cost.

Exactly. Plenty of people work hard every day and plenty of people do nearly nothing and make 10x money.

And I agree it will be a problems when millions become unemployeed due to AI automation, but that doesn't mean it overall bad for society. Again, we could stop making backhoes and go back to digging ditches by hand, but I suspect few will think that is a good idea for civilization.

The first big pain point will be full self driving. There are ~2M over the road truckers in the US. When FSD trucks are available for under $100k, I'd guess it won't be 5 years before there are only 1% of those truckers still getting paid. That's a lot of decently paid people who mostly don't have other skills that can offer a similar income. They (and their families) will not be happy and their response is TBD, but I can't imagine it will be pleasant.

Automation isn't a bad thing. And gaining efficiencies isn't bad either. Men can dig holes with shovels and take hundreds of hours, or a single man can dig a hole with a backhoe and take a half a day.

This is fine for stores to do it to unsold products. But as others have noted, I don't like ANYONE to have the ability to remotely power on my device and push software to it without any interaction or alerts. It can't be categorized as anything other than a security risk.

What law says brake job recalls give liability and paint job recalls don't? It makes sense, but there isn't a 100% distinction around it, hence it can be fuzzy. The fact that you provided 2 scenerios that could go either way show it can be a judgement call. And its dangerous to presume everyone else believes your judgement to always be perfect.

Most people have wised up and determined that moving to the cloud can be a one way street unless you are ready to potentially spend millions of $$ to get your data back when you decide to move to a "new" solution. And anyone who has been in corporate IT for 10+ years can attest that they like to retool periodically and the inability to move data to the new tool can be a non-starter. Vendors love lock-in, but most corporations won't pick a solution they can't back out of after learning that the hard way a time or two.

"The laws must be absolutely cut n dry super clear"

Are they now? If you drive a recalled car that you know there is a recall, who is liable? What if you are driving it to the dealer to have the issue corrected? There is and always will be fuzzy components legally when operating a vehicle.

Bugs in software seem like they would have the same liability as bad welds on a frame that could cause a car to break apart and bad things happen. Both seem to be "factory" issues and not the driver/owner's responsibility, as long as they haven't been notified by a recall or have knowledge the vehicle is dangerously defective.

No matter what though, if either of the above failed and caused your vehicle to run over a 3 year old girl playing on the sidewalk, EVERYONE associated who has any assets are going to be sued.