27.xhtml 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246
  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/03-March/27.xhtml" />
  27. <title>My credit card&apos;s now functional! &lt;https://y.st./en/weblog/2017/03-March/27.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/03-March/27.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/03-March/26.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/03-March/28.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 credit card&apos;s now functional!</h1>
  67. <p>Day 00751: Monday, 2017 March 27</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2017/27.jpg" alt="Xscreensaver, displaying on the Fred Meyer gift registry terminal" class="weblog-header-image" width="800" height="480" />
  70. <section id="to-do">
  71. <h2>To-do list</h2>
  72. <ul>
  73. <li>
  74. Acquire stuff for my new home:
  75. <ul>
  76. <li>
  77. A bed
  78. </li>
  79. <li>
  80. <del>A bicycle</del>
  81. </li>
  82. <li>
  83. <del>A bicycle helmet</del>
  84. </li>
  85. <li>
  86. A broom
  87. </li>
  88. <li>
  89. A dustpan
  90. </li>
  91. <li>
  92. A carpet broom
  93. </li>
  94. </ul>
  95. </li>
  96. <li>
  97. Inform people that I&apos;ve moved
  98. <ul>
  99. <li>
  100. <del>The post office (change of address forms)</del>
  101. </li>
  102. <li>
  103. Relevant online accounts
  104. </li>
  105. <li>
  106. My boss
  107. </li>
  108. </ul>
  109. </li>
  110. <li>
  111. Finish stabilizing <a href="https://git.volatile.ch./y.st./include.d/releases">include.d</a> and put out another release (low priority)
  112. </li>
  113. </ul>
  114. </section>
  115. <section id="general">
  116. <h2>General news</h2>
  117. <p>
  118. The lanyard merchant sent me a <abbr title="Portable Document Format">PDF</abbr> containing an image of the lanyars they planned to produce on my behalf, asking for approval before production.
  119. However, the image shows the lanyards will be totally blank!
  120. I ordered lanyards with text on them.
  121. If I wanted blank lanyards, I certainly wouldn&apos;t need them to be custom made.
  122. It&apos;s a good thing they asked before starting.
  123. Otherwise, I&apos;d demand my money back, and if they refused, file a charge dispute with the bank.
  124. </p>
  125. <p>
  126. I was going to begin my day by filling out a little paperwork, but I needed tape for my jury summons.
  127. They want me to fill it out, fold it, and tape the top, sending it without an envelope.
  128. I haven&apos;t had a use for tape at home though, so I never bought any.
  129. So, I headed to Fred Meyer to buy tape and take care of my Chase errand first.
  130. </p>
  131. <p>
  132. At Chase, the representative had no idea why Web support would ask me to come in-branch for help.
  133. They telephoned some line, provided their name and authorization code, then asked someone on the other end about the issue.
  134. The person on the other end didn&apos;t know what was going on, so the representative put me on the telephone.
  135. I explained the situation once more, and the telephone representative still couldn&apos;t see such a transaction.
  136. They then came to the realization that it was the fraud department that I needed to reach, so they transfered me there.
  137. After a long pause of <del>elevator</del> <ins>hold</ins> music, tasting through three songs, the fraud department came on the line.
  138. They asked me questions I didn&apos;t have answers to, such as how much I pay in loan payments every month.
  139. I have a couple outstanding loans from when I attended my old school, but I don&apos;t remember how much I pay every month.
  140. Every month since they canceled autopay on me, they send me an email telling me my payment is due tomorrow.
  141. Either that day or the next, I log in and make the payment for the default amount, the full amount due that month with no extra.
  142. I don&apos;t like my loan provider, and I don&apos;t spend time lingering there or looking at the numbers.
  143. I could tell you about how much I still owe, but not how much I pay each month.
  144. The fraud department representative was able to substitute the questions I couldn&apos;t answer with other questions, so it all worked out.
  145. Honestly, as you may have guessed, I suspected Chase was maliciously discriminating against <abbr title="The Onion Router">Tor</abbr> users with their &quot;security&quot; system.
  146. You may have guessed I thought that, but I didn&apos;t want to accuse them until I knew for sure.
  147. Thankfully, I was dead wrong.
  148. Instead, they don&apos;t allow foreign transactions by default.
  149. They located my attempted transaction, explained the issue, then removed the restriction on my account.
  150. Does that mean I can make any foreign transaction I like now, or only transactions with the <code>//st.</code> registry?
  151. One day, I might find out, but for now, <code>//y.st.</code> has its domain fees paid through <span title="Day 03652: Thursday, 2025 March 06">2025-03-06</span>.
  152. </p>
  153. <p>
  154. While at Fred Meyer, I passed by their gift registry terminal.
  155. Much to my surprise and delight, is was displaying Xscreensaver.
  156. The terminal&apos;s running some flavor of Linux!
  157. Their bottle machines still rune Windows unfortunately, and I think their cash register computers do as well, but at least they&apos;ve got a Linux machine running in their store.
  158. It might be a sign that they&apos;re moving forward and away from Microsoft&apos;s noxious grasp.
  159. I mean, the bottle return machines are running Windows XP or Vista, I forget which.
  160. Those machines don&apos;t show what Fred Meyer is using on their newer machines, they just show that Fred Meyer isn&apos;t going through and systematically replacing Windows, or even upgrading their operating systems.
  161. They&apos;re artifacts of Fred Meyer&apos;s past.
  162. Perhaps newer machines bought by Fred Meyer are Linux-based.
  163. </p>
  164. <p>
  165. The other day, I received this website&apos;s first pull request.
  166. An update to this site&apos;s <abbr title="Extensible Markup Language">XML</abbr> had left an old journal entry broken due to a careless error on my part.
  167. In my defense, that update likely updated a few hundred pages, so it&apos;s not too surprising that I made a mistake on one of them.
  168. In any case, the pull request fixed the issue, but I wasn&apos;t able to process the pull request as easily as I should&apos;ve been.
  169. The journal entry was old, back from the time I put entire paragraphs on one line of code.
  170. The Gogs Web interface couldn&apos;t show me the difference the pull request would make, and I had to find a way to compare the two versions of the document by hand.
  171. After all, blindly trusting strangers without auditing their changes to my site would be a bad idea.
  172. Now though, I&apos;ve gone back and reformatted every old journal entry that needed reformatting.
  173. Every entry has only one sentence per line, which Gogs should be more than capable of dealing with.
  174. Checking future pull requests before accepting them should be quick and painless now.
  175. </p>
  176. <p>
  177. I filled out the jury summons form, which says I&apos;m ineligible for jury duty if I live outside Coos County, along with the change-of-address forms I&apos;ve been neglecting to complete.
  178. I was going to walk them over to the post office and enjoy the nice weather, but it started to rain before I left the complex.
  179. The elderly person that lives with the on-site property manager, who I just today learned is the parent of the manager, slowed down my departure a bit and had wanted to talk.
  180. Had they not, the rain would&apos;ve started on the way and I&apos;d&apos;ve likely gotten my forms wet!
  181. I ended up just depositing them in the on-property mailbox.
  182. Had the forms been less important, I&apos;d likely have just taken them another day when the weather was drier.
  183. </p>
  184. <p>
  185. My mother visited me at work today, annoyed that I didn&apos;t answer their email.
  186. Strangely though, I <strong>*did*</strong> answer it before I left for work.
  187. Once I got home, I found no second email from them, so they must have somehow missed my reply.
  188. At the time though, I figured they&apos;d sent another email after I left for work.
  189. Of course I wouldn&apos;t&apos;ve answered that, I was on the clock!
  190. My mother got weird about my hair clips, which they hadn&apos;t seen before.
  191. The fact is, I wear them only at work, where I&apos;m not allowed to wear non-company hats and where they&apos;ve failed to provide me a company hat, despite having promised to do so.
  192. With no hat, I need the clips to keep my hair out of my face.
  193. My mother&apos;s pretty stuck on traditional gender roles though, and as a male, they consider me to be masculine.
  194. Because of my mother&apos;s email before work, I anticipated that they might visit me on the clock, so I brought a gift I&apos;d been meaning to give them for a while.
  195. They had several bags of food for me supposedly, stuff they didn&apos;t want to eat themself and figured I&apos;d want.
  196. It wasn&apos;t even just vegan-specific stuff I&apos;d left behind, which if I recall, was only one pseudo-ice-cream bar.
  197. Instead, it was various other things that they just don&apos;t want, such as saltines, which I have been known to eat.
  198. However, they refused to give it to me at work, despite having it in their car.
  199. Instead, they insist on driving it to my place.
  200. It sounds like they&apos;re coming over tomorrow morning.
  201. </p>
  202. <p>
  203. My mother wanted me to come on a trip to Portland with them, and was looking into my schedule to find when I could come.
  204. They were considering making it an overnight trip, and the premise was supposedly that they needed to visit Alyssa in Gresham to do laundry at their place.
  205. I offered to do their laundry for them though, which took away the whole alleged point of the trip.
  206. They agreed that would be much faster.
  207. However, they later mentioned wanting to visit their mother in Portland, so I don&apos;t know if the trip has actually been canceled, and I&apos;ve already agreed to go.
  208. </p>
  209. <p>
  210. My mother also got caught using my complex&apos;s dumpster, and admitted to knowing me personally.
  211. I&apos;m not sure if I&apos;ll get in trouble for telling them they can use my complex&apos;s trash services or not.
  212. </p>
  213. <p>
  214. After my mother left, one of my coworkers quit on us.
  215. They&apos;ve been complaining of a rash for a while now, a rash thought to be induced by something in our workplace.
  216. They can&apos;t take it any more, and can&apos;t stand it long enough even to give two weeks notice.
  217. I&apos;m now covering one of their shifts, so I only have one day off this week.
  218. An overnight trip is a very bad idea at this point.
  219. I let my mother know of my singular day off once I got home.
  220. </p>
  221. <p>
  222. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  223. </p>
  224. </section>
  225. <hr/>
  226. <p>
  227. Copyright © 2017 Alex Yst;
  228. 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>.
  229. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  230. My address is in the source comments near the top of this document.
  231. This license also applies to embedded content such as images.
  232. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  233. </p>
  234. <p>
  235. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  236. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F03-March%2F27.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%2F03-March%2F27.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  237. </p>
  238. </body>
  239. </html>