Mix of Nostrmo, Amethyst, Nostrudel, and 0xChat

Hmm, ini sih parah udah.

I see, it is quite hard for critical computation that need fast processing (< 100 ms) especially if the implementation can't be rewritten totally.

Based on your experiences, is it possible to generate zk proof for external API request? Or is it limited to computation that was calculated directly on host machine?

Examples:

1. We provide DVM that gives weather data that were processed from external weather Rest API service

2. Text Summary DVM that gives summary after request them into external AI service (GPT4, Lllama3.1 405, etc) due to can't self host it

Both cases need external service

I see, it is quite hard for critical computation that need fast processing (< 100 ms) especially if the implementation can't be rewritten totally.

Based on your experiences, is it possible to generate zk proof for external API request?

Examples:

1. We provide DVM that gives weather data that were processed from external weather Red API service

Oh, I think many devs who are not familiar with ZK proof might choose second aproach due to minimum modification of the original code or they just can't due to all dependencies which hard to be rewriten all over. 😅

> However there is big overhead

Does it slow down much to generate the proof along the code? More than 1000ms?

Hi Abdel, thank you for giving showcase on using ZK Proofs as verifiable DVM. It is interesting case and love your work.

I have no experince yet integrate ZK Proofs in practical application. Given these following function:

https://github.com/atrifat/sentiment-analysis-api/blob/2f16b2ebbec2d2ded723cf00dccf4ef86a0367b3/app.py#L137

How do we implement ZK proofs in those "predict" function?

Congratulations, 🎉

Well, top relays with big traffic, can't be helped 😅

Update:

Will recently shared his dedicated server info for Damus Relay

nostr:nevent1qqs0dcf7243utuweq7fjxlezcrs282znkr73r2fhg0c6sqakeas0hmspzamhxue69uhhgetnwshxuenjv4kxz7fwv9c8qtcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzpmhxue69uhk2tnwdaejumr0dshsyspnxfjnzwpjxumrxdf5x5cx2cnzxd3n2cfhvscnyce3vcux2dmzxf3r2vf5xsenjctrxycxzd3hv4jkvvmy89nxgwtrx43nvwr9xg6r2cza9e6

Congratulations Tsururun-san, wish you in a good way 🎉

Nostrmo, parent of Yana 👀

I think Japanese users have been quite affected with limited Air-reply and other interactions 😅

It has 6 event/minute rule (note, like, zap, repost, any event) 😅

Are you okay, Takumi-san? Hopefully you are in good way 🫂

Yes, it sits like a proxy relay in front of its backend relay. Let me know your experieces self-host it 👀

Thank you Sherry 🫡

Yes, it depends on client whether they offer all the features to freely customized their feed settings. This relay can complement any filtering features that were probably not exist yet (language, sentiment, topic, user type, untagged non sfw content, etc) in the client.

Hopefully, all the features that were offered in nostr-filter-relay fully implemented in the client.

Yes, it can be integrated freely with any backend relay (nostream, nostr-rs-relay, and other relays). We just need to setup relay url config in env variable.

This repo only integrate several modules which can be replaced and customized individually.

cc nostr:nprofile1qqsxu35yyt0mwjjh8pcz4zprhxegz69t4wr9t74vk6zne58wzh0waycppemhxue69uhhjctzw5hx6ef0qythwumn8ghj7un9d3shjt3s0p3ksct59e3k7mf0qyt8wumn8ghj7mn0wd68ytndd9kx7afwd3hkctctqc4jq nostr:nprofile1qqs8d3c64cayj8canmky0jap0c3fekjpzwsthdhx4cthd4my8c5u47spzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7qg5waehxw309aex2mrp0yhxgctdw4eju6t0qy3hwumn8ghj7urjdau8jtt90pcx2unfd4jkuapwdah8yetwv3jhytnrdaks0duay6 nostr:nprofile1qqsverg89m7ucem0ewkpfakddqj7ms6hde27k7r292t4acp556szdjcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq32amnwvaz7tm9v3jkutnwdaehgu3wd3skueqknmcfe nostr:nprofile1qqsqxapvypwtdjxcvqcujw7y4xearpyycvkgv43lcr3p3yg29hu65hgpzemhxue69uhkummnw3ez6un9d3shjtnpwpcz7qgawaehxw309ahx7um5wgknqvfw09skk6tgdahxuefwvdhk6tcpzamhxue69uhkvun9deejumn0wd68yvfwvdhk6tc69d7cc nostr:nprofile1qqsqexc7nlhhdjytv0uxv3wuxwahwalsyk0vg8n8fdslflz48akmpcqpzamhxue69uhhxetpwf3kstnwdaejuar0v3shjtcpr9mhxue69uhkymmnw3ezumn0ddhhgctjduh8wmmjdvqs6amnwvaz7tmev9382tndv5yf5jj2 Thank you 🙏

nostr-filter-relay v0.3.0 update

"Browse global. Know that mostr exists. Follow lots of people. Nostr is NOT an echo chamber, if you use it right." (Gigi)

Thank you to our users and OpenSats for supporting this project 🤗.

This release bring new major features, modules updates, several code improvements, security fix, better documentation, and mark the completion of nostr-filter-relay features as follows:

- (New 🚀) Sentiment analysis filtering (Check USAGE.md)

- (New 🚀) Topic classification filtering (Check USAGE.md)

- Language filter

- NSFW/SFW image content filter

- User type filtering (Nostr native user/non bridged user, activitypub/mostr bridged user)

- Toxic comment filter

Feel free to check USAGE.md documentation to see more Examples on how to use nostr-filter-relay.

All filtering features can be easily disabled (opt-out) with parameters content=all :

wss://nfrelay.app/?content=all

One last major issue that will become next development target:

- NIP-32 Label Event Compatibility

What's Changed?

- Topic classification filtering support

- Sentiment filtering support

- Update nostr-monitoring-tool and nostr-filter dependencies

- Documentation of nostr-filter-relay new features

- All detail update for nostr-filter, nostr-monitoring-tool, and other modules were listed in release note link below

#NostrFilterRelay Release Note v0.3.0:

https://github.com/atrifat/nostr-filter-relay/releases/tag/v0.3.0

Glad to hear. 🫂