pull down to refresh

16 sats \ 6 replies \ @ek 6h \ on: Knots stop workin after two yr if you don't udate bitcoin
Nice find, but I think it's not as bad as it looks.
It doesn't "stop working" if it's already running, it will only not start again if you don't do what the message tells you.
I think the message makes sense. Let the user know that they are running an outdated version and if they don't care, they can simply pass -softwareexpiry=0 to continue running that version.
write
preview
100 sats \ 2 replies \ @TheCharlatan 5h
No, it does stop working for all intents and purposes. At the timeout will start rejecting blocks, effectively forking the node off the chain. If timed correctly, the node could be fed a chain with less work. This is arguably worse than just shutting down, since other services relying on the node will not notice immediately.
reply
0 sats \ 0 replies \ @ek 5h
You're right, I missed that this code runs inside CheckBlockHeader. Thank you!
reply
0 sats \ 0 replies \ @_Bubble_2009 OP 5h
This answer of yours is in line with what I was reading elsewhere. This is worrying. It is true that in two years, everything could change, maybe other programmers will start working on Knots and things could change. I was installing a well-known Knots, when they cut my fibre optic cables and now I am without a network for the whole week.
reply
115 sats \ 2 replies \ @_Bubble_2009 OP 6h
Ok, on the one hand it is correct to incentivize the user to abandon software that is no longer supported, but on the other hand, I see it as a sort of censorship.
Let's try to look at it from this point of view: many users are thinking of switching to Knots for everything that has happened around the issue OP_RETURN, let's say that all (or most of the community) switches to Knots, Let's say that in a year Luke decides to make an update that the community doesn't like, the user wouldn't even be free to continue to keep an old version active without having an annoying warning.
What do you think?
reply
0 sats \ 1 reply \ @ek 5h
What do you think?
You lost me at "a warning is a sort of censorship." My opinion didn't change.
If you don't like it and really cared, it's literally a few lines of code you could patch out.
Don't be an entitled FOSS user.
reply
0 sats \ 0 replies \ @_Bubble_2009 OP 5h
A few lines of code, but getting your hands on it without adequate testing, leads to frightening risks. One of the biggest criticisms made of this decision to remove the OP_RETURN limit is the lack of testing on this implementation. Here we would be in the same solution.
reply