Yes, exactly. The Sublinks Service (which I considered calling Interact Service) allows for multiple indexes to be used. A single Index Service isn’t as powerful. Plus, the Index Service doesn’t have a UI for users. I see how combining them could simplify it, but I think having them separate gives more power. I want to build the Sublinks Service as more of a front-end framework, so that new UIs are built on it rather than everyone reinventing the wheel each time they want a new look. This will allow people to create their own view of the Fediverse.

Thanks! The Mobile apps would operate much like a Sublinks instance, choosing which identity services and indexes to show. I would imagine they’d just allow all of them. An alternative approach would be for the Mobile App developer to create a web service to manage those decisions and build their own API for their app to integrate with.

This microservice plan allows more people to hold different parts and reduces the risk of duplication and total loss when one instance goes down.

In the 70s the cars won but not the people. Modern vehicles let the people survive instead of themselves.