IPFS Implementations: iroh claims not to be an IPFS implementation

[ijsnow]

I found iroh on the IPFS implementations list but their documentation website explicitly says it is not an ipfs implementation, but instead an ipfs system.

Iroh is an IPFS system. It uses content identifiers (CIDs). Content addressing is a powerful primitive that belongs at the foundation of the internet.

Iroh is not an IPFS implementation. An implementation of IPFS should be able to interoperate with kubo the reference implementation of nearly all IPFS Specs. Iroh can interoperate with kubo by bridging the two technologies, but by default one shouldn't expect to be able to add content to kubo and get it out with iroh, or vice versa.

Should the project be removed for the list? If not, whats the qualification for the term "implementation"?

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.tech if you just need general support.

[2color]

We should have more information on interoperability between implementations.

The qualification for an implementation is laid out here: https://specs.ipfs.tech/architecture/principles/#ipfs-implementation-requirements

[2color]

Closing this in favour of #1904