Pablo Fernandez

> We can't fetch only NUDs, right? For example, do we need `["l", "nud"]`? You can fetch by `#c: ["Nostr"]` to get all the nostr-specific things

NACK; this would be a hard-fork. If there's interest in this idea relays should send a new/separate command along with the `EVENT` (`SUMMARY`?) with this data which non-supporting clients would...

Isn't the idea that this would be embedded by the relay inside the event object? So to verify the signature, the client would need to strip this `.nip17` part to...

I must be misunderstanding something, if the client generates the event, serializes (obviously without that `nip17` path), but then the relay injects that nip17 path into the returned event then...

I retire the hard-fork comment still don't think this is a good idea, it increases costs on relays, relays that adopt this will get beneficial treatment, etc etc, etc, [insert-reasons-why-BSV-is-stupid-here]

Concept NACK -- this adds too much complexity that I don't think is warranted, and adds a path for ever increased complexity with the `x_` prefixes and protocol fragmentation. Even...

this is a really good idea and the pubkey prefix of an existing p-tag. Maybe we can suggest that `N` should be the smallest length that disambiguates the p-tags in...

> > Nostr is not only microblogging > > This is true. But I implement most NIPs and I frankly don't remember using relay hints in any of them. You...

A third option would be to use NIP-46 for this (which was actually my original motivation behind starting to work on nsecBunker). A key is stored in a bunker and...

are you sure you are connected on the server side? keep in mind those are two separate connections; worth checking what's on ndk.pool.connectedRelays (iirc) on the server side, you might...