#NostrFilterRelay v0.4.0 update
"Compatibility bring various apps grow together" π±
This release bring important change with NIP-32 compatibility (kind: 1985). Starting from this release, legacy custom event (kind: 9978) that were used for classification data in nostr-filter-relay has been deprecated. Other #nostr apps can freely uses NIP-32 label.
Legacy support is still available by setting nostr-filter-relay with environment variable as follows:
ENABLE_NIP_32_CLASSIFICATION_EVENT=false
ENABLE_LEGACY_CLASSIFICATION_EVENT=true
USE_NIP_32_EVENT_FORMAT=false
Explanation of NIP-32 structure were documented in NIP32-COMPATIBILITY.md . Thank you nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn for valuable discussion π.
Release note:
https://github.com/atrifat/nostr-filter-relay/releases/tag/v0.4.0
PSA:
Demo relay wss://nfrelay.app will be updated. If you are using old event format (kind: 9978) from the relay, please prepare to migrate and use NIP-32 event (kind: 1985). After 1 week, nfrelay.app will publish NIP-32 event and stop publishing old event format. Thank you.
Cool. Is this using LLM to generate summary of topic keywords and use NIP-50 relay to search using those keywords? π
/cc nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c in the context of language filtered content, you can try out this relay (and use a client which only will show the content from this relay π§)
Yes, nostr client devs can also use directly classification events (NIP-32 kind: 1985) and filter kind: 1
Example:
nak req -k 1985 -t L=app.nfrelay.language wss://nfrelay.app
#NostrFilterRelay v0.4.0 update
"Compatibility bring various apps grow together" π±
This release bring important change with NIP-32 compatibility (kind: 1985). Starting from this release, legacy custom event (kind: 9978) that were used for classification data in nostr-filter-relay has been deprecated. Other #nostr apps can freely uses NIP-32 label.
Legacy support is still available by setting nostr-filter-relay with environment variable as follows:
ENABLE_NIP_32_CLASSIFICATION_EVENT=false
ENABLE_LEGACY_CLASSIFICATION_EVENT=true
USE_NIP_32_EVENT_FORMAT=false
Explanation of NIP-32 structure were documented in NIP32-COMPATIBILITY.md . Thank you nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn for valuable discussion π.
Release note:
https://github.com/atrifat/nostr-filter-relay/releases/tag/v0.4.0
Yes. You can test it using nfrelay.app as demo relay, elsat
wss://nfrelay.app/?lang=ja,th
Exporting and importing events into a new strfry instance (which you need to do when the DB version changes) takes too long. Here's a feature I just added that speeds this up a lot:
https://github.com/hoytech/strfry/blob/next/docs/fried.md
Going forward, there is a release-0.9 branch. I'm going to tag one more release on that branch soon (after back-porting a couple fixes). It will have strfry export --fried but not import. I'm planning on this being the last release of the 0.9 series.
I'm working on a 1.0 release in the next branch. I just did a big refactor of the DB format that I've wanted to do for some time. I also removed prefix matching on id/pubkey (this was removed from NIP-01) and fixed a bunch of bugs. This release will also have the latest negentropy protocol version and BTree code.
Thank you for all your works Doug. Happy to see you are working on strfry again π
I just upgraded it yesterday π
Congrats Alex π
Oh, let me know if you have found the model. I want to make similar API server for those case later
Lol, they might be suprised with the usage π
Yeah, you can probably get better performance with your home server especially if you have CUDA enabled. It can process image faster (around 20-40 ms)
Thank you. Hopefully it can help Wired solve the problems. I have seen one irresponsible anons who posts CP through Wired.
added images/videos back to getwired.app- weβll see how that goes this time, and will probably be very slow for now.
used nostr:npub19dn7fq9hlxwjsdtgf28hyakcdmd73cccaf2u7a7vl42echey7ezs2hwja7 βs cool repo for detecting NSFW stuff.
Oh nice. Did you deploy it on Render? π
I've run it on my VPS and it tooks around 100-200 ms to classify one image
I just received this in the morning and quite excited to try it π
Is there anyone who have tried Github Model? What is your experience?
nostr:npub1r27775s4thzj5gdz4j0dr8jygvtldnur2qxlzw0muu7z57k83c4qtsyqx6
Where I can find addresses of tor-only relays?
#asknostr
You can probably check some listed relay here
No worries. Enjoy your holiday Dashu π
Hi nostr:npub19yeqjawls407xjnmgkk6yss7936pcd7qzd5srlj8wye6j8433vrsjazqwk , what do you think about this PR?
i think this is one setting that we missed in Nostrmo, useful to save data usage π
'FuLlSt4Ck DeVs' π
"Also please fix our office's printers please"
Client and relay can implement some content filter feature.
For client, especially web clients, can use these libraries to implement the feature easily.
https://github.com/infinitered/nsfwjs
or
https://github.com/NsfwSpy/NsfwSpy.js
I think there are other libraries for iOS and Android that can be easily included in native clients.
I have already implemented in relay code of wss://nfrelay.app which gives filtering feature to its users.
