I feel that the current abstraction level of #Fedify is not high enough which makes the tutorial lengthy, so I'm considering adding a higher-level API. One way would be to add a façade to the @fedify/fedify package, and another way would be to create a sort of metaframework as a separate package (e.g., @fedify/start?).
Which way would be better?
I find that database agnosticism, one of #Fedify's design principles, is a hindrance to raising its abstraction level. 
The database agnosticism of #Fedify as an #ActivityPub server framework is …
@hongminhee I think it depends on whether you want Fedify to be an #ActivityPub server itself, or a library for writing servers.
@basus Yeah, it's definitely the latter!
@hongminhee the way I would do it is to keep Fedify as general-purpose library, and then build a functioning ActivityPub server with it (using a particular database etc.) that people can use, or use as a guide to building their own.