IDs are insecure, local, and labor-intensive. Nakamoto consensus is secure, global, and automated.
-
-
@NickSzabo4@iang_fc@timpastoor@marttimalmi hashcash was also conscious rejection of ID assuming ID leads to garbage in garbage out design -
.
@NickSzabo4@iang_fc@timpastoor@marttimalmi idea that sysadmins operating identd & smtp checking identd would be useful in stopping spam. -
.
@NickSzabo4@iang_fc@timpastoor@marttimalmi flawed thinking. identd unsecurable & broken architecture. building anti-spam on it is GIGO. -
.
@NickSzabo4@iang_fc@timpastoor@marttimalmi so hashcash was an attempt at solution to spam, at least had a logical non-ID threat-model. -
@adam3us@NickSzabo4@iang_fc@marttimalmi I didn't mean IDENT, nor identd. I was referencing to "Identifi" and its one-way trust model. -
@timpastoor@adam3us@NickSzabo4@marttimalmi There are multiple senses of ID in this conversation ... -
@iang_fc@adam3us@NickSzabo4@marttimalmi Do same principles apply though? When it comes to preventing Sybil nodes from harming honest ones -
@timpastoor@adam3us@NickSzabo4@marttimalmi my risk-analysis question: when you have attacker's ID, does it make you whole? recourse? - 5 more replies
New conversation -
-
-
@NickSzabo4@iang_fc@marttimalmi Obssesed with IDs because IDs & reputation go hand-in-hand. Reputational incentive == economical incentiveThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.