hydrus/help/access_keys.html

24 lines
1.7 KiB
HTML
Executable File

<html>
<head>
<title>access keys</title>
<link href="hydrus.ico" rel="shortcut icon" />
<link href="style.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div class="content">
<h3>first off</h3>
<p>I have purposely not pre-baked this into the client's install. You have to put it in yourself. The client won't connect anywhere until you tell it to.</p>
<h3>access keys</h3>
<p><b><i>If this stuff be-fuzzles you, you can now go </i>help->i don't know what I am doing->just set up some repositories for me, please<i> and you _should_ be all set up automatically.</i></b></p>
<p>I run a public, objective tag repository that <a href="tagging_schema.html">you are welcome to contribute</a> to. I also run a read-only file repository that you can search to get a feel for the interface. The files on my file repo are appropriately tagged in my tag repo.</p>
<p><img src="edit_repos_public_tag_repo.png" /></p>
<p><img src="edit_repos_file_repo.png" /></p>
<p>Here's the info so you can copy it:</p>
<ul>
<li>public tag repository: 4a285629721ca442541ef2c15ea17d1f7f7578b0c3f4f5f2a05f8f0ab297786f@hydrus.no-ip.org:45871</li>
<li>read-only file repository: 8f8a3685abc19e78a92ba61d84a0482b1cfac176fd853f46d93fe437a95e40a5@hydrus.no-ip.org:45872</li>
</ul>
<p><b>Tags are rich, cpu-intensive metadata. My repository has millions of mappings (about 70MB of network data, at last count), so expect your computer to take <i>hours</i> to synchronise fully. You can close the client at any time, and it will continue where it left off when it next boots. If it is slowing your normal browsing, you can pause it at <i>services->pause->repositories synchronisation</i>.</b></p>
</div>
</body>
</html>