I didn't dive deep enough into delegation myself to have a say about delegation in a technical protocol/ implementation manner.

However nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c has implemented delegation into gossip for a long time and I am assuming that users will have the say about using or not using delegation, if clients support it ( nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s ).

Relays will either get paid more by delegated notes, even if the cost is produced at the get/fetch side of other following npubs. Or some relays will just not accept delegated notes and we will see delegation friendly and unfriendly relays. (Is this the way how relays can avoid costs of delegated notes in the first place or are relays helpless currently? )

I assume that individual relays must feel the constrains first, before a protocol or relay implementation adoption will happen. Always has been, hasn't it?

Therfore I propose that *tool creators don't censorship possibilities for users* just because the costs for the network are considered too high at the moment for using a tool.

PV nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl and thank you for bringing awareness of delegation costs into my field. 🫂

Reply to this note

Please Login to reply.

Discussion

Going to try to implement delegation in nostrdb to test the theory that it complicates things. I don’t think it’s as bad as everyone is claiming, but i could be wrong.

It has the same complexity issues that the 'k' tag does, where you need an event.effective_kind() and do all your indexes against the effective kind. With delegation, you need an effective_author() and do all your indexes thusly. I'm simplifying.

Wait, what’s a k tag.

Kind. It is the kind of another event also referenced, usually. In a PR (that I can't find at the moment) it is the effective kind of an event whose kind field is used to indicate it is a community-only event.

Bird X killer nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 spotted. He appears as white cat next to the nostr:npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl. See the images as proof.

Just look at nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6's cute paw. This is where the interface between his vision and the physical realignment of open communication thanks to nostr is/was.

Under this new circumstances, nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w can wrap himself up in a doggy bag and should reincarnate from his own ashes like a Phoenix. But probably this happend in the past already.

❓ Do we have a Catdog aka nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w? #asknostr

#artchain #plebchain #cat #animal #grownostr

Do not take the gossip implementation of delegation to mean that I support that alternative. I suspect there is a better way. I haven't looked into it much. It was someone else's PR that I just merged. Delegation is kind-of a pain, but I added an index to make it less costly.