pilcrow - Run-It-Yourself web chat, maybe

	Commit message (Collapse)	Author	Age
*	Return a flat message list on boot, not nested lists by channel.	Owen Jacobson	2024-10-09
\| \| \| \|	This is a bit easier to compute, and sets us up nicely for pulling message boot out of the `/api/boot` response entirely.
*	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.
*	Use `/api/boot` to bootstrap the client.	Owen Jacobson	2024-10-05
\| \| \| \| \| \| \| \| \| \| \|	The client now takes an initial snapshot from the response to `/api/boot`, then picks up the event stream at the immediately-successive event to the moment the snapshot was taken. This commit removes the following unused endpoints: * `/api/channels` (GET) * `/api/channels/:channel/messages` (GET) The information therein is now part of the boot response. We can always add 'em back, but I wanted to clear the deck for designing something more capable, for dealing with client needs.
*	Provide named operations for stored state.	Owen Jacobson	2024-10-05