aboutsummaryrefslogtreecommitdiff
path: root/html/blog
diff options
context:
space:
mode:
authorAlex Scerba <alex@scerba.org>2025-09-18 10:32:11 -0500
committerAlex Scerba <alex@scerba.org>2025-09-18 10:32:11 -0500
commit9e93eb48ecd3c605b653a1de147a916c899ec7c1 (patch)
tree70e55007767b1a72eca44f9e159d38d65de3516c /html/blog
parent7309d6895f9cfee7ecf61568b81aceb8adc1ccc6 (diff)
Fix typo
Diffstat (limited to 'html/blog')
-rw-r--r--html/blog/2025-02-10+The_Problem_With_Web_Links_In_Reporting+tech.tmpl.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/html/blog/2025-02-10+The_Problem_With_Web_Links_In_Reporting+tech.tmpl.html b/html/blog/2025-02-10+The_Problem_With_Web_Links_In_Reporting+tech.tmpl.html
index 2fbdfb9..e3ac3ed 100644
--- a/html/blog/2025-02-10+The_Problem_With_Web_Links_In_Reporting+tech.tmpl.html
+++ b/html/blog/2025-02-10+The_Problem_With_Web_Links_In_Reporting+tech.tmpl.html
@@ -5,7 +5,7 @@
<p>This article was from 2016, and I'm accessing this link 9 years later. As I expected from the language on the quote, it was nowhere to be found on today's webpage &lpar;it felt particularly brand unsafe for 2016 or 2025&rpar;. Wanting to see where it came from, and to see if that link would have even worked at the time of writing, I fired up <a href="https://web.archive.org" target="_blank" rel="noopener noreferrer">Archive.org</a>.</p>
<p>As expected, but also unfortunately, the link in 2016 redirected to something very similar to today's page. No sweeping claims relating Intel's own customers to car buyers reciting back processor speeds akin to knowing what engine configuration various cars have. This means even in the time, the source was misleading.</p>
<p>Traveling back in time further, the last date I could find with the quote in the article was from <a href="https://web.archive.org/web/20130220025650/http://www.intel.com/pressroom/intel_inside.htm" target="_blank" rel="noopener noreferrer">Febuary 20th, 2013</a>, right before the launch of Haswell &lpar;Intel 4th Generation Core i products for the layman&rpar;.</p>
- <p>I find this in many articles, be it tech review or eventually my own website. Links die or redirect to new areas with different meanings than what was originally quoted in the article or blog. What is especially frustrating, however, is linking to a broken link at the time of writting and misquoting it without date clarifications, which is the case here. In the case of Harvard Business Review, they still accurately quoted the old site, but the fact that broken links are so common make it more difficult for the average reader to fact check a quote. This makes situations of intentionally fabricating misquotes to paint a narrative even easier.</p>
+ <p>I find this in many articles, be it tech review or eventually my own website. Links die or redirect to new areas with different meanings than what was originally quoted in the article or blog. What is especially frustrating, however, is linking to a broken link at the time of writing and misquoting it without date clarifications, which is the case here. In the case of Harvard Business Review, they still accurately quoted the old site, but the fact that broken links are so common make it more difficult for the average reader to fact check a quote. This makes situations of intentionally fabricating misquotes to paint a narrative even easier.</p>
<p>What's the solution? I believe it's sites like Archive.org. But, while this archive works today, it might not tomorrow as was <a href="https://blog.archive.org/2024/10/21/internet-archive-services-update-2024-10-21/" target="_blank" rel="noopener noreferrer">demonstrated recently</a>. There needs to be a more resilient effort made for archiving the web with many public mirrors. I'll be looking into this more in the next few months.</p>
<p><b>Created:</b> {{ .Date }}</p>
</article>