You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! I was wondering about using this in a project, but due to #18 and the fact that most of the code in the repository hasn't been updated recently and still uses raw HTTP calls instead of e.g. boxo, I decided to instead try rewriting it with "modern" ipfs/boxo and containers/image - to hopefully avoid having to deal with layers of legacy implementations later on.
However, I'm not convinced that's ideal, and I would love to contribute as many as possible of those improvements upstream.
Hence my question: if I were to work on modernizing this repository to use boxo and on exposing a nicer programmatic API, is there any chance that such a PR would be reviewed and merged? I'd be willing to stick around and fix any subsequent bugs this might cause.
If no, that'd be a pity, because it'd mean I'd need to start (/continue) my own separate fork, while this repository already has a lot of the community-building and code structure groundwork in place.
The text was updated successfully, but these errors were encountered:
Hey! I was wondering about using this in a project, but due to #18 and the fact that most of the code in the repository hasn't been updated recently and still uses raw HTTP calls instead of e.g. boxo, I decided to instead try rewriting it with "modern"
ipfs/boxo
andcontainers/image
- to hopefully avoid having to deal with layers of legacy implementations later on.However, I'm not convinced that's ideal, and I would love to contribute as many as possible of those improvements upstream.
Hence my question: if I were to work on modernizing this repository to use
boxo
and on exposing a nicer programmatic API, is there any chance that such a PR would be reviewed and merged? I'd be willing to stick around and fix any subsequent bugs this might cause.If no, that'd be a pity, because it'd mean I'd need to start (/continue) my own separate fork, while this repository already has a lot of the community-building and code structure groundwork in place.
The text was updated successfully, but these errors were encountered: