Nostr Web Client

If there are any board JavaScript developers out there that want to build a nostr thing and earn sats. I'm officially putting up a bounty to integrate rx-nostr into node-red

I'm offering 100k sats to anyone who will build and publish a working rx-nostr -> node-red integration

It needs to fulfill the following requirements

- Easy to install ( should be searchable in the UI )

- Support for all options in `createRxNostr` including signer and default relays

- Support for creating subscriptions using `createRxForwardReq`

- Events returned from subscriptions should be node-red messages

- A node for easily publishing an event to the default or custom set of relays ( using `rxNostr.send` )

50k bonus if you can also create a package that integrates applesauce EventStore into node-red

- Configuration node for creating a global EventStore

- Query node for subscribing to the store using one of the Queries

I don't know if I'm asking too much but I really want to see this built. I think we could do a lot of bot / DVM prototyping if we had a way to use nostr in node-red

For example. if we had both of these integrations it would be easy to setup a node-red flow that would

- Connect to a set of relays and listen for events (kind 1 mentions)

- Do some work with new events

- Easily respond using applesauce factory to create a reply event

- repeat... ( profit? )

sites:

rx-nostr https://penpenpng.github.io/rx-nostr/

node-red https://nodered.org/

applesauce https://hzrd149.github.io/applesauce/core/event-store.html

Reply to this note

Please Login to reply.

Discussion

Vveerrgg 1y ago

Oh Yaah? I’m looking to earn Sats to dev … been sharpening my skills on some utilities so I can build stuff useful for our world here.

brugeman 1y ago

Adding 100k on top

Vveerrgg 1y ago

so would a couple of useful usecases for this be ...

Event Archival - Archive specific types of Nostr events for later analysis.

-Flow Description

```

[Nostr Subscribe] → [Event Filter] → [Transform] → [EventStore Save] → [Query API]

```

### Implementation Details

- Subscribe to multiple event kinds

- Filter events based on content or tags

- Transform events into desired format

- Store in Applesauce EventStore

- Provide query endpoints for data analysis

-- or something like --

Automated Response System - Create automated responses based on event patterns.

### Flow Description

```

[Nostr Subscribe] → [Pattern Matcher] → [Response Generator] → [Nostr Publish]

```

### Implementation Details

- Define trigger patterns (keywords, commands)

- Create response templates

- Support for dynamic content insertion

- Rate limiting and spam prevention

- Store interaction history

I'm starting to mock something together and from the top of my head ... these seem like useful actions.

hzrd149 1y ago

something closer to the Automated Response System would be a good start. I'd imagine building the Query API could be difficult and wouldn't really be that useful since most of the use-cases I have in mind would only deal with nostr relays

Vveerrgg 1y ago

… ya I’m wondering if this is as much a NodeRed service as much as a simple node/express server that uses Postgres (or Supabase) for data management & just listens to a handful of relays & performs an action as configured by the user / request maker.

Eg. listen for user nPUB on kind # containing #keyword trigger #action

hzrd149 1y ago

It could be its own thing, but that's not really what I'm asking for.

I only want a way to subscribe to relays using rx-nostr in node-red and then publish new events

My goal is to build various custom bots that I run on my raspberry pi at home

brugeman 1y ago

Bounty!

nostr:nevent1qqsrgfff70htlm9wtrcaz3mmdcrmdzlvapctev6dj33az7tkam47hqqpz9mhxue69uhkummnw3ezuamfdejj7q3qye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjsxpqqqqqqztu5m7v

சாரு-秋陽 1y ago 💬 1

nostr:nprofile1qqsgckfrjvvkxluhuqra45xks8n9ec6mrt8rxwmznckn872xtsfjvzqpp4mhxue69uhhjctzw5hx6egpzamhxue69uhkummnw3ex2ctd9ehkx6rp9ehkuegprfmhxue69uhkuun9d3shjtnr94ehgetvd3shytnwv46q54nmc0-san, did you know about this?

nostr:nevent1qqsrgfff70htlm9wtrcaz3mmdcrmdzlvapctev6dj33az7tkam47hqqppemhxue69uhkummn9ekx7mp0qgszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgrqsqqqqqp7eeewj

Vveerrgg 1y ago

so this node flow ... what are we thinking for Access Options?

- Headless: flows can run as backend services without any UI

- API Endpoints: an exposed HTTP endpoints from a pre-configured flow

- Custom UI: including a built frontend that communicates with your flows

- Dashboard: a node-red-dashboard with all the state / config views?

... if were talking fast and dirty, I'd probably try and do a headless / API version ... but I'll need a bit of context on what ya'llz thinking.

hzrd149 1y ago

Headless is probably the most useful. I'd like to be able to build simple bots using it so it doesn't need and API or a dashboard ui

Vveerrgg 1y ago

So … if a service had a server that you request a DM magic link from … and it provided you a URL login to a dashboard … might that work?

With the underlying headless NodeRed service open sourced & available… would that be sat worthy?

Vveerrgg 1y ago

... for anyone else looking to see the results of this ... I got this plugin put together over the past couple of days / week. I'm still VERY green to NodeRED & dev'ing for SATs ...

... but if you find use in it , or have suggestions on ways to improve it ... I'm open to the feedback. AND if you wanna zap a bit ... I'm also up for that.

https://github.com/HumanjavaEnterprises/node-red-contrib-nostr