Nostr Web Client

Honestly, neither is Nostr. I've had discussions here about this topic here with AJ and Matt, neither of which were very productive because short text blocks aren't exactly conducive to honest discussion. Pride and wrath are much easier to express and harder to bypass in this format.

In other words, it's not teh botses.

nostr:nevent1qvzqqqqqqypzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qqs8nhaalvfdzafjplkc7sha43kwv68pfyj7q66xu0j4dlqhv5l84vcp2szfg

mac 3mo ago 💬 1

I’m coming at this with honest questions…I’m not going to pretend I know which implementation is “better.” I want to run a node, but honestly, the political tribalism around Core vs. Knots is discouraging. It feels like the same kind of division Bitcoin was supposed to help us move beyond.

1. What specific issues with Core v29 motivated the push for v30?

2. Is it realistic or even productive to consider rolling back to v29 as a clean slate for developer discussions?

3. I guess depending on the answer to #1 is it safe to just to run v29?

Reply to this note

Please Login to reply.

Discussion

Geek 3mo ago 💬 1

Running 29 will continue to work until there is some issue identified and fixed in a later version.

Running 30 you lose the ability to filter OP_RETURN > 80 bytes.

Running knots you get all the fixes applied to 30 and later plus you retain the ability to filter OP_RETURN size. But you can also turn that off if you want.

To me knots gives me the most options. 30 removes an option that I wish to exercise. So for me, it's knots.

monarx 3mo ago

What this guy said