28.xhtml 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177
  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/01-January/28.xhtml" />
  27. <title>The day was going well, but PayPal had to ruin it. &lt;https://y.st./en/weblog/2017/01-January/28.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/01-January/28.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/01-January/27.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/01-January/29.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>The day was going well, but PayPal had to ruin it.</h1>
  67. <p>Day 00693: Saturday, 2017 January 28</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2017/01/28.jpg" alt="A last-minute photograph: the empty lobby at work at night" class="weblog-header-image" width="800" height="480" />
  70. <section id="general">
  71. <h2>General news</h2>
  72. <p>
  73. I grabbed a pen and walked home, though this time, I didn&apos;t bring anything with me that I&apos;d be leaving.
  74. I&apos;m way too tired for now.
  75. It didn&apos;t help that I had a closing shift last night and that the post office would only be open for a couple hours before noon, so I didn&apos;t get a full night&apos;s sleep.
  76. Once home, I grabbed my paperwork in case I&apos;d need it and headed to the post office.
  77. I left my mother&apos;s place an hour before the post office opened, so I thought that I&apos;d get there about fifteen minutes before they opened, but the post office must be about half an hour from home.
  78. It took me a full hour to reach the post office, and I got there a minute after they opened.
  79. A full like had already formed in that time; others were probably waiting outside because of the short business day.
  80. They didn&apos;t have time to come after the doors had been open a while.
  81. Thankfully, the post office did have my key; three copies of it, actually.
  82. All three showed signs of corrosion on at least one side.
  83. I&apos;m not sure what that is about.
  84. I took the keys home and checked the mail box, both to make sure that the keys actually fit and to update my name in the box.
  85. Both of my known-at-the-time surnames were already in the box though.
  86. Juddy had followed through.
  87. I couldn&apos;t know at what point my names would be added to the box though, so without the key, I couldn&apos;t have ordered Marc&apos;s records yet anyway.
  88. </p>
  89. <p>
  90. I tried photographing the tops of the keys at home for my journal entry, but I messed up again.
  91. When I got the photographs back to my mother&apos;s place, I found that all of the clear photographs had been taken in the wrong orientation!
  92. I really wish that I could find a way to lock my mobile&apos;s camera in landscape mode.
  93. I <strong>*never*</strong> use portrait mode, and any time any of my photographs are in portrait mode, it&apos;s because I was photographing something from above and I slightly tilted the mobile in a way that was incorrectly interpreted as an indication that I wanted to switch to portrait mode.
  94. It always ruins my photographs at the worst of times and it&apos;s really getting old.
  95. </p>
  96. <p>
  97. I updated my address in Discover&apos;s records, then updated my credit card information on file with Bandcamp.
  98. Updating it with Bandcamp was for nothing though.
  99. I had forgotten that Bandcamp will only process payments for physical items through PayPal!
  100. Oh, scrap.
  101. Paypal.
  102. Discover said that they&apos;d block payments to PayPal Pro.
  103. Would this payment be through PayPal Pro?
  104. PayPal declined my card, but when I logged into the Discover website, I found that Discover was allowing the charged and that Paypal was just taking them back.
  105. Joy, PayPal is being a pain as always, but at least there&apos;s not a problem on Discover&apos;s end.
  106. Trying again, I found myself banned from the PayPal website.
  107. I had no doubt shifted to a new exit node, one that PayPal is particularly unfond of.
  108. </p>
  109. <p>
  110. PayPal also keeps claiming that I might have an account that is attached to the email address that I entered, and that I must log in.
  111. I never had an account with that email address though.
  112. PayPal supposedly closed the account that is associated with a different email address, but just to be sure, I tried logging in.
  113. GAH!
  114. The account is back!
  115. Also, PayPal now attached my payment email address to an existing account, probably using my credit card number, which makes me wonder how that even worked.
  116. I&apos;ve never used any credit card with my account!
  117. I don&apos;t have <strong>*time*</strong> for this garbage!
  118. </p>
  119. <p>
  120. Except that now I do have time.
  121. I explained the situation to <a href="https://marcwithac.bandcamp.com/">Marc</a> and asked for an extension on the deadline, which they agreed to grant if the purchase came through at some point.
  122. PayPal hides their contact information though, so I had to take to Twitter again to publicly yell at them instead of handling this privately via email as I&apos;d have preferred to do.
  123. </p>
  124. <p>
  125. I installed a few new camera applications to see if I could find one that would allow me to lock the orientation.
  126. The one that I found to have this seemingly-basic feature that all camer applications should realistically have was Open Camera.
  127. Thankfully, it also offers the low-resolution option that I enjoy in the default camera, so this should work out well.
  128. Furthermore, this camera application can add the time and date to photographs automatically.
  129. It doesn&apos;t have the option to use dashes in the date instead of slashes, but at least it can be set to put the date elements in the correct order and can be set to use the twenty-four hour time format.
  130. It also add custom text of the user&apos;s choice to every photograph, so there&apos;s no longer a need for me to edit the photographs to add my <abbr title="Uniform Resource Identifier">URI</abbr> before uploading them.
  131. Lastly, with four new camera applications installed, the camera option showed up on my lock screen finally!
  132. It only allosed choosing one of three camera applications though, none of which were the default camera.
  133. Perhaps the reason that I couldn&apos;t access the camera from the lock screen, despite having configured the device to allow it, is that the default camera application on this device is somehow not considered to be a camera application.
  134. This is strange, as the version of the operating system that runs on the GT-i9300 instead of the GT-i9100 <strong>*does*</strong> allow the default camera application to be accessed from the lock screen.
  135. </p>
  136. <p>
  137. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  138. </p>
  139. </section>
  140. <section id="university">
  141. <h2>University life</h2>
  142. <p>
  143. I finished reading the <span title="Ethics and Social Responsibility">PHIL 1404</span> reading assignment, though I didn&apos;t have time to act on it today.
  144. Too many other things were going on.
  145. I must say though that I found the Aristotle piece from the reading list to be appalling.
  146. The style of writing made it difficult to read, being that it was from a different time period and we write differently these days, but it was very clear that Aristotle was advocating the subjugation of women and claiming that it was right and just to own slaves.
  147. The piece also was claiming that souls were proof of the relationship between master and slave being just, but I firmly disagree.
  148. For one thing, we have no proof that souls even exist; they&apos;re not proof of anything as we don&apos;t even have proof of them.
  149. That is to say, I can&apos;t claim that Bigfoot proof of something, as we don&apos;t have any evidence that Bigfoot is even real.
  150. For the sake of continuing this though, let&apos;s just substitute souls for brains.
  151. There&apos;s a difference between a brainless body being controlled by a brain and a slave with a mind of their own being controlled by a master.
  152. There&apos;s more in there that I&apos;d love to comment on, but I&apos;m simply out of time for today.
  153. I have to head in to work.
  154. </p>
  155. </section>
  156. <hr/>
  157. <p>
  158. Copyright © 2017 Alex Yst;
  159. 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>.
  160. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  161. My address is in the source comments near the top of this document.
  162. This license also applies to embedded content such as images.
  163. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  164. </p>
  165. <p>
  166. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  167. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F01-January%2F28.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%2F01-January%2F28.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  168. </p>
  169. </body>
  170. </html>