matrix-org / matrix-org/pinecone
Integrating with libp2p
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 486
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I was very excited to read in https://matrix.org/blog/2021/05/06/introducing-the-pinecone-overlay-network
> If Pinecone works out, our intention is to collaborate with the libp2p and IPFS team to incorporate Pinecone routing into libp2p (if they'll have us!) while incorporating their gossipsub routing to improve Matrix federation... and get the best of both worlds :)
and was wondering whether there are steps to take earlier, before one knows "whether Pine works out", to optimistically prepare for that integration ahead of time while not hurting (and ideally helping) development now.
For example, maybe there are deps from https://github.com/libp2p/go-libp2p/blob/master/go.mod that would help here?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Pinecone announcement linked in the issue and comparing the dependencies in libp2p's go.mod. Investigate whether any early integration steps are identified without constraining current development. Done would require a concrete, agreed integration plan or actionable preparatory change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100