25.xhtml 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <!--
  3. h t t :: / / t /
  4. h t t :: // // t //
  5. h ttttt ttttt ppppp sssss // // y y sssss ttttt //
  6. hhhh t t p p s // // y y s t //
  7. h hh t t ppppp sssss // // yyyyy sssss t //
  8. h h t t p s :: / / y .. s t .. /
  9. h h t t p sssss :: / / yyyyy .. sssss t .. /
  10. <https://y.st./>
  11. Copyright © 2016 Alex Yst <mailto:copyright@y.st>
  12. This program is free software: you can redistribute it and/or modify
  13. it under the terms of the GNU General Public License as published by
  14. the Free Software Foundation, either version 3 of the License, or
  15. (at your option) any later version.
  16. This program is distributed in the hope that it will be useful,
  17. but WITHOUT ANY WARRANTY; without even the implied warranty of
  18. MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  19. GNU General Public License for more details.
  20. You should have received a copy of the GNU General Public License
  21. along with this program. If not, see <https://www.gnu.org./licenses/>.
  22. -->
  23. <!DOCTYPE html>
  24. <html xmlns="http://www.w3.org/1999/xhtml">
  25. <head>
  26. <base href="https://y.st./en/weblog/2016/10-October/25.xhtml" />
  27. <title>Privacy Badger &lt;https://y.st./en/weblog/2016/10-October/25.xhtml&gt;</title>
  28. <link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
  29. <link rel="stylesheet" type="text/css" href="/link/basic.css" />
  30. <link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
  31. <script type="text/javascript" src="/script/javascript.js" />
  32. <meta name="viewport" content="width=device-width" />
  33. </head>
  34. <body>
  35. <nav>
  36. <p>
  37. <a href="/en/">Home</a> |
  38. <a href="/en/a/about.xhtml">About</a> |
  39. <a href="/en/a/contact.xhtml">Contact</a> |
  40. <a href="/a/canary.txt">Canary</a> |
  41. <a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
  42. <a href="/en/opinion/">Opinions</a> |
  43. <a href="/en/coursework/">Coursework</a> |
  44. <a href="/en/law/">Law</a> |
  45. <a href="/en/a/links.xhtml">Links</a> |
  46. <a href="/en/weblog/2016/10-October/25.xhtml.asc">{this page}.asc</a>
  47. </p>
  48. <hr/>
  49. <p>
  50. Weblog index:
  51. <a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
  52. <a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
  53. <a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
  54. </p>
  55. <hr/>
  56. <p>
  57. Jump to entry:
  58. <a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
  59. <a rel="prev" href="/en/weblog/2016/10-October/24.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/10-October/26.xhtml">Next&gt;</a>
  61. <a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
  62. </p>
  63. <hr/>
  64. </nav>
  65. <header>
  66. <h1>Privacy Badger</h1>
  67. <p>Day 00598: Tuesday, 2016 October 25</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/25.jpg" alt="A black chicken" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>249 scheme-specific <abbr title="Uniform Resource Identifier">URI</abbr>-parsing classes to write and add to <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d/releases">include.d</a></li>
  75. <li>1 free elective left in my associate degree program</li>
  76. <li>4 free electives left in my bachelor degree program</li>
  77. </ul>
  78. <p>
  79. Website cleanup tasks left to accomplish:
  80. </p>
  81. <ul>
  82. <li>Remove numeric <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> entities; these pages are written in Unicode, non-<abbr title="American Standard Code for Information Interchange">ASCII</abbr> characters can be used directly.</li>
  83. <li>Find and tag any references to <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> tags in my journal pages.</li>
  84. <li>Find and tag any references to functions, classes, and constants that can be <code>grep</code>ed for; look for backslashes and empty parentheses.</li>
  85. <li>Find and clean up references to <code>/domain_research/</code>.</li>
  86. <li>Build error pages.</li>
  87. </ul>
  88. <p>
  89. I installed <a href="https://addons.mozilla.org./en-US/firefox/addon/privacy-badger-firefox/">Privacy Badger</a> on a bit of a whim today, not thinking that I&apos;d keep it for too long.
  90. After all, extensions such as this use hacky domain blacklists, which are incomplete and messy.
  91. However, it seems that Privacy Badger doesn&apos;t do that! Instead, it starts with a clean slate, allowing everything to track you, then as it learns where trackers are through your own Web browsing habits, it blocks them! THis is a much nicer, more complete, and less hacky solution.
  92. I&apos;ll be keeping this extension around for the forseeable future.
  93. </p>
  94. <p>
  95. Discover wrote back saying that they&apos;ll &quot;attempt&quot; to prevent future charges from my old domain registrar.
  96. Why didn&apos;t they agree to do that last time that I asked them to? Also, why are they only <strong>*attempting*</strong> to block charges instead of just blocking the charges? My old domain registrar can&apos;t charge me if Discover doesn&apos;t allow it to happen.
  97. I&apos;ll need to keep a close eye on my credit card statement over the next year.
  98. </p>
  99. <p>
  100. My <span title="Online Education Strategies">UNIV 1001</span> course discussion board had enough posts today that I was able to complete my responses for the week:
  101. </p>
  102. <blockquote>
  103. <p>
  104. I don&apos;t know if you&apos;ve heard about how the net neutrality rules were overturned in the United States, but it was because Verizon fought to take the authority to enforce those rules away from our <abbr title="Federal Communications Commission">FCC</abbr>.
  105. Thankfully, the net neutrality rules are back in effect, at least for now, but without them, <abbr title="Internet service provider">ISP</abbr>s are allowed to discriminate against Internet traffic of their choosing.
  106. For example, another company, Comcast, used this period in which the net neutrality rules didn&apos;t apply to slow down all traffic between Comcast customers and Netflix until Netflix agreed to pay a high fee to Comcast.
  107. This means that Comcast was double-dipping, demanding payment both from Netflix <strong>*and*</strong> Comcast&apos;s own customers for any traffic between the two.
  108. This is just one example of the problems that Verizon worked to create.
  109. Verizon is an enemy of the Internet, which makes them my enemy as well.
  110. </p>
  111. <p>
  112. That aside, Verizon is also well-known for ripping off their customers.
  113. My mother&apos;s been overpaying them for their service for years.
  114. My mother also can&apos;t use the full amount of data connection use that they pay for out of fear of going over the limit and raking up overage fees.
  115. A reasonable carrier would cut you off at that point unless you specifically asked them for more data connection usage.
  116. A few carriers here in the United States will even allow you to keep using your data connection beyond your usage rate without overage fees, they just slow down the connection until you pay for more data connection usage or your billing cycle restarts.
  117. And to top it off, these more reasonable carriers charge <strong>*less*</strong> for their <strong>*better*</strong> service! There&apos;s also an issue with iPhones on Verizon.
  118. non-iPhones on Verizon don&apos;t have this issue and iPhones on other carriers don&apos;t have this issue.
  119. It makes communication with my mother difficult, as messages come in as attachments instead of as regular messages.
  120. <a href="https://community.verizonwireless.com./thread/783773?start=0&amp;tstart=0">Many people have complained about the problem.</a> Instead of fixing it though, Verizon kept insisting that the problem didn&apos;t exist.
  121. When people kept complaining, as the problem very much <strong>*does*</strong> exist, instead of actually dealing with the issue, they locked the forum topic about it so that they wouldn&apos;t have to listen to the complaining any more.
  122. My mother constantly complains to me about it, but I can&apos;t fix it.
  123. The problem is on my mother&apos;s carrier&apos;s end, Verizon&apos;s end, and they won&apos;t fix it.
  124. I&apos;m no fan of iPhones or Verizon, but if my mother would switch just one of those things, their issue would be solved.
  125. </p>
  126. <p>
  127. I&apos;m aware of the <abbr title="Transport Layer Security">TLS</abbr> issue, but it&apos;s not my website that has it; it&apos;s modern Web browsers.
  128. Specifically, Web browsers complain if the <abbr title="Transport Layer Security">TLS</abbr> certificate isn&apos;t signed by a &quot;trusted&quot; authority.
  129. However, Web browsers don&apos;t complain at all when even <strong>*less*</strong> security is used, such as is the case with unencrypted <code>http:</code> connections.
  130. It could be argued that websites should use certificates from &quot;trusted&quot; authorities, but in that case, websites with no <abbr title="Transport Layer Security">TLS</abbr> certificate should be rejected as well.
  131. Having a <abbr title="Top Level Domain">TLD</abbr> certificate allows for encryption, which is <strong>*always*</strong> safer than not having any encryption at all.
  132. I couldn&apos;t afford to pay the overprices <abbr title="Transport Layer Security">TLS</abbr> certificate fees, and now that I understand better and know where to get gratis &quot;trusted&quot; <abbr title="Transport Layer Security">TLS</abbr> certificates, I&apos;m in no position to change the certificate.
  133. At the moment, I don&apos;t control my own <abbr title="Hypertext Transfer Protocol">HTTP</abbr> server, as I currently don&apos;t even have home Internet service.
  134. Only my Web host is able to swap out the <abbr title="Transport Layer Security">TLS</abbr> certificate.
  135. </p>
  136. <p>
  137. My domain name was never overly important.
  138. I only got it because it made me happy.
  139. Sometimes you have to set goals that make you happy instead of goals that are strictly productive.
  140. I&apos;m a bit of a geek, and domain name length has some interesting properties.
  141. All domain names, including subdomains of other domains, have a length limit of 256 characters, including the trailing dot that most people don&apos;t use or know about.
  142. When you own a domain, you usually own all the subdomains as well.
  143. By registering a shorter name, you get a larger chunk of the domain name space! Does that really matter? No, technically, it doesn&apos;t matter at all.
  144. Even the longest domain name on the market has far more subdomains that someone could possibly use in a lifetime; more subdomains than there are <abbr title="Internet Protocol version Four">IPv4</abbr> and <abbr title="Internet Protocol version Six">IPv6</abbr> addresses combined.
  145. Still, it makes me happy that I own this unbroken chunk of the domain name space.
  146. Getting a bigger chunk would require more money or more political power than I&apos;ll ever have too, which means that I don&apos;t have to worry about what will happen if I run across a more favorable domain.
  147. I can build my Web presence here and know that unless major unforeseen circumstances pop up, I&apos;ll get to keep any backlinks that I build up.
  148. </p>
  149. </blockquote>
  150. <blockquote>
  151. <p>
  152. Different failures have different effects.
  153. Some failures help show my my limits and/or keep me grounded in reality.
  154. Others fire me up and make me fight harder.
  155. In the case of carrier-switching issue, it shows me that no matter how convincing I think that I&apos;m being, I don&apos;t know what other people are thinking.
  156. People are a wild card, and even when you think that you have gotten them over to your side, you may not have.
  157. </p>
  158. </blockquote>
  159. <blockquote>
  160. <p>
  161. If this money were coming from my own pocket, it wouldn&apos;t be going toward iPhones or Verizon, that&apos;s for sure.
  162. If they want those, they have to pay for them themself.
  163. </p>
  164. <p>
  165. My mother isn&apos;t the type that handles &quot;I told you so&quot; well, and will insist to the death that they made the right decision.
  166. Despite all their Windows problems, iPhone problems, and Verizon problems, they refuse to try replacing any of these things (or more).
  167. If they even just tried something else, then went back to what they originally had, it would show that they were open-minded enough to accept the fact that the first choice isn&apos;t always the right choice.
  168. </p>
  169. </blockquote>
  170. <blockquote>
  171. <p>
  172. I pronounce the domain name as &quot;wye dot ess tee dot&quot;, though I use the name &quot;Yst&quot; to refer to myself, which I pronounce as &quot;ist&quot;, like the end of the word &quot;catalyst&quot;.
  173. I actually chose the <code>y.st.</code> domain because all of the standard vowels were taken.
  174. &quot;Y&quot; was the only (sometimes-)vowel left, making it the only unpronounceable short string left.
  175. </p>
  176. </blockquote>
  177. <blockquote>
  178. <p>
  179. When I first started reading that your unacomplished goal was your bachelor degree, I thought that you hadn&apos;t missed that just yet, as you&apos;re still in school! I didn&apos;t realize yet that you&apos;ve returned to school as I have.
  180. I&apos;m sorry to hear about your hard times in the past, but I know how you feel.
  181. I ended up having to leave school as well because of outside pressures from work, and especially from my family.
  182. It looks like we&apos;re both back on the road to education though.
  183. I wish you well in your studies!
  184. </p>
  185. <p>
  186. Balance can be very difficult, and I don&apos;t think that I&apos;m going to be able to accomplish it.
  187. This time though, it won&apos;t be school that has to drop.
  188. Instead, I&apos;ll be putting most of my effort into school and work.
  189. I used to hang out a lot with my family, but it was never because <strong>*I*</strong> wanted to hang out, it was because <strong>*they*</strong> wanted to.
  190. It was a burden to deal with on top of everything else, and finally, something had to break.
  191. This time, they&apos;ll just have to deal with the fact that my time is a limited resource for the next four years.
  192. After that, time will be plenty.
  193. After that, I can hang out, go on hikes, visit relatives, and whatever else they want to do.
  194. </p>
  195. </blockquote>
  196. <blockquote>
  197. <p>
  198. Being a <a href="tel:911;phone-context=+1">911</a> operator sounds like it could be an interesting experience.
  199. I&apos;m not really a fan of telephones, but you could learn a lot about what happens in your town and help people in trouble while doing it.
  200. I can easily see why you&apos;d want such a career.
  201. </p>
  202. <p>
  203. I&apos;m glad to hear that you got out of your old job that you wanted to leave.
  204. If you&apos;re better at finding employment while already employed, maybe you&apos;ll be able to get your 911 operator job if you interview while employed as well.
  205. </p>
  206. </blockquote>
  207. <blockquote>
  208. <p>
  209. Some goals aren&apos;t meant to be.
  210. Once you learn what achieving the goal is like, it may not be the right path to take.
  211. We can grow and learn from our experiences though.
  212. </p>
  213. <p>
  214. You learned a second language.
  215. That&apos;s awesome! I worked on learning a new language, Esperanto, for about a year, but I&apos;ve had to put that aside for now.
  216. I hope to get back to that after graduating school, but for now, it takes more time than I currently have.
  217. </p>
  218. </blockquote>
  219. <p>
  220. I made progress on both on my &quot;learning journal&quot; assignments as well, but I might need to take the extra day granted for these assignments beyond the regular school week again.
  221. I&apos;ve also filled out both course-evaluation surveys for the courses, which are now available, and I used them to complain about the fact that some of the course materials for both courses actively block some users, and in <span title="Online Education Strategies">UNIV 1001</span>, many materials are behind a <abbr title="Completely Automated Public Turing test to tell Computers and Humans Apart">CAPTCHA</abbr> wall.
  222. I could have mentioned <span title="Globalization">POLS 1503</span>&apos;s malfunctioning videos, but I don&apos;t know what the cause of it is.
  223. It used to be that I couldn&apos;t play videos hosted by YouTube, and I blamed Google for that.
  224. However, it turned out later that the problem was actually on my end.
  225. The same could be true of the <span title="Globalization">POLS 1503</span> videos.
  226. </p>
  227. <p>
  228. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  229. </p>
  230. <hr/>
  231. <p>
  232. Copyright © 2016 Alex Yst;
  233. You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
  234. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  235. My address is in the source comments near the top of this document.
  236. This license also applies to embedded content such as images.
  237. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  238. </p>
  239. <p>
  240. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  241. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F25.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F25.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  242. </p>
  243. </body>
  244. </html>