Fernando Bittencourt
Fernando Bittencourt
I think what's more interesting than what NIPs are supported is what types the relay accepts. From what I understand, the blocking on the relays is being done by the...
nostr relays are quickly migrating from I will accept everything to I only accept what I want and block the rest. If there is no simple way for customers to...
> > * 10312 > > This is probably a list of Live Event in NIP-53. Its `REQ` message is being sent by [Nostr Nests](https://nostrnests.com). > > As far as...
> 10009 is a list specified in the NIP-29 PR that will be merged very soon. The lists are kind of around 10,000 as you typed. And 10009 really exists....
> > Doesn't the NIP-53 say anything about kind 10312? I only found it about 1311. > > Lists are defined in NIP-51, but kind 10312 hasn't been said yet....
@Egge7 Is BSON not supported by NOSTR just because no relay or client has implemented support for it? Or is it due to some BSON data parser issue where it...
About the "hash" tag really makes no sense. It ended up coming in copy/paste on NIP94. I will remove it. I also changed it to be a regular event as...
This suggestion of dividing the data into several parts is very good. But perhaps the use of the e tag is not the ideal way. Because I need to know...
> The issue with that idea is that every part cites every other part. They become heavier objects to parse. Instead, my proposal was to do just one header kind...
It can be used in the same way. As I put in the description, the NIP-94 must be used to disclose the NIP-95 file referencing the event. Because the NIP-95...