13 | | |
14 | | == History == |
15 | | |
16 | | Note that the introducer furl has changed recently (as of Feb. 2013). |
17 | | |
18 | | A version of the pubgrid existed until some time in 2012, when the introducer was lost. In February of 2013, a new introducer was created, resulting in a change of furl. |
19 | | |
20 | | It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not. If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible. |
21 | | |
22 | | == Cautions == |
23 | | |
24 | | The canonical way to access Tahoe-LAFS grids is to run your own client node. Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext. However, writing to the publically-writeable test directory (below) means that others can see and change your files. |
25 | | |
26 | | == Publicly writable test directory == |
27 | | |
28 | | URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa . Note that anyone may view and change this data. |
| 65 | == History == |
| 66 | |
| 67 | Note that the introducer furl has changed recently (as of Feb. 2013). |
| 68 | |
| 69 | A version of the pubgrid existed until some time in 2012, when the introducer was lost. In February of 2013, a new introducer was created, resulting in a change of furl. |
| 70 | |
| 71 | It is an interesting philosophical question as to whether the pubgrid with the new introducer is a different grid or not. If servers that had been connecting to the new introducer are repointed to the new introducer, it can be considered the same grid with a change of introducer, with the property that files from the old grid may still be accessible. |
| 72 | |
| 73 | == Cautions == |
| 74 | |
| 75 | The canonical way to access Tahoe-LAFS grids is to run your own client node. Having one's own node is necessary for the data that should remain private (plaintext, capabilities) to remain on your computers, while storage nodes provide storage of ciphertext. However, writing to the publically-writeable test directory (below) means that others can see and change your files. |
| 76 | |