The peering agreements are based on network traffic of the customers. Passing through costs to customers is always a thing.
Peering agreements have been around for a long time on the internet, they're part the backbone of the internet.
Peering agreements for internet traffic, what a stupid concept.
Tux is a blackbelt in Karate, and has many combat skills including using Katanas and flips (which he learned from Kat and Ana). Tux also has an iq of 135. He's also a skilled Marksman. He's good at driving, can slide on his belly, and is resistant to extreme cold, being a penguin. He's also a good general, and of course, he's great at using Computers. Mostly Linux, but he can use Windows a bit too. He's especially good at Emulation.
LOL
At least I got a laugh out of it. It does seem pretty useless as a reference though.
Many of the functions provided by a Mastodon service is split into separate services in the AT Protocol. This means there are instances that just handle an end users data, instances that just handle indexing and streaming out the amalgamated end user data being streamed to the "relay", there are instances that are just filtering the stream from the indexing relay. so basically the various backend parts are modular with the AT Protocol rather than monolithic as is assumed by the ActivityPub protocol where separation is assumed to be only between the frontend and backend of the service.
Bluesky is probably going to capture more of that than Mastodon. But threads is similarly struggling to develop it as well and they have very low barrier for new signups for anyone with a Facebook or Instagram account.
Many people are most interested in profit as their only KPI and mastodon puts up a lot of hurdles for those people.
@ericjmorey
@discuss.online