I don’t know how it would be implemented but I always thought it would have been better if there was more meaningful separation of domains, and that you need a different browser to connect to a different domain. That way the net could be divided. There could be a domain for only verified information. A domain for public use. A domain for only educational content, etc. I have no idea how it would be moderated though
Such a categorisation already existsed in the form of the original top-level domain names, but it was never enforced. .gov for government, .mil for military, .com for commercial, .edu for educational facilities, etc. For good reason, though. Who says what information is "verified", the government, the news media, the publishers? And what governments, media, and publishers get a say? Perhaps it'd be nice for browsers…
Ask HN: You have one shot to redesign the Internet – what do you change?
51–60 of 322 posts
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#52What a great question. One of two things: A) Establish the expectation that websites "close" in the middle of the night for ~5-6 hours, local time / for each timezone. I don't know if would best be done via cultural influence -- giving talks, writing essays, personal communication, testifying / making inroads with politicians -- or via creating some sort of protocol. The idea is to prevent the unhealthier aspects of…
You can read a bit about how it works in practice on the web.
https://www.huffpost.com/entry/ultraorthodox-jews-are-co_b_1...
http://www.hareidi.org/en/index.php/Hareidi.org%27s_Kosher_I...
Background: https://www.journals.uchicago.edu/doi/pdfplus/10.14318/hau7....
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#53Find a way to better decentralize it, so that it doesn't rely on single hosts(and later sites) as the source of truth for any particular function. The original idea was that protocols would allow any one to participate by simply making their own webpage. But dynamic IP addresses, the DNS system, and even just HTML design were out of reach for most people so that got lost and monsterous websites under centralized cont…
Now, it could've been done in a better fashion, more deliberately, or more broadly, but there are at least two notable early protocols with decentralization/distribution in mind: email (consisting of several protocols) and nntp. Now an individual may still access a, to them, centralized authority for sending/receiving content, but the protocols themselves were meant to support a distributed architecture.
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#54Honestly most of it is pretty great. Folks who want to give it better, more reliable performance end up reinventing circuit switching, and anything involving security is difficult to solve at the IP layer. The last big things to secure are DNS (can be done with DNSSEC), and possibly somehow mandate TLS for connections (although you definitely don't want that all the time). One big glaring problem is BGP, which we don…
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#55Consequences:
* There is no live user tracking.
* Access control can be user/password or ssh keys
* You always have an archive of what you read
* You always have an archive of chats
* Everything is in principle decentralized (whether it is in practice depends on whether people keep files.
* Clients are in control.
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#56I'd advocate to build DARPANET for an untrusted environment with the expectation that DARPANET would be unleashed on the masses at some later point.
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#57What a great question. One of two things: A) Establish the expectation that websites "close" in the middle of the night for ~5-6 hours, local time / for each timezone. I don't know if would best be done via cultural influence -- giving talks, writing essays, personal communication, testifying / making inroads with politicians -- or via creating some sort of protocol. The idea is to prevent the unhealthier aspects of…
Regarding the second point, it would probably just make people say things like "you sound fat". It's still anonymous enough. In fact, people say mean things in public all the time. It seems some people are just inherently mean.
I see this is as a problem of the medium of discussion more than anything else.
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#58Oh, something minor. I’d make both domains and paths go from least significant to most significant, so com.google.mail/u/0/html
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#59Earlier quoted context omitted.
Good question. Ideally, each user's timezone would be required information. The server would check to see if the requesting user's local time meant that the website should be "open" for them.
Honestly this would probably just make VPN services more widely used to workaround shutdowns.
Re: Ask HN: You have one shot to redesign the Internet – what do you change?
#60TL;DR: Constants shouldn't be hard coded in the software, they should always be in a separate config The problem is that it's the 60s. My first thought was "security", but unless you an also teach them about elliptic curves, they're going to use the security of the 1960s, which as we now know isn't very secure. Maybe at least having security baked in would help make it easier to switch to better security later, like…
I really don't understand what stopped ipv4 from being extended like this: w.x.y.z == 0.0.0.0.w.x.y.z In fact, you can even ping any 32 bit unsigned integer and it will turn it into an ipv4. Try it: `ping 134744072` will ping `8.8.8.8` So why not 64 bit? 32 bits fit in 64. Instead we now have 2 concurrent protocols. ps. 8*256^3 + 8*256^2 + 8*256 + 8 = 134744072
The address is not the real issue. An IPv4 header contains 32 bits for the source address and 32 bits for the destination address. That's what needed to be extended. IPv4 implementations expect the destination address to be 32 bits after the source address.
Any fix you can think of to extend the address fields in the header will fall into the situation of having an additional protocol. Because changing the v4 header and calling it a v4 header would probably get your packet dropped as bad. Or have it being sent to somewhere else. Or some other undefined behavior.
So your best option is to have it identify as a new version. Yes, v4 implementations will reject your packet, but that's what you want in this case.