I don't think that BIP110 is actually per say technically anti-spam. It aims to completely prevent the two ways of posting contiguous data via the p2p network. Meaning you might still be able to post contiguous data, but via 3rd party like Mara only. Mostly, BIP110 rejects the change implemented in core 30 that effectively makes 188bwt a sanctioned file sharing app. And it sends the signal that core's complaisance towards spam will no longer be tolerated. For example, guys like Tone Vale are saying that BIP110 effectively kills core. But I don't think so. Core can still save itself if it takes an anti-spam stance. But core will never regain a complete monopoly of 188bwt nodes. Especially with Knots and Sampson Mow's implementation showing up over the horizon. I'd like to see other implementations gain popularity. Not really. He still has to go through a 3rd party. Inhiss case, Mara. Now how liky would Mara react if he attempted to post illicit content instead of the stoopit crying Luke TIFF? As I see it, the most important part of BIP110 is the signal it sends: 188bwt is money, not jpeg hosting service for shitcoins. But no doubt, spam will still exist after BIP110 goes through. Fighting spam is like installing a moskito zapper in your garden. It needs to be a continuous and perpetual fight. BIP110 fixes the op_return limit at 83 bytes in consensus. So that nobody can ever attempt to fuck with it a again. And it puts an end to the use of op_of in Taproot. Still you will have access to op_ifioutsidebof Taproot. Every known use cases of op_if in Taproot are for spam. So far, about 6 months into the BIP110 debate and nobody has cone out and said they are using op_if in Taproot, outside of spammers. "[188bwt] takes advantage of the nature of information being easy to spread but hard to stifle."
I don't think that BIP110 is actually per say technically anti-spam. It aims to completely prevent the two ways of posting contiguous data via the p2p network. Meaning you might still be able to post contiguous data, but via 3rd party like Mara only. Mostly, BIP110 rejects the change implemented in core 30 that effectively makes 188bwt a sanctioned file sharing app. And it sends the signal that core's complaisance towards spam will no longer be tolerated. For example, guys like Tone Vale are saying that BIP110 effectively kills core. But I don't think so. Core can still save itself if it takes an anti-spam stance. But core will never regain a complete monopoly of 188bwt nodes. Especially with Knots and Sampson Mow's implementation showing up over the horizon. I'd like to see other implementations gain popularity. Not really. He still has to go through a 3rd party. Inhiss case, Mara. Now how liky would Mara react if he attempted to post illicit content instead of the stoopit crying Luke TIFF? As I see it, the most important part of BIP110 is the signal it sends: 188bwt is money, not jpeg hosting service for shitcoins. But no doubt, spam will still exist after BIP110 goes through. Fighting spam is like installing a moskito zapper in your garden. It needs to be a continuous and perpetual fight. BIP110 fixes the op_return limit at 83 bytes in consensus. So that nobody can ever attempt to fuck with it a again. And it puts an end to the use of op_of in Taproot. Still you will have access to op_ifioutsidebof Taproot. Every known use cases of op_if in Taproot are for spam. So far, about 6 months into the BIP110 debate and nobody has cone out and said they are using op_if in Taproot, outside of spammers. "[188bwt] takes advantage of the nature of information being easy to spread but hard to stifle."

I don't think that BIP110 is actually per say technically anti-spam. It aims to completely prevent the two ways of posting contiguous data via the p2p network. Meaning you might still be able to post contiguous data, but via 3rd party like Mara only. Mostly, BIP110 rejects the change implemented in core 30 that effectively makes 188bwt a sanctioned file sharing app. And it sends the signal that core's complaisance towards spam will no longer be tolerated. For example, guys like Tone Vale are saying that BIP110 effectively kills core. But I don't think so. Core can still save itself if it takes an anti-spam stance. But core will never regain a complete monopoly of 188bwt nodes. Especially with Knots and Sampson Mow's implementation showing up over the horizon. I'd like to see other implementations gain popularity. Not really. He still has to go through a 3rd party. Inhiss case, Mara. Now how liky would Mara react if he attempted to post illicit content instead of the stoopit crying Luke TIFF? As I see it, the most important part of BIP110 is the signal it sends: 188bwt is money, not jpeg hosting service for shitcoins. But no doubt, spam will still exist after BIP110 goes through. Fighting spam is like installing a moskito zapper in your garden. It needs to be a continuous and perpetual fight. BIP110 fixes the op_return limit at 83 bytes in consensus. So that nobody can ever attempt to fuck with it a again. And it puts an end to the use of op_of in Taproot. Still you will have access to op_ifioutsidebof Taproot. Every known use cases of op_if in Taproot are for spam. So far, about 6 months into the BIP110 debate and nobody has cone out and said they are using op_if in Taproot, outside of spammers. "[188bwt] takes advantage of the nature of information being easy to spread but hard to stifle."

I don't think that BIP110 is actually per say technically anti-spam. It aims to completely prevent the two ways of posting contiguous data via the p2p network. Meaning you might still be able to post contiguous data, but via 3rd party like Mara only. Mostly, BIP110 rejects the change implemented in core 30 that effectively makes 188bwt a sanctioned file sharing app. And it sends the signal that core's complaisance towards spam will no longer be tolerated. For example, guys like Tone Vale are saying that BIP110 effectively kills core. But I don't think so. Core can still save itself if it takes an anti-spam stance. But core will never regain a complete monopoly of 188bwt nodes. Especially with Knots and Sampson Mow's implementation showing up over the horizon. I'd like to see other implementations gain popularity. Not really. He still has to go through a 3rd party. Inhiss case, Mara. Now how liky would Mara react if he attempted to post illicit content instead of the stoopit crying Luke TIFF? As I see it, the most important part of BIP110 is the signal it sends: 188bwt is money, not jpeg hosting service for shitcoins. But no doubt, spam will still exist after BIP110 goes through. Fighting spam is like installing a moskito zapper in your garden. It needs to be a continuous and perpetual fight. BIP110 fixes the op_return limit at 83 bytes in consensus. So that nobody can ever attempt to fuck with it a again. And it puts an end to the use of op_of in Taproot. Still you will have access to op_ifioutsidebof Taproot. Every known use cases of op_if in Taproot are for spam. So far, about 6 months into the BIP110 debate and nobody has cone out and said they are using op_if in Taproot, outside of spammers. "[188bwt] takes advantage of the nature of information being easy to spread but hard to stifle."