summaryrefslogtreecommitdiff
path: root/content/entry/future-proof-digital-timestamping.md
diff options
context:
space:
mode:
authorNicholas Johnson <nick@nicksphere.ch>2022-09-07 00:00:00 +0000
committerNicholas Johnson <nick@nicksphere.ch>2022-09-07 00:00:00 +0000
commit5fc217637e458b9571c8e022c841c81c4fe9f5170c8b948a31f5bc0c7d584935 (patch)
treec49f6602d8fcfadb1f7fbfe9e1b9d0118128c3d128621b86cf178707a5e270ec /content/entry/future-proof-digital-timestamping.md
parent1e978fcf08ae667e0decbe41e1e47f958dbcad6aa354bb6e056b597b4491efa0 (diff)
downloadjournal-5fc217637e458b9571c8e022c841c81c4fe9f5170c8b948a31f5bc0c7d584935.tar.gz
journal-5fc217637e458b9571c8e022c841c81c4fe9f5170c8b948a31f5bc0c7d584935.zip
Remove excess path traversal in URLs
The path traversal in the URLs make it possible to navigate the journal through static files, but it's not worth the trouble. Hosting a local web server is easy enough.
Diffstat (limited to 'content/entry/future-proof-digital-timestamping.md')
-rw-r--r--content/entry/future-proof-digital-timestamping.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/entry/future-proof-digital-timestamping.md b/content/entry/future-proof-digital-timestamping.md
index df6199f..7ed47c5 100644
--- a/content/entry/future-proof-digital-timestamping.md
+++ b/content/entry/future-proof-digital-timestamping.md
@@ -69,10 +69,10 @@ I just decided to timestamp my journal to create that extra assurance that it's
Link(s):
[1: OpenTimestamps](https://opentimestamps.org/)
-[2: Avoid Using Cryptocurrency](../../../../2021/07/18/avoid-using-cryptocurrency/)
+[2: Avoid Using Cryptocurrency](/2021/07/18/avoid-using-cryptocurrency/)
[3: OpenTimestamps Merkle Trees](https://petertodd.org/2016/opentimestamps-announcement#merkle-trees)
[4: Timestamp Tag](https://git.nicksphere.ch/nicksphere-gmi/tag/?h=timestamp-1)
-[5: Timestamp Commit Data](../../../../resource/timestamp-1.txt)
+[5: Timestamp Commit Data](/resource/timestamp-1.txt)
[6: SHAttered](https://shattered.io/)
[7: SHA1 Is Broken, But It's Still Good Enough for OpenTimestamps](https://petertodd.org/2017/sha1-and-opentimestamps-proofs)
[8: How OpenTimestamps 'Carbon Dated' (almost) The Entire Internet With One Bitcoin Transaction](https://petertodd.org/2017/carbon-dating-the-internet-archive-with-opentimestamps)