@circlebuilder mentioned(@aschrijver on this forum) that Murmurations could help with implementing an ecosystem-wide crawler like ForgeFlux/Starchart. So I performed feasibility evaluation of Murmurations for Starchart within the ForgeFlux and the broader ActivityPub ecosystem.
ForgeFlux deals with implementing federation external to the forge. As a result, we are unable to source events that are not published on the
forge’s notification endpoints in real-time. Murmurations require the data owner/subject to notify aggregators(Starchart in this case), of
changes so that the aggregator might update the data relevant to the subject stored on their systems.
For events that are published on the forge’s notification endpoints, they can be discovered by simply subscribing to the actor via
ForgeFlux ActivityPub implementation includes WebFinger, which is essentially an index for all related resources that are owned by an actor. Murmurations seem to provide a similar functionality. What is missing, however, is a map that charts all the various actors in the network. In software forge federation context, a map of all Free repositories, users and forges in the federated ecosystem.
It would be interesting if we could come up with tools to offer access and privacy control options on a per actor(repository and user) basis.
This would be similar to a robots.txt file per repository/user to instruct spiders on how their data should be used/served.