| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Expire channels, too. | Owen Jacobson | 2024-09-28 |
| | | |||
| * | Delete expired messages out of band. | Owen Jacobson | 2024-09-28 |
| | | | | | | | | | Trying to reliably do expiry mid-request was causing some anomalies: * Creating a channel with a dup name would fail, then succeed after listing channels. It was very hard to reason about which operations needed to trigger expiry, to fix this "correctly," so now expiry runs on every request. | ||
| * | Assign sequence numbers from a counter, not by scanning messages | Owen Jacobson | 2024-09-28 |
| | | |||
| * | Push message body into its own object in events | Owen Jacobson | 2024-09-28 |
| | | |||
| * | Make `/api/events` a firehose endpoint. | Owen Jacobson | 2024-09-27 |
| It now includes events for all channels. Clients are responsible for filtering. The schema for channel events has changed; it now includes a channel name and ID, in the same format as the sender's name and ID. They also now include a `"type"` field, whose only valid value (as of this writing) is `"message"`. This is groundwork for delivering message deletion (expiry) events to clients, and notifying clients of channel lifecycle events. | |||
 |
index : pilcrow | |
| Run-It-Yourself web chat, maybe |
| summaryrefslogtreecommitdiff |