09.xhtml 9.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143
  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/09.xhtml" />
  27. <title>Mushroom-hunting &lt;https://y.st./en/weblog/2016/10-October/09.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/09.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/08.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/10-October/10.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>Mushroom-hunting</h1>
  67. <p>Day 00582: Sunday, 2016 October 09</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/09.jpg" alt="Yst&apos;s mother harvesting chanterelles in the forest" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>8 days until my old domain registrar can no longer counter my charge dispute</li>
  75. </ul>
  76. <p>
  77. I reworked my two <span title="Globalization">POLS 1503</span> essays, expanding them to provide more details, then merged the two into a two-part essay, adding an introduction and conclusion to tie the two together.
  78. I&apos;m only able to actually submit one essay, so merging the two allows me to submit both, but also, the two topics tie together very nicely.
  79. In both cases, a country is going about trying to preserve culture in the wrong way.
  80. In Canada&apos;s case, they claimed to be trying to preserve culture, but they were disrupting the international magazine culture that their citizens enjoyed to try to impose a domestic magazine culture that if their citizens had wanted, wouldn&apos;t have needed to have been imposed.
  81. In Japan and Norway&apos;s case, these countries are trying to preserve their old culture by getting exceptions to a global ban.
  82. These exceptions would apply to only these two countries, creating a double standard, as citizens outside those countries would still be affected by the ban.
  83. If this essay were graded by the professor, I think that I&apos;d score well for addressing both issues completely, though because this essay will be peer-graded using a rigid grading rubric that I won&apos;t be able to see until it&apos;s too late, I&apos;m not sure how the unexpected double-essay will will fare against a strict rubric that isn&apos;t designed for that.
  84. Once that essay was tuned up, I finished my writing to go along with my notes on nuclear energy.
  85. I was going to write up my replies to other students&apos; discussion posts, but not enough students have posted yet.
  86. I much prefer to write my replies in a given course in one sitting.
  87. That way, I can adapt my posts so that I&apos;m not saying the same thing several times and I can take into account all of what I&apos;m replying to, instead of contradicting myself between posts.
  88. </p>
  89. <p>
  90. Lately, I&apos;ve been trying to be more effective with my use of time.
  91. I&apos;ve attempted to rid myself of certain distractions, and I&apos;ve tried to get my homework done as early in the week as is feasible.
  92. I&apos;ve even kept my <abbr title="Internet Relay Chat">IRC</abbr> client disconnected while I have any homework that needs to be done.
  93. It&apos;s really paying off.
  94. Today, I&apos;ve saved enough time to finish the last of my missing journal entries.
  95. Starting now, I can actually move forward on projects such as <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d">include.d</a> and my efforts to clean up this website.
  96. </p>
  97. <p>
  98. I&apos;ve now added per-file copyright years to this website&apos;s source code that are used in the website&apos;s main template in the copyright messages.
  99. What this means is that each year, on the first of January, the entire website won&apos;t need to be rebuilt just because the a new copyright year was added.
  100. Instead, each page has it&apos;s own relevant copyright year or years.
  101. Mostly, this will help with my journal, which in a few years, will have over a thousand pages.
  102. As the number of pages builds up, it would have been an even bigger upload each and every January first.
  103. As I make other improvements to the template though, there will be times in which the entire website will be rebuilt, it&apos;s just no longer the guaranteed and ever-worsening time bomb that it once was.
  104. For journal pages, the copyright year flag is optional, and if unspecified, will default to the year of the day that the journal entry represents.
  105. On all other pages, the copyright year flag is mandatory.
  106. Speaking of ever-worsening time bombs, there are a couple of others that I need to fix as well.
  107. A secondary yearly time bomb is present in the yearly weblog index pages.
  108. They have a &quot;current year&quot; link that gets automatically updated on every year index each time that a new year is added.
  109. Likewise, there&apos;s a similar link to the current month in the weblog month index pages.
  110. I&apos;ve got some code that fixes that little issue for the latest daily entry links, so I just need to apply the same concept in these two other places by setting up dedicated <abbr title="Uniform Resource Identifier">URI</abbr>s that always represent the current month and current year, whatever month and year that they might be at a given time.
  111. I&apos;ll probably work on that tomorrow.
  112. </p>
  113. <p>
  114. I went out to the woods to hunt mushrooms with my mother.
  115. Specifically, we were cutting <a href="https://en.wikipedia.org./wiki/Chanterelle">chanterelles</a>.
  116. We got a couple medium-sized bowls of them by the time that we left.
  117. At first, I wasn&apos;t finding any, but I did manage to find one small patch of them.
  118. Hopefully they&apos;ll get eaten before they go bad.
  119. I don&apos;t particularly like mushrooms myself, but Vanessa and our mother eat them.
  120. Mushrooms don&apos;t last long though, so if not eaten quickly, they can&apos;t be salvaged.
  121. </p>
  122. <hr/>
  123. <p>
  124. Copyright © 2016 Alex Yst;
  125. 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>.
  126. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  127. My address is in the source comments near the top of this document.
  128. This license also applies to embedded content such as images.
  129. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  130. </p>
  131. <p>
  132. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  133. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F09.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%2F09.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  134. </p>
  135. </body>
  136. </html>