Forcefully removing the limit configuration option for individuals is the real shady shit.

If you wanna change the default, that's a separate conversation. Ignoring this giant lashback and removing limits, while banning mechanic from github, just REEKS of fuckery.

Reply to this note

Please Login to reply.

Discussion

Yes, that is where the discussion has moved to.

Unfortunately Core don’t seem to have noticed.

nostr:nevent1qqsrtczg5kct43tfxl3aea0kcz9484lppm2ante2xq0mdj7sfwqjevqppemhxue69uhkummn9ekx7mp0qgspsjp3x4faxllye0vt45kkh33rwc2aw072ge8dktglgd2eqr85fasrqsqqqqqpt5wh6v

Core's argument comes down to "Yeah but let's make OP_return unlimited because they'll have to pay 4x more to store their bs than using the witness discount, the filter isn't working"

Then they proceed to say let's remove the filter. If the filter isn't working according to you, why not leave it the fuck in.

All this completely ignores the fact that I DO NOT WANT ANY ARBITRARY DATA, yet OP_RETURN gives them a corner of every individual's room to shit in. Imagine removing the filter that allows them to shit in the entire room.

Exactly, it leads to a compromise of being just a default setting instead of no option to configure. It's a big ask.

"The big ask" in "The Art of the Deal" refers to the strategy of making a bold, ambitious request in negotiations. By starting with a significant ask, you create a strong position that allows for negotiation and potential concessions. This approach can lead to better outcomes, as it encourages the other party to engage and find a middle ground, rather than settling for a lower initial request.

So if this happens to be the strategy, the response should be to capitulate that core is captured and just run knots.

lol I switched to Knots this morning