pull down to refresh

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?
0 sats \ 1 reply \ @ek 6h
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
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