commit 33c4622b5e0605acba9b269fa40e47fc0bde0e2e
Author: root <root@hub.scroll.pub>
Date: 2025-01-10 01:00:21 +0000
Subject: Initial commit
diff --git a/feed.scroll b/feed.scroll
new file mode 100644
index 0000000..8090681
--- /dev/null
+++ b/feed.scroll
@@ -0,0 +1,2 @@
+buildRss
+printFeed All
\ No newline at end of file
diff --git a/footer.scroll b/footer.scroll
new file mode 100644
index 0000000..df06393
--- /dev/null
+++ b/footer.scroll
@@ -0,0 +1,3 @@
+importOnly
+center
+scrollVersionLink
\ No newline at end of file
diff --git a/header.scroll b/header.scroll
new file mode 100644
index 0000000..6771f5e
--- /dev/null
+++ b/header.scroll
@@ -0,0 +1,14 @@
+importOnly
+buildHtml
+buildTxt
+homeButton
+leftRightButtons
+baseUrl https://ssl-mistake.scroll.pub
+metaTags
+editButton
+editBaseUrl /edit.html?folderName=ssl-mistake.scroll.pub&fileName=
+metaTags
+style.css
+script.js
+container
+printTitle
\ No newline at end of file
diff --git a/index.scroll b/index.scroll
new file mode 100644
index 0000000..dc2211c
--- /dev/null
+++ b/index.scroll
@@ -0,0 +1,4 @@
+title SSL Was a Mistake
+header.scroll
+printSnippets All
+footer.scroll
\ No newline at end of file
diff --git a/prompt.json b/prompt.json
new file mode 100644
index 0000000..32a0fa0
--- /dev/null
+++ b/prompt.json
@@ -0,0 +1,25 @@
+{
+ "id": "d25f7b5d-0a33-4301-bfde-54f77165fe6c",
+ "object": "chat.completion",
+ "created": 1736470799,
+ "model": "deepseek-chat",
+ "choices": [
+ {
+ "index": 0,
+ "message": {
+ "role": "assistant",
+ "content": "---domain---\nssl-mistake.scroll.pub\n---index.scroll---\ntitle SSL Was a Mistake\nheader.scroll\nprintSnippets All\nfooter.scroll\n---ssl-was-a-mistake.scroll---\ntitle SSL Was a Mistake\ntags All\nheader.scroll\nIn 1994, Netscape introduced SSL to encrypt web traffic. It was a noble goal, but the implementation was flawed from the start. SSL (and its successor TLS) created a false sense of security while introducing complexity, performance overhead, and centralization risks.\n\nConsider this: over 90% of web traffic is now encrypted, yet phishing and malware attacks are at an all-time high. Encryption didn't solve security - it just moved the battlefield. Meanwhile, the certificate authority system has become a bloated, expensive mess. In 2022 alone, Let's Encrypt issued over 2.5 billion certificates, creating a massive attack surface.\n\nThe real mistake was tying encryption to identity verification. We could have had encryption without the CA system. But now we're stuck with a brittle, centralized infrastructure that's one CA compromise away from catastrophe.\nfooter.scroll\n---the-future-is-unencrypted.scroll---\ntitle The Future is Unencrypted\ntags All\nheader.scroll\nAs we enter the post-SSL era, it's time to rethink web security. The future belongs to protocols like Gemini and Gopher that prioritize simplicity over false security. These lightweight protocols prove that encryption isn't always necessary.\n\nConsider that most web content is public anyway. Do we really need to encrypt every cat video and blog post? The energy cost of SSL is staggering - a 2018 study found that HTTPS adds 35% more server energy usage. For what? To encrypt content that's meant to be public?\n\nThe unencrypted web is faster, simpler, and more decentralized. It's time to embrace it.\nfooter.scroll\n---header.scroll---\nimportOnly\nbuildHtml\nbuildTxt\nhomeButton\nleftRightButtons\nbaseUrl https://ssl-mistake.scroll.pub\nmetaTags\neditButton\neditBaseUrl /edit.html?folderName=ssl-mistake.scroll.pub&fileName=\nmetaTags\nstyle.css\nscript.js\ncontainer\nprintTitle\n---feed.scroll---\nbuildRss\nprintFeed All\n---footer.scroll---\nimportOnly\ncenter\nscrollVersionLink\n---style.css---\n:root {\n --primary: #2c3e50;\n --secondary: #34495e;\n --accent: #e74c3c;\n --text: #ecf0f1;\n --bg: #1a1a1a;\n}\n\nbody {\n font-family: system-ui, sans-serif;\n line-height: 1.6;\n margin: 0;\n padding: 2rem;\n background: var(--bg);\n color: var(--text);\n max-width: 800px;\n margin: 0 auto;\n}\n\na {\n color: var(--accent);\n text-decoration: none;\n}\n\na:hover {\n text-decoration: underline;\n}\n\nh1, h2, h3 {\n color: var(--primary);\n margin-top: 2rem;\n}\n\nheader {\n border-bottom: 2px solid var(--secondary);\n padding-bottom: 1rem;\n margin-bottom: 2rem;\n}\n\nfooter {\n border-top: 2px solid var(--secondary);\n padding-top: 1rem;\n margin-top: 2rem;\n text-align: center;\n}\n\n@media (max-width: 600px) {\n body {\n padding: 1rem;\n }\n \n h1 {\n font-size: 1.8rem;\n }\n}\n\n@keyframes fadeIn {\n from { opacity: 0; }\n to { opacity: 1; }\n}\n\n.container {\n animation: fadeIn 0.5s ease-in;\n}\n\nblockquote {\n border-left: 4px solid var(--accent);\n padding-left: 1rem;\n margin: 1.5rem 0;\n color: var(--secondary);\n}\n---script.js---\n// Smooth scroll for anchor links\ndocument.querySelectorAll('a[href^=\"#\"]').forEach(anchor => {\n anchor.addEventListener('click', function (e) {\n e.preventDefault();\n document.querySelector(this.getAttribute('href')).scrollIntoView({\n behavior: 'smooth'\n });\n });\n});\n\n// Lazy load images\ndocument.addEventListener('DOMContentLoaded', function() {\n let lazyImages = [].slice.call(document.querySelectorAll('img.lazy'));\n \n if ('IntersectionObserver' in window) {\n let lazyImageObserver = new IntersectionObserver(function(entries, observer) {\n entries.forEach(function(entry) {\n if (entry.isIntersecting) {\n let lazyImage = entry.target;\n lazyImage.src = lazyImage.dataset.src;\n lazyImage.classList.remove('lazy');\n lazyImageObserver.unobserve(lazyImage);\n }\n });\n });\n\n lazyImages.forEach(function(lazyImage) {\n lazyImageObserver.observe(lazyImage);\n });\n }\n});\n---end---"
+ },
+ "logprobs": null,
+ "finish_reason": "stop"
+ }
+ ],
+ "usage": {
+ "prompt_tokens": 396,
+ "completion_tokens": 1089,
+ "total_tokens": 1485,
+ "prompt_cache_hit_tokens": 0,
+ "prompt_cache_miss_tokens": 396
+ },
+ "system_fingerprint": "fp_3a5770e1b4"
+}
\ No newline at end of file
diff --git a/readme.scroll b/readme.scroll
new file mode 100644
index 0000000..ee26992
--- /dev/null
+++ b/readme.scroll
@@ -0,0 +1,3 @@
+# ssl-mistake.scroll.pub
+
+blog generated by DeepSeek from prompt: a blog arguing SSL was a mistake
\ No newline at end of file
diff --git a/script.js b/script.js
new file mode 100644
index 0000000..7a50cab
--- /dev/null
+++ b/script.js
@@ -0,0 +1,31 @@
+// Smooth scroll for anchor links
+document.querySelectorAll('a[href^="#"]').forEach(anchor => {
+ anchor.addEventListener('click', function (e) {
+ e.preventDefault();
+ document.querySelector(this.getAttribute('href')).scrollIntoView({
+ behavior: 'smooth'
+ });
+ });
+});
+
+// Lazy load images
+document.addEventListener('DOMContentLoaded', function() {
+ let lazyImages = [].slice.call(document.querySelectorAll('img.lazy'));
+
+ if ('IntersectionObserver' in window) {
+ let lazyImageObserver = new IntersectionObserver(function(entries, observer) {
+ entries.forEach(function(entry) {
+ if (entry.isIntersecting) {
+ let lazyImage = entry.target;
+ lazyImage.src = lazyImage.dataset.src;
+ lazyImage.classList.remove('lazy');
+ lazyImageObserver.unobserve(lazyImage);
+ }
+ });
+ });
+
+ lazyImages.forEach(function(lazyImage) {
+ lazyImageObserver.observe(lazyImage);
+ });
+ }
+});
\ No newline at end of file
diff --git a/ssl-was-a-mistake.scroll b/ssl-was-a-mistake.scroll
new file mode 100644
index 0000000..38e2152
--- /dev/null
+++ b/ssl-was-a-mistake.scroll
@@ -0,0 +1,9 @@
+title SSL Was a Mistake
+tags All
+header.scroll
+In 1994, Netscape introduced SSL to encrypt web traffic. It was a noble goal, but the implementation was flawed from the start. SSL (and its successor TLS) created a false sense of security while introducing complexity, performance overhead, and centralization risks.
+
+Consider this: over 90% of web traffic is now encrypted, yet phishing and malware attacks are at an all-time high. Encryption didn't solve security - it just moved the battlefield. Meanwhile, the certificate authority system has become a bloated, expensive mess. In 2022 alone, Let's Encrypt issued over 2.5 billion certificates, creating a massive attack surface.
+
+The real mistake was tying encryption to identity verification. We could have had encryption without the CA system. But now we're stuck with a brittle, centralized infrastructure that's one CA compromise away from catastrophe.
+footer.scroll
\ No newline at end of file
diff --git a/style.css b/style.css
new file mode 100644
index 0000000..36a5f87
--- /dev/null
+++ b/style.css
@@ -0,0 +1,71 @@
+:root {
+ --primary: #2c3e50;
+ --secondary: #34495e;
+ --accent: #e74c3c;
+ --text: #ecf0f1;
+ --bg: #1a1a1a;
+}
+
+body {
+ font-family: system-ui, sans-serif;
+ line-height: 1.6;
+ margin: 0;
+ padding: 2rem;
+ background: var(--bg);
+ color: var(--text);
+ max-width: 800px;
+ margin: 0 auto;
+}
+
+a {
+ color: var(--accent);
+ text-decoration: none;
+}
+
+a:hover {
+ text-decoration: underline;
+}
+
+h1, h2, h3 {
+ color: var(--primary);
+ margin-top: 2rem;
+}
+
+header {
+ border-bottom: 2px solid var(--secondary);
+ padding-bottom: 1rem;
+ margin-bottom: 2rem;
+}
+
+footer {
+ border-top: 2px solid var(--secondary);
+ padding-top: 1rem;
+ margin-top: 2rem;
+ text-align: center;
+}
+
+@media (max-width: 600px) {
+ body {
+ padding: 1rem;
+ }
+
+ h1 {
+ font-size: 1.8rem;
+ }
+}
+
+@keyframes fadeIn {
+ from { opacity: 0; }
+ to { opacity: 1; }
+}
+
+.container {
+ animation: fadeIn 0.5s ease-in;
+}
+
+blockquote {
+ border-left: 4px solid var(--accent);
+ padding-left: 1rem;
+ margin: 1.5rem 0;
+ color: var(--secondary);
+}
\ No newline at end of file
diff --git a/the-future-is-unencrypted.scroll b/the-future-is-unencrypted.scroll
new file mode 100644
index 0000000..ff19a1f
--- /dev/null
+++ b/the-future-is-unencrypted.scroll
@@ -0,0 +1,9 @@
+title The Future is Unencrypted
+tags All
+header.scroll
+As we enter the post-SSL era, it's time to rethink web security. The future belongs to protocols like Gemini and Gopher that prioritize simplicity over false security. These lightweight protocols prove that encryption isn't always necessary.
+
+Consider that most web content is public anyway. Do we really need to encrypt every cat video and blog post? The energy cost of SSL is staggering - a 2018 study found that HTTPS adds 35% more server energy usage. For what? To encrypt content that's meant to be public?
+
+The unencrypted web is faster, simpler, and more decentralized. It's time to embrace it.
+footer.scroll
\ No newline at end of file