mleku on Nostr: this flow seems overcomplicated wouldn't it work better like this: * you have a list ...
this flow seems overcomplicated
wouldn't it work better like this:
* you have a list of blossom nodes that you know about, and send out a query for hash
* one or more returns the hash
there is no participation of pubkeys in the protocol as i understand it
theoretically, a cluster of blossom nodes can propagate queries and cache the results for future queries
blossom makes no assumptions about blossom node caching strategies or how much or which data they might delete, this is part of the point, i think
wouldn't it work better like this:
* you have a list of blossom nodes that you know about, and send out a query for hash
* one or more returns the hash
there is no participation of pubkeys in the protocol as i understand it
theoretically, a cluster of blossom nodes can propagate queries and cache the results for future queries
blossom makes no assumptions about blossom node caching strategies or how much or which data they might delete, this is part of the point, i think