monlovesmango
monlovesmango
agree this workflow is pretty slick but it makes me concerned about the user experience for non paying users. most paid relays will likely still allow some level of querying...
>Most of the "NOTICE" messages are completely ignored. agree, but its the only message type that is ignored, and it is needed bc we need at least one way to...
>Why do you need to filter, then? The relay can just send it at any point in the regular subscription. because otherwise there is no specific sub id to associate...
yeah perhaps, but would also need to be integrated into restricted events NIP. I think both are already introducing enough complexity so I would prefer not to add more. however,...
yes, true. was just thinking about this myself. actually don't think I would need to change anything other than add it as another option to the filter condition right?
really like the idea @arthurfranca ! being able to allow access to different subscription levels or different sets of content is so neat.
this is different from NIP26 in that this only gets added to kind 22242 event tags and the permissions in the token refer to what access is granted on the...
love this. very simple but powerful (but as with all nostr policy, only as powerful as its adoption). honestly surprised me that this hasn't already been done. I kinda think...
>That's why I proposed changing the serialization: to reject by default on current relays and make it backward compatible (relays don't need to change) and they shouldn't be working with...