Nostr Web Client

Replying to

Vveerrgg

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

Reply to this note

Please Login to reply.

Discussion

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