Community events
From mnema-talk v3.3.13, rendered on this site.
Community events let organizers schedule voice hangouts or server-wide activities, gather RSVPs, and remind members before start. The server advertises the feature as events in the features list of GET /api/health; web clients hide the events interface when the flag is absent.
Overview
- Sidebar entry: An Events link appears at the top of the channel sidebar, showing a count badge of upcoming events. Clicking it opens the Events list dialog.
- Events list & detail: Members can browse upcoming and past events, view full details, read markdown descriptions, see participant counts, and RSVP.
- Access control: An event's location can be either a Talk (voice channel) or free text. When linked to a Talk, only members with View channels on that Talk can see the event, view its cover image, or RSVP. Free-text location events are visible to all server members.
Past events
The Past tab lists events that are over (completed, cancelled, or ended), newest first, and loads older ones with Show older events. It uses GET /api/events?when=past with limit (1 to 200) and the cursor before / before_id: the start time and id of the last event of the previous page. Visibility is the same as for upcoming events: an event in a Talk shows only to members who may view that channel. Without when the endpoint keeps returning the window from one day ago to 90 days ahead.
Managing events
Creating, editing, cancelling events, or uploading cover images requires the Manage events permission (1 << 25 in internal/perm). Administrators and the Owner have it implicitly. On upgrade and on a new server it is granted to every role that holds Timeout members (the seeded Moderator and Admin roles); grant or remove it for other roles in the role settings. @everyone does not have it.
- Title: Up to 100 characters.
- Description: Up to 2,000 characters of Markdown (same formatting as chat messages).
- Start & End time: ISO 8601 timestamps. Start time is required; optional end time must be at or after start time.
- Location: Either a voice channel (Talk) within the server or custom free text (up to 255 characters). A conversation's call Talk is no community channel and cannot be a location, on create or on edit: it is refused (
400) exactly like a channel that does not exist, so that nothing about the call reaches the event lists or the audit log. - Cover image: Optional 3:1 banner image (PNG, JPEG, GIF or WebP up to 5 MB), processed through the same pipeline as profile banners (re-encoded, metadata stripped).
RSVPs and reminders
Members who can view an event can submit their RSVP:
- Going: Indicates attendance. The event dialog displays going member avatars and count.
- Interested: Expresses interest.
- Not going: Declines attendance.
Reminders
15 minutes before an event starts, the server automatically delivers a reminder notification (in-app notification and Web Push) to every member who RSVP'd going or interested. Reminders respect member notification settings, including Do Not Disturb and muted channels.
Roles and waitlist
An event can have roles with places, for example a raid with Tank, Heal and DPS. The server advertises the feature as events.roles in GET /api/health; the web app hides the role UI without it.
- Roles: up to 12 per event, each with a name (up to 40 characters, unique within the event), an optional emoji, a capacity of 1 to 1,000 or none (unlimited) and a position. The event dialog lists them as cards with their fill (
3/5) and the members. - Sign-up: everyone who can view the event signs up for one role while it is scheduled or active (
PUT /api/events/{id}/signup). A sign-up counts as RSVP going; leaving keeps the RSVP as it is. Signing up for another role moves the member over. - Waitlist: a full role puts the next sign-up on its waitlist (
state: waitlist, with the place in line). When a place frees (the member leaves or is removed, switches role, or the capacity grows), the oldest waitlisted member moves up first in, first out, in the same transaction, and is told in-app and by Web Push (event_signup_notice; do-not-disturb and a muted Talk hold the push back). A scheduler pass moves members up where a place was freed without a request, for example after an erased account. - No overbooking: every roster change locks the event's role rows, so the last place is never given twice.
- Who changes the roster: the creator of the event and members with Manage events set the roles (
PUT /api/events/{id}/roles, replaces the list;DELETE /api/events/{id}/roles/{roleID}) and remove sign-ups (DELETE /api/events/{id}/signup/{userID}; the member is told). A capacity below the confirmed members is refused with 409 naming how many to remove; a role that still has sign-ups is removed only with?move_to=<other role>, which takes them over. Leaving (DELETE /api/events/{id}/signup) is always allowed. A completed or cancelled event keeps its roster read-only. - Visibility: the roster follows the event: members who cannot view the event's Talk neither see nor change it and are told nothing.
GET /api/events/{id}carriessignups; the list and the live updates carryroleswith the counts and the caller's ownmy_signuponly in answers to the caller's requests. - Role templates: sets of roles to start from (
GET /api/event-role-templates). Members see only the templates an administrator enabled. Two presets (Party of five, Raid of ten) ship disabled; administrators enable or disable them, create their own and delete custom ones (POST/PATCH/DELETE, audited asevent.role_template_*). Nothing shows to members until then. - Audit, erasure and export: role and roster changes are audited as
event.edit(event.talk_editin a Talk) with arosterdetail. Erasing an account deletes its sign-ups;event_signups.jsonin the account export lists a member's own.
Comments
Every event has a flat discussion under it (no replies).
- Model: a comment has a text of 1 to 2,000 characters; an event keeps at most 500 comments and one member at most 50 of them, so nobody fills the thread alone (the next one answers
409). Comments stay open after an event is completed and close when it is cancelled (409; reading, deleting and muting stay). Posting and editing are rate limited to 10 a minute per member (429). Comments are plain text with the chat's Markdown. - API:
GET /api/events/{id}/commentsreturns the newest page, oldest first (beforenames the oldest comment already loaded;has_moresays older ones exist;mutedis the caller's own setting);POSTadds a comment,PATCH /api/events/{id}/comments/{commentID}changes the author's own text (shown as edited),DELETEremoves one,PUT /api/events/{id}/comments/muteswitches the notices off or on. - Permissions: everyone who can view the event reads it. Commenting and editing need Send messages like a chat message (in the event's Talk when it has one), so a timeout, rules not yet accepted and a new member's hold refuse them (
403,RULES_NOT_ACCEPTED); deleting and muting stay open. Automod screens a comment and an edit like a message in the event's Talk (400from a blocking rule; see Automod), and so it screens an event's title, description and location. Authors edit and delete their own comments; the event's creator and members with Manage events or Manage messages (both server-wide) delete any (audited asevent.comment_delete,event.talk_comment_deletein a Talk; not at all for an event of a conversation's call Talk, which can only exist from before such a location was refused). Nobody edits another member's words. - Live and notices: a created, edited or deleted comment is announced to everyone who may see the event (
event_comment); open lists follow. The event's creator and everyone who answered going or interested or holds a role are told about a new comment (event_comment_noticeand Web Push, which respects do-not-disturb, focus and a muted Talk), except the author, members who switched the event's comment notices off and members who blocked the author. The creator comes first, then those who go or hold a role, then those who are interested. Do-not-disturb, focus and a muted Talk hold the toast back as well as the push. Up to 5,000 members are considered in that order, those who may not view the Talk are dropped, and the first 1,000 are told (pushes go out through a few workers). A member who cannot view the Talk is told nothing. The notices go out in the background, not while the author waits. - Erasure and export: erasing an account deletes the member's comments and mute settings; the export holds the comments in
event_comments.jsonand the mutes inevent_comment_mutes.json.
Recurring events
An event can repeat every week, every two weeks or every month. The first event is created as usual, with a recurrence (frequency: weekly, biweekly or monthly; timezone, the IANA time zone of the person who sets it up, UTC when omitted; an optional until); it is the first occurrence of a series. Occurrences are ordinary events (reminders, RSVPs, roles, comments, the audit log all work as before), each marked with its series (series.index, series.frequency, series.ended).
- Time rule: every start is counted from the series' anchor (the first start, later the start set by an edit of the following events) in the series' time zone, so a 19:00 event stays at 19:00 across the change to or from summer time. A monthly series keeps the day of the month and falls back to the last day of a shorter month (the 31st becomes the 28th), counted from the anchor, so a short month moves nothing after it.
- Creation: the server creates the occurrences of the next 60 days when the series is made and then once every ten minutes as time passes. A series has at most 200 occurrences and none starts after
until. Occurrences that would start in the past (after a long downtime) are skipped, not created late. - Scope of a change:
PATCH /api/events/{id},POST /api/events/{id}/cancelandPUT /api/events/{id}/rolestakescope=this(default) orscope=following;followingon an event without a series answers400.- Edit, following: the occurrence and every later open one take the edit, and the series' template changes with it, so later occurrences carry it too. A new
start_timebecomes the new anchor: the edited occurrence takes it and the later ones keep their distance in the series' frequency and zone. Earlier occurrences, cancelled and finished ones stay as they are. - Cancel, following: the occurrence and every later open one are cancelled and the series ends there.
- Roles, following: the list becomes the template of occurrences created later and replaces the roles of later open occurrences that have no sign-ups; those with sign-ups keep their roles.
- This only: the one event changes and stays in its series; a later edit of the following events overwrites such a one-off change.
- Edit, following: the occurrence and every later open one take the edit, and the series' template changes with it, so later occurrences carry it too. A new
- Sign-ups: role definitions are copied to every occurrence, sign-ups and RSVPs never carry over.
- Web: the new-event dialog has a "Repeat" choice (when the server lists
events.recurrence); editing, cancelling or setting the roles of an occurrence asks whether it applies to this event only or to it and all following events. Events of a series show "Repeats every week" and so on. - GDPR: a series holds nothing personal besides its creator, which is set to empty when the member's account is erased.
Active events and joining Talks
When an event's start time arrives:
- The event's status automatically transitions from
scheduledtoactive. - If the event takes place in a Talk channel, members see a Join Talk button that immediately connects to the voice channel (subject to normal channel join permissions).
- After the scheduled end time (or two hours after start if no end time was set), active events transition to
completed.
Privacy and audit logging
- Audit log: Changes are recorded in the audit log under the actions
event.create,event.edit, andevent.cancel. - Account erasure (GDPR): When a member deletes their account or an operator erases it, the member's RSVPs are purged immediately, and any events they created have their creator field set to NULL.
- Account export: When exporting personal data (
POST /api/users/me/export), the member's own RSVPs are included inrsvps.json. Events and series the member created are community content: they are not part of the export and stay after an erasure with their creator set to empty.