i agree with the views of Bitcoin Mechanic and with the comment of John Carvalho in the google groups discussion where he basically says that Core should not govern node Policy. People running nodes should be able to choose the node policy.
Not that i know of. but if or when there is i think it would be easier to update the implementation you already have than to change the implementation you are using in that moment. Apart from that i guess the point now is people are losing trust/unhappy with the decisions that Core is taking and are signaling that by choosing an implementation that aligns more with their views. I think its good. Not updating is another option sure, but if new feats/updates that you want comes along you will have to deal with it at that point.
if there is a security patch you wont get it without updating.
if filters are useless then i guess we dont need to change the current op_return setting.
using in your daily smartphone i dont think its pratical, android kills all tasks in the background, and even if you only put it back on when making a tx you will wait forever imo. but using an old phone always plugged in at home is a good option imo. Also people think they need a dedicated server for a node, you can run it on your daily personal laptop.
So citria wants to have some sort of permissionless bridge from base layer to them, so they need op_return limits out to do it, oh but if Core doesn't do it its worse, because they will send the txs directly to miners out of band that have a deal with them. This makes its seem that for citrea its all the same, and for the network is worse,well if they need some deals with some miners that doesn't seem that trustless anymore does it? Seems to me that not merging this change is worse for citrea that has money invested and not a solid product than for the network.
I am a dev and devs are often "stupid" because we think in absolutes and we either have a perfect solution for a problem or its useless. Bitcoin is more probabilistic and it is also social/political.
The fact that bitcoin has fees does not stop/prevent spam, spam as in undesirable data, fees prevent Denial Of Service attacks, if a bad actor wants to flood the chain, fees will rise and eventually stop that attack, but if you just send some crap randomly just because you think Bitcoin is a nice DB for jpegs fees wont do shit, you need other methods, and yes they are never fully effective.
satoshi talked about this, unlike gold where price follows cost of production, in bitcoin, cost of production (mining/hashrate) follows price. Bitcoin hashrate/network security will always find a balance according to price. If bitcoin doubles in price, double market cap, you can bet security (hashrate) will follow, the opposite is also true.
i dont think there is any good enough solution, bunker is probably the best but not too convenient.
you can choose not to, or use a burner if you want, its your choice and there is a clear warning. Nostr browser extension signers also store it in browser local storage.
My point is, did anyone asked for this? is this necessary for improving bitcoin or txs?no, its just to have a better way to store random data, so why is Core, that should be very conservative pushing this. The argument of they can already do it in other ways is not a valid argument.
but if core does some security update or other kind of core improvement, you either stay frozen in that version or you have to update and take it all because its not a plugin based. we need a plugin kind of node implementation.
Portugal down too.
No power in Portugal. rekt.
i think like every sunday every npub should not post. No posts on Sundays.
plausible deniability my bank transfer to bank x can be for anything, and my bank wont probably "talk" to bank X, its hard for them to coordinate like that and there is privacy rules they must follow, so they probably do not know the account owner , the data is partitioned between the two entities. They have little basis to block a regular bank transfer, but they can easily block a transfer to binance or coinbase.