diff --git a/CHANGELOG.md b/CHANGELOG.md
index 70bc65d..14b4483 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -5,6 +5,17 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.3.1] - 2021-12-30
+
+### Added
+
+- Short explanation in the home page.
+
+### Changed
+
+- Explanation in about & readme.
+- Shorten server ids from 512 to 256bit.
+
 ## [1.3.0] - 2021-12-22
 
 ### Added
diff --git a/README.md b/README.md
index 017bc28..679bd78 100644
--- a/README.md
+++ b/README.md
@@ -30,7 +30,12 @@ Check out the demo and see for yourself https://cryptgeon.nicco.io.
 
 ## How does it work?
 
-each note has a 512bit generated <i>id</i> that is used to retrieve the note. data is stored in memory and never persisted to disk.
+each note has a generated <code>id (256bit)</code> and <code>key 256(bit)</code>. The
+<code>id</code>
+is used to save & retrieve the note. the note is then encrypted with aes in gcm mode on the
+client side with the <code>key</code> and then sent to the server. data is stored in memory and
+never persisted to disk. the server never sees the encryption key and cannot decrypt the contents
+of the notes even if it tried to.
 
 ## Screenshot
 
diff --git a/client/src/lib/views/Create.svelte b/client/src/lib/views/Create.svelte
index bb1133c..9bfc06f 100644
--- a/client/src/lib/views/Create.svelte
+++ b/client/src/lib/views/Create.svelte
@@ -97,6 +97,10 @@
 	<br />
 	<Button on:click={reset}>new note</Button>
 {:else}
+	<p>
+		Easily send <i>fully encrypted</i>, secure notes or files with one click. Just create a note and
+		share the link.
+	</p>
 	<form on:submit|preventDefault={submit}>
 		<fieldset disabled={loading}>
 			{#if file}
diff --git a/client/src/routes/about.svelte b/client/src/routes/about.svelte
index c417e41..0644742 100644
--- a/client/src/routes/about.svelte
+++ b/client/src/routes/about.svelte
@@ -22,10 +22,12 @@
 
 	<AboutParagraph title="how does it work?">
 		<span>
-			each note has a 512bit generated <i>id</i> that is used to retrieve the note. the note is then
-			encrypted with aes in gcm mode on the client side and then sent to the server. data is stored in
-			memory and never persisted to disk. the server never sees the encryption key and cannot decrypt
-			the contents of the notes even if it tried to.
+			each note has a generated <code>id (256bit)</code> and <code>key 256(bit)</code>. The
+			<code>id</code>
+			is used to save & retrieve the note. the note is then encrypted with aes in gcm mode on the client
+			side with the <code>key</code> and then sent to the server. data is stored in memory and never
+			persisted to disk. the server never sees the encryption key and cannot decrypt the contents of
+			the notes even if it tried to.
 		</span>
 	</AboutParagraph>
 
diff --git a/src/note/model.rs b/src/note/model.rs
index 6cbb092..c9e1792 100644
--- a/src/note/model.rs
+++ b/src/note/model.rs
@@ -20,7 +20,7 @@ pub struct NotePublic {
 }
 
 pub fn generate_id() -> String {
-  let mut id: [u8; 64] = [0; 64];
+  let mut id: [u8; 32] = [0; 32];
   let sr = ring::rand::SystemRandom::new();
   let _ = sr.fill(&mut id);
   return bs62::encode_data(&id);