Jacob O'Bryant

For now this could be added as another page, with a link next to the existing "Subscribers" link.

(I think good enough at this stage to just do a regular save; no need to try to get fancy with storing diffs or something)

It occurred to me that since we're already using netlify, and netlify's backend fns are just wrappers for AWS lambda fns, we could try to use those. For example, platypub...

I think this is the answer: https://fly.io/blog/fly-machines/ > Fly Machines are VMs with a fast REST API that can boot instances in about 300ms.

We'll need to figure out how to cache npm/deps.edn deps. doing it in a dockerfile might be ok--are there security risks with putting untrusted code in dockerfiles for fly machines?

Some reading material: - https://disaev.me/p/sandboxing-untrusted-code/ - https://github.com/glotcode/docker-run - https://github.com/rapidlua/luajit.me/wiki/On-running-untrusted-code-in-AWS-Lambda

You can also give Tagify a list of suggested tags (see the deceptively named "whitelist" argument). Let's populate that with all of the user's tags, sorted by how often each...

Perhaps we should wait until #43 is closed, since we'll want to update the navigation once that's finished anyway.

Now that platypub supports custom item types, I think the data model won't change too much more. It would be worth thinking about how to structure Platypub's UI. I chose...

The transformations would be interesting to look into. Though a downside of using those would be that Platypub couldn't be used with other S3 providers. (I like using DigitalOcean's S3...