kikoreis

Usually with these things people pursue a quasi impossible vision that ends up generating useful technological advances along the way. The funding will come from an ultra high risk R&D grade allocation and there will be someone in the supply chain that will benefit regardless of the final outcome. If you look at it from that angle then it is less surprising people around the planet will give it a go. Plus the mockup pictures look cool so free marketing and shocking headlines.

Space is pretty big. Where would you propose putting them and what will you do when a switch port fails?

This is an idea that is getting a lot of airtime but not sure if anyone practical minded thinks it is viable in the next 15 years.

Wow, that is one badass move! Possibly the last time something like this can be attempted before bet money is so ingrained into power it's a non starter.

I was just starting to get bored going into October. It's going to be enlightening to see society now grind it out to decide whether it really wants to get rid of the industry.

"Nothing" is not accurate in the context of Debian as per comments above; it's not like Github in that sense.

Yeah.

And there is also the group of parents that at the moment have decided no device is safe enough to be given to a child or adolescent.

They are a good litmus test of the bill; would they be happy to provide devices if there was age verification built in?

I am in this group and I wouldn't.

Do you have children? Have you witnessed what they can do with restricted $300-2000 devices? My kids hack restaurant tablets at every place we go. I don't even know how they do it most of the time.

This is going to be one hell of a slippery slope. And the actual publisher-driven proposal in this thread is so much more useful; I would love to filter out anything with excess violence and generally NSFW content from my view of the Internet -- and I am over 18.

It's not completely wrong, but overly simplistic:

> In 2006, Amazon launched what is now AWS, exposing the internal compute, storage, and database services its retail group had built. The internal pitch was identical to Marketplace seven years earlier.

These were not internal services, and it wasn't exactly the retail group that built them (Chris and Ben were dedicated to EC2 and the team ran remote from Seattle). Nor was Marketplace run on the 1P Amazon platform, so it would have been a strange analogy to use for a pitch.

In the end, though, the point is the same as I made elsewhere in the thread — once you are big enough you can try and bootstrap pretty much anything adjacent to your business and have a good shot at success.

This read was mildly interesting, but I'm left thinking that the study of any sprawling monopoly will come up with similar mildly interesting and irrelevant rationalizations of success. Once you get as as big as Amazon was in the early 2010s, provided your culture doesn't melt down (by itself no small feat), you are well positioned to expand and flatten adjacent parts of the economy.

So the question is whether you read this to be inspired by it and attempt to create your own monopoly, or to be afraid of it and start thinking about regulation. Or both :-)

Oh this almost makes me want to go back and consider NFS for our local lab. I used to run it but everywhere having a centralized SPOF was a constant concern, and there isn't a simple HA story for it sadly.

As a user for over a decade, just here to submit my appreciation. healthchecks.io is fantastic.