These are just the initial limits while we work out any issues. It'd be bad for everyone if the network was immediately overrun with spammers launching PDS hosts with millions of fake users/posts, etc. Even though our infra might be able to weather this kind of abuse, there are many independent feed generators (custom algorithms) operated by individuals that would likely fall over.

The plan is to increase limits sufficiently to account for all legitimate usage.

(It's also worth pointing out that these limits only apply to our Relay service. The expectation is that there will be other Relays on the network in the future.)

> Ah yes, incredibly low limits with no way to say "hey look we're quality, let us do more". That's "basic anti-spam". Sure.

Then please suggest how they can remedy this problem without giving spammers the same opportunity.

- Requiring upfront financial commitments would deter most low-yield spams, at the cost of raising requirements for running your own node - Domain-based filtering likely works for this, but this brings back in the topic of censorship (see Mastadon's domain blocking)

> It's actually "you can host yourself and your friends but anyone who doesn't know someone with a server and technical knowledge must use our platform"

You're complaining about the immediate first steps and how it doesn't immediately land on the moon. Simplifying the deployment process for everyone else still takes time. At minimum:

- Purchasing gateway for a custom domain name (requires partnerships with domain name sellers) - Server/Compute+DB rental gateway (because the average normal person doesn't have the hardware to run the service 24/7, nor do they want to know about Linux) - Togglable automatic updates to the federation service

Each simplification would require effort on the devs & partners to setup & maintain.