| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Separate `/api/boot` into its own module. | Owen Jacobson | 2024-10-05 |
| | | |||
| * | List messages per channel. | Owen Jacobson | 2024-10-03 |
| | | |||
| * | Represent channels and messages using a split "History" and "Snapshot" model. | Owen Jacobson | 2024-10-03 |
| | | | | | | | This separates the code that figures out what happened to an entity from the code that represents it to a user, and makes it easier to compute a snapshot at a point in time (for things like bootstrap). It also makes the internal logic a bit easier to follow, since it's easier to tell whether you're working with a point in time or with the whole recorded history. This hefty. | ||
| * | Package up common event fields as Instant | Owen Jacobson | 2024-10-02 |
| | | |||
| * | Retire top-level `repo`. | Owen Jacobson | 2024-10-02 |
| | | | | | This helped me discover an organizational scheme I like more. | ||
| * | Transmit messages via `/:chan/send` and `/:chan/events`. | Owen Jacobson | 2024-09-13 |
| | | |||
| * | Remove the notion of "channel members." | Owen Jacobson | 2024-09-11 |
| | | | | | | | This came out of a conversation with Kit. Their position, loosely, was that seeing scrollback when you look at a channel is useful, and since message delivery isn't meaningfully tied to membership (or at least doesn't have to be), what the hell is membership even doing? (I may have added that last part.) My take, on top of that, is that membership increases the amount of concepts we're committed to. We don't need that commitment yet. | ||
| * | Support joining channels. | Owen Jacobson | 2024-09-04 |
| | | |||
| * | Support leaving a channel | Owen Jacobson | 2024-09-04 |
| | | |||
| * | Allow any login to create channels. | Owen Jacobson | 2024-09-04 |
