diff --git a/Makefile b/Makefile
index 3ee7ff57..45a2b693 100644
--- a/Makefile
+++ b/Makefile
@@ -4,7 +4,7 @@ build:
 	$(PELICAN) -s pelican.conf.py content
 
 upload: build
-	rsync -e "ssh -p 22" -P -rvz --delete output/* alexis@172.19.2.119:/home/www/notmyidea.org/blog
+	rsync -e "ssh -p 22" -P -rvz --delete output/* files:/home/www/notmyidea.org/blog
 
 serve: build
 	 cd output && python -m pelican.server 8000
diff --git a/content/crypto/webcrypto-distribution-signing.rst b/content/crypto/webcrypto-distribution-signing.rst
index 98e99a93..b74f77ce 100644
--- a/content/crypto/webcrypto-distribution-signing.rst
+++ b/content/crypto/webcrypto-distribution-signing.rst
@@ -117,3 +117,15 @@ this design has many security problems attached to it.
 However, that's a problem I would really like to see solved one day, so here
 the start of the discussion, don't hesitate to `get in touch
 </pages/about.html>`_!
+
+Addendum
+========
+
+It seems possible to increase the level a user has in a Web Application by
+adding indicators in the User-Agent. For instance, when using an application
+that's actually signed by someone considered trustful by the User-Agent (or the
+distributor of the User-Agent), a little green icon could be presented to the
+User, so they know that they can be confident about this.
+
+A bit like User-Agents do for SSL, but for the actual signature of the files
+being viewed.