19.xhtml 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217
  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/19.xhtml" />
  27. <title>A panic-filled essay rush &lt;https://y.st./en/weblog/2016/10-October/19.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/19.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/18.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/10-October/20.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>A panic-filled essay rush</h1>
  67. <p>Day 00592: Wednesday, 2016 October 19</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/19.jpg" alt="Chinese lanterns" 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. Perhaps this the upcoming term is a good one to only be enrolled in one course during.
  80. Theoretically, we&apos;re going to be moving soon, so having less coursework could play in my favor.
  81. I&apos;m still not too happy about what course that I have to take though, as it&apos;s not at all helpful toward my degree.
  82. </p>
  83. <p>
  84. I finished up my <a href="/en/coursework/POLS1503/Global_pathogens_and_GMOs.xhtml"><span title="Globalization">POLS 1503</span> essay</a> finally.
  85. I went over it after completing it to check for basic errors, but it would have really helped if I&apos;d finished it early like I usually do.
  86. Each day that I have to reread my essays is another day that I find small ways to improve them.
  87. On this essay, I made each in-line citation into a link to the specific entry in the references section that it corresponded to, but the University of the People submission form stripped all my <code>id</code> attributes, breaking the links.
  88. I had to remove the broken links to avoid causing confusion for whatever students end up reading my work.
  89. I almost skipped rereading my <a href="/en/coursework/UNIV1001/A_conflict_with_T-Mobile.xhtml"><span title="Online Education Strategies">UNIV 1001</span> essay</a> today, but I thought better of it and did go over it again.
  90. I&apos;m glad that I did! I found several mistakes and things that I needed to rephrase.
  91. This is exactly the kind of touch-up work that I am unable to do on my <span title="Globalization">POLS 1503</span> essay due to having only completed it today.
  92. I mean, I did reread it after finishing, but that&apos;s nu substitute for rereading it on several different days.
  93. </p>
  94. <p>
  95. Strangely, after my panic-filled essay rush, I sat down for some unnecessary schoolwork.
  96. Though I&apos;ve already made every discussion reply that I need to for my grade, I submitted four more posts in response to people that had directly addressed me.
  97. </p>
  98. <blockquote>
  99. <p>
  100. Sure, if you redefine the word &quot;religion&quot;, science would be one.
  101. In that case though, environmentalism, veganism, the free culture movement, and several other things would be religions as well.
  102. That&apos;s not necessarily a bad thing, but it&apos;s important to take into account.
  103. </p>
  104. <p>
  105. Funny story: I&apos;ve actually heard that some modern scientists believe that the big bang never happened.
  106. One current theory states that perhaps the universe always was.
  107. According to this theory, the universe isn&apos;t expanding either, and the blue-shift of light from other galaxies is explained by some quantum mechanics principle that I don&apos;t understand.
  108. Quantum mechanics always confuse me.
  109. In any case, our existence wouldn&apos;t prove the big bang, as our existence doesn&apos;t rule out other theories.
  110. </p>
  111. <p>
  112. Yeah, medical professionals of old might have though I was mentally ill as well, as I&apos;m asexual.
  113. </p>
  114. </blockquote>
  115. <blockquote>
  116. <p>
  117. I can&apos;t say that there&apos;s no way of anything in particular.
  118. There&apos;s always a chance that I&apos;ll lack the specific skills that they&apos;re looking for! All that I can do is try to do my best to learn the best skills that I can, especially critical thinking skills.
  119. </p>
  120. </blockquote>
  121. <blockquote>
  122. <p>
  123. I&apos;ve never been a fan of those &quot;11 - 1 = 1&quot;-type &quot;mathematical&quot; solutions.
  124. That second method about chopping off the corner of a polygon to form another polygon is very clever though!
  125. </p>
  126. </blockquote>
  127. <blockquote>
  128. <p>
  129. I completely agree that the person working in the freezer had no excuse for not knowing that it was a bad idea to stack full boxes on an empty box.
  130. Not only do you risk a collapse like that, it also blocks access to the already-open box, so you have to prematurely open a new one.
  131. If they&apos;d put any thought into their actions in any direction, they wouldn&apos;t have done that.
  132. I just think that &quot;common sense&quot; is the wrong label for actually thinking things through.
  133. </p>
  134. </blockquote>
  135. <p>
  136. My program advisor wrote back saying that I don&apos;t need to send proof of high school completion after all, as the school does indeed already have it.
  137. They also said that I might be able to register for different courses during the late registration period.
  138. They did not elaborate on that, but said that in future terms, there should be many more courses available to me.
  139. They didn&apos;t say this, but it&apos;s possible that my account is under some sort of probation due to this being my first term at the university.
  140. Once this term is over, the probationary period may be over, which might be when new courses become available for registration.
  141. </p>
  142. <p>
  143. Thankfully, there are no essays this week.
  144. This week&apos;s section of the course has been made available, along with part of next week&apos;s course material.
  145. Next week will include the final exams.
  146. This week&apos;s course materials include a course evaluation for each course, which I believe is for the students to provide feedback about the courses.
  147. However, both evaluation are closed,listing close dates in the past.
  148. I believe that these were evaluations for past iterations of the courses, and that at some point, the new evaluation forms will be made available.
  149. </p>
  150. <p>
  151. I wrote up my main response for the discussion assignment in <span title="Online Education Strategies">UNIV 1001</span>, which asked us to talk about one failure and one success that we&apos;ve had, then explain why we felt that these were a failure and a success.
  152. I didn&apos;t have time to complete the <span title="Globalization">POLS 1503</span> discussion assignment response, but I got started on it, and will finish it tomorrow.
  153. </p>
  154. <blockquote>
  155. <p>
  156. If you thumb through my <a href="https://y.st./en/weblog/">journal</a>, you&apos;ll probably find several failures that I&apos;ve had, though nothing particularly outstanding is coming to mind right now.
  157. I did fail to convince my mother to switch away from Verizon recently though.
  158. Verizon&apos;s been ripping my mother off for years, and finally, it looked like they&apos;d had enough.
  159. I showed them better, cheaper networks.
  160. For a mere $30 <abbr title="United States Dollars">USD</abbr> per month, my mother could have unlimited talk, <abbr title="Short Message Service">SMS</abbr>, and data transfer with no overage fees! With Verizon, they&apos;re instead paying over $100 <abbr title="United States Dollars">USD</abbr> for limited data transfer, monthly threats of overage charges, and frequent arguments with the carrier.
  161. I put pressure on my mother to switch, brought my mother pamphlets showing several very good deals that they could get to replace Verizon, and even came in-store with my mother to debunk misinformation from the Verizon representatives and get the representatives to expose Verizon&apos;s inadequacies.
  162. It was all in vain though.
  163. Alas, my mother is a creature of habit, and would rather complain about their situation than actually do anything about it.
  164. </p>
  165. <p>
  166. Why do I consider my efforts toward this goal a failure? Well, my mother signed away another two years to Verizon to get the latest iTrash, which of course raised their bill even further.
  167. They&apos;re bound to both Verizon and Apple again, and I won&apos;t have another chance to try to brake the awful cycle again for at least two years.
  168. Next time that they complain about Verizon, all that I&apos;ll be able to do is say &quot;I told you so.&quot;.
  169. </p>
  170. <p>
  171. The most memorable goal that I set for myself and successfully met was that of getting a five-character domain name in the form &quot;{one character}.{two characters}.&quot;.
  172. I&apos;ve wanted a short domain name like that for years.
  173. I finally sat down and started doing research on all the <abbr title="country code top-level domain">ccTLD</abbr>s available, and one by one, I checked to see which <abbr title="country code top-level domain">ccTLD</abbr>s allowed registration by foreigners and which allowed registration of single-character <abbr title="Second Level Domain">SLD</abbr>s.
  174. I checked registration renewal pricing, I checked initial registration pricing, and I checked which domain names had already been registered.
  175. I kept detailed notes on my efforts and findings, most of which were lost due to a hard drive failure later.
  176. While the bulk on my notes were on my efforts, the process, and the experience and were lost, I do still have most of the notes on <a href="https://y.st./en/URI_research/ccTLDs.xhtml">my findings</a>.
  177. After nearly a month of research, I had a list of what I thought at the time were the most likely chances for me to find the domain name that I had wanted for so long.
  178. I couldn&apos;t do any further work in isolation though, and had to actually reach out to the registries themselves, along with one registrar that seemed to be tied to an expired domain.
  179. One by one, each registrar that even wrote back to me turned me down, until the <a href="http://www.nic.st./"><code>st.</code></a> registry said &quot;yes&quot;! Fortunately, I waited a bit to take them up on their offer, because I soon after suffered from a hard drive failure.
  180. I normally have a full backup of everything, but I had just backed up my data and wiped my laptop, removing the primary copy.
  181. By the time that I tried to restore my data from the backup, I found that the drive on which the backup resided had died.
  182. I lost all my files, including my encrypted password database.
  183. In losing that password file, I lost my passwords for every account that I had everywhere.
  184. I lost all my domain names that I had at the time, due to losing the password to the accounts that I had at my registrars&apos; websites, and had I bought my new short name already, I would have lost that too.
  185. It took some time to put the pieces back together, but I did manage to buy that domain, one week after I&apos;d initially planned to finalize the purchase.
  186. </p>
  187. <p>
  188. Why do I feel that I was successful at acquiring a short domain name? Try running <code>whois y.st.</code> on your command line and see for yourself! That&apos;s my legal name and contact information that reside in the whois database.
  189. I use that domain daily for <a href="https://y.st./">Web</a>, <a href="mailto:contact@y.st">email</a>, and <a href="xmpp:y@y.st"><abbr title="Extensible Messaging and Presence Protocol">XMPP</abbr></a>, among other things.
  190. I used to use it for <abbr title="Internet Relay Chat">IRC</abbr> as well, though my <abbr title="Internet Relay Chat">IRC</abbr> server is currently offline.
  191. </p>
  192. </blockquote>
  193. <p>
  194. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  195. </p>
  196. <hr/>
  197. <p>
  198. Copyright © 2016 Alex Yst;
  199. 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>.
  200. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  201. My address is in the source comments near the top of this document.
  202. This license also applies to embedded content such as images.
  203. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  204. </p>
  205. <p>
  206. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  207. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F19.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%2F19.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  208. </p>
  209. </body>
  210. </html>