| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Provide a view of logins to clients. | Owen Jacobson | 2024-10-09 |
| | | |||
| * | Simplify channel IDs in events. Remove redundant ones. | Owen Jacobson | 2024-10-09 |
| | | |||
| * | Use a two-tier hierarchy for events. | Owen Jacobson | 2024-10-09 |
| | | | | | This will make it much easier to slot in new event types (login events!). | ||
| * | Flatten nested `channel` and `message` structs in events and API responses. | Owen Jacobson | 2024-10-09 |
| | | | | | This structure didn't accomplish anything and made certain refactorings harder. | ||
| * | 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. | |||
 |
index : pilcrow | |
| Run-It-Yourself web chat, maybe |
| summaryrefslogtreecommitdiff |