Nostr Web Client

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl I need some very specific help.. I'm running a local strfry instance on my Android phone and when I'm trying to post to that instance from jumble I get:

Protected event, skipping

from strfry. The error also shows up in jumble. Posting to a local Citrine works fine and also posting to my local strfry from Amethyst works fine. Any ideas?

Cody 2mo ago 💬 3

Looks like strfry’s default configuration doesn’t accept protected events. You might need to ask the strfry experts what configuration needs to be changed to allow them.

Reply to this note

Please Login to reply.

Discussion

cloud fodder 2mo ago 💬 1

unfortunately those that PR'd this protected event protection into strfry did not think to make it optional. if you want you can patch it to the previous behavior of accepting them. I have a fork where I reverted it. https://github.com/jeremyd/strfry

chrizzz 2mo ago

Learning a lot right now.. strfry implements NIP-70 but not NIP-42. There is some recent work for NIP-42:

https://github.com/hoytech/strfry/pull/156

So maybe that will be merged soon.

chrizzz 2mo ago

nostr:npub1hqlxlq57nvlq70ugmsmu9y5lmyc5k2lh5w7y85j7dgsr5u7zwavq5agspw accepts local protected events because nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 fixed it in the 0.8.2 release:

https://github.com/greenart7c3/Citrine/commit/973be4290e3af0aaaf2a46b509c8ecc65bddbcc3

chrizzz 2mo ago 💬 1

Do I understand the jumble code correctly that when a post is written to non-write relays that it will be a protected event?

Cody 2mo ago 💬 1

If you don’t select write relays, then it will be a protected event.

chrizzz 2mo ago

Then I understood the code correctly. Thanks for clarifying.