new feature: Support storj

[Shylock-Hg]

Feature Description

Support storj as new backend service

Problem and Solution

Now the ipfs will lose the file if it's not accessed in a period. So storj will be safer.

Additional Context

No response

Are you willing to contribute to the development of this feature?

• Yes, I am willing to contribute to the development of this feature.

[jorgehermo9]

I see that storj aims to be s3-compatible https://storj.dev/dcs/api/s3/s3-compatibility. Isn't this already supported with the s3 opendal service, using storj s3 credentials?

[Shylock-Hg]

I see that storj aims to be s3-compatible https://storj.dev/dcs/api/s3/s3-compatibility. Isn't this already supported with the s3 opendal service, using storj s3 credentials?

Thanks. I'm not sure too. I will try later.

[Xuanwo]

OpenDAL's goal is to connect services natively, so it would make sense to add native Storj support.

However, the issue is that Storj lacks a native Rust SDK. To use its Go SDK, we would need to go through multiple layers: Rust -> FFI -> C -> cgo -> Go. This approach is unacceptable both from the project's perspective and in terms of performance.

[jorgehermo9]

Maybe @Shylock-Hg was talking about Storj IPFS Pinning Service and not about storj object store service? https://storj.dev/dcs/api/storj-ipfs-pinning I see It has an HTTP interface very similar to IPFS @Xuanwo, but there are a few differences from the IPFS standard. Although, I don't know if there current ipfs service implementation works for storj's ipfs service.

[Shylock-Hg]

Maybe @Shylock-Hg was talking about Storj IPFS Pinning Service and not about storj object store service? https://storj.dev/dcs/api/storj-ipfs-pinning I see It has an HTTP interface very similar to IPFS @Xuanwo, but there are a few differences from the IPFS standard. Although, I don't know if there current ipfs service implementation works for storj's ipfs service.

Yes, I plan to try storj for the pinning issue of ipfs.