Consider keeping CreateActivityDialog for unticketed/unapproved community events #29

New issue

Open

opened 2026-04-27 16:13:25 +00:00 by padreug · 0 comments

padreug commented

2026-04-27 16:13:25 +00:00

Owner

Context

The activities module now has two event creation paths:

CreateEventDialog — submits to LNbits events extension via POST /events/propose, goes through admin approval, supports ticketing. This is the primary path.
CreateActivityDialog — publishes NIP-52 calendar events directly to Nostr relays, no approval needed, no ticketing. Currently being replaced by CreateEventDialog.

Proposal

Keep CreateActivityDialog for a "community events" section where users can publish lightweight, unticketed events directly to Nostr without admin approval. These would be informal announcements (e.g., "Pickup soccer game at the park, Saturday 3pm") vs formal ticketed events.

Considerations

How to differentiate in the UI: "Propose Event" (goes through approval) vs "Share Activity" (direct to Nostr)
Whether community events should also be discoverable in the activities feed alongside approved events
Relates to aiolabs/webapp#25 (task vs activity disambiguation) — community events need their own category/tagging

## Context The activities module now has two event creation paths: 1. **CreateEventDialog** — submits to LNbits events extension via `POST /events/propose`, goes through admin approval, supports ticketing. This is the primary path. 2. **CreateActivityDialog** — publishes NIP-52 calendar events directly to Nostr relays, no approval needed, no ticketing. Currently being replaced by CreateEventDialog. ## Proposal Keep CreateActivityDialog for a "community events" section where users can publish lightweight, unticketed events directly to Nostr without admin approval. These would be informal announcements (e.g., "Pickup soccer game at the park, Saturday 3pm") vs formal ticketed events. ## Considerations - How to differentiate in the UI: "Propose Event" (goes through approval) vs "Share Activity" (direct to Nostr) - Whether community events should also be discoverable in the activities feed alongside approved events - Relates to aiolabs/webapp#25 (task vs activity disambiguation) — community events need their own category/tagging

padreug added the

app:activities

enhancement

labels

2026-05-17 21:24:06 +00:00

padreug referenced this issue from a commit

2026-05-29 20:17:22 +00:00

chore(api): remove User.prvkey field + thread-through helpers (Q1.2 Option b)

padreug referenced this issue

2026-05-29 20:18:30 +00:00

chore(api): remove User.prvkey field + thread-through helpers (Q1.2 Option b) #84

padreug referenced this issue from a commit