[Blog Post] New IPFS implementations are happening and welcome #74

Closed
opened 2026-10-05 05:12:48 +02:00 by adam · 6 comments
Owner

Done Criteria

Post making it clear that there are multiple IPFS implementation, that more are welcome, others are already doing this, and there are tools available to help (e.g., Boxo)

Notes

  1. This is a tracking issue in GitHub so there is a public place for people to follow along, and so it can be added to project boards.
  2. Planned content to cover:
  • Brief motivation of why (link to Juan’s talk from IPFS Thing 2022)
  • There is funding for new implementations (include link to video sessions and impact evaluator rounds)
  • Highlighting IPFS Implementations | IPFS Docs - feel free to add more
  • There is a lot of latitude around what can be in an IPFS implementation: https://specs.ipfs.tech/architecture/principles/
  • Implementers can join the bi-weekly implementer working group (link to notes)
## Done Criteria Post making it clear that there are multiple IPFS implementation, that more are welcome, others are already doing this, and there are tools available to help (e.g., Boxo) ## Notes 1. This is a tracking issue in GitHub so there is a public place for people to follow along, and so it can be added to project boards. 2. Planned content to cover: - Brief motivation of why (link to Juan’s talk from IPFS Thing 2022) - There is funding for new implementations (include link to video sessions and impact evaluator rounds) - Highlighting [IPFS Implementations | IPFS Docs](https://docs.ipfs.io/basics/ipfs-implementations/) - feel free to add more - There is a lot of latitude around what can be in an IPFS implementation: https://specs.ipfs.tech/architecture/principles/ - Implementers can join the bi-weekly implementer working group (link to notes) <!-- github-sync-id:1315813945 -->
adam closed this issue 2026-10-05 05:12:48 +02:00
Author
Owner

I'll be supporting this, but will assign to @mishmosh once https://github.com/ipfs/github-mgmt/pull/27 is merged.

I'll be supporting this, but will assign to @mishmosh once https://github.com/ipfs/github-mgmt/pull/27 is merged. <!-- github-comment-id:1193250650 -->
Author
Owner

2022-11-10 conversation across stack leads: Outercore will take the lead here but I am game to review.

2022-11-10 conversation across stack leads: Outercore will take the lead here but I am game to review. <!-- github-comment-id:1310622282 -->
Author
Owner

A somewhat related post is happening with @darobin in https://hackmd.io/PlKnkKUJR9yeecvflIBOOw?both

A somewhat related post is happening with @darobin in https://hackmd.io/PlKnkKUJR9yeecvflIBOOw?both <!-- github-comment-id:1480620762 -->
Author
Owner

Related post about IPFS implementations is in https://github.com/ipfs/ipfs-blog/pull/550

Related post about IPFS implementations is in https://github.com/ipfs/ipfs-blog/pull/550 <!-- github-comment-id:1489699661 -->
Author
Owner

I still think this post makes sense, and maybe now we should capture the latest from IPFS Thing 2023. I updated the issue description with additional info.

I still think this post makes sense, and maybe now we should capture the latest from IPFS Thing 2023. I updated the issue description with additional info. <!-- github-comment-id:1514080404 -->
Author
Owner

The discussion of multiple IPFS implementations beyond Kubo has been happening for 1.5 years. This realistically isn't going to get prioritized by anyone at this point beyond the comms that have already been done. Closing as not planned.

The discussion of multiple IPFS implementations beyond Kubo has been happening for 1.5 years. This realistically isn't going to get prioritized by anyone at this point beyond the comms that have already been done. Closing as not planned. <!-- github-comment-id:1876066691 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/ipfs-blog#74