Skip to content

Commit 2e54e1a

Browse files
authored
Update page.md links to storj.io/blog (#466)
The URL scheme changed, removing dates in URL eg. (right) https://storj.io/blog/reputation-matters-when-it-comes-to-storage-nodes/ instead of (wrong) https://storj.io/blog/2019/01/reputation-matters-when-it-comes-to-storage-nodes/
1 parent 16e45ac commit 2e54e1a

File tree

1 file changed

+4
-4
lines changed
  • app/(docs)/learn/concepts/file-repair

1 file changed

+4
-4
lines changed

app/(docs)/learn/concepts/file-repair/page.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -25,10 +25,10 @@ All of this analysis of Storage Nodes is fed into the data science engine which
2525

2626
There are a number of great blog posts on the math behind the redundancy model using erasure codes and how the repair system works. Probably the most important takeaway is that erasure codes are an alternative to replication that deliver much higher durability at a much lower expansion factor. As a result, an approach whereby objects are erasure coded and distributed over dozens, hundreds, or thousands of endpoints will provide superior durability to making multiple replications in a small number of endpoint locations or using erasure codes in a single location. If you want the details, check out:
2727

28-
- [Replication is bad for decentralized storage, part 1: Erasure codes for fun and profit](https://storj.io/blog/2018/11/replication-is-bad-for-decentralized-storage-part-1-erasure-codes-for-fun-and-profit/)
28+
- [Replication is bad for decentralized storage, part 1: Erasure codes for fun and profit](https://storj.io/blog/replication-is-bad-for-decentralized-storage-part-1-erasure-codes-for-fun-and-profit/)
2929

30-
- [Why (Proof-of-) Replication is Bad for Decentralized Storage, Part 2: Churn and Burn](https://storj.io/blog/2019/01/why-proof-of-replication-is-bad-for-decentralized-storage-part-2-churn-and-burn/)
30+
- [Why (Proof-of-) Replication is Bad for Decentralized Storage, Part 2: Churn and Burn](https://storj.io/blog/why-proof-of-replication-is-bad-for-decentralized-storage-part-2-churn-and-burn/)
3131

32-
- [Reputation Matters When it Comes to Storage Nodes](https://storj.io/blog/2019/01/reputation-matters-when-it-comes-to-storage-nodes/)
32+
- [Reputation Matters When it Comes to Storage Nodes](https://storj.io/blog/reputation-matters-when-it-comes-to-storage-nodes/)
3333

34-
- [Decentralized Auditing and Repair! The Low-key Life of Data Resurrection](https://storj.io/blog/2018/12/decentralized-auditing-and-repair-the-low-key-life-of-data-resurrection/)
34+
- [Decentralized Auditing and Repair! The Low-key Life of Data Resurrection](https://storj.io/blog/decentralized-auditing-and-repair-the-low-key-life-of-data-resurrection/)

0 commit comments

Comments
 (0)