Nostr Web Client

No, it's mostly just the core structures that I use. I could migrate to go-nostr, but nostrlib is genuinely better in this area.

I attempted to switch to rely this morning and decided against it for now due to the lack of negentropy and blossom support. I get not wanting to include that stuff, but examples or external libraries would make the process easier (I do think negentropy should be table stakes for relays nowadays).

Pip the WoT guy 2mo ago

Thanks for the feedback.

To me, blossom is an orthogonal thing, which can be added in this way:

- create an http server (there are many many frameworks in go, even the standard library is fine).

- create a relay

- use the relay handlers in the http server (relay.ServeWS, relay.ServeNip11)

- add the blossom handlers to the server

and voilà, server is now relay + blossom.

For negentropy, that is another story since it used the websocket protocol.

It would be a nice addition to rely, so I'll add it to the roadmap. I am just conscious about complexity in general, since I want to maintain rely long term, not leave it rotting.

Reply to this note

Please Login to reply.

Discussion

hodlbod 2mo ago

Absolutely, I think that breakdown is the right call. A blossom library could be built separately