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
\|
*	All kinds of styling	Kit La Touche	2024-10-08
\|
*	Style more things	Kit La Touche	2024-10-08
\|
*	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.
*	Handle basics of interface scrolling	Kit La Touche	2024-10-03
\|
*	Absorb and display events	Kit La Touche	2024-09-30
\| \| \| \| \|	At least message-type ones, and at least without styling or memory-limit concerns.
*	Move layout concerns into layout	Kit La Touche	2024-09-30
\|
*	Add lots of style and layout	Kit La Touche	2024-09-27
\|
*	Add basic browser client	Kit La Touche	2024-09-27
	Using Svelte. No tests, no linting, yet. This is just starting to get familiar with things. You'll still have to run the dev server and the dev client builder each in their own terminals. Enjoy!