Feature Request: Calendar

[KentuckyFriedBlyat]

Specialized calendar channel / room where events can be coordinated, users can flag themselves as going to attend scheduled events, auto ping them 15 minutes before, etc.

Ability to flag event as repeatable (daily, weekly, monthly, etc) , one time only, and so on.

[ancsemi]

Appreciate the idea! This is a cool concept, but it leans pretty heavily into "app within an app" territory. A full calendar system with recurring events, RSVPs, auto-reminders, etc. would be a pretty big scope expansion for a chat platform.

Something like this would probably work better as a standalone tool or a bot integration that posts event reminders to a channel. I'll leave this open for now in case anyone has thoughts, but it's not something I plan to build into Haven directly.

[AlexT2803]

If your still looking for this functionality i can share my / bot code that does this.

[Amnibro]

Calendar channels are doable as a new channel type rather than a parallel feature — that lets them inherit channel permissions, role gating, and the existing org / drag-reorder infra for free.

Sketching what I'd do if I picked this up:

Schema (one new table + one column):

```sql
ALTER TABLE channels ADD COLUMN type TEXT DEFAULT 'text'; -- 'text' | 'voice' | 'calendar' | future...

CREATE TABLE channel_events (
id INTEGER PRIMARY KEY AUTOINCREMENT,
channel_id INTEGER NOT NULL REFERENCES channels(id) ON DELETE CASCADE,
title TEXT NOT NULL,
description TEXT DEFAULT '',
start_at DATETIME NOT NULL,
end_at DATETIME,
rrule TEXT, -- RFC-5545 RRULE for repeats; NULL = one-off
created_by INTEGER NOT NULL REFERENCES users(id),
created_at DATETIME DEFAULT CURRENT_TIMESTAMP
);

CREATE TABLE channel_event_rsvps (
event_id INTEGER NOT NULL REFERENCES channel_events(id) ON DELETE CASCADE,
user_id INTEGER NOT NULL REFERENCES users(id) ON DELETE CASCADE,
status TEXT NOT NULL, -- 'going' | 'maybe' | 'not_going'
PRIMARY KEY (event_id, user_id)
);
```

Reminders: ride on the existing FCM infra. Server background loop ticks once a minute, finds events where start_at is between (now+14m, now+15m) and the user is RSVP'd going, fires push. Same loop also expires next_occurrence for RRULE events using the existing rrule lib.

UI: the calendar channel renders as a month/week grid in the main pane instead of the message list (the channel type selects the renderer). Day cells are clickable; per-event detail modal has RSVP buttons + the host's description in markdown.

Permissions: `create_event` (channel-level), `manage_event` (server-level), `rsvp` (default-on for any channel member).

Repeats: RRULE strings are well-understood and there's a maintained Node lib (`rrule`). Daily/weekly/monthly cover 99% of asks; full RFC-5545 support is overkill but free with the lib.

Mid-size feature — a few thousand LOC including the calendar grid renderer, but each piece is self-contained. Let me know if this is the direction you'd want and I'll open a tracking issue + put up an initial PR with schema + a stub channel renderer.

[AlexT2803]

I personally think this would be cool functionality (im currently managing this with a bot) but given the scope it seems like this is down to @ancsemi