Still an idea floating in my mind, what use case could solve? Have better events synch of relays?
Discussion
Yes I would like to obtain the orders from source to populate it to robosats relays so users can interact with them in Robosats' app. I'm already doing that with lnp2pbot
We will speak with nostr:nprofile1qqsqqqqqqqr99ezjae52qyv8lvyv3x2fdj6xedgar2sgq0gx8t8dhfcpyfmhxw309ahx7um5wf4xztttv9exjttgw368qtngv4nh2un09e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uascxh2 about!
Any update on this?
what is negentropy? Mostro relay is using Rust relay
It's the most efficient way to synchronize 2 relays. Seems like rust noatr implements it https://github.com/rust-nostr/negentropy
then we will implement it, let me give it a look
nostr:nprofile1qqsqqqqqqqr99ezjae52qyv8lvyv3x2fdj6xedgar2sgq0gx8t8dhfcpyfmhxw309ahx7um5wf4xztttv9exjttgw368qtngv4nh2un09e3k7mf0qy88wumn8ghj7mn0wvhxcmmv9uq3gamnwvaz7tmwdaehgu3wxymrvvfwd9hj7jegwrl, if it helps, here is how I implemented it for the nostr-relay-builder: https://github.com/rust-nostr/nostr/blob/06dd1b6e532a611929278f9374aa4340455f0f54/crates/nostr-relay-builder/src/local/inner.rs#L698
👀 thanks Yuki 🤛 🤜
In the case of the lnp2pbot, the source tag with the link to Telegram is published in the kind 38383 events.
In the case of nostr:nprofile1qqsdhc93hklp988r3km4844fjln298nf8t7s92sar7dsqha88ph9cfspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7qg4waehxw309aex2mrp0yhxummnw3ezucn89uv7r8lk, to take an order, it must be within a client that sends Gift Wrap events indicating to the Mostro instance that they want to take that order.
For now, there is no other way to take it other than within a client with those characteristics.