spam

Search documents
X @Nick Szabo
Nick Szabo· 2025-10-19 01:37
RT omerskywalker⚡️ (@0merskywalker)@NickSzabo4 @adam3us @satflation @jabulanijakes @BitMEXResearch @giacomozucco Lowering the barrier to abuse = increasing the ease of exploitationSure, motivated actors could already get their consensus-valid txs mined despite getting filtered out of the p2p network — but the latest changes make it trivial for even casuals to spam the timechainCui bono? ...
X @Nick Szabo
Nick Szabo· 2025-10-17 19:43
RT Gilded Pleb (@gildedpleb)There are many things wrong with the now infamous quote from Gloria Zhao (@glozow), Bitcoin Core Maintainer. In this post I will attempt to show why, exactly, it's problematic. Admittedly, it is hard to see on first glance, so lets attempt to be systematic about it.The quote:> "Like you, like if you don't like cat photos. You don't like wizards or whatever. That's your choice. But I don't think this is not a legitimate transaction. Or this is a waste of block space. Because NFTs ...
X @TechCrunch
TechCrunch· 2025-10-17 14:16
WhatsApp is testing a way to limit number of messages someone can sending in a month without getting a response to limit spam https://t.co/XWSJPyomz1 ...
X @Nick Szabo
Nick Szabo· 2025-10-11 01:52
RT Luke Dashjr (@LukeDashjr)Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently ...
X @Nick Szabo
Nick Szabo· 2025-10-08 14:49
Transaction Cost Analysis - The total cost of "spam" transactions exceeds their price in fees [1] - The infrastructure cost that spam forces the entire ecosystem to pay is a key concern [1] - Every transaction, whether spam or essential payment, contributes to this cost [1]
X @Nick Szabo
Nick Szabo· 2025-10-05 13:48
Protocol Abuse - The protocol is being obviously abused, which they can't see [1] - Using ONE OP_RETURN would be an endorsed way to spam, which is also bad [1] - Both protocol abuse and spam need addressing [1] Regulatory Concerns - Using ONE OP_RETURN is regulatory worse [1]
X @Nick Szabo
Nick Szabo· 2025-10-04 17:22
RT Adam Back (@adam3us)evidence piling up that censorship resistance and curbing spam are fundamentally in conflict, the internet physics of this are that:A) prioritizing fighting spam conflicts withB) privacy and uncensorability/decentralizationPrioritize 1. ...
X @Nick Szabo
Nick Szabo· 2025-10-03 07:51
Risks Associated with Arbitrary Content - The core developers may be underestimating the risks and objections associated with arbitrary content compared to financial transactions [1] - Arbitrary content introduces a far greater and more unpredictable variety of risks and objections for node operators [1] - The primary concern is not the volume of content (spam), but the content itself [2] - Arbitrary content carries a vastly greater variety of legal risks and moral objections than financial transactions [2]
X @Nick Szabo
Nick Szabo· 2025-10-02 06:24
RT Rajwinder Singh (@rajwinder)@heavilyarmedc @NickSzabo4 As a node runner I do not want to relay spam, especially CSAM.Increasing default setting of datacsrriersize to enable spam/CSAM is utterly deranged.Nothing justifies it. ...