56 lines
5.6 KiB
HTML
Executable File
56 lines
5.6 KiB
HTML
Executable File
<html>
|
|
<head>
|
|
<title>getting started - messages</title>
|
|
<link href="hydrus.ico" rel="shortcut icon" />
|
|
<link href="style.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class="content">
|
|
<p><a href="getting_started_tags.html"><--- Back to ratings</a></p>
|
|
<h3 class="warning">messaging, you say?</h3>
|
|
<p class="warning">Caveat: this is a mess. I'll get round to improving it sometime.</p>
|
|
<p class="warning">Secondly: I use encryption to protect your privacy. Although I am confident my code is mostly good, cryptography is <i>really difficult</i> to get 100% right. I use the right random number generator and key lengths and everything, but don't work under the assumption a dedicated and well funded attacker will never be able to break what I have done. I can guarantee your guildmaster will not be able to read your messages, not the NSA. Don't Do Drugs™.</p>
|
|
<h3>ok, let's messaging</h3>
|
|
<p>With the aid of a service called a <i>message depot</i>, the clients can send messages to one another.</p>
|
|
<p>A message depot is a bit like an IMAP email server. It has a number of contacts registered with it, and any client who knows those contacts can upload messages to it. A client can have many contacts (you can be several different people on the same computer), and a contact many clients (you can be the same person on several different computers). Clients check their appropriate message depots regularly, and download any new messages.</p>
|
|
<h3>how is it different from email?</h3>
|
|
<p>All hydrus network messages are stored on the message depots in an encrypted format, and <i>only</i> the recipient's client(s) have the key to decrypt them. If someone hacks/steals/whatever a message depot, they cannot read the messages, nor tell who they are from.</p>
|
|
<p>Messages are verifiable, meaning the client knows for sure if they came from who they say they did.</p>
|
|
<p>A client can send messages anonymously. These messages cannot (right now) be replied to.</p>
|
|
<h3>adding contacts</h3>
|
|
<p>First, let's discern a couple differences:</p>
|
|
<ul>
|
|
<li>contact: <b>An address that can send and recieve messages.</b></li>
|
|
<li>identity: <b>A contact you control.</b></li>
|
|
</ul>
|
|
<p>The dialog under <i>services->manage contacts and identities</i> lets you add new contacts.</p>
|
|
<p><img src="contacts.png" /></p>
|
|
<p><i>add manually</i> lets you enter the information in each field, while <i>add by contact address</i> grabs the public key from the server for you after you put in the contact_key@host:port. If you do add manually, make sure you copy the public key <i>very</i> carefully, and check the resultant contact key is correct; if your OS converts newlines incorrectly, it'll all go wrong!</p>
|
|
<p>Your identities are listed here (and you can rename them), but you do not create them here.</p>
|
|
<h3>how do i create a new identity?</h3>
|
|
<p>If you want to send messages as anything other than Anonymous, you need an access key at a message depot. The access key is not the same as your eventual contact key; the first gives you access, the second is how people's clients will identity you. They are both random numbers.</p>
|
|
<p><a href="server.html">Creating</a> or adding a message depot works exactly the same as for any other type of service.</a> When you add it, the client will do some heavy math in the background, which should freeze the interface for a few seconds. This is it generating the contact's <i>private key</i>, which is the secret that lets it decrypt messages.</p>
|
|
<p><img src="manage_services_edit_message_depot.png" /></p>
|
|
<p class="warning">If you want to use the same identity with several clients, don't try to add the service in the usual way on your extra clients, or they will generate their own private keys, overwriting each other! Instead, export the message depot from <i>services->manage services</i> on the first client, and import (drag and drop the .yaml file onto the dialog) into the second, third, whatever client. This will copy the original private key across without any errors.</p>
|
|
<p>When you are done, the 'messages' F9 menu will show your new identity.</p>
|
|
<p>If you want to share your identity, you can either send people your contact_key@host:port, or you can just message them, which will add you to their contacts automatically.</p>
|
|
<h3>composing messages</h3>
|
|
<p>Composing messages is easy. Just hit the button on your messages page. The 'recipients can see each other' checkbox does email's cc vs bcc.</p>
|
|
<p>I will add file attachments in future.</p>
|
|
<h3>finding messages</h3>
|
|
<p>The interface is just like searching for files. Put in a normal word to search message bodies/subjects, or use the system predicates to perform more complicated queries. Conversations that match will appear on the top right, and any selected convo will appear below.</p>
|
|
<p><a href="example_convo.png"><img src="example_convo.png" width=604 height=964/></a></p>
|
|
<p>You can hit F7 or delete or just right click on a conversation above to archive or delete it. Beside each message, you can see its current status with each recipient. If it says <i>failed</i>, you can click on it to retry, and if your identity is the recipient, you can switch between <i>read</i> and <i>unread</i>.</p>
|
|
<p>I will add:</p>
|
|
<ul>
|
|
<li>rich text</li>
|
|
<li>file attachments</li>
|
|
<li>custom status</li>
|
|
<li>auto-adding of new messages</li>
|
|
<li>live times (3 mins 21 seconds ago auto-updating)</li>
|
|
</ul>
|
|
<p>in future.</p>
|
|
<p class="right"><a href="index.html">Go back to the index ---></a></p>
|
|
</div>
|
|
</body>
|
|
</html> |