I just manually 1-year banned a Core v30 node that I happened to notice was connected to my nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshsqgygaer47rtnxz288s9j7l4s5vps94k5nyz50kgx5mmq7cslury7x5z5v9a4 node (just to test the feature out on a node that I didn't particularly care for trading data with) & it got me thinking... 🤔

...What is stopping nostr:nprofile1qyxhwumn8ghj7cnjvghxjme0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcqyr7at68k4cxms9a7pdca5gzf3svqd95d3fj9j4vuyj0nyta8x3j2whad7ya, nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqwnlu28xrq9gv77dkevck6ws4euej4v568rlvn66gf2c428tdrptqcjfkft & other Knots devs from implementing a feature for Knots to auto-disconnect & auto-ban any discovered nodes that broadcast a version that the node runner doesn't approve of? 🤷‍♂️

If it was off by default & you allowed node runners to select which node versions they approved/disapproved of & the duration of ban desired, wouldn't that be the ultimate freedom for node runners to exercise their agency? It would also be a natural mechanism for consensus & broadcast depth. 💁‍♂️

Just a thought. 🤙

Reply to this note

Please Login to reply.

Discussion

No replies yet.