pull down to refresh

hoping no one catches on to how it can be deployed maliciously [...] while also hoping our enemies don't have the balls to do it if they do know.
That's not how security works. That sounds a lot like "security by obscurity" which is heavily frowned upon in the itsec community (for good reasons).
I totally can understand why @super_testnet did this. I just don't agree it's a problem and see more risk in enabling censorship if we do something about this.
However, if inscriptions are really as bad as some think, bring it on. The earlier, the better. I think that's the same reasoning as @super_testnet has.
This post can be compared to LNsploit, I guess.
That's not how security works. That sounds a lot like "security by obscurity" which is heavily frowned upon in the itsec community (for good reasons).
I don't disagree, but that's what I'm seeing how the collective is essentially treating this situation, otherwise they're entirely missing how this can be used as an attack.
However, if inscriptions are really as bad as some think, bring it on. The earlier, the better.
In this case, I disagree. no one is ready for this kind of attack. many are in denial about it.
reply