Live data from Hacker News

Ask HN: If the Internet were redesigned today, what changes would you make?

news.ycombinator.com

131–140 of 327 posts

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#131

Earlier quoted context omitted.

“ But this was only possible due to the history of Harvard within the advent of the internet and the fact that they had such an excess of addresses that Zuck could bind to a public IP address.” This sounds interesting. Can you ELI5?

This is an example of how the internet was originally intended: Every user of the internet has a public address that any other user can send and receive messages from. The design works just like postal addressing. Your postal address contains the directions to your building from any location on earth. Even if you live in a dormitory building with many other residents, I can still send you a letter directly by adding…

> IPv6 reintroduces equity to the internet that facebook benefited from in it's inception

Except for the fact nobody can type, much less remember any IPv6 address.

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#132
I would wish there was something better for SMTP.

I tried to learn it a while ago and got super frustrated with how things are. The whole thing looked upside-down to me.

I mean The DKIM, SPF, DMARC, Bayesian filtering, etc sound like band-aids upon band-aids to fix something that's really broken inside.

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#133
post #131

Earlier quoted context omitted.

This is an example of how the internet was originally intended: Every user of the internet has a public address that any other user can send and receive messages from. The design works just like postal addressing. Your postal address contains the directions to your building from any location on earth. Even if you live in a dormitory building with many other residents, I can still send you a letter directly by adding…

> IPv6 reintroduces equity to the internet that facebook benefited from in it's inception Except for the fact nobody can type, much less remember any IPv6 address.

This is true, which is why I expect mDNS and DNS to become standard even for local addresses.

I'm looking forward to using `router.local` over `192.168.1.254`.

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#134

IPv6 dates back to 1997 and it really should have been adopted more urgently. IPv4 isn’t a huge issue but it sucks that so much of the internet is dependent on cloud providers because it’s the simplest way to get a public IP address. The decentralized web didn’t happen, in part, because of this. Facebook was famously started and hosted in a dorm room. But this was only possible due to the history of Harvard within th…

> Facebook was famously started and hosted in a dorm room. But this was only possible due to the history of Harvard within the advent of the internet and the fact that they had such an excess of addresses that Zuck could bind to a public IP address.

I'm fairly certain the version of Facebook that was hosted from Zuckerberg's dorm room was just for Harvard students, and wasn't accessible from outside the campus network. Keep in mind that early FB was rolled out to only select universities on a campus-by-campus basis over the course of a year or two; it wasn't like it was today. Part of the whole appeal of FB early on was its exclusivity.

There were and are lots of places with routable IPv4 addresses that still have various kinds of traffic management and firewalling. My uni handed out real IPv4 addresses in the early 2000s (may still today!), but absolutely didn't allow inbound connections from anywhere outside of the campus network, at least not on well-known ports. You could (and lots of people did) run a server, SMB or AppleTalk file share (so much porn...), etc., but it wasn't accessible to the entire Internet. (Hotline and Carracho servers, OTOH...) I would be absolutely astounded if Harvard didn't have some inbound filtering on its network at the time; keep in mind this was 2004: peak Windows XP era... students would have been getting hacked left and right if they hadn't.

There are still some big companies around with very large IPv4 allocations for historic reasons (HP has at least two /8s I believe, its own original one plus one acquired from DEC; IBM has at least one; Apple has one, etc.) and some of them use routable addresses internally. I know IBM did this in its major offices in the mid to late 2000s. But you couldn't just spin up a server at your desk and hit it from home without going through IT and having them put in a firewall rule for you. This was all pretty standard network security stuff at that point.

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#136
post #128

The "browser" is a blank execution sandbox with a rendering context. The remote server sends programs (using something like WASM) with a standardized ABI. The program can use the rendering context to put stuff on the screen or receive user input. Indexing and page interoperability is done by exposing standard functions which yield the necessary metadata. For example, if you want your site to be indexable by a search…

We already have that. It’s called Java

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#137
post #128

The "browser" is a blank execution sandbox with a rendering context. The remote server sends programs (using something like WASM) with a standardized ABI. The program can use the rendering context to put stuff on the screen or receive user input. Indexing and page interoperability is done by exposing standard functions which yield the necessary metadata. For example, if you want your site to be indexable by a search…

Maybe this could be approached by compiling the servo browser engine to wasm...

Re: Ask HN: If the Internet were redesigned today, what changes would you make?

#140

Get rid of most of JS to prevent 'appification' and keep the focus document centered. Edit: I think this would result in protocols over walled gardens. The problem is JS makes HTTP/HTML everything to everyone.

> I think this would result in protocols over walled gardens.

I don't see how it would. I think it would have led to something equivalent to JavaScript, because that's exactly the route we took to get to here. The WWW started as just documents, and there were plenty of protocols for other internet things. Businesses and consumers (and almost everyone else) want more than documents, and avoiding requiring people to install and run a separate client for every purpose (and requiring developers to build said cross-platform clients) led to plug-ins and then capable JavaScript.

Post reply on HN