Hmm it seems weird need to debug it 😅

I have tested using nak manually

nak req -k 1 -l 2000 wss://nfrelay.app/?user=activitypub | grep -v activitypub

It gives 0 since the returned events because all the returned value were all from mostr.

While

nak req -k 1 -l 2000 wss://nfrelay.app/?user=activitypub | grep activitypub

Show all the activitypub events

Reply to this note

Please Login to reply.

Discussion

Doesn't seem to make a difference if I have the ?user= or not 😅

Ah maybe it was entries in the local dB from before. Cleaned it now. Any plans to enable negentropy?

Oh, does it work for now?

If not I think the probably reason is you fetch kind 7 directly with wss://nfrelay.app/?user=activitypub ? Right?

["REQ","subid",{"kinds":[7]}]

Currently filter logic in nfrelay.app only process REQ with kind 1. So you can't directly use kind 7 with any filter for now. Other kind beside kind 1 is not filtered 😅

You can probably use those kind 7 but need to check again from "e" tag in those kind 7 to nfrelay.app . Did certain kind 1 exist with those "e" tag

["REQ","subid",{"kinds":[1], "ids":["eventId1", "eventId2"]}]

into wss://nfrelay.app/?user=activitypub

> Negentropy implementation

Not at the moment. I think will add into backlog feature later. Currently want to finish the main features at first.

nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 Did you deactivate Mostr DVM? It seems there is no response in the last few days

It sometimes dies because I have to grab on the fly from relays because none supports nengentropy compared to the others. Will restart

Thank you. It works properly now. 🫡

By the way, did you cross check the trending notes into nfrelay.app to filter in the last step?