about summary refs log tree commit diff
path: root/kittybox-rs/src
Commit message (Collapse)AuthorAgeFilesLines
* webmentions: check webmentions and save them to the databaseVika2023-07-222-6/+183
|
* database: add "add_or_update_webmention" operationVika2023-07-224-0/+168
| | | | | | | This is an operation that atomically adds or updates a webmention cite attached to a post. This is used so a database backend can optimize for it (for example, using a transaction or shifting the JSON modification operation to the database)
* postgres: optimize fetching of non-feeds by forgoing a second queryVika2023-07-221-0/+9
|
* Allow loading TLS root certificates from fileVika2023-07-211-7/+33
| | | | | Untested, but will be useful when testing Webmentions in the end-to-end test.
* Split Postgres schemas into twoVika2023-07-212-12/+16
| | | | | Now the postgres schemas are completely independent of each other. This took a while to figure out!
* Move MentionType into util and fix bugs in -check-webmention appVika2023-07-211-12/+12
|
* Put Micropub background processing tasks in a JoinSetVika2023-07-173-28/+71
| | | | | | | This allows using tree-structured concurrency to keep background tasks in check and allow them to finish running before shutting down β€” a necessary prerequisite for shutdown-on-idle. (A background task may take a bit too long to complete, and we may need to wait for it.)
* database/file: tokio::fs::create_dir_all is idempotentVika2023-07-171-6/+3
|
* FileStorage: properly fsync() files and directoriesVika2023-07-171-9/+21
| | | | | | Total crash-safety. Yank the power cord all you want, your data is going to be safe and sound. (Unless your drive controller lies to you about flushing its caches)
* WIP: bind to UNIX socketsVika2023-07-171-13/+36
| | | | | | Apparently this requires a helper crate to make Hyper aware of UNIX sockets. That's fine. That's not a priority for now β€” but the code is practically there.
* Allow listening on several TCP socketsVika2023-07-171-46/+117
| | | | | | | | I would also love to be able to listen on Unix stream sockets, but that would require some additional support that can thankfully be just introduced later. (It also requires a second loop over the file descriptor array)
* cargo update, part 2: AxumVika2023-07-175-26/+31
| | | | | | | | | Axum got some breaking changes and gained some nice features β€” however, features come later, breaking changes come first. Perhaps it would be nice to actually construct a State with all of my stuff, and then make functions generic over that. Could reduce the amount of generic stuff I am producing... maybe.
* cargo update, part 1Vika2023-07-172-10/+10
|
* webmentions/queue: move JobQueue trait into kittybox-utilVika2023-07-092-47/+128
| | | | | | | The trait itself seems basic enough that it could be reused elsewhere. Better to keep it in a separate crate. `-util` is a dumping ground for various things anyway.
* webmentions/supervisor: ability to cancel a background taskVika2023-07-091-13/+54
| | | | | | | | This requires the background task to be cancellation-safe, as it is dropped after receiving a cancellation event. Perhaps in the future there will be a supervisor version that may forward the cancellation to the task itself.
* webmentions/queue: give up on an item after 5 attemptsVika2023-07-092-17/+63
| | | | | | This also involves a crude "async drop" implementation that fires a future incrementing an attempt if a Job has been dropped without marking it as done.
* New debug utilities to test checking webmentions and parsing mf2Vika2023-07-092-0/+201
|
* WIP: incoming webmention supportVika2023-07-091-0/+75
|
* Create a job queue based on PostgresVika2023-07-091-0/+179
| | | | | It's generic enough to be used for anything, but for now it's only gonna be used for webmentions.
* micropub: a little bit more loggingVika2023-07-091-0/+2
|
* kittybox-indieauth-helper: move client_id to a real pageVika2023-07-091-1/+1
| | | | | This allows to use the helper on production websites that do security checks on redirect URIs, as the URI is now properly declared.
* Implement Postgres backendVika2023-07-093-0/+440
| | | | | | | A single giga-commit that took me weeks to produce. I know, this is not exactly the best thing ever β€” but I wanted to experiment first before "committing" to the implementation, so that I would produce the best solution.
* main: use tracing_tree in debug buildsVika2023-07-091-1/+9
| | | | | | This gives me much more readable traces. JSON logging is still superior in production, where logs are stored in systemd-journald and preferably need to be self-contained lines.
* indieauth/backend/fs: debug tracingVika2023-07-091-1/+6
|
* database/memory: cleaner update_post implementationVika2023-07-091-1/+70
| | | | | | | | | | | | This one manages to avoid extraneous allocations as much as possible, by deconstructing the update into pieces and using a mutable reference taken directly from the hashmap in which the posts are stored. Now if only this hashmap were to be serialized on Drop, we could even have persistence in the database and therefore gain another backend that requires no dependencies to run, just like FileStorage, but avoids extraneous file access (or maybe shunts it into the background?)
* frontend: filter out privacy-sensitive information from postsVika2023-07-091-2/+124
| | | | | This was the job of the database before. Now the frontend should do it before passing the post to the templates.
* database{,/file}: clean up code, add documentation and loggingVika2023-07-092-206/+215
| | | | | | | | | | | | `filter_post` is now out of here and moved into the frontend. This kind of non-intrusive filtering can be done on the frontend, and the database need not concern itself with this. It can still be done as an optimisation... probably? but the frontend is going to sanitize things like location in the post by itself now, so it is not required anymore (and might be harmful, if frontend starts indicating that there are some hidden fields by replacing them with placeholders that ask one to log in to view information).
* fixup! database: add add_to_feed and remove_from_feedVika2023-07-081-2/+2
|
* onboarding: fix improper usage of the put_post APIVika2023-07-081-1/+5
|
* micropub: use the new, better typed updates internallyVika2023-07-014-172/+53
|
* Better Micropub update object typingVika2023-06-221-4/+13
|
* database: more realistic pagination testVika2023-06-221-1/+7
| | | | | | We insert published time into all objects anyway, and expect feeds to be ordered by publishing time. We should let databases rely on that assumption when returning feeds.
* database: add add_to_feed and remove_from_feedVika2023-06-222-2/+9
| | | | | Some database backends may have optimized ways of tracking feed contents. Others might just use the "children" property directly.
* database: use domains instead of authorities as owner keyVika2023-06-225-41/+65
| | | | | This allows disregarding http/https comparisons and simplifies some database designs.
* database: introduce read_feed_with_cursorVika2023-06-224-9/+39
| | | | | read_feed_with_cursor allows using an arbitrary string as a cursor, unlike read_feed_with_limit, which uses last post's UID as a cursor.
* StorageError: use std::borrow::Cow for msg fieldVika2023-06-223-21/+36
| | | | | This allows avoiding an unnecessary allocation whenever the error message is static.
* main: refactor Kittybox constructionVika2023-06-225-192/+204
| | | | | | This allows proper separation of backend initialization and Kittybox construction code. Some boilerplate is still present, but there's much less of it now thanks to functions being generic.
* Notes on how to replace lazy_static! with a LazyCellVika2023-06-151-0/+6
| | | | should've been a LazyLock tho
* Smallish code tweaksVika2023-06-151-1/+3
| | | | | | - cleaner format!() - syndication links - broke up a long line
* Add support for the IndieWeb Webring πŸ•ΈπŸ’Vika2023-06-153-1/+29
| | | | Optional at first. Onboarding UI not yet exposed.
* Database: use newtypes to represent settingsVika2023-06-155-57/+113
| | | | This allows much for a cleaner and idiomatic settings interface.
* tempfile -> tempdir, remove mockitoVika2023-02-272-3/+3
|
* Clarity improvementsVika2023-02-272-2/+3
|
* media: get rid of an extraneous Arc over BytesVika2022-11-071-5/+9
| | | | | Bytes buffers are already reference-counted and cheaply clonable; there is no need to wrap them further.
* indieauth: parse application metadataVika2022-10-243-30/+82
|
* media: implement file range requests for backendsVika2022-10-142-16/+274
| | | | | | | For now it is not yet exposed on the frontend, but that is merely a matter of time. TODO possibly remove the legacy methods, since they're obsoleted
* templates: move static assets to the templates crateVika2022-10-076-279/+10
| | | | | | | | | | | | It makes more sense to keep CSS near the templates, and the client-side JavaScript code too, since it depends on the DOM structure to work. Additionally, the overhead of `include_dir!()` is almost completely mitigated by the fact that this is a separate crate that isn't recompiled often. The linking stage, however, is still expected to take a little bit long. But I doubt it'd be longer than what it was before, since it's the same exact files that get linked into the app.
* media: Use ETag and If-None-MatchVika2022-10-043-4/+38
| | | | | | | | | | | | | | | | | | | | Note: this requires a reindex of the media database. For the default CAS backend, use the following: ```bash for i in */*/*/*/*.json; do etag="$(echo $i | sed -e 's/\///g' -e 's/\.json$//')"; mv "$i" "$i.bak" cat "$i.bak" | jq '. + { "etag": '\""$etag"\"'}' > "$i" rm "$i.bak" done ``` This change is backwards compatible, but caching headers won't be emitted without etags present in the metadata. Actual etags are backend-specific and might differ from backend to backend.
* LibreJS compatibilityVika2022-10-031-0/+3
| | | | | | I don't know how worthwhile that was, given that LibreJS developers themselves don't care to properly declare licenses on the Bazaar frontend they use to host the extension's source code on the Web 🀑
* companion-lite: rewrite to use IndieAuthVika2022-10-022-1/+6
| | | | | This is a naive implementation that doesn't have some security checks. It's ok tho, should work fine... can refine it later
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-23 00:30:22 +0000