Nice, will wait for that 🙂
BTW I have already run relay tray latest version ? Haven't seen any "hub" yet, is it not implemented yet in the current version?
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.
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
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 ?
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
Oh I thought You need volunteers for server hub. Alright I will test nostr-relay-tray later.
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.
Interesting. I think i can probably participate as hub server volunteer for early testing. Is there any hub server code that need to be run?
Is it like ngrok/cloudflared (reverse proxy service) to local nostr-relay-tray? The hub aggregates those local relay content?
https://github.com/atrifat/nostr-filter-relay
It has several independent modules (listed) to support the main relay app.
Really grateful, Thank you nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f for supporting #NostrFilterRelay 🤗 developments. It has been a great honor and opportunity to me working on Open Source project in #Nostr . Especially, since this is my first experience working in public project.
Please let me know if you have suggestions, experience, and feedback for the project. Thank you.
## Amber 1.1.1
- Support for sending and receiving bunker requests with nip44
- Fix remember my choice not working for reject when not using content resolvers
- Improvements to edit relay screen
- Option to listen to new connections without creating new application
- Option to setup biometrics/pin
Download it with [zap.store](https://zap.store/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v1.1.1)
If you like my work consider making a [donation](https://greenart7c3.com)
Thank you for the updates. It seems the issue in Nostrmo indirectly fixed by this update /cc nostr:npub19yeqjawls407xjnmgkk6yss7936pcd7qzd5srlj8wye6j8433vrsjazqwk
Not a DVM but you can also probably try using
wss://nfrelay.app/?user=activitypub
as "global feed" relay, to see Mostr or Momostr only notes. While we are waiting better DVM from nostr:npub1nxa4tywfz9nqp7z9zp7nr7d4nchhclsf58lcqt5y782rmf2hefjquaa6q8 👀
Thankfully, glad to hear that. Yes, I think other media provider (Primal, Satellite, Nostrcheck) need to do that too.
Cc nostr:nprofile1qqsgnc2tuj0dqpea4qak0qnee55m5kkcdncqpd4r6xjv8hz25n7aqtqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgewaehxw309aex2mrp0yhxummnw3exx6r9vd4jumt9qyg8wumn8ghj7vf5xqhxvdm69e5k7addye4 nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzfmhxue69uhhqatjwpkx2urpvuhx2uc86mqq0
Nostr relay operators, block
_npub1dfxq6ktz7mkw8h276p9h3kx67u2rh4mrpp2wj6cpw0pfdunh9nrq7eu42e
That user is distributing CP via Primal
Tag other relay ops here
nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w
Done. Thank you for report.
Do you mean to make some list known pubkey actor that often to post CSAM? Nostr event list or other place?
Not sure if it can help nostr.build but you can probably fetch raw event kind 9978 in wss://nfrelay.app . You can get NSFW classification data which some might capture CSAM content (if it is nude or porn). Hopefully it can help you Fishcake.
I just upload a beta version to nostrmo's webclient. https://web.nostrmo.com/
It supports login with NIP07 extension now!
Last version, we had add support to other signers too. *We are happy to receive your feedback.*
Thank you for the update Dashu.
I want to report small bug in v2.8.0 . It seems that currently Nostrmo didn't remember Amber setting request. This is example when client auth relay (NIP-42) request. I have already check remember choice and reject the request but Nostrmo still request again moment later. I have tried on Amethyst and it seems that it will ask once only.
It seems so. Using version 0.27.0 and it gives error
```
InvalidResponseCodeException: Response code: 403
```
Probably due to google block some YouTube API access 😅
Maybe keyword, regex, and basic anti duplication policy
Hopefully it will have features like original Alex Gleason policy script
https://gitlab.com/soapbox-pub/strfry-policies/-/tree/main/src/policies