rich1.0cloud fodder (npub10n…ztl5h)https://yabu.me/npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5hnjumphttps://yabu.menostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 I found some bugs on your lockbox relay while messing around testing it. 1) Scenario: two pubkeys. Pubkey1, does not have a follow list on lockbox. Pubkey2 does have a follow list, but is not following pubkey1. Start streaming from both pubkeys on their own connections. Post a message from Pubkey1 or vice versa, and the relay will stream the event through to the other pubkey, but only while the stream is open. On a refresh of the REQ, the message is not listed. (LOCKBOX BREACHED!) :) 2) Scenario: trying to post a follow list for Pubkey1 with an existing follow list on Lockbox. Lockbox says "failed: msg: blocked: we only accept events protected with the nip70 "-" tag" I'm curious if this second one is a bug or if you're expecting clients to include a ["-"] in the follow lists too. That's as far as I got. Tested via. https://relay.tools/posts?relay=wss://lockbox.fiatjaf.com