logoalt Hacker News

inigyouyesterday at 1:11 PM1 replyview on HN

We have that, it's called an <a> tag.


Replies

__MatrixMan__yesterday at 2:09 PM

Its not stored separately, so:

1. You need write access to the server if you want to add one

2. The server could change its behavior at any time and there's no way to know that caches now need to be invalidated

3. If something goes wrong with connectivity or name resolution, there's no fallback since the authoritative thing was not something durable like a trusted human via a public key but rather an ephemeral thing: a named server which has pinkey promised to stay online.

It asks the user to treat a server like a trustworthy source of perisisant data.

But there's no reason to couple these kinds of trust. The skills necessary to persist and traffick data are orthogonal to being trustworthy about content. Coupling them creates needless load on single sources of failure which are simultaneously single points for corruption to target.

Trust people, not servers. Use digital signatures to validate that what you're seeing came from those people.

<a> tags are the opposite of this. They encourage us to trust servers by name, which isn't really working out.