Can't wait to walk Grandma through this on the phone when she buys a Firefox-enabled lightbulb.

The only way I see to do it the "right way" for the masses is to have the lightbulb phone-home to the manufacturer. It's a little silly, but an IoT lightbulb is silly in the first place.

Ah the fridge as a service model. Instead of buying something that just works for decades you now get to pay service fees to keep some remote server online. Oh wait the company just went under and nobody can host trusted replacement servers, guess I need a new fridge.

Right, any software that's hooked up to the internet needs to be updated over time to stay secure, therefore needing to pay for a service or having it go insecure in 2 years.

Grandma should not be installing her own network, no normal person should.

Do you also expect a regular end-user to install their own electrical outlets ?

Accessing a network-connected TV or other home gadget is also "using a local server", do you really suggest people should not do this without a networking professional? That's just not going to happen.

Of course that's going to happen. It's just too dangerous to let someone without the right qualifications do it. I expect it to become a legal requirement to have a licensed technician install networks just like it is with electricity or gas.

The internet is just too important to leave to amateurs, look at how much damage badly configured home networks and computers are causing already. This stuff needs to be secured properly.

You also didn't need a drivers license when cars just became available, but now there are shitloads of cars we have to make sure drivers are capable before letting them drive. Same goes for network-connected equipment.

Also, being part of a botnet should directly impact your internet bill. I don't really see another option. It's a bit silly that nobody knows when their devices are saturating their bandwidth 24/7 because they are compromised.

That way people are then motivated to hire a professional. Also, people making devices will be motivated to not use a default "admin" password because customers will start saying "uh, this smart toaster cost me hundreds of dollars when I plugged it in."

Most home broadband users don't have domains and would be unlikely to want to pay for one, just to remote login to their router.

Let's Encrypt supports wildcard certificates (since a couple of days ago), you could automate it.

Automate what exactly? the point is most home users access their router with 192.168.0.1, they don't have a domain name, nor are they likely to want to buy one. This is now no longer a niche thing that a few people want to do, it's a 100s millions (if not a billion) of households needing to do this to access their own router, so it doesn't say "not secure".

Every internet-connected device should have a FQDN, that's just common sense.

Should? Yes. I can get on board with this.

A ridiculous proposition given the current state of technology? Also yes.

If it happens, implemented in turnkey devices (such as SOHO routers) in a way that enhances vendor control rather than empowering home users with the option to use their own domain names and certs? Likely, that's the trend these days and doesn't show signs of receding.

The last line is kinda a tangent, but if that came to be the case, I would no longer be on board with the idea every device should have a FQDN.

Source? Their blog post had mentioned 27th Feb as the date for wildcard support in production.