Commit graph

7 commits

Author SHA1 Message Date
fd8c2073f0 pivot away from 11ty and instead store data in sqlite
The idea is going to be to build an 11ty frontend that pulls from this back-end
(or perhaps just the database, we'll see)
Also considering a mastodon-compatible api wrapper, or at the very least creating a separate wrapper and completely dropping the existing admin routes.
... ooh, I could do a micropub wrapper, too...

tl;dr: microservices. This is just the activitypub server now.
2023-10-11 16:25:14 +11:00
6647dabdc8 Added eleventy templates from death.id.au
Needed a little modification here and there to make it work with the activity pub data structure, but it's looking pretty good!
2023-09-27 17:06:56 +10:00
b76eb76e1a Utilize 11ty to build static pages and modify server to serve them 2023-09-27 14:13:10 +10:00
2701786de8 Some refactoring and removing the need to specify user
This is going to be single user anyway, so why use https://death.id.au/death.au when I can just be https://death.id.au
2023-09-27 09:49:32 +10:00
9481edbce6 Bit of a refactor to put inbox and outbox function in their own files
Also, added the ability to like and unlike stuff, so yay.
2023-09-20 16:43:48 +10:00
48081b63a0 Update the readme 2023-09-16 11:24:47 +10:00
6f3e2f65ad Initial commit
Code based on (but not identical to) https://github.com/jakelazaroff/activitypub-starter-kit
Instead of using node/express, it's using Bun/bun's inbuilt server
Right now it can follow/unfollow (be followed/unfollowed) and create notes which get sent to followers
No UI yet
Stores posts as markdown with YAML frontmatter
Stores activities for creating those posts as json
Stores following/followers in json files
2023-09-16 10:28:06 +10:00