Skip to content

Separating implementations list into 2 #1456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Feb 2, 2023
Merged

Conversation

TMoMoreau
Copy link
Contributor

@TMoMoreau TMoMoreau commented Jan 26, 2023

Describe your changes

Per issue #1360

Separating the list of implementations into 2, one for actively maintained and one for "legacy".

Files changed

  • docs/concepts/ipfs-implementations.md

What issue(s) does this address?

Does this update depend on any other PRs?

Checklist before merging

  • No spelling errors (vale is reporting a special term)
  • Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.
  • Passing all required checks (The beta Check Markdown links for modified files check is not required)

Copy link
Contributor

@ElPaisano ElPaisano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Once the spelling is fixed, LGTM - I like how the layout looks on the UI

| auspinner | <https://github.com/2color/auspinner> | go | CLI tool to deal with the pinning service API and upload files through bitswap. |
| Agregore | <https://github.com/AgregoreWeb/agregore-ipfs-daemon> | go, javascript | Mobile friendly Kubo daemon. |
| ipfs tiny | <https://gitlab.com/librespacefoundation/ipfs-tiny> | c++ | Tiny embeddable, os-independent IPFS implementation. |
| ipget | <https://github.com/ipfs/ipget> | go | Minimal wget insipired tool to download files from IPFS nodes over bitswap. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 41, spelling flagged by vale

insipired

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow don't know how that slipped by, let's leave it as a legacy typo.

Haha jk, I'll make the fix.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"legacy typo" 😆

@TMoMoreau
Copy link
Contributor Author

@ElPaisano should be good to go now.

@ElPaisano
Copy link
Contributor

Approved @TMoMoreau


| Name | URL | Language(s) | What it's trying to do |
|------------------|-------------------------------------------------------------------------|------------------------|--------------------------------------------------------------------------------------------------------------------------|
| auspinner | <https://github.com/2color/auspinner> | go | CLI tool to deal with the pinning service API and upload files through bitswap. |
Copy link
Member

@2color 2color Jan 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On another thought, I think that because Auspinner still works and while not actively maintained still lives up to its promise so it may make sense to move it to Actively maintained.

However, this can be leading because its functionality is not on par with Kubo.

Therefore, If I think about this page more holistically, some ideas for better organisation come to mind:

  • Adding an experimental column
  • Adding a column for some of the IPFS subsystems, e.g.
    • IPFS Gateway ('server' or 'client')
    • IPFS Pinning API Client
    • RPC API
    • DHT (client or server)
    • Level of IPLD support (not too sure about this one, but as an example, Auspinner takes CAR files which can be UnixFS or DAG-CBOR but it can't chunk and create UnixFS blocks for you)
    • PubSub support
    • Blockstore
    • IPNS support
    • Delegated Routing Spec Support
    • Bitswap support (Lotus doesn't support as far as I know)
    • Long lived vs. ephemeral (js-ipfs, ipfs-lite)
    • NAT hole punching (Circuit Relay v2) support

@ElPaisano
Copy link
Contributor

@TMoMoreau do you think you'll get to this this week? If not, I can pick it up

@ElPaisano ElPaisano merged commit 5e8ec53 into main Feb 2, 2023
@ElPaisano ElPaisano deleted the Separate-implementation-list branch February 2, 2023 23:55
@ElPaisano ElPaisano self-assigned this Feb 3, 2023
@2color 2color added this to the 1/27/23 - 2/3/23 milestone Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Reorg implementations page into 2 separate lists
3 participants