05.xhtml 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213
  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/11-November/05.xhtml" />
  27. <title>My next term might work out better than current projections predict. &lt;https://y.st./en/weblog/2016/11-November/05.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/11-November/05.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/11-November/04.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/11-November/06.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>My next term might work out better than current projections predict.</h1>
  67. <p>Day 00609: Saturday, 2016 November 05</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/11/05.jpg" alt="The local burnt-out house" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>236 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. Topics for essays that I want to write outside of school:
  80. </p>
  81. <ul>
  82. <li>How the <abbr title="GNU &quot;Free&quot; Documentation License">GFDL</abbr> isn&apos;t a free license, and is effectively nonfree even when invariant sections aren&apos;t used</li>
  83. <li>How the telephone number system is screwy</li>
  84. <li>How postpaid mobile plans are bad for customers</li>
  85. <li>How connections using &quot;untrusted&quot; <abbr title="Transport Layer Security">TLS</abbr> certificates are more trustworthy than connections without any <abbr title="Transport Layer Security">TLS</abbr> certificate at all</li>
  86. <li>The importance of free software</li>
  87. <li>The importance of free media</li>
  88. </ul>
  89. <p>
  90. I had another strange dream last night.
  91. This time, I tried to contact my sibling using an ancient, magic, communication pool.
  92. It was a deep rut in the middle of a hallway.
  93. Passing through the hallway required jumping over this rut, which was filled with water.
  94. The pool had some sort of hologram functionality and audio features, and could record incoming messages for later retrieval or could relay messages in real time.
  95. I tried to reach out to my sibling, who was the one at the communication pool, but they declined the message by telling the pool that they didn&apos;t want to accept the message when it reported that they had an incoming transmission.
  96. It wasn&apos;t that Alyssa didn&apos;t want to talk to me, they just didn&apos;t like using the magic communication pool because they had never taken the time to learn how to use it and didn&apos;t want to bother.
  97. I decided to reach out via email instead, which they do use, and I opened my message with something to the effect of &quot;since you don&apos;t want to use magical email, I&apos;ll try reaching you with regular email instead&quot;.
  98. Next, I was headed to the train station to leave our shared school with on-campus housing.
  99. We passed by a strange tower, which had caught fire, so my friend mentioned something about staying away from it because the flames were dangerous.
  100. Though we weren&apos;t originally headed to the tower, I explained that the tower always caught fire on certain days, and during that time, you could reach parts of the tower that were normally inaccessible.
  101. Furthermore, the frequent floods in the tower were also on a schedule, and opened up access to other parts of the tower.
  102. No one besides me seemed to notice this pattern, but I myself made use of to to reach hidden areas of the tower sometimes.
  103. We peeked into the tower, which had a doorway but no door, but the stairs were messed up.
  104. The stairs that would normally lead down, into the ground, now lead up a short way, dropping off.
  105. The stairs headed up in the other direction were normal, but accessible even without the fire.
  106. I was confused and unable to demonstrate my point.
  107. The friend wanted to show me something though, so we headed in another direction.
  108. They ended up not showing me though, and we split up.
  109. I tried to make it back to the train station, but I got lost.
  110. After a while, I remembered that I knew how to teleport short distances, to I simply teleported to the train station.
  111. It was too late though, I&apos;d missed my train home for the summer.
  112. I went to talk to the school staff about the situation, and the topic of how lost I&apos;d gotten came up, and when I explained that I had to give up looking for the train station and teleport there, they asked why I didn&apos;t just teleport home.
  113. I explained that it was too far, so they said to take short leaps through space, making the journey in several hops, but I said again that it was too far.
  114. Multi-hop or not, it would be exhausting and dangerous.
  115. When they asked what would happen if I tried, I explained that with the multi-hop method, I&apos;d tire and end up splitting myself at some point, killing myself as I ended up with part of myself having teleported and part of myself staying behind.
  116. If I tried to make the journey in one hop, I&apos;d end up completely shredding myself across a longer stretch of the journey, with my body matter split between thousands of places in a straight line between my point of departure and my intended definition, to the point where so little of me would be left at each place that what was left of me would be too small to be visible.
  117. I&apos;d have practically disappeared! One of the staff agreed to help me get home after their several-hour meeting was over, but what I really wanted was for them to activate the portal functionality of the ancient communication device that I&apos;d used earlier, though it was clear that that wasn&apos;t going to happen.
  118. I&apos;m not sure why I wanted to use the teleportation functionality, but I had an ulterior motive.
  119. At that point, I wasn&apos;t trying to get home, or anywhere else in particular.
  120. I ended up wandering off, killing time while I waited for the staff meeting to end, but I ended up in a situation where someone was chasing me.
  121. I ran on the sides of buildings, I teleported, I phased through solid objects, I flew through the air, but none of it mattered.
  122. They remained on my tail, intent on catching me.
  123. I have no idea what would happen if they did, but it scared me too much to allow them to do it.
  124. In the end, i tried flying straight up in the air, but while they struggled to do the same, they managed to draw closer to me than before.
  125. I somehow became aware of the fact that I was dreaming and forced myself to wake up.
  126. </p>
  127. <p>
  128. After waking up, it looked like there was strange, barley-visible writing filling the top half my wall, but it was too dark to make out.
  129. By the light of my laptop monitor though, it was of course not actually there.
  130. After taking note of my strange dream (this journal doubles as a dream journal on the rare occasion that I actually remember dreams), I went back to bed.
  131. </p>
  132. <p>
  133. I had another strange dream, but the memory slipped away too quickly.
  134. There was some sort of &quot;sky sea otter ore&quot;; a mystical mineral that had turned an ordinary human being into an inhuman monster that survived by eating other people.
  135. To eat them, it would open up a diagonal slit in its chest, sucking the people in as they liquefied in its hand.
  136. </p>
  137. <p>
  138. My program advisor wrote back, again insisting that I take <span title="Principles of Business Management">BUS 1101</span> and only <span title="Principles of Business Management">BUS 1101</span>.
  139. I am not amused.
  140. If this is the only term in which this happens, I&apos;ll only be set back one term.
  141. I will be set back that one term though, as because I&apos;m only taking one course this term, I&apos;ll have another term at the end of my degree program where I&apos;ll have one course left to take.
  142. Come to think of it, I might even turn this into a good thing by taking a second course on that final term, allowing me to fit in an extra course that I otherwise wouldn&apos;t have been able to take.
  143. However, if I am repeatedly only able to take one course during various terms, every other time will set me back a term.
  144. Even worse, if they keep putting me in stupid courses that don&apos;t count toward my degree program, I&apos;ll run out of elective credits and will no longer be making progress toward my degree program at all.
  145. They could also continue to only offer courses to me that I&apos;ve already taken, which again, means that I can&apos;t make any progress.
  146. </p>
  147. <p>
  148. Twice now, TotBirdy has disabled itself, allowing Icedove (Thunderbird) to run without it.
  149. This is concerning.
  150. What&apos;s the point of TorBirdy if it&apos;s going to keep causing <abbr title="Domain Name System">DNS</abbr> leaks by shutting off without shutting off the connection with it? Luckily, my proxy settings block all but the <abbr title="Domain Name System">DNS</abbr> requests from going over the clearnet, but still, something must be done about this.
  151. </p>
  152. <p>
  153. I did a bit of research for my <code>cap:</code>-scheme <abbr title="Uniform Resource Identifier">URI</abbr> class, and it seems that the main thing that had been bothering me about that scheme, its lack of strict compatibility with <abbr title="Request for Comments">RFC</abbr> 3986, was just a misunderstanding.
  154. When I had arrived at the conclusion that there was a small compatibility issue, I had been too tired to properly process what I was reading, I guess.
  155. Not only is that scheme&apos;s syntax completely compatible with <abbr title="Request for Comments">RFC</abbr> 3986, <abbr title="Request for Comments">RFC</abbr> even offers a compatibility table for helping <a href="https://tools.ietf.org./html/rfc3986#appendix-D.2">understand old <abbr title="Uniform Resource Identifier">URI</abbr> scheme definitions</a>.
  156. Apparently, it redefines some of the old rules to make them a bit more flexible too, though it also makes some of the old rules less flexible.
  157. For example, &quot;uric&quot; is redefined to disallow five characters that it formerly allowed: exclamation points, asterisks, apostrophes, and open and close parentheses.
  158. In this case, it introduces an incompatibility between some old previously-minted <abbr title="Uniform Resource Identifier">URI</abbr>s and the specification, but in general, the updated rules might bring some ancient <abbr title="Uniform Resource Identifier">URI</abbr> schemes into compliance with the new general <abbr title="Uniform Resource Identifier">URI</abbr> specification, which as far as I&apos;m concerned, is a very good thing.
  159. I completed the <code>cap:</code>-scheme class, then repaired the <code>acap:</code>-scheme class to account for the new syntax definitions.
  160. Those two appear to be the only schemes that I&apos;ve worked with yet that I needed to go back and fix.
  161. </p>
  162. <p>
  163. It seems that today&apos;s assignments at work were just meant as a refresher.
  164. Because I remembered things too well, I ended up getting sent home early.
  165. It&apos;s kind of ironic; doing better led to less hours and less pay.
  166. I had forgotten how convenient is to work the drive-through and do dishes.
  167. We always have to wash our hands between handling money and performing other tasks, but when washing dishes, we&apos;re already headed back to a sink, so there&apos;s no extra point to stop at.
  168. I also forgot how crusty our hands get when working the lobby register while also flattening dough into pans.
  169. The dough-flattening process involved coting the dough balls in flower, and due to the constant rush, we almost never have time to make sure our hands are perfectly dry after washing them.
  170. So we wash our hands after handling money, then go back and handle the flower with slightly-damp hands.
  171. The one new thing that I did learn was how to work the new drive-through headsets.
  172. We used to have customers order at the drive-through window when I last worked there, but now, we&apos;ve got the menu board actually functioning.
  173. The new headsets allow us to speak with customers at the board, then they drive forward, pay, and receive their products as usual.
  174. It doesn&apos;t seem any more efficient to me, but it does seem a lot more professional.
  175. I&apos;ve also picked up my schedule for next week.
  176. </p>
  177. <p>
  178. University of the People wrote to me, though they weren&apos;t writing back about the course registration issue.
  179. However, it looks like it might get solved.
  180. Students here are required to pass their first term&apos;s courses before being officially admitted as a degree-seeking student.
  181. With an A+ and an A-, I have done that.
  182. Now, it looks like by the end of the week, they plan to choose two courses for me that will count toward my degree and enroll me in them.
  183. I fear that they&apos;ll leave me enrolled in this stupid <span title="Principles of Business Management">BUS 1101</span> course because I&apos;m already in it, then enroll me in only one useful course, but it&apos;d be better than the position that I&apos;m in now.
  184. Another option would be that they leave me enrolled in <span title="Principles of Business Management">BUS 1101</span>, but register me in two courses like they said that they would.
  185. This option seems unlikely, but if I can keep up with the course load, would leave me with more credits at the end of next term.
  186. I think that the solution that I&apos;m hoping for though is that they&apos;ll unregister me from <span title="Principles of Business Management">BUS 1101</span> and enroll me in two actually-needed courses.
  187. I feel like I <strong>*should*</strong> want to take three courses at once to make more progress, but I honestly don&apos;t know if I could handle the work load of three courses, a part-time job, and working on sorting things so that we can get moved.
  188. </p>
  189. <p>
  190. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  191. </p>
  192. <hr/>
  193. <p>
  194. Copyright © 2016 Alex Yst;
  195. 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>.
  196. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  197. My address is in the source comments near the top of this document.
  198. This license also applies to embedded content such as images.
  199. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  200. </p>
  201. <p>
  202. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  203. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F11-November%2F05.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%2F11-November%2F05.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  204. </p>
  205. </body>
  206. </html>