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.
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.
Doesn’t help that they have offered no explanation at all.
Are you aware of https://granary.io/? It may be helpful for implementing your ideas
Discoverablility of what?
How would this help? What is the problem this addresses?
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.
Anything that you’re not willing and able to keep financially sustained yet rely upon will likely be used against you by someone with more resources. This is why groups like Fosstodon, Beehaw, and Fedihosting Foundation stand out in these spaces. They are both transparent and financially sustainable. But most of that sustainability relies on unpaid volunteer labor.
I’ve been using mojeek and ddg, but I’ve been considering setting up SearXNG on a server.
Are you talking about blusky’s indexer?
Not yet
You can even question if the compiled version running on an instano is the same as the version posted to GitHub. There’s no way to even check what’s running on the server you don’t have access to.
Trust is necessary at some level if your going to participate on any hosted or federated service as you pointed out.
They’re purposely disruptive to the community, they are not part of the community.
I agree with just about everything you said, except that it won’t be a technical can of worms to implement the change according to the devs.
That’s just how federation works out in every federated service ever.
I think it’s good.
Quality over quantity is what I would prefer. I think LemmyNSFW is a potential determent for other instances.
Lemmy.world has no lock in on their “power”. They have the most volunteer labor, money, and infrastructure. That’s makes them stable, so people aren’t worried about their data suddenly going offline (like kbin) and they don’t worry about the service being flaky.
there’s tremendous value in repairing and upgrading existing things.
Value created doesn’t translate to value extracted and VCs and managers and marketers and the general public fork over more money in exchange for new shiny than old, reliable, maintained. There are few exceptions.
The peering agreements are based on network traffic of the customers. Passing through costs to customers is always a thing.