So a Setting that everyone can set free now has a CVE number what the fucking hell is wrong with this inscription hater’s 😂🤡 nostr:note1007wspucpse5ae4cuzyxngwdug6h8j4eep92h6y524xhc7pt6x7s4stcmh
Happy Friday and a great weekend! 💜
Also lifeguards are making mistakes
Let them try! We have nothing to loose, but they could loose everything.
Hard to say on iOS but for android you could use material me so the client is always themed like the phone 🤔
Hey nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is there a way to consolidate this? 
Correct, but then you should stop name it spam. Just because you don’t like it doesn’t mean it’s Spam.
Many people like mailing lists where they become news, tips and tricks once a week directly. They think it’s useful information. For me it’s useless, but it’s definitely not spam, because someone sees a value in it. Same thing for inscriptions. I think it’s useless bullshit no body needs, but this doesn’t make it spam because somebody sees a value in it.
As you already said, Bitcoin is a decentralized system. So any action of „filtering“ is useless because everyone can run it in a different way. Why are we investing time and energy in the attempt to exclude something from the blockchain when we already know that someone is including it either way?
Every effort we make is pointless and noting more than a waste of lifetime.
I really don’t get it 😅
They do? Mine are still sleeping 🙃
Better believe no one and do your own research.
The recent discussions and negative sentiment surrounding the potential
filtering of
nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze and
coinjoin transactions appear to be driven primarily by speculation and
misunderstandings of how complicated spam filtering has historically been.
Filtering spam over the past two plus decades has consistently been a delicate
dance between accuracy and false positives, requiring ongoing adaptation and
refinement of filtering algorithms. This same principle applies to the potential
filtering of spam Bitcoin transactions.
Combating spam is a continuous and ever-evolving endeavor, similar to a
never-ending cat and mouse game. The notion of creating a static filter and
abandoning it is unrealistic. Constant adjustments and updates are necessary to
maintain their effectiveness. This situation is no different, and future
challenges will inevitably arise. When they do, we must question the situations
and infrom those running the application, mining pool, etc. of the potential
issues. By collaborating and openly sharing information, we can develop
solutions that address spam while safeguarding legitimate transactions and
privacy focused transactions.
Simply put: Have you ever encountered the frustration of searching for an
important email only to discover it buried in your spam folder? How did you fix
that? You instructed your email client to no longer flag those types of emails
as spam or you added the email sender to a safe sender list. Sometimes, this
worked right away and other times this took additional tweaking of spam
filtering algorithms. Still, this is so much easier than it used to be. Back in
the day, you'd have to send that email along with the headers to someone like me
and then I'd have to go update the SpamAssassin filters that I wrote.
I'm hopeful that they'll work it out.
Bitcoin doesn’t need a „Spam Filter“! A valid transaction is a valid transaction. Just because someone is using bitcoin in a different way than you doesn’t mean it’s wrong. Maybe both sides are wrong. Maybe both are right.
It doesn’t matter, because bitcoin has a very effective „Spam Filtering“ already implemented. It’s called transaction fees.
Where is the indication that nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze is filtering coinjoins?
Knots filters OP_RETURN bigger than 42 bytes. Whirlpool uses 46 bytes. You can find more information about this at the official samurai twitter account.
Thanks for your opinion, but I don’t care!
Push notifications are not on the iPhone they are send from backend servers and transmitted over apple’s push service. That’s why you should never pack user information in a push notification because it’s not encrypted.
Yes it does and also Paynym is affected
Sorry to say that but Luke lost all his integrity after he lost many bitcoin just of pure stupidity and then called for the FBI!
I think exactly like you, but I’m against censorship or stopping people from interacting with bitcoin their way. Everyone can use bitcoin the way they want. If this means someone wants to save monkeys in the bitcoin ledger then feel free to do so
It’s nearly a 10 BTC difference but okay 👌🏻
Feel free to censor transactions because you don’t like how people use bitcoin my node will never do so