11.xhtml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218
  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 © 2017 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/2017/04-April/11.xhtml" />
  27. <title>Further recovery? &lt;https://y.st./en/weblog/2017/04-April/11.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/2017/04-April/11.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/2017/04-April/10.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/04-April/12.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>Further recovery?</h1>
  67. <p>Day 00766: Tuesday, 2017 April 11</p>
  68. </header>
  69. <section id="general">
  70. <h2>General news</h2>
  71. <p>
  72. I had a flash of inspiration as I sat down with my breakfast to work on my coursework.
  73. How would it turn out if I cooked marinara into my stew?
  74. I&apos;ll have to try that some time, but only with a small batch.
  75. My stew is sadly lacking in tomatoey goodness.
  76. This might be what it needs!
  77. That said, it could also go horribly, horribly wrong, and I&apos;m going to have to eat this mess.
  78. Making a full pot of it without starting with a smaller batch first would be ill-advised.
  79. </p>
  80. <p>
  81. Before heading to work, I went to the bank to pay my credit card bill.
  82. </p>
  83. <p>
  84. I&apos;m tired of my coworkers, especially my shift leaders, trying to talk to me when I&apos;m dealing with a customer.
  85. They specifically wait until I&apos;m talking to someone at the menu board, then try to give me instructions.
  86. Seriously?
  87. The customer can&apos;t see or hear my coworkers.
  88. That means when my coworkers start talking, the customer doesn&apos;t stop.
  89. As the customer has no idea what&apos;s going on and my coworkers do, it&apos;s my coworkers I have to tune out, so I can carefully listen to what the customer wants.
  90. This frustrates me to no end.
  91. After dealing with this for the umpteenth time, my mood went a bit sour.
  92. Next time it happens, I think I&apos;ll deal with the customer as always, then have a short chat with my coworker explaining exactly whey I can&apos;t listen to them when I&apos;m on the line with a customer and exactly whey they won&apos;t be able to get any message through to me until I&apos;ve finished talking to the customer and had them pull up to the window.
  93. Seriously.
  94. It only takes five to ten seconds usually, my coworkers, including my shift leaders, can wait that long.
  95. </p>
  96. <p>
  97. One of our customers came back through the drive-through claiming I&apos;d given them the wrong pizza.
  98. Assuming this is true, it could&apos;ve easily happened for any number of reasons.
  99. I could&apos;ve gotten distracted and grabbed a pizza from the wrong section of the warmer.
  100. The customer couldn&apos;ve specified the wrong type of pizza (it&apos;s happened before).
  101. Or the people working landing could&apos;ve put the pizza in the wrong spot.
  102. In any case, I tried to follow our usual protocol, which is to have them give back the pizza they didn&apos;t want but got anyway, then give them the right pizza.
  103. However ... they hadn&apos;t brought back the pizza.
  104. They supposedly dropped it off, then got a telephone call from whoever they dropped it off with saying the wrong pizza had been brought.
  105. The only thing to do is go get a shift leader.
  106. However ... both of the on-duty shift leaders had disappeared on me.
  107. I couldn&apos;t find either one of them, and I had to make a judgement call.
  108. Without instruction from higher up, I erred to the side of caution and tried to preserve our image: I just gave them the pizza.
  109. However, once they both returned and I told one what happened, they said I&apos;d done the wrong thing.
  110. They think the customer was a scammer.
  111. Now I know for next time though: no pizza brought back, no replacement.
  112. No exceptions.
  113. The shift leader admitted though that this was exactly why both shift leaders aren&apos;t supposed to disappear at the same time.
  114. </p>
  115. <p>
  116. One of my final customers for the night came through the drive-through with a bottle of alcohol in hand.
  117. Seriously?
  118. While driving?
  119. They even raised their bottle to me and said &quot;cheers&quot;.
  120. I guess it&apos;s not my problem, but it seems highly irresponsible.
  121. </p>
  122. <p>
  123. When I got home, I found a letter to me from my father.
  124. They tried to email me, but had problems for some reason.
  125. Likely, they didn&apos;t type my email address correctly.
  126. Many people have problems with <abbr title="Top Level Domain">TLD</abbr>s they don&apos;t recognise, and <code>//st.</code> isn&apos;t that common in my country.
  127. It&apos;s like ... how is a known <abbr title="Top Level Domain">TLD</abbr> any easier to use than an arbitrary one you&apos;ve never heard of?
  128. I don&apos;t get it.
  129. Strings are strings.
  130. In any case, they wanted me to write to them to get my email address to their email client.
  131. </p>
  132. <p>
  133. I decided to try a new email address as my main one, so I set up Authenticator on my mobile so I could perform the two-factor authentication process required by Zoho&apos;s control panel.
  134. As soon as I logged in though, Zoho complained that my <abbr title="Sender Policy Framework">SPF</abbr> and <abbr title="DomainKeys Identified Mail">DKIM</abbr> records in <abbr title="Domain Name System">DNS</abbr> were incorrect.
  135. I had both set up, but it seems Zoho has deleted my <abbr title="DomainKeys Identified Mail">DKIM</abbr> signing key on their end.
  136. Since they now have no key, they don&apos;t have a key that matched the key in the <abbr title="Domain Name System">DNS</abbr> record.
  137. I had to tell Zoho to generate a new key pair; there was no recovering the old signing key.
  138. I logged into my <abbr title="Domain Name System">DNS</abbr> account to update the public key&apos;s <abbr title="Domain Name System">DNS</abbr> record, but the stupid website kept logging me out.
  139. After at least half a dozen tries, I managed to get far enough in the system to actually update the <abbr title="Domain Name System">DNS</abbr> record.
  140. After that, I had to log in at least another half dozen times to get the <abbr title="Sender Policy Framework">SPF</abbr> record added.
  141. I was sure I&apos;d already added it, but unlike the <abbr title="DomainKeys Identified Mail">DKIM</abbr> setup, I had no proof of having already done it.
  142. With the <abbr title="DomainKeys Identified Mail">DKIM</abbr> setup, while Zoho had lost the private key, the old public key was still in <abbr title="Domain Name System">DNS</abbr>.
  143. It turned out I couldn&apos;t use the colon character I&apos;d wanted to use in my email address though.
  144. It&apos;s a perfectly valid character in email addresses, but Zoho doesn&apos;t allow it.
  145. </p>
  146. <p>
  147. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  148. </p>
  149. </section>
  150. <section id="mental">
  151. <h2>Mental health watch</h2>
  152. <p>
  153. Thinking back, I&apos;m almost certain that breach of trust from my childhood I mentioned yesterday was the day I lost my capacity to trust.
  154. I mean, not all types of trust, I lost other facets of my ability to trust from other causes, but my ability to trust people with secrets.
  155. I wonder if I need a counsellor.
  156. I&apos;d very much like to see what a counsellor could help me with, but I lack the money and I lack the time.
  157. If I had a guide to the mind, I could probably be more effective at finding the tears in my psyche.
  158. If I find these tears, can I repair them in some way?
  159. For as long as I can recall, I haven&apos;t had the capacity to truly love.
  160. I mean, I like my family for the most part, but I don&apos;t think I actually feel a bond with them.
  161. If they all went away and I never saw any of them again, I&apos;d be perfectly fine.
  162. I think trust is supposed to be a major component of love.
  163. Is my cold heart a result of my destroyed ability to trust?
  164. Am I ... supposed to be able to love?
  165. Is that inability not just a part of what I naturally am?
  166. What in Squiddy&apos;s name am I supposed to be!?
  167. I&apos;m so confused, but I&apos;ll figure the important things out with time.
  168. </p>
  169. <p>
  170. As I cut up ingredients for breakfast, a delicious mixed vegetable stew, I listened to <a href="https://kubbi.bandcamp.com/album/transmittance">some music that I really should get around to writing a review for</a>.
  171. I&apos;d planned to listen and take note so I could leave a meaningful review of it, but that&apos;s not what happened.
  172. Instead, I got lost in the music and dances while I worked.
  173. That&apos;s not a thing that I do though!
  174. Dancing, I mean.
  175. I kind of wonder if exposing my psychological cracks is enough to at least partially recover.
  176. I felt awesome all day today, at least until later at work.
  177. Is this how normal people feel all the time?
  178. I highly doubt passively locating my issues is enough to fully recover, but until I know better how to act, it does seem to be a good start on getting better.
  179. That said, it&apos;s been too soon to see if this is a long-term change, not to mention there&apos;s too many variables to be sure this is what&apos;s helping.
  180. I&apos;m not exposed to my freaky mother on a daily basis.
  181. When I <strong>*am*</strong> exposed to them, they don&apos;t hold the power over me they once did.
  182. They still hold some influence over me though, I suppose.
  183. I&apos;ve been living alone.
  184. That means I haven&apos;t needed to put up a constant facade, having to act socially acceptable on a twenty-four seven basis.
  185. At home, I can shed the shell I wear in public and just be me.
  186. I&apos;ve been in control.
  187. I don&apos;t have all the luxuries that&apos;d be nice to have, such as a home Internet connection and home server, but now, it&apos;s not because someone else has chosen to do without them, requiring I do so as well.
  188. Now it&apos;s because <strong>*I&apos;ve*</strong> reviewed the options and <strong>*I*</strong> don&apos;t like the <abbr title="Internet service provider">ISP</abbr>s.
  189. I haven&apos;t had the time or desire to put together an actual nutrition plan, but I&apos;ve been eating loads better than I had in my mother&apos;s home.
  190. My home isn&apos;t so packed with junk that I can&apos;t even walk down the hall without turning my body sideways (Squiddy, my mother has a lot of junk).
  191. There&apos;ve been other ... more personal factors as well, things I don&apos;t care to write about here at this time.
  192. In any case, it&apos;s difficult to pinpoint a single source of this change, assuming it&apos;s even permanent, and assuming only a single factor is involved (it&apos;s likely a combination of factors)
  193. I&apos;ll need to monitor my mental state as time progresses.
  194. With any luck, I&apos;ll continue to improve.
  195. </p>
  196. </section>
  197. <hr/>
  198. <p>
  199. Copyright © 2017 Alex Yst;
  200. 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>.
  201. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  202. My address is in the source comments near the top of this document.
  203. This license also applies to embedded content such as images.
  204. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  205. </p>
  206. <p>
  207. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  208. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F04-April%2F11.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%2F2017%2F04-April%2F11.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  209. </p>
  210. </body>
  211. </html>