The basic idea here is that many applications will have a difficult time implementing sharing and other functionality directly with the decentralized data storage interface provided by Gaia. The solution is to provide a indexing service which is open-source, configurable, and easy to deploy. The exact specifications for this, however, still need to be ironed out.
Easily realizable version
The most directly realizable version is something like a simple search indexer, which uses multi-player reads of gaia-stored data. The indexer would consume a data schema, and be provided with a filename to regularly index (this is a pretty direct generalization of the profile indexer that powers our currently deployed search service (see https://github.com/kantai/blockstack-search-indexer/)
This could emit data in a number of different formats: JSON, by default, but also importantly it should be able to
POST to an elasticsearch endpoint. However, the repository should have a pretty easy to deploy setup which will initialize both the indexer, and a search endpoint.
Support for notifications?
Can this service be used to enable notifications (i.e., pushed from the indexer to a client)?
If so, is there a standard that we’d like to implement? How should this interact with the notion of a “gaia inbox”?