[INTPenis]

I thought this would address the scaling of federating activitypub messages, but it's really just problems from an end user perspective. Those problems we can easily solve. Mastodon auth is already a thing, allowing the same app to authenticate against multiple types of backend software, and oauth can also be enabled to use a central identity.

When I hosted a fedi node I disabled search engine crawling with robots.txt, but it can easily be enabled.

Learning curve is all about giving it time and earning experience in accessibility.

But regarding the scaling out of messages; I am writing a small activitypub app in Python, because it's just so fast to prototype in, but I want the option to rewrite heavily used components in another language. So instead of passing pickled or serialized Python/Ruby code around background job processing, I aim to only pass ActivityStream objects, simple JSON that is language agnostic.

Just put it in different queues depending on its destination. Then any background job processing program can process the queues and put the data into DB, or whatever needs to happen.