What happens if someone has a pubkey in a categorized list kind 30000 but it doesn't appear in his/her contact list kind 3?
Which clients support these new kinds besides Gossip?
#nostr
You're wasting the world's water.
Boiling oceans yada yada.
Working on it, only need some funding.
These coinjoin protocols relay on a non-standard feature that should not be relied on.
They need to modify their coinjoin protocol to adjust to a more standard definition of the bitcoin protocol.
It is not Ocean's fault. It is nobody's fault, just a misunderstanding.
Privacy can be one of the reasons.
I don't even own a phone. So this would be my preferred method.
Freedom and V4V environment.
Those labels don't apply in a freedom based environment.
People are actually just people, not labels. Nostr only does is revealing that not-so-evident truth.
Alice using Client Y <--- magic ---> Bob using Client Z
Or the boy that cried "censorship", as in this case.
(I say this with love, guys, don't take it personal, please.)
He is technically correct.
40 bytes OP_RETURN should be more than enough for any and all blockchain arbitrary data storage needs.
Don't let lazy programmers and greedy hype riders tell you otherwise.
Forgot to tag nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk
Anyway, this thread explains it fairly well:
That is regrettable.
Blockchain data storage limit disagreements date back to Satoshi times.
Luke's 40 byte limit is by no means unreasonable. People should just chill and keep coding.
The arbitrary data storage on Bitcoin's blockchain can't be censored. It can only be overt or covert, but it will keep happening.
The decision to create OP_RETURN was to allow for a normalization of the practice, so that it happens in a well regulated frame.
Limits is a different story. We can have limits. Making everyone go crazy about a size limit is a genius move by nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk imo. Although he could've been more polite and ask people to modify their systems beforehand.
However, there are tensions between Ordinals people and Bitcoin Core people so... But that is a human failure. Technically speaking Luke is correct and there is no reason to keep any data storage limit high.
Just to be clear, I am merely stating the obvious: it is orders of magnitude easier to implement a second layer solution for blockchain data storage.
No idea what is wrong with everyone nowadays.
nostr:note18ka3ezt782au8x6tg84x33xtd4svakrcntdgd6u0hq2yrfsshzfsp5wtql

