[image] Building on the distributed cloud speeds up media workflows. Recent data on Storj transfer speeds were shared at IBC 2024 showing Storj is 42% faster than AWS for 5MB downloads. This blog post will examine how building on the Storj distributed cloud makes workflows even faster—he…

Yes, they also sliced to segments, then - erasure stripes, which are sliced to erasure shares, then these shares are combined to the unique pieces and then - distributed, not replicated. [image] But do the potential customers want to see these overwhel…

[image] Alexey: not replicated. That is my point. If there is no replication then Storj should not use that term in their publications.

Yes, I shared this concern with the team and explained my expectations and guessing. For me the promotion looks ok, because all these details we can explain later. We do not need to overwhelm our potential customers with all complex maths right from the start, as we did in the past.

[image] Alexey: We do not need to overwhelm our potential customers with all complex maths That’s correct, but I’m not referring to complex math; I’m concerned about providing accurate information. One of the internet’s great features is that it allows us to link to detailed explanations suc…

[image] jammerdan: Shouldn’t that be Shouldn’t that be Media files are encrypted,erasure coded, divided,

Actually you even have it on the new website like this: https://www.storj.io/benefits/availability-and-durability [no_replication]

Got ChatGPT to overheat a bit and suggest some better wording. The simplest ones that are technically correct: redundantly encoded, or made fault-tolerant. Not perfect. If anybody wants a lecture (by ChatGPT) on why there’s no nice single verb form for made fault-tolerant: ▶ Lecture hidden

Storj Community Forum (official)

Media files are encrypted, divided, replicated?

Ideas & Suggestions site feedback