Assuming you’re referring to the supposed legal risk, see: nostr:nevent1qqsrfx5ultlcpyxgeq9axmak8eg2fvu4gm9k733zwjrn8vm9emlzf6gprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqgsw34nugddy5kfsfc2pg2qwj5h0u9a7gf20egnez6lk870h8e22hfqrqsqqqqqpsegare
No it’s not legal risk I’m talking about; Bitcoin is anarchy, legal threat does fuck all.
In referring to the computational, memory overload my node - which I paid for - has to overwork for someone else’s data storage.
nevent1qqsvtczt5gna8qqu488t2j3sazaxfxk9kqsdc9kll5cc7nh9eqcm0qqppamhxue69uhkummnw3ezumt0d533sm6w
This doesn’t sound like a Szabo argument to me, do you have a link?
In any case, if it’s this kind of bandwidth consumption you’re worried about, you are free to use filters, or better yet run your node in blocksonly mode. (Bitcoin Core allows you to configure both, fwiw.)
I definitely use filters in my node, and I’m riled up on the fact that they are
a) changing the filter standardness
b) plan to deprecate one of the filters I use.
My trust in core developers has broken.
You don't have to upgrade at all if you don't want to of course.
(But fyi nothing has been deprecated.)
