I wanted to understand their perspective. But that doesn’t seem to be something they are willing to share in any more detail.

There was no implication being made.

What measure of difficulty of content discovery are you using to determine that it is difficult? What would not difficult content discovery be? What content is there is desired to be discovered What do you mean by, ‘there is no “why” here’?

I have many questions about how people perceive the current state of things and what they view as potential areas for improvement.

You’ve made an awful lot of bad assumptions about me based on a single question that you haven’t answered.

Seriously. What’s up? You’re responding with a great amount of negativity. You’ve accused me of gaslighting and being moronic with no provocation that would warrant either response.

I have presented no take.

Are you doing ok? What’s bothering you?

Why do you view these as issues to be overcome?

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.

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.

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.

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.

Bluesky has no documentation for running a relay (indexing node). It doesn’t seem like they intend to have any documentation on it any time soon. But it is possible to set one up yourself. I don’t know anyone that has done so.

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

Kinda ignored the internet for a week and nothing fell apart, so I’d say they’re going well.