None of the bridge relays seem to support nengentropy, so can't fetch the events currently to locally work with them.
nengentropy 🤣🤣🤣
Negentropy*
Dear god, I started building the DVM and after seeing content from Mostr I want to burn it immediately. https://media.tenor.com/6R9RCMrt_GoAAAAM/flame-thrower-leonardo-dicaprio.gif
If you need the "tamed" version of it then you can fetch the events using wss://nfrelay.app/?user=activitypub . It has default filter for those wild content 😅 I think the "tamed" version is quite good. There are also variety good accounts there.
Trying now
Argh, negentropy also not supported. 🫣 Need to work around then
If you still found the content that you don't want then you can also probably tweak it with confidence score parameter setting https://github.com/atrifat/nostr-filter-relay/blob/main/USAGE.md
If you are on Amethyst can you check the trending on mostr DVM 👀 (it's not deployed yet, it's using your filter relay rn)
It btw seems that some nostriches appear there too, not just bridged accounts 👀
It works. But it seems there are mixed events with nostr native user (non bridged). 🤔 How did you fetch the events? Does it using parameter user=activitypub ? https://image.nostr.build/292e48689d188db043c649b5417570ab4314530108f60998adad9e0171fcf256.jpg
Yeah that's the relay I'm using with the flag
(btw great example of the content coming from there lol)
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
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.
@Don't ₿elieve the Hype 🦊 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?