6 commits

Author	SHA1	Message	Date
oxalica	0c28c00c3d	refactor(webapi)!: put all API under path /_blah	2024-09-19 05:12:42 -04:00
oxalica	ab756f78ab	fix(frontend): fix parsing and validation of msgs	2024-09-19 05:11:48 -04:00
oxalica	a9ca9b976c	feat(frontend): impl register and fix	2024-09-17 21:44:36 -04:00
oxalica	73eb441a26	refactor(*): use term msg to replace item ... - `Msg` or `msg` is now the canonical term for the substructure in a room. It includes a `chat` subtype and (in the future) other administration subtypes like member joining or leaving. - `Message` or `message` can used in human oriented context like docs and comments, but only when it is unambiguous. - `message` is not chosen in code because it's hard to type (at least for me!), and have ambiguous meaning of: - "Human readable text" in context of `ApiError`'s field. - "A unit of data transfer, datagram" in context of WebSocket Message. - `item` is not chosen because it is overly generic.	2024-09-13 03:32:11 -04:00
oxalica	74c6fa6f6a	refactor(webapi): hoist RoomMetadata to blah_types and rename last_chat to last_item	2024-09-10 09:19:15 -04:00
oxalica	7160e5adbd	refactor: reorganize docs and aux files	2024-09-10 03:59:31 -04:00