summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Provide named operations for stored state.Owen Jacobson2024-10-05
|
* Turns out this flag does not do what I thought it didOwen Jacobson2024-10-05
|
* Merge branch 'wip/ui'Owen Jacobson2024-10-05
|\
| * Pre-commit needs the UI available, so make it available.Owen Jacobson2024-10-05
| |
| * Render the UI at /.Owen Jacobson2024-10-05
| |
| * Configure the SvelteKit build process to build a static site.Owen Jacobson2024-10-05
| | | | | | | | | | | | This is the [recommended] adapter for a single-page app. That's approximately how I expect to deploy the UI. [recommended]: https://kit.svelte.dev/docs/single-page-apps
| * Remove delete-message buttonsKit La Touche2024-10-05
| | | | | | | | They're badly styled and don't do anything yet anyway.
| * Merge branch 'main' into feature-frontendKit La Touche2024-10-04
| |\
| * | Add some FlowbiteKit La Touche2024-10-04
| | | | | | | | | | | | For the styling.
| * | Merge branch 'main' into feature-frontendKit La Touche2024-10-03
| |\ \
| * | | Handle basics of interface scrollingKit La Touche2024-10-03
| | | |
| * | | Absorb and display eventsKit La Touche2024-09-30
| | | | | | | | | | | | | | | | | | | | At least message-type ones, and at least without styling or memory-limit concerns.
| * | | Merge branch 'main' into feature-frontendKit La Touche2024-09-30
| |\ \ \
| * | | | Move layout concerns into layoutKit La Touche2024-09-30
| | | | |
| * | | | Merge branch 'main' into feature-frontendKit La Touche2024-09-28
| |\ \ \ \
| * | | | | Make message input tolerable as mock-upKit La Touche2024-09-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's not robust, and it's not yet able to handle multiline or rich input. We'll get there.
| * | | | | Add lots of style and layoutKit La Touche2024-09-27
| | | | | |
| * | | | | Add basic browser clientKit La Touche2024-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!
* | | | | | Dependency update.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Replace `unsafe` impl of backups with `rusqlite`.Owen Jacobson2024-10-05
| | | | | | | | | | | | | | | | | | | | | | | | The unsafe code still exists, but I have more faith in the rusqlite authors than in myself to ensure that the code is correct.
* | | | | | Implement `sqlite3_backup_step`'s multi-step protocol.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Use the right functions for determining error messages.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Improve ergonomics of `Backup`Owen Jacobson2024-10-05
| | | | | |
* | | | | | Limit unsafe{} blocks even more tightly.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Remove an unchecked operation in favour of a panicOwen Jacobson2024-10-05
| | | | | |
* | | | | | Wrote down the DB recovery processOwen Jacobson2024-10-05
| | | | | |
* | | | | | Tighten up `unsafe{}` blocks in backup logic.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Use sqlx's API, not SQL groveling, to find unwanted migrations.Owen Jacobson2024-10-05
| | | | | |
* | | | | | Make a backup of the `.hi` database before applying migrations.Owen Jacobson2024-10-05
| | | | | | | | | | | | | | | | | | | | | | | | This was motivated by Kit and I both independently discovering that sqlite3 will happily partially apply migrations, leaving the DB in a broken state.
* | | | | | Start fresh with database migrations.Owen Jacobson2024-10-04
| |_|_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | The migration path from the original project inception to now was complicated and buggy, and stranded _both_ Kit and I with broken databases due to oversights and incomplete migrations. We've agreed to start fresh, once. If this is mistakenly started with an original-schema-flavour DB, startup will be aborted.
* | | | | Clean up naming and semantics of history accessors.Owen Jacobson2024-10-04
| |_|_|/ |/| | |
* | | | Stray warningsOwen Jacobson2024-10-03
| | | |
* | | | List messages per channel.Owen Jacobson2024-10-03
| | | |
* | | | Add endpoints for deleting channels and messages.Owen Jacobson2024-10-03
| | | | | | | | | | | | | | | | It is deliberate that the expire() functions do not use them. To avoid races, the transactions must be committed before events get sent, in both cases, which makes them structurally pretty different.
* | | | Represent channels and messages using a split "History" and "Snapshot" model.Owen Jacobson2024-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 InstantOwen Jacobson2024-10-02
| | | |
* | | | Retire top-level `repo`.Owen Jacobson2024-10-02
| | | | | | | | | | | | | | | | This helped me discover an organizational scheme I like more.
* | | | Split login and token handling.Owen Jacobson2024-10-02
| | | |
* | | | First pass on reorganizing the backend.Owen Jacobson2024-10-02
| | | | | | | | | | | | | | | | This is primarily renames and repackagings.
* | | | Organize IDs into top-level namespaces.Owen Jacobson2024-10-01
| | | | | | | | | | | | | | | | (This is part of a larger reorganization.)
* | | | Provide a resume point to bridge clients from state snapshots to the event ↵Owen Jacobson2024-10-01
| | | | | | | | | | | | | | | | sequence.
* | | | Track event sequences globally, not per channel.Owen Jacobson2024-10-01
| | | | | | | | | | | | | | | | Per-channel event sequences were a cute idea, but it made reasoning about event resumption much, much harder (case in point: recovering the order of events in a partially-ordered collection is quadratic, since it's basically graph sort). The minor overhead of a global sequence number is likely tolerable, and this simplifies both the API and the internals.
* | | | Prevent racing between `limit_stream` and logging out.Owen Jacobson2024-10-01
| |_|/ |/| |
* | | Reimplement the logout machinery in terms of token IDs, not token secrets.Owen Jacobson2024-09-29
| | | | | | | | | | | | | | | | | | This (a) reduces the amount of passing secrets around that's needed, and (b) allows tests to log out in a more straightforwards manner. Ish. The fixtures are a mess, but so is the nomenclature. Fix the latter and the former will probably follow.
* | | Shut down the `/api/events` stream when the user logs out or their token ↵Owen Jacobson2024-09-29
| |/ |/| | | | | | | | | | | | | expires. When tokens are revoked (logout or expiry), the server now publishes an internal event via the new `logins` event broadcaster. These events are used to guard the `/api/events` stream. When a token revocation event arrives for the token used to subscribe to the stream, the stream is cut short, disconnecting the client. In service of this, tokens now have IDs, which are non-confidential values that can be used to discuss tokens without their secrets being passed around unnecessarily. These IDs are not (at this time) exposed to clients, but they could be.
* | Wrap credential and credential-holding types to prevent `Debug` leaks.Owen Jacobson2024-09-28
| | | | | | | | | | | | | | | | | | | | | | | | The following values are considered confidential, and should never be logged, even by accident: * `Password`, which is a durable bearer token for a specific Login; * `IdentitySecret`, which is an ephemeral but potentially long-lived bearer token for a specific Login; or * `IdentityToken`, which may hold cookies containing an `IdentitySecret`. These values are now wrapped in types whose `Debug` impls output opaque values, so that they can be included in structs that `#[derive(Debug)]` without requiring any additional care. The wrappers also avoid implementing `Display`, to prevent inadvertent `to_string()`s. We don't bother obfuscating `IdentitySecret`s in memory or in the `.hi` database. There's no point: we'd also need to store the information needed to de-obfuscate them, and they can be freely invalidated and replaced by blanking that table and asking everyone to log in again. Passwords _are_ obfuscated for storage, as they're intended to be durable.
* | Clean up use of bare tuple as a vector element for ResumePoint.Owen Jacobson2024-09-28
| |
* | Expire channels, too.Owen Jacobson2024-09-28
| |
* | Delete expired messages out of band.Owen Jacobson2024-09-28
| | | | | | | | | | | | | | | | Trying to reliably do expiry mid-request was causing some anomalies: * Creating a channel with a dup name would fail, then succeed after listing channels. It was very hard to reason about which operations needed to trigger expiry, to fix this "correctly," so now expiry runs on every request.
* | Assign sequence numbers from a counter, not by scanning messagesOwen Jacobson2024-09-28
| |
generated by cgit v1.2.3 (git 2.39.1) at 2026-01-02 18:03:29 +0000