serapath【ツ】☮

i dont see what that paper has to do woth my expressed thoughts. some think first and do later. some do first and think later. over time both are a cyclic execution model. The problem i tried to point at is when somebody does use: act first, think later, to introduce urgency and push towards artificial complications ON PURPOSE, because it leads to complicated systems which require centralized management to coordinate ppl to keep it working. This is a deliberate attack to capture an organization.

i dont see any connection between your shared article and what i said before you posted it. And my feedback was mainly about the article being lots of words about everything that we can all agree on, but they dont really help. Imhonunclear what you want to say by posting it.

you used time to propose USRF - but have you considered proposing an upgrade to BIP110 that mitigates the issue?

try https://keet.io instead

a large DHT without eclipse attack protection can be worse than a smaller DHT with eclipse atrqck protection. Wthout an attacker can occupy a specific area of the DHT with relatively few sock puppet nodes. With the protection the cant attack specific areas and need to just spam the entire DHT nodes to eventually attack the DHT keys they are interested in. Also, if every DHT node supported holepunching and assisted new nodes with holepunching as well, things become a lot more useful. The sybill attack mitigation and the assisted distributed holepunching is both supported by hyperdht which the pear and bare runtime use. Would be cool to bundle it with a nostr node. If all nostr nodes supported it, it would improve the resistance against the sybil attacks by an order of magnitude more than with other DHTs like bittorrent mainline

hyperdht is smaller and additional benefits 1. used by keet and pear runtime 2. protects against eclipse attack 3. has best in industry holepunching built in pear runtime as dat started out with bittorrent mainline dht too, but moved on because of issues related to holepunching and eclipse attacks that cant be fixed in bittorrent mainline, because it wpuld be a breaking change and bittorrent mainline is too widely distributed. the scale of mainline is much less helpful when it cokes to eclipse attacks and smaller size is sometimes as secure because of the additional sybil eclipse attack protection. anyway - would recommend to talk to the pear runtime team at holepunch. hyperdht is the most advanced and modern dht i am aware of and would definitely recommend 🙂