no-js.html 6.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151
  1. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
  2. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
  3. <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
  4. <head>
  5. <title>Any Browser and Why it's Important - Kevin "The Nuclear" Bloom's Personal Website</title>
  6. <link rel="shortcut icon" type="image/png" href="/img/guy-in-space.png"/>
  7. <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
  8. <meta name="generator" content="Org mode" />
  9. <meta name="author" content="Kevin &quot;The Nuclear&quot; Bloom" />
  10. <meta http-equiv="cache-control" content="no-cache, must-revalidate, post-check=0, pre-check=0" />
  11. <meta http-equiv="cache-control" content="max-age=0" />
  12. <meta http-equiv="expires" content="0" />
  13. <meta http-equiv="expires" content="Tue, 01 Jan 1980 1:00:00 GMT" />
  14. <meta http-equiv="pragma" content="no-cache" />
  15. <link rel='stylesheet' href='/styles/main.2.css' />
  16. </head>
  17. <body>
  18. <div id="preamble" class="status">
  19. <div id="banner">
  20. <h1><a href="/home.html">Kevin "The Nuclear" Bloom</a></h1>
  21. <hr />
  22. <div id="navit">
  23. <a href="/contact.html">Contact</a>
  24. &nbsp;
  25. <a href="/blog.html">Blog</a>
  26. &nbsp;
  27. <a href="/projects.html">Projects</a>
  28. &nbsp;
  29. <a href="/about-me.html">About Me</a>
  30. </div>
  31. </div>
  32. </div>
  33. <div id="content">
  34. <div id="outline-container-org12fd46b" class="outline-2">
  35. <h2 id="org12fd46b">Any Browser and Why it's Important</h2>
  36. <div class="outline-text-2" id="text-org12fd46b">
  37. <div class="PREVIEW">
  38. <p>
  39. You've come to the site of a web developer (me) and were shocked. You immediately
  40. thought: "Lol, why is his site so <i>old</i> looking? This isn't the 90s!" Due to my
  41. prediction abilities, I foresaw this happening, thus, this article was born.
  42. </p>
  43. </div>
  44. <p>
  45. But seriously, I do have a valid explanation as to why the site looks like
  46. this. In fact, I have 3 reasons: aesthetics, laziness, and freedom. The first
  47. two in the list are quick hitters and don't really need to be explain in too
  48. much detail. Aesthetics: I like how old sites look. They are simple, easy to
  49. understand, and have a hacker feel. Laziness: I didn't really feel like putting
  50. that much effort into this. I'd rather spend my time writing articles and
  51. lisping.
  52. </p>
  53. <p>
  54. That's right, a new paragraph for explaining the freedom part. To explain this
  55. we must think outside of the first world country that you are probably in right
  56. now. We have to consider what the computing situation for people who are less
  57. fortunate; namely, those in lesser developed countries or poorer people in
  58. developed countries. Think about it. What kind of computer does someone in a
  59. third world country look like? How powerful might it be? Chances are that the
  60. machine probably isn't the best. It's either old and "obsolete" or under-powered
  61. and slow. Chances are that machine probably has slow Internet as well. Keep that
  62. in your head for a moment.
  63. </p>
  64. <p>
  65. Now imagine someone using that computer to access a JS-bloated site such as
  66. Facebook, Twitter, Amazon, etc. That computer probably isn't going to work all
  67. that well. This is an issue because those sites are preventing people who don't
  68. have high-quality machines to properly use their site. This becomes a more
  69. serious problem if the site is an educational, news, or religious site. What
  70. that means is that the site owners are preventing that less fortunate person
  71. from education and information. This is a disjustice towards that person.
  72. </p>
  73. <p>
  74. I found out about this concept when reading the literature found on the amazing
  75. <a href="https://www.dillo.org/">dillo</a> web browser's site (<a href="https://www.dillo.org/funding/objectives.html">here</a>). Dillo allows people with any kind of computer
  76. to access the web as best as they can. It is a truly great browser and probably
  77. my favorite. They can do this because their browser doesn't support JS. So a lot
  78. of the web is broken when using it, but at least you get the content. Another
  79. related reason is called <a href="http://www.anybrowser.org/campaign/">Any Browser</a>. This is basically a movement to make web
  80. content viewable on any browser with or without JS or CSS.
  81. </p>
  82. <p>
  83. Most likely you think that those reasons are stupid - and that's okay! If the
  84. entire web looked like this site it would be pretty dang boring! However, it
  85. would make the web a better place. "Better place? How?" Well, there are a few
  86. issues with JS, especially when that <a href="http://www.fsf.org/blogs/licensing/no-one-should-have-to-use-proprietary-software-to-communicate-with-government">JS is nonfree</a>; meaning you have <i>no idea</i>
  87. what is being ran on your browser! JS can unmask your IP address if you're using
  88. a proxy such as <a href="https://www.torproject.org/">Tor</a>, it can contain spyware that can do all sorts of nasty
  89. things, and since it's nonfree, it's a destruction of <i>your</i> freedom!
  90. </p>
  91. <p>
  92. Once again, you probably don't care. I can understand that. I'm not super
  93. serious about the nonfree JS argument but I am careful whenever I do use
  94. JS. Especially on Internet tyrants such as <a href="https://stallman.org/google.html">Google</a>, <a href="https://stallman.org/facebook.html">Facebook</a>, or <a href="https://stallman.org/amazon.html">Scamazon</a>!
  95. Attempt to not poison your computer by visiting these site. For web search, use
  96. a freedom respecting search engine like <a href="https://duckduckgo.com/">DuckDuckGo</a>, <a href="https://www.startpage.com/">StartPage</a>, or (my favorite)
  97. <a href="https://searx.me/">SearX</a>. If you have Facebook, don't use it on your personal machine. I only use
  98. Facebook on my already-compromised iPhone. Twitter isn't really any better and
  99. I'm sure I'll write an article about it someday. Reddit isn't bad but still
  100. requirements nonfree JS, but if you can get past that, you're good! There are
  101. also a few free software social medias but realistically they don't compare to
  102. the bigger ones due to lack of mainstream use. Screw Amazon&#x2026; (Middle fingers
  103. to the sky screaming)
  104. </p>
  105. <p>
  106. Anyways, I got a little off topic&#x2026; Moral of the story is, I keep the site
  107. minimal such that any one with a slow or old computer can still view the site
  108. with ease! Also, I don't have any JS because I'm lazy, don't like the language,
  109. and don't want to mess around with licensing my JS.
  110. </p>
  111. </div>
  112. </div>
  113. </div>
  114. <div id="postamble" class="status">
  115. <p class="author">Author: Kevin "The Nuclear" Bloom</p>
  116. </div>
  117. <div id="footer">
  118. <hr />
  119. <p>
  120. <a href="https://anybrowser.org/campaign/">
  121. <img src="/img/any-browser.png" alt="Viewable with any browser! No JS, no cookies, no bullshit!"/></a>
  122. &nbsp;
  123. <a href="http://validator.w3.org/check?uri=nuclearkev.org"><img
  124. src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0 Strict" height="31" width="88" /></a>
  125. &nbsp;
  126. <a href="http://NetBSD.org/"><img
  127. src="https://www.netbsd.org/images/powered-by-NetBSD.png" alt="NetBSD" width="88" /></a>
  128. </p>
  129. <p>
  130. Copyright © 2017-2022 Kevin "The Nuclear" Bloom
  131. </p>
  132. </div>
  133. </body>
  134. </html>