I was reading @aral 's blogpost about ActivityPub's scaling issues:
https://ar.al/2022/11/09/is-the-fediverse-about-to-get-fryed-or-why-every-toot-is-also-a-potential-denial-of-service-attack/
And that got me thinking: if the problem is that this post will generate one Sidekiq job *per server used by my followers*, would it not make sense to create "batch" Sidekiq jobs between popular servers that would put multiple actions in a single job?
The overhead would go down. But I guess that would require a change in the spec.
Also, yeah, we should use smaller instances.
senooken JP Social is a social network, courtesy of senooken. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All senooken JP Social content and data are available under the Creative Commons Attribution 3.0 license.