3 ms·
I don't get it. You have to host the static page somewhere. Why not host the data in the same place (as a json blob or whatever)? It seems like the implication
by bawolff 5y ago
I don't get it.
You have to host the static page somewhere. Why not host the data in the same place (as a json blob or whatever)? It seems like the implication is all the data in dns is static, so what's the benefit of adding dns to the mix - you already have to use something else to host some of your static resources, why not just have a single static host instead of two separate static hosting systems?
(Yes in theory you could write a dns server to dynamically answer queries, but that doesn't seem like its what is being proposed here)
Dont get me wrong, its cool you can access dns from a browser, but i dont think this is a compelling usecase (something like web torrent in the browser with magnet links in dns for a decentralized web, seems like it would make a good demo for this technique)
- elliottinvent 5y agoWhat we're trying to do here is standardise how machine-readable data is stored and retrieved, primarily for companies. Any of the companies on this page can adopt the standard and override the data on the website. So the point is, it's not static. Sure, at the moment all this data is coming from one DNS zone (num.net) but that's only a failover query location, first we query e.g. barclays.co.uk for this data, so Barclays can override (or remove) this data if they want to.
- bawolff 5y agoSo the interesting part here is not supposed to be querying dns data from the client side of a website, but a new standard for machine readable data in TXT records? I mean between microdata, rdf, etc there's been a lot of standards for machine readable data storage on the internet. Most fail not for technical reasons, but because there is an incentive mismatch, where the people who have to maintain such data get no benefit out of maintaining it so they don't bother. In this scheme you can't even google it, so why would a company bother to use this?
- elliottinvent 5y ago> So the interesting part here is not supposed to be querying dns data from the client side of a website, but a new standard for machine readable data in TXT records? Correct > I mean between microdata, rdf, etc there's been a lot of standards for machine readable data storage on the internet. Most fail not for technical reasons, but because there is an incentive mismatch, where the people who have to maintain such data get no benefit out of maintaining it so they don't bother. I'd argue the inconsistent way these standards have been adopted (or not in many cases) is the reason they are not an effective, reliable way for developers to find machine-readable data about _any_ business. Since they are not a reliable way to find data, developers can't build anything with that data and there's little incentive for companies to keep it up to date. Currently, the only reason to adopt these standards is for SEO or to make your website look pretty when you share your website on Facebook / whatever. > In this scheme you can't even google it, so why would a company bother to use this? Google hold a lot of the data we're proposing to publish using NUM (contact data for example). The difference between our approaches is that we're going to make it freely available to developers, Google don't (not really). Google could consume NUM data like anyone else. As far as the protocol is concerned Google is the same as any other developer so it's a level playing field.
- detaro 5y agoAnd now you are adding another standard that will be inconsistently adopted, especially since it's even less accessible to web developers than the alternatives?
- elliottinvent 5y agoWe're pre-populating NUM with useful data, so it doesn't require domain registrants to adopt it. NUM modules are much simpler than other comparable web standards so any data stored will be consistent and easy for developers that consume the data. Edit: typo