kittybox - An IndieWeb-centric blogging engine designed for self-hosting

	Commit message (Collapse)	Author	Age	Files	Lines
*	Expose ?q=category queries in Micropub API	Vika	2024-03-04	1	-1/+15
\|
*	Switch reply contexts from a Vec to HashMap	Vika	2023-11-13	1	-16/+15
\| \| \| \|	This reduces the worst-case complexity to O(n) from O(n^2).
*	Fix bug with likes/bookmarks on h-entries lacking URLs in markup	Vika	2023-10-15	1	-7/+21
\|
*	Moved the entire Kittybox tree into the root	Vika	2023-07-29	1	-0/+846
\|
*	flake.nix: reorganize	Vika	2022-05-24	1	-964/+0
\| \| \| \| \| \| \| \| \| \| \| \|	- 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
*	feat: webmention sending and reply context enrichment	Vika	2022-05-14	1	-44/+160
\| \| \| \| \| \| \|	These features share some code since they both require fetching reply contexts, so it makes sense to implement them together. TODO cover webmention sending with integration tests
*	treewide: prepare for mf2 parsing and cleanup unused code	Vika	2022-05-12	1	-23/+82
\|
*	media: move to separate subtree	Vika	2022-05-10	1	-50/+0
\| \| \| \| \| \| \| \|	This will ease future extraction of the media endpoint to a separate crate. This is highly desirable since it will allow Kittybox's media endpoint to be used separately in instances where a standalone media endpoint is desirable (e.g. custom solutions using my code to polyfill for desired functionality that is undesirable to implement by oneself)
*	Get rid of todo!() invocations	Vika	2022-03-23	1	-4/+32
\| \| \| \| \| \|	This stubs the neccesary code with enough stuff that it will work and be accepted by most compliant Micropub implementations. Later, this can be extended when the neccesary amendments and refactors are done.
*	Get rid of legacy code, fix mistakes in fluff text and comments	Vika	2022-03-23	1	-3/+3
\|
*	Port onboarding	Vika	2022-03-07	1	-3/+15
\|
*	Restored most of the functionality (except onboarding and some queries)	Vika	2022-03-06	1	-67/+550
\|
*	Added stubs for Micropub posts and the media endpoint	Vika	2022-02-21	1	-1/+83
\|
*	micropub: flesh out query	Vika	2022-02-21	1	-47/+180
\|
*	WIP: convert to Tokio and Warp	Vika	2022-02-15	1	-29/+99
\| \| \| \| \| \| \| \| \| \| \|	Warp allows requests to be applied as "filters", allowing to flexibly split up logic and have it work in a functional style, similar to pipes. Tokio is just an alternative runtime. I thought that maybe switching runtimes and refactoring the code might allow me to fish out that pesky bug with the whole application hanging after a certain amount of requests...
*	Appease rustfmt, clippy and cargo check	Vika	2021-07-29	1	-3/+7
\|
*	Added CORS middleware	Vika	2021-07-27	1	-0/+21
\| \| \| \| \|	This prevents Micropub requests fired from web apps on other domains from being blocked by overzealous browsers.
*	Make rustfmt happy	Vika	2021-05-17	1	-1/+1
\|
*	Refactoring, easter egg, healthcheck endpoint, support for rel= indieweb ↵	Vika	2021-05-17	1	-3/+4
\| \| \| \|	APIs and preparation for onboarding
*	Initial commit	Vika	2021-05-04	1	-0/+5
	Working features: - Sending posts from the database - Reading posts from the database - Responding with MF2-JSON (only in debug mode!) - Not locking the database when not needed - All database actions are atomic (except for a small race where UIDs can clash, but that's not gonna happen often) TODOs: - Send webmentions - Send syndication requests - Send WebSub notifications - Make tombstones for deleted posts (update adding dt-deleted) - Rich reply contexts (possibly on the frontend part?) - Frontend? - Fix UID race Code maintenance TODOs: - Split the database module - Finish implementing the in-memory test database - Make RedisDatabase unit tests launch their own Redis instances (see redis-rs/tests/support/mod.rs for more info) - Write more unit-tests!!!