TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: Dat-keyserver: a distributed PGP keyserver based on the Dat protocol

106 pointsby tdjsnellingover 5 years ago

4 comments

jnbicheover 5 years ago
I like the ability to remove keys. I understand the theoretical reason for append-only keyservers, but in practice it just turns people off from using them. No one wants to look at their entries from 2005 from when they screwed up while learning about subkeys, or their defunct 2008 entry which they never could revoke because they lost the revocation certificate (all examples purely fictional).<p>In any case, a keyservers job is not even to be some kind of source of trust, so all that really should matter is that it has a user&#x27;s most up-to-date keys on it. Validating a key should come from web-of-trust or some secure second channel verification method (like listing your key ID on a TLS-enabled website).
评论 #20812596 未加载
评论 #20813968 未加载
progvalover 5 years ago
I&#x27;m not fluent in modern JS, but I think the level of callbacks nesting makes it hard to see what else&#x2F;catch belong to what if&#x2F;then, especially: <a href="https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;blob&#x2F;12fa3e8389a6f90d312e1e664006df4d8391ecd5&#x2F;index.js#L288-L369" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;blob&#x2F;12fa3e8389...</a><p>You could try splitting this big function into smaller functions to reduce the length of the code largest callbacks.<p>It also makes commits harder to read. eg. for <a href="https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;commit&#x2F;12fa3e8389a6f90d312e1e664006df4d8391ecd5" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;commit&#x2F;12fa3e83...</a> a reader can&#x27;t see easily what changed in the function, as every line&#x27;s indentation was changed. (And the commit message does not explain what the bug was)
评论 #20814922 未加载
评论 #20813445 未加载
评论 #20813336 未加载
评论 #20815776 未加载
fwipover 5 years ago
I&#x27;m concerned about the key-removal functionality. The website (<a href="https:&#x2F;&#x2F;keys.tdjs.tech" rel="nofollow">https:&#x2F;&#x2F;keys.tdjs.tech</a>) reads: &quot;Enter a message clearsigned with the key you wish to remove (message content is not important)&quot;<p>My understanding of this is that anyone with a copy of anything you&#x27;ve ever signed can revoke your key. I hope I&#x27;m misunderstanding.
评论 #20813199 未加载
评论 #20812920 未加载
Leaceover 5 years ago
Project looks definitely interesting. Too bad the code looks like callback-hell from 10 years ago: <a href="https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;commit&#x2F;12fa3e8389a6f90d312e1e664006df4d8391ecd5" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;tdjsnelling&#x2F;dat-keyserver&#x2F;commit&#x2F;12fa3e83...</a><p>Still, an interesting alternative for people who consider <a href="https:&#x2F;&#x2F;keys.openpgp.org" rel="nofollow">https:&#x2F;&#x2F;keys.openpgp.org</a> too radical.
评论 #20812722 未加载