Natanael

In fact, it is worse than the storage requirements, because the message delivery requirements become quadratic at the scale of full decentralization: to send a message to one user is to send a message to all. Rather than writing one letter, a copy of that letter must be made and delivered to every person on earth

That’s written assuming the edge case of EVERYBODY running a full relay and appview, and that’s not per-node scaling cost but global scaling cost.

Because they don’t scale like that, global cost is geometric instead (for every full relay and appview, there’s one full copy with linear scaling to network activity), and each server only handles the cost for serving their own users’ activity (plus firehose/jetstream subscription & filtering for those who need it)

For Mastodon instance costs, try ask the former maintainers of https://botsin.space/

There’s literally no restrictions other than simple rate limiting, which you can ask for exceptions for.

I don’t know a Mastodon/lemmy server which wouldn’t rate limit new peers

Partially - something running independent infrastructure like Whitewind (blogging on atproto) will still work just like before (it’s easier for them to run it independently because you don’t need a full network view, just pull in the posts from the user’s PDS for standalone display)

When the work to make appviews easier to run makes it more practical this will be less of a risk.

No, it doesn’t scale “quadratically”. That’s what going viral on Mastodon does to a small instance, not on bluesky. Pretty much everything scales linearly. The difference is certain components handle a larger fraction of the work (appview and relay).

Both a bluesky appview and a Mastodon instance scales by the size of the userbase which it interacts with. Mastodon likes to imagine that the userbase will always be consistent, but it isn’t. Anything viewed by a large part of the whole Mastodon network forces the host to serve the entirety of the network and all its interactions. So does a bluesky appview, in just the same way, but they acknowledge this upfront.

Meanwhile, you CAN host a bluesky PDS account host and have your traffic scale only by the rate of your users’ activity + number of relays you push these updates to. Going viral doesn’t kill your bandwidth.

No, PDS federation is fully open now.

They’re also actively supporting development of 3rd party appviews and relays.

Maybe you remember PDS federation not being open for a while, but it’s open now.

Running a public appview can be very expensive, but they’re working on making it cheaper to run one with a limited scope.

They never said they’d do so natively with other protocols - but they support Bridgy, so you already can do that.

Domains only help you verify organizations and individuals you recognize directly.

This verification system also allows 3rd parties (it’s NOT just bluesky themselves!) to issue attestations that s given account belongs to who they say they are, which would help people like independent journalists, etc.

One shelter is very valuable, a second shelter has extremely questionable value to me.

There’s no definition of “inherently valuable” which doesn’t rely on arbitrary axioms. Especially because no amount of inherentness can guarantee a minimum price.

Those are factors that create an expectation of value.