Implement reverse index for Nostr hashes (event ids) to Minds posts
Goal
In order to support many Minds posts and channels being available on Nostr, we need to store a reverse index of the nostr has to the entity.
What needs to be done
Subscribe to the new 'entities-ops' event stream and record relationship of its nostr id (hash) to entity urn.
Why?
Nostr clients make a request for events based off a sha-256 hash of an event id. We don't have any mechanism of translating these hashes into entities in order to return a response.
QA
Use the provided api endpoint to return an entity from a nostr hash
UX/Design
N/A
Personas
Digital Nomads
Experiments
N/A
Acceptance Criteria
-
A new table that maps nostr hashes to entity urns -
A mechanism (preferably a background runner) that does the reverse indexing stage -
An api endpoint that will return an entity from a nostr hash -
Nostr relay and communication with Nostr is out of scope for this task and is not required or expected -
Spec tests
Definition of Ready Checklist
-
Definition Of Done (DoD) -
Acceptance criteria -
Weighted -
QA -
UX/Design -
Personas -
Experiments
Edited by Mark Harding