Live data from Hacker News

Show HN: DNS over Wikipedia

github.com

81–90 of 109 posts

Re: Show HN: DNS over Wikipedia

#81
post #65

DNS translates a name into an IP address. This is not DNS per-se, it is just a search plugin for the url bar. If an analogy was needed with a network service perhaps this is more like a proxy redirector than DNS. Keep in mind: with this you will still be misdirected if your DNS/hosts file is pointing the name into a different IP than it should be.

Indeed. Even the GitHub repositories description has this error. > Resolve DNS queries using the official link found on a topic's Wikipedia page @aaronjanse: you probably want to correct this. "Resolving DNS records" carry a specific meaning in that you have a DNS record and you "resolve" it to a value, which actually. You're kind of doing, in a way, I suppose. I was convinced when I started writing this comment that…

I mean once we account for all the different types of DNS records - regardless of its original intent, isn't it essentially just a networked, hierarchical key store? For example the TXT field is "dns".

This project is still doing key -> value. It just fetches the value from Wikipedia first, much like your normal dns servers have to fetch non-cached keys from their sources (other dns servers normally)?

Re: Show HN: DNS over Wikipedia

#82
post #61
post #18

Pretty neat! Similarly, I often use Wikipedia to find translations for specific technical terms that aren't in bilingual dictionaries or Google Translate. If you go to a wiki page about a term, there are usually many links on the sidebar to versions in other languages, which are usually titled with the canonical term in that language.

Dict.cc is excellent for that, if you're translating between German and English. Linguee can also be really good.

Similarly, jisho.org for English Japanese often has search results from Wikipedia too.

Re: Show HN: DNS over Wikipedia

#83

Earlier quoted context omitted.

Indeed. Even the GitHub repositories description has this error. > Resolve DNS queries using the official link found on a topic's Wikipedia page @aaronjanse: you probably want to correct this. "Resolving DNS records" carry a specific meaning in that you have a DNS record and you "resolve" it to a value, which actually. You're kind of doing, in a way, I suppose. I was convinced when I started writing this comment that…

I mean once we account for all the different types of DNS records - regardless of its original intent, isn't it essentially just a networked, hierarchical key store? For example the TXT field is "dns". This project is still doing key -> value. It just fetches the value from Wikipedia first, much like your normal dns servers have to fetch non-cached keys from their sources (other dns servers normally)?

Yeah, agree! I'd take it a step further and say it doesn't even have to be "networked" (in the technical sense) but could be local or even done person-to-person, which would also work albeit be slow.

Let's call that sneaksolving (from the infamous sneakernet/FloppyNet)

Re: Show HN: DNS over Wikipedia

#84
post #6

Earlier quoted context omitted.

I think it directs to the correct link when it is labeled `URL` in wiki. In the other cases the link is labeled `Website`.

This was exactly the issue! I just pushed fixes for this problem.

I've written a userscript[0] before regarding official websites and I feel this is the hierarchy you should be using:

1. Try getting the Wikidata "official website" property

2. Then any link inside of a {{url}} template or |website= in an infobox

3. And if you really want to try to get something to resolve to, the first site wrapped in {{official website}}

If you need code to reference: https://en.wikipedia.org/wiki/User:Opencooper/domainRedirect...

[0]: https://en.wikipedia.org/wiki/User:Opencooper/domainRedirect

Re: Show HN: DNS over Wikipedia

#85

Earlier quoted context omitted.

Whats funny and ironic is that this actually makes finding pirated content much easier since only actual sites that contain pirated content are the ones that will be listed on DMCA complaint list

Yes I wonder if these URLs have to be made public by law in DMCA notices. I assume that, if they legally could, they wouldn't show you anything

The notices don't have to be disclosed to anyone but the alleged infringer. The URLs don't have to be hyperlinked either. This is one part of Google giving the trolls a middle finger.

Re: Show HN: DNS over Wikipedia

#87
This may be a little off topic, but has anyone ever considered a web standard that includes a cryptographic signed file in a standard "well known" location that would contain content such as

- Domains used by the site (first party)

- Domains used by the site (third party)

- Methods allowed per domain.

- CDN's used by the site

- A records and their current IP addresses

- Reporting URL for errors

Then include the public keys for that payload in DNS and in the APEX of the domain? Perhaps a browser add-on could verify the content and report errors back to a standard reporting URL with some technical data that would show which ISP is potentially being tampered with? Does something like this already exist beyond DANE? Similar to HSTS maybe the browser could cache some of this info and show diffs in the report? Maybe the crypto keys learned for a domain could also be cached and warn the user if something has changed (show diff and option to report)? Maybe more complex would be a system that allows a consensus aggregation of data to be ingested by users so they may start off in a hostile network and some trusted domains populated by the browser in advance, also similar to HSTS?

Re: Show HN: DNS over Wikipedia

#89
> Wikipedia keeps track of official URLs for popular websites

This should be Wikidata. Wikipedia does that, but this is more and more moved into Wikidata. This is a good thing, because Wikidata is much easier to query, and the official website of an entity is stored at a single place, that is then reused by all articles about that entity in all languages.

Re: Show HN: DNS over Wikipedia

#90
post #68

There's a risk of phishing by editing Wikipedia articles if the plugin gets popular. Perhaps it's useful to crosscheck the current URL against the 24-hour earlier and 48-hour earlier versions of the same article. Crosscheck back in time, not back in revision, since one can spam the history by making a lot of edits.

I believe the German version of Wikipedia had(has?) a feature where you only get verified versions of a page when you browse it anonymously.

> I believe the German version of Wikipedia had(has?) a feature where you only get verified versions of a page when you browse it anonymously.

What’s a “verified version”? Who verifies?

Post reply on HN