Correct it's not part of ActivityPub, but it supports a bunch of IndieWeb niceties, like:
The public version version of the instance is really a personal blog/microblog that supports ActivityPub + IndieWeb. It's quite different from regular "fediverse" software.
i. The single-user part is really strict/part of the design, as there are literally no concept of users, everything is assumed to be authored by the instance actor.
I do host multiple instances on the same server (like @email@example.com), but if you're looking to support more than a couple of users, I think it's not the right fit.
ii. And poetry is used because pip alone is not really enough in term of features to lock packages. It tries to implement a "modern package manager" in Python. It is working well so far.
@dev@t thanks for your reply. Indieweb is new to me. From what I understood it is quite reasonable to bridge with activitypub.
So, just thinking aloud for my case, giving my handful of users each their own instance would mean, they all have their own domain (I guess separation by, url path won't work), and all have their own db and config etc? Well, this might work, but seems to be a hassle for the admin.
@dev@gotosocial Thanks. I'm already playing around with #GoToSocial. It's running on the vps an serves good so far; it works basically. And now I am also interested in #indieweb I will take some time to think about it