241–250 of 327 posts
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…
Earlier quoted context omitted.
Domain squatting is like a disease, but how would you regulate it? Where is the line between just a parked domain that a lot of tech (and non-tech) people reserve for their future projects, and a domain acquired for re-sale? Given a good offer you would probably sell one of the domains you own just as well, wouldn't you?
A fairly simple approach for all is to up the price based on contention. Regularly auction out the lease f.ex Allowing “ownership” of such resources just leads to rent-seeking.
Why should he have more right to it, or my renewal costs go to $100/yr? I could afford that now, since I'm a software engineer, but when I was a broke teenager?
This type of behavior exists for many of the new TLDs and for a lot of the blockchain proposals and is one of my big reasons for avoiding both.
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…
Earlier quoted context omitted.
God, IPv6 got the shaft hard. People complain that it's too complex and that it solves too many problems at once, but that's because they've become used to the ancient stack of random protocols that make IPv4 work. There are also a lot of people who have it out for IPv6 because their ISPs aren't handing out static addresses, somehow equating IPv6's problems with the shittiness of their ISP. It's not widely implemente…
> There are also a lot of people who have it out for IPv6 because their ISPs aren't handing out static addresses, somehow equating IPv6's problems with the shittiness of their ISP. My ISP isn't handing out static IPv4 nor IPv6. However IPv4 works just fine while for IPv6 it's a giant pain. The world isn't static though, so maybe IPv6 is the problem here? Or do you seriously suggest I should manually change all my dev…
Causing a conflict in your LAN with address is a problem of IPv4 and the tiny address space it has. It forces you to keep a tight administration and use a bolt on address space management technology like DHCP. IPv6 does not have that problem and you'll have a service less to run.
Indeed, it's not trivial. Many parties will have to do something. I hope they'll get more motivated as the price for IPv4 addresses rises even further. When CGNAT solutions get starved of socket space and adding extra IPv4 addresses gets prohibitively expensive maybe IPv4 will get so slow and unreliable people will give up on it.
The graph of IPv4 address space pricing gives some hope: https://postimg.cc/QKKx847B
Earlier quoted context omitted.
There are efforts in those directions: https://delta.chat/en/ implements encrypted IM over email. https://jmap.io/spec-calendars.html is the calendaring spec for IMAP's likely successor https://webfinger.net/ is the (appallingly named) http protocol for finding named people such that social connections can be made and managed. Some extensions exist for services that commonly run with email that provide webfinger serv…
Delta chat look very interesting, thanks for mentioning it. What are the possible downsides? Looks like a winning tech to my non-tech eyes.
By making it truly decentralized: Like in a mesh network.
then who'd own the cables and satellites?
This make the internet grid a true free market that anyone can participate in.
No remote code execution is allowed on the web. You can download binaries and run them, but not in the browser's context.
So instead of running code in the browser's sandbox, you have to run it at user level? Sounds terrible and this is what things where like in the 90s. Say you wanted to do some banking, you would have to download and install the bank's application, which usually only ran on Windows. No thanks.
Earlier quoted context omitted.
> There are also a lot of people who have it out for IPv6 because their ISPs aren't handing out static addresses, somehow equating IPv6's problems with the shittiness of their ISP. My ISP isn't handing out static IPv4 nor IPv6. However IPv4 works just fine while for IPv6 it's a giant pain. The world isn't static though, so maybe IPv6 is the problem here? Or do you seriously suggest I should manually change all my dev…
Why would you care what address your PC is using ? If your ISP gives you an other IPv6 assignment your router should just advertise that and your PC will use it. You wouldn't even notice. If your router doesn't do that is has a bad IPv6 implementation. The protocol itself is perfectly fine for that. That is one of the big stumbling blocks for IPv6: bad implementations in networking equipment. Causing a conflict in yo…
That's my point. I don't really care. Yet for IPv6 I suddenly need some way to automatically update the firewall rules etc, because the internal IP is also the public IP.
> IPv6 does not have that problem and you'll have a service less to run.
But how do you distribute DNS and NTP server addresses without something ala DHCP?
Earlier quoted context omitted.
how is ipv6 more complicated then ipv4? the friction comes from having to manage two different network stacks at once, not the so called complexity of ipv6. ipv4 is a mess in many ways, ARP for instance, is a disaster once you reach a certain scale and many of the ipv4 header fields are unneeded leading to inefficiencies. multicast on ipv4 is a mess, rfc1918 is a neat idea but ipv6 fixes it in a far better way and ge…
Most people don't care about ipv4 problems, it works. Does ipv6 solves ipv4 problems such as impossibility to extend it in backwards compatible way? Say, I want 256 bit address space... can IPv6 be extended in that way?
Also, forward-compatible address extension is something which is simply not possible with routing protocols in place today, and i highly doubt it will be a possibility in the near or far future considering the enroumous coordination effort required between Core players on the Default-free zone and internet at large.
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.