about summary refs log tree commit diff
path: root/kittybox-rs/src/micropub
Commit message (Collapse)AuthorAgeFilesLines
* Put Micropub background processing tasks in a JoinSetVika2023-07-171-6/+21
| | | | | | | 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.)
* cargo update, part 2: AxumVika2023-07-171-5/+5
| | | | | | | | | 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.
* micropub: a little bit more loggingVika2023-07-091-0/+2
|
* fixup! database: add add_to_feed and remove_from_feedVika2023-07-081-2/+2
|
* micropub: use the new, better typed updates internallyVika2023-07-011-17/+28
|
* Better Micropub update object typingVika2023-06-221-4/+13
|
* database: add add_to_feed and remove_from_feedVika2023-06-221-2/+1
| | | | | 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-221-4/+16
| | | | | This allows disregarding http/https comparisons and simplifies some database designs.
* main: refactor Kittybox constructionVika2023-06-221-0/+1
| | | | | | 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.
* Clarity improvementsVika2023-02-271-0/+1
|
* fix param name for media endpointVika2022-09-281-1/+1
| | | | AAAAAAAAAAAAAAAAAAAAAAAAA
* Use tokens from the auth backend to authenticate for MicropubVika2022-09-282-99/+101
|
* PoC for modularity and WIP built-in Micropub client reworkVika2022-07-151-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | | This is the living, breathing proof that Kittybox can be split into independent components without sacrificing any functionality. Just make sure all neccesary backing storage components are available to the modules that need them. Also the Micropub client was split into several files, because it's about to get much bigger and more full-featured. Yes, I am going to write it in vanilla JavaScript. I don't trust anything from NPM to run on my computer. Not anymore. Not after the node-ipc malware fiasco. And I am definitely not going to spin up a VM or a Docker container (who uses Docker containers as a security measure?) to hack on my own code. Cargo can at least be sandboxed inside Nix, where it can't do much harm. NPM basically requires unrestricted network access to download dependencies, and it runs arbitrary code upon **downloading** them. Cargo and rust-analyzer, on the other hand, can be configured to not trust the source code and its dependencies (for example, Cargo doesn't execute code on fetching dependencies - only on building, and rust-analyzer's proc-macro expansion support can be sacrificed for more security).
* micropub: handle invalid/empty query properlyVika2022-07-101-6/+16
| | | | On query parsing error, this will return a MicropubError.
* micropub: move MicropubError into kittybox-utilVika2022-07-101-77/+2
| | | | | Looks like this shared data structure will be useful to me later when splitting off the media endpoint into its own crate.
* indieauth: rename to tokenauthVika2022-07-102-8/+8
| | | | | | | | | | | | This frees up the name for the future in-house IndieAuth implementation and also clarifies the purpose of this module. Its future is uncertain - most probably when the token endpoint gets finished, it will transform into a way to query that token endpoint. But then, the media endpoint also depends on it, so I might have to copy that implementation (that queries an external token endpoint) and make it generic enough so I could both query an external endpoint or use internal data.
* media: media endpoint PoCVika2022-07-101-3/+3
| | | | | | | | | | Supported features: - Streaming upload - Content-addressed storage - Metadata - MIME type (taken from Content-Type) - Length (I could use stat() for this one tho) - filename (for Content-Disposition: attachment, WIP)
* format using rustfmtVika2022-07-071-64/+81
|
* treewide: rewrite using AxumVika2022-07-073-1538/+903
| | | | | | | | | | | | | | Axum has streaming bodies and allows to write simpler code. It also helps enforce stronger types and looks much more neat. This allows me to progress on the media endpoint and add streaming reads and writes to the MediaStore trait. Metrics are temporarily not implemented. Everything else was preserved, and the tests still pass, after adjusting for new calling conventions. TODO: create method routers for protocol endpoints
* flake.nix: reorganizeVika2022-05-243-0/+1990
- Kittybox's source code is moved to a subfolder - This improves build caching by Nix since it doesn't take changes to other files into account - Package and test definitions were spun into separate files - This makes my flake.nix much easier to navigate - This also makes it somewhat possible to use without flakes (but it is still not easy, so use flakes!) - Some attributes were moved in compliance with Nix 2.8's changes to flake schema
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-26 15:58:59 +0000