you can, just by turning on auth and payments. and use nip70 when publishing, but yeah you already know how things can leak a bit.
Discussion
Ok. I wasn't sure how payments worked on the read side. I thought it was just pay to write. Thanks for tolerating my ignorance 😅
I'm not thinking so much about keeping something exclusive, so much as making it easy to find.
Placing gems amongst a bunch of hard to find but already distributed content, thats been organized, any leaks might inspire people to look for the source. Recipes just seem like the perfect playground for this, at least right now.
there is no standard for auth, the pay to read+write was just how I ended up implementing it for relay tools (using the same access control list for both)
many possibilities, there may be additional modes in the future.. 🌱
I had no idea lol oi
probably cause i havent made any tutorials or anything.. really need to do that #soon 😂
usually i try to mention it in the UI, but.. i think i didnt do that either.
the idea was relays as communities, with auth.. but there were no clients for it before jumble came out. i think its a semi popular mode tho for those that used it 🤔
I imagine it is popular. I am aware of a few, but I don't participate. That's a me thing, more than anything.
I was just curious. I'm seeing all sorts of possibilities emerging lately. Thanks for explaining.