this is happening sooner than i expected

nostr:nevent1qqsyf0wx3ts3mx9skrexmsztv2wlavykeqp6ugqh538vcnq98pld0xspzpmhxue69uhkummnw3ezuamfdejszxthwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dspzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qvzqqqqqqyauakmu

Reply to this note

Please Login to reply.

Discussion

🤷

I hope they hurry up and just get it over with

Yes please

Tf is a bitcoin holy edition?

lukes fork

ChastityCoin

Luke said he absolutely will not allow CSAM on his node and I think he meant it like his place in heaven depends on it. Not adding my opinion or judgement, not being dramatic, just repeating what he expressed on the recent Jimmy Song, Tone, Bitcoin Mechanic discussion.

i don't see how he can stop that. nostr:npub1ej493cmun8y9h3082spg5uvt63jgtewneve526g7e2urca2afrxqm3ndrm already showed you can store data in a way that is already fully compatible with his proposal.

since you can push data in scripts there will always be a way.

https://x.com/mononautical/status/1982601377923891530

It seems that is his motivation regardless. Unless I misinterpreted his statement, but I think he communicated it pretty clearly.

Also seems highly likely that any future attempt at putting CSAM in a block will come from knots users.