relayer
relayer copied to clipboard
fiatjaf
A Nostr relay server framework.
The README should contain a list of supported NIPs by this framework and ideally the basic reference implementation, as it is not clear otherwise and going through PRs might not...
The timeout may make memory leak of chan since the chan is not pulled out. This may be leak of result set.
Single e tag works as expected ``` nostcat ws://localhost:9000 ["REQ","RAND",{"kinds":[1],"#e":["8b1013c2d137bab5a7026e5adc65dcd641025c1a8ae2b7ecdec848cca44f1297"]} ``` Two values returns nothing: ``` nostcat ws://localhost:9000 ["REQ","RAND",{"kinds":[1],"#e":["8b1013c2d137bab5a7026e5adc65dcd641025c1a8ae2b7ecdec848cca44f1297","e32f75bfce9513bab7c7e82b9a61fd56f80f68946a9d0a384f7f17989bd91f13"]}] ``` I suspect this has to do with the `LIKE` query...
All the storage adapters loose the association between tag key and value and generally just query by value. There's kinda some todos about this in the code and conversation about...
Not really an issue, just a writeup on which data might come in handy for various custom implementations: 1. **ws connection that sent the event** - This could be a...
Was thinking about this lately: ```go QueryEvents(filter *nostr.Filter) (events []nostr.Event, err error) ``` could be changed to: ```go QueryEvents(filters ...nostr.Filter) (events []nostr.Event, err error) ``` or: ```go QueryEvents(filters []nostr.Filter) (events...
Currently the onAccept event returns a Boolean. What about changing it type to error or some new type. This could help implement nip20.
Normal closures (1000) are currently logged as: `unexpected close error from %s: %v` https://datatracker.ietf.org/doc/html/rfc6455#section-11.7 This PR adds code 1000 to the list of expected codes to prevent these logs lines...
