Changes between Version 85 and Version 86 of TestGrid


Ignore:
Timestamp:
2014-06-10T20:02:22Z (10 years ago)
Author:
PRabahy
Comment:

Rearrange sections so that it is more readable.

Legend:

Unmodified
Added
Removed
Modified
  • TestGrid

    v85 v86  
    1111  * The pubgrid is not intended to provide large-scale storage, and it is not intended to be reliable.   Don't store any data in the pubgrid if losing it would cause trouble.
    1212  * Don't view the pubgrid as a free hundreds-of-MB backup service.
    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.
    2913
    3014== How To Connect To The Public Test Grid ==
     
    6145We created a shared public directory: feel free to use it for experimentation -- once your node is up and listening on port 3456, [http://127.0.0.1:3456/uri/URI%3ADIR2%3Addg5n76x6stjb35psrcn7i3ytu%3Aetbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa/ this URL] should give you access to that directory.
    6246
     47== Publicly writable test directory ==
     48
     49URI:DIR2:ddg5n76x6stjb35psrcn7i3ytu:etbtnftlaeylm4gmi7mxzq6pg2ntgra7dyjeronyoo4pvkgtttqa .  Note that anyone may view and change this data.
     50
    6351== Social Norms ==
    6452
     
    7563 * Enable expiration with 1-month lease maximums on your node, to keep it from just filling up.
    7664
     65== History ==
     66
     67Note that the introducer furl has changed recently (as of Feb. 2013).
     68
     69A 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
     71It 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
     75The 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
    7777== Other Public Volunteer Grids ==
    7878