storj VS juicefs

I did storj.io but was not profitable and the support was worthless. Did join NTP Pool (as I have a stratum 2 GPS NTP) but the power supply died and I haven't been able to get time to fix it.

Storj is based on blockchain technology and peer-to-peer protocols to provide secure, private, and encrypted cloud storage.

storj.io

I will eventually move to a synology ds260slim, but tbh I feel cloud storage is better storj.io not trying to sell it just saying it’s really really good and cheap.

That's storj.io. No need to reinvent the wheel.

You can even make money from storj.io !

- velero backups local pvc/manifests to storj.io (150GB is free)

Take a look at Storj for object storage. You can not beat it for pricing: $4/TB/month. The interface is compatible with S3 and there are only minimal changes to be done at mastodon's setup. Plus having your storage separate from your server makes migration and upgrades a 1000 times easier.

I'd recommend that you consider https://storj.io . They offer ridiculously redundant, and quite fast cloud storage.

I want to expose all ports. I’m trying to run a https://storj.io node that recommends noip but I want to switch to funnel. Im not exactly sure of the configuration, but I think it’s just every UDP/TCP port from a device.

Support for Kerberos keytab files

JuiceFS under the Apache License 2.0, is a high-performance POSIX file system optimized for cloud-native environments. It stores data in Object Storage (e.g., Amazon S3) and metadata in databases like Redis, MySQL, or TiKV. JuiceFS integrates massive cloud storage with big data, machine learning, and AI applications efficiently, akin to local storage. It features full POSIX and Hadoop compatibility, S3 interface, Kubernetes support, and shared file storage for numerous clients. Some cool features are - strong consistency, scalable performance, data encryption, global file locks, and compression with LZ4 or Zstandard.

To improve the handling process of capacity overrun, the JuiceFS client supports deletion operations in the case of Ceph cluster fullness (see related code changes in JuiceFS Community Edition). Therefore, for newer client versions, there is no need to use set-full-ratio for temporary adjustments.

If you have any questions or would like to learn more, feel free to join discussions about JuiceFS on GitHub and the JuiceFS community on Slack.

The architecture image shows GCS and others, so I suspect it does.

https://github.com/juicedata/juicefs#architecture

See also: JuiceFS: https://juicefs.com/

Adds a DBMS or key-value store for metadata, making the filesystem much faster (POSIX, small overwrites don't have to replace a full object in the GCS/S3 backend).

Almost certainly a better solution if you want to turn your object storage into a mountable filesystem, with the (big) caveat that you can't access the files directly in the bucket (they are not stored transparently).

JuiceFS can do the same thing as s3fs-fuse, but better. Because it supports robust data consistency and caching policies to improve performance.