06.xhtml 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192
  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/12-December/06.xhtml" />
  27. <title>A disappointing outing &lt;https://y.st./en/weblog/2016/12-December/06.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/12-December/06.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/12-December/05.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/12-December/07.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 disappointing outing</h1>
  67. <p>Day 00640: Tuesday, 2016 December 06</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/12/06.jpg" alt="A large, evergreen tree, trimmed at the bottom" class="weblog-header-image" width="809" height="480" />
  70. <h2 id="general">General news</h2>
  71. <p>
  72. <a href="https://wowana.me./">Wowaname</a> got back to me, and confirmed that replacing the <abbr title="Transport Layer Security">TLS</abbr> certificates that I can access on the server will update what certificates the server uses for encryption next time that the server is restarted.
  73. Or rather, the update will occur next time that the server is instructed to rehash the configuration.
  74. I don&apos;t have the option to initiate that, so until wowaname happens to make a configuration change or the server is restart, the certificate won&apos;t be replaced.
  75. That&apos;s all the more reason that I need to get the certificate replaced as soon as time allows, as I don&apos;t want to miss the rehashing.
  76. I don&apos;t have time to mess with that today though.
  77. I could ask wowaname to rehash the configuration, but I&apos;d rather not be begging them to do more things for me than they already do by hosting my website.
  78. </p>
  79. <p>
  80. I took a walk to the street that supposedly has the tree with a sidewalk leading straight through its trunk.
  81. There is no evidence that such a tree existed there in the recent past.
  82. There&apos;s no tree, no stump, no anything.
  83. There is a large tree that looks similar to the one in the shift leader&apos;s photograph though.
  84. It has droopy branches that would have made it possible for a tunnel through the branches to be cut, as the branches could still be connected to the tree from above.
  85. Likewise, it looks like in the recent path, it might have had branches reaching all the way down to the sidewalk, though these have now been trimmed away, along with most of the branches touching the ground on the property as well.
  86. Long story short, not only was the trip disappointing in that there was no sidewalk through a tree trunk, but also in that I can&apos;t tell for sure if I found the tree that my shift leader saw, nor did I even get to see a tunnel through branches, which while nowhere near ad cook as a tunnel through a the trunk, would still be kind of cool.
  87. </p>
  88. <p>
  89. I love living in a city full of trees though.
  90. This tree wasn&apos;t as cool as described, but it was still a pretty tall tree, and there were countless trees that I passed on the way to it.
  91. It&apos;s easy to take them all for granted, but it truly is awesome living on this half of the state.
  92. Western Oregon sees a lot of rain, but it really greens up the place.
  93. Plant life here is everywhere, and you can&apos;t take even a short walk without seeing a few dozen trees.
  94. </p>
  95. <p>
  96. The head manager emailed me today asking if I could cover an opening shift tomorrow.
  97. Apparently, one of the shift leaders (not the one with the tree photograph, but another that usually makes the dough in the mornings) has hurt their arm and can&apos;t come in tomorrow.
  98. Even if they could come in, cutting the dough requires a bit of arm strength.
  99. With an injured arm, dough-cutting would be painful.
  100. (I assume that their good arm is the one injured, but I could be wrong.) I don&apos;t have the details on how they hurt their arm or how badly, but the head manager asked me to take their place.
  101. There must be a second shift leader on duty that morning, as while I&apos;m authorized to make dough, I&apos;m not authorized to manage the store.
  102. Hopefully the shift leader is feeling better soon.
  103. </p>
  104. <p>
  105. I&apos;m considering writing a fantasy story.
  106. I considered setting it in the <a href="http://floraverse.com./">Floraverse</a> or <a href="https://peppercarrot.com/en/static3/webcomics">Pepper&amp;Carrot</a> universe, but those universes don&apos;t really meet my needs.
  107. Specifically, I&apos;m kind of adamant about having eight basic types of magic, represented by the eight basic colors (black, blue, green, cyan, red, magenta, yellow, and white).
  108. I&apos;m not even picky about what each type of magic does, but neither universe has this.
  109. The Floraverse universe has five main magic types, fifteen secondary magic types, and an unlimited number of very specialized magic types.
  110. I&apos;ve never seen anyone make use of the super-specialized types, as it&apos;s more useful to use a known set instead of building your own type of magic that only you ever use.
  111. Still, that leaves Floraverse with five, twenty, or an unlimited number of magics to work with, not the eight that I&apos;m looking for.
  112. Pepper&amp;Carrot&apos;s universe on the other hand, offers six types of magic.
  113. I think that I might use the magic of Floraverse and Pepper&amp;Carrot to draw inspiration for my own magic system though.
  114. As of writing this, I&apos;ve only come up with four of the eight magic types, and I&apos;m having trouble coming up with the other four.
  115. At first, I was going to release the story that I write under the <abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr>, as it&apos;s textual.
  116. In general, I prefer to release text-based works, including source code and articles, under this license.
  117. However, I&apos;ve come to the conclusion that this license is too strict to support derivatives.
  118. After all, what if someone wants to create graphic art from it? This would require releasing the art&apos;s source code, and it&apos;s tricky to even know what the &quot;source code&quot; of a graphic image is.
  119. In some cases, it&apos;s quite obviously the <abbr title="GNU Image Manipulation Program">GIMP</abbr> project file.
  120. However, without proper use of layers, source elements are effectively lost, which seems illegal according to the license.
  121. In other cases, a simpler image editor is used, no project file exists, and the source is destroyed as it&apos;s used.
  122. Again, bordering on illegal.
  123. Again, this seems to border on illegal.
  124. With this in mind, I decided to release the story instead under the <abbr title="Creative Commons Attribution-ShareAlike 4.0 International">CC BY-SA 4.0</abbr> license, to sidestep the legal complications.
  125. Additionally, as <a href="https://creativecommons.org./share-your-work/licensing-considerations/compatible-licenses/"><abbr title="Creative Commons Attribution-ShareAlike 4.0 International">CC BY-SA 4.0</abbr> is one-way compatible with the <abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three">GPLv3</abbr></a>, I don&apos;t have to jump through any hoops such as releasing parts of my page under <abbr title="Creative Commons Attribution-ShareAlike">CC BY-SA</abbr> and other parts of the same page under the <abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License">GPL</abbr> when I release the story on my <abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr>-licensed website.
  126. </p>
  127. <p>
  128. That all said, I&apos;ve come to the conclusion that while I want to write this story, I can&apos;t do it just yet.
  129. I still have about twelve opinionative essays to write, which are more important than goofy fantasy stories.
  130. I need to complete at least some of those before I begin my creative writing project.
  131. </p>
  132. <p>
  133. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  134. </p>
  135. <h2 id="dreams">Dream journal</h2>
  136. <p>
  137. I had a really strange dream.
  138. I was working in a high-security building and had accidentally tripped the security system, locking myself out of the most secure parts.
  139. Later, I was sent to retrieve some wire from a secure part of the building, but my superiors refused to reset the security system.
  140. Instead, they gave me a small, cylindrical, silver robot on wheels, about as small as could be gripped by both hands, and told to go through the space under the floor.
  141. I was instructed to have the robot drag me, as there was barely any space for me to lay down; I wouldn&apos;t have been able to move if not being dragged.
  142. I remember thinking that this was a huge hole in the security system that could have been exploited by people that, unlike me, weren&apos;t supposed to be there.
  143. Additionally, I thought that it was extremely lazy of the higher-ups to not simply reset the alarm so I wouldn&apos;t have to be dragged under the floor.
  144. The space under the floor was full of obstacles to avoid, such as support pillars and wasp traps, and once I got through to where the wire was, I saw a much nicer path that my superiors could have sent me through that didn&apos;t involve going under the floor and didn&apos;t even require resetting the security system.
  145. I retrieved the wire, though I later found out that I was supposed to allow the robot to drag me until the first day of the new calendar year, which would have put me in a different room with different wire.
  146. I had grabbed the wrong stuff.
  147. </p>
  148. <p>
  149. At this point, premise of the dream changed.
  150. I was getting ready to go on vacation with my family.
  151. Strangely, both of my parents were involved, despite the fact that they&apos;re divorced in the real world and my mother hates my father.
  152. I didn&apos;t have time to pack though, as I had been under the floor being dragged by the small robot, and had to pack in a hurry.
  153. I didn&apos;t actually get to the packing though, as my father wanted to keep jabbering on about the vacation and some missing unflavored tortilla chips until it was time for us to leave.
  154. </p>
  155. <p>
  156. I also dreamed that the canonical spelling of the name of the Arby&apos;s restaurant was &quot;Arbys&apos;&quot;, not &quot;Arby&apos;s&quot;.
  157. With the apostrophe in the wrong place like that, I remembered wondering if there was more than one Arby and they all owned the restaurant.
  158. I even saw a photograph of the sign in my dream, verifying the location of the apostrophe.
  159. Upon awaking, I did a Web search verifying that this was not true; Arby&apos;s does have their apostrophe in the correct place.
  160. It&apos;s worth noting though that some restaurants are idiotic when it comes to their names.
  161. For example, Little Caesars Pizza doesn&apos;t have an apostrophe at all.
  162. They use the plural, non-possessive form of the word &quot;Caesar&quot;.
  163. Do they mean then that it&apos;s the Little Caesars (plural) that run the store, and not that Little Caesar (singular) owns it?
  164. </p>
  165. <h2 id="university">University life</h2>
  166. <p>
  167. I finally took the ungraded quiz for the week, which I usually take as soon as I complete the reading material.
  168. However, this week, I was extremely tired that day, and ended up putting it off.
  169. I had planned to get a lot more schoolwork done today as well, but I just wasn&apos;t feeling up to it.
  170. </p>
  171. <hr/>
  172. <p>
  173. Copyright © 2016 Alex Yst;
  174. 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>.
  175. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  176. My address is in the source comments near the top of this document.
  177. This license also applies to embedded content such as images.
  178. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  179. </p>
  180. <p>
  181. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  182. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F12-December%2F06.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%2F12-December%2F06.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  183. </p>
  184. </body>
  185. </html>