12.xhtml 20 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252
  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/11-November/12.xhtml" />
  27. <title>PayPal wants unfettered access to my bank account, no doubt for shady reasons. &lt;https://y.st./en/weblog/2016/11-November/12.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/11-November/12.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/11-November/11.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/11-November/13.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>PayPal wants unfettered access to my bank account, no doubt for shady reasons.</h1>
  67. <p>Day 00616: Saturday, 2016 November 12</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/11/12.jpg" alt="€2.25 EUR" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>234 scheme-specific <abbr title="Uniform Resource Identifier">URI</abbr>-parsing classes to write and add to <a href="https://git.vola7ileiax4ueow.onion/y.st./include.d/releases">include.d</a></li>
  75. <li>1 free elective left in my associate degree program</li>
  76. <li>4 free electives left in my bachelor degree program</li>
  77. </ul>
  78. <p>
  79. Last night, my dream was even more layered than before.
  80. I&apos;ve had dreams that contained dreams, but now I had a dream that contained two dreams, each of which contained three dreams.
  81. It seems too that I&apos;m starting to document my dreams in my dreams.
  82. Upon actually waking up though, I forgot five of the six most deeply-nested dreams.
  83. In the sixth though, I was riding my bike and accidentally pulled into the wrong driveway.
  84. A child asked me if a certain someone was home, so I explained that I had stopped at the wrong house and began to leave.
  85. They asked if they could borrow a pen, so I handed them one, but then they tried to stab me with it! I managed to wrestle it out of their hands, but then in self-defense, I had to stab <strong>*them*</strong> with it, which was horrifying.
  86. I rode away, but decided to wake up.
  87. In the dream that I awoke to, I had to go blow my nose.
  88. That was the extent of that layer of the dream.
  89. Once I awoke from that, I ended up in the layer where I was trying to get to my laptop so that I could write about my dream.
  90. On the way to my laptop, I noticed a strange mobile device that I couldn&apos;t make sense of.
  91. The screen had been left on overnight, but it wasn&apos;t plugged into a power source and hadn&apos;t drained its battery from the prolonged screen use.
  92. </p>
  93. <p>
  94. I can&apos;t help but wonder if I&apos;m remembering dreams more often because of my recent attempts to document them.
  95. I woke up way too early, but I haven&apos;t been very productive on the schoolwork front, so I got to work on my <a href="/en/coursework/BUS1101/Leadership_Entrepreneurship_and_Strategy.xhtml">essay</a>.
  96. Yesterday wasn&apos;t my fault.
  97. I legitimately didn&apos;t have time.
  98. On the day before though, I just wasn&apos;t feeling like doing schoolwork, but I should have done it anyway.
  99. </p>
  100. <p>
  101. On the way to work, I found a small stack of coins outside the grocery store.
  102. Based on their color, I assumed that they were some sort of tokens, but upon closer inspection, it was actually a pile of euros! This wouldn&apos;t be too strange if not for the fact that I&apos;m in the United States; we don&apos;t use euros here.
  103. Why had someone left €2.25 <abbr title="euros">EUR</abbr> outside the store? After work, I photographed the coins that I&apos;d found, though the glare of the sun made a couple of the coins a bit difficult to make out.
  104. I learned a new trick for dealing with light sources on reflective objects that don&apos;t reflect images (as a mirror would or smooth surface would reflect images).
  105. By holding my hand on the side of my mobile/camera, using it as a visor, I can block unwanted light! If the surface of the object is too reflective though, an image of my hand would show up in the photograph.
  106. However, it turns out that my mobile&apos;s camera fell from landscape mode to portrait mode and I didn&apos;t notice.
  107. Once I arrived back home, to my huge disappointment, all of my good photographs were flipped the wrong way.
  108. I tried to take new photographs, but the sun had gone down too much.
  109. There wasn&apos;t enough light.
  110. Likewise, without light, I couldn&apos;t take a photograph of something else and photograph the euros tomorrow.
  111. I can&apos;t edit them either due to the way that <abbr title="Joint Photographic Experts Group">JPEG</abbr> compression works.
  112. When <abbr title="Joint Photographic Experts Group">JPEG</abbr> images are edited and saved, new data is lost each time.
  113. Editing one of the good photographs would deteriorate it.
  114. Instead, I had to include one of the photographs with glare in today&apos;s journal entry.
  115. I have learned my lesson.
  116. Always be sure that my mobile&apos;s camera is reading in the correct orientation before photographing something when the subject matter is directly below the camera.
  117. </p>
  118. <p>
  119. My first task at work today was to stuff the crusts of some stuffed crust deep dish pizzas, something that I&apos;ve not done before.
  120. Before I quit my job there about a year ago, I used to often joke that one day we&apos;d have a stuffed crust deep ddish pizza, but I never thought that that would actually happen.Working with the deep dish dough is kind of gross, and not just because of the handling of meat and cheese.
  121. The dough for that pizza is covered in oil, so pretty quickly after starting my task, my hands felt ...
  122. unpleasant.
  123. </p>
  124. <p>
  125. I discovered a quicker way to use the credit card machine.
  126. When I last worked here, we didn&apos;t use the chips in credit cards.
  127. We simply swiped the card, be it a chip card or a non-chip card.
  128. However, these days, our chip reader (which was present even back then) is now in use.
  129. However, it takes several seconds to do anything, which leaves me feeling awkward, as the customer is pretty much just sitting there waiting for the transaction to take place.
  130. However, it seems that the several second wait can be avoided.
  131. Instead of swiping the card (required even for the chip-based cards), entering the transaction amount, then inserting the card into the chip reader when told to, I can swipe the card, insert it into the reader, then enter the transaction amount.
  132. The several-second wait doesn&apos;t need to occur <strong>*after*</strong> the transaction amount has been decided, so it can occur at the same time as I&apos;m using the <abbr title="personal identification number">PIN</abbr> pad to specify the price.
  133. By the time that I&apos;ve finished entering the price, the waiting period is usually over.
  134. </p>
  135. <p>
  136. The crown of voices was driving me nuts today.
  137. Many of the voices are difficult to make out, and when the drive-through is busy, the crown beeps in my ear repeatedly while I&apos;m trying to deal with the current customer.
  138. I&apos;m starting to get the hang of the thing though, so by putting the next customer on hold, I can actually make the beeping go away, but I hadn&apos;t started doing that until later in my shift.
  139. Even if I do make the beeping go away, the crown&apos;s speaker stays on as long as a customer is at the menu board, again making it difficult to hear the customer that&apos;s actually at the window.
  140. Furthermore, the crown blocks use of one of my ears.
  141. Almost no sound seems to get through, and I often can&apos;t make out what my coworkers say even if they&apos;re right next to me.
  142. I can&apos;t tell the management how annoying the crown is though.
  143. With the way that we have the tip system set up, we only receive tips if we work a till.
  144. If I don&apos;t work the drive-through (or the front counter, but I hardly ever end up being assigned to work the front counter), I make less money.
  145. I will deal with it and I&apos;ll try to get used to it.
  146. </p>
  147. <p>
  148. Many customers are fine, don&apos;t get me wrong, but a few are just idiots.
  149. One customer today was splicing the names of different menu items together, confusing me as to what they were after.
  150. It reminded me a lot of customers that I&apos;ve dealt with in the past.
  151. In the past, every few days, I&apos;d receive an order for &quot;cheesy breadsticks&quot;; we have no such menu item, and to the best of my knowledge, we never did.
  152. What many of them are after is actually our cheese bread.
  153. Yes, our cheese breads are cut into strips, but that doesn&apos;t make them breadsticks.
  154. If I pulled out a loaf of bread and cut the slices into strips, would that be breadsticks? No! Most certainly not! The word &quot;breadsticks&quot; does not refer to strips of bread, but bread that has been baked into a long, thin shape.
  155. We also sell breadsticks, which do have a light dusting of Parmesan cheese power, but when I ask customers if that&apos;s what they want, they almost always tell me that it&apos;s not.
  156. That &quot;almost&quot; makes it worse, too.
  157. It&apos;s not consistent, as they&apos;re using invalid menu item names, so I can&apos;t for sure know what they mean by &quot;cheesy breadsticks&quot; at any given time.
  158. Less bad was when customers would order a diet to drink.
  159. A diet? Really? I can&apos;t sell you a diet, that doesn&apos;t make sense.
  160. What they really wanted was a <strong>*diet cola*</strong>.
  161. It&apos;s amazing how many people would just call it a &quot;diet&quot; though.
  162. Sadly, we only carried one diet drink.
  163. I&apos;d love to have been able to ask &quot;A diet what?&quot;, but instead, I&apos;d always ask &quot;Do you mean a diet cola?&quot;.
  164. </p>
  165. <p>
  166. I decided that I can&apos;t avoid the house with the scary person from yesterday in it, at least not by daylight.
  167. I need to keep an eye on my surroundings.
  168. Part of that means keeping an eye on suspicious places near my home.
  169. If I notice anything that seems out of the ordinary, I need to let the police know.
  170. Furthermore, I can&apos;t let that person think that they can intimidate people and keep them from using public sidewalks.
  171. Still, I need to avoid the place at night.
  172. Not only am I unable to see much at night, so there&apos;s nothing that I can witness and report, it&apos;s easier to sneak up on me at night.
  173. As long as the sun is out, it&apos;s much easier for me to see people that approach and it&apos;s easier for other people to see if I&apos;m under attack.
  174. With both of those in mind, people are less likely to attack in the day, especially on a public street (as opposed to an alleyway or the inside of an uncrowded building).
  175. </p>
  176. <p>
  177. This part-time job is cutting into my coursework time more than expected.
  178. This is the third day, and I&apos;ve still gotten next to nothing done.
  179. Thank goodness I&apos;m only in one course right now.
  180. After moving, I need to try to find a job in which I can work only two or three days each week tops.
  181. The inconsistent schedule at this job doesn&apos;t help either.
  182. It didn&apos;t used to bother me too much, but now, it&apos;s really causing problems.
  183. For example, for this work week, I have three days off.
  184. However, due to the way this work week and last work week were scheduled and the fact that the school week is offset from the work week, I only have two days off from work this school week.
  185. What a pain.
  186. </p>
  187. <p>
  188. I received a letter from PayPal telling me that my statement for last moth is ready.
  189. That seemed to be kind of strange, as I don&apos;t use my PayPal account.
  190. I clicked the link, wary of the fact that the host of the <abbr title="Uniform Resource Identifier">URI</abbr> wasn&apos;t PayPal
  191. s usual domain name, but when I clicked the link on the page that said that it&apos;d show me the statement, it sent me to PayPal&apos;s real main website to log in.
  192. From there, the login form wouldn&apos;t allow me to access my account though without having PayPal call me by telephone to be sure that I was me! What kind of idiocy is this? Like with several other large websites, there is no way to turn this antifeature off.
  193. What are those of us without telephone service supposed to do? That doesn&apos;t even touch the fact that telephone lines aren&apos;t secure, so any &quot;security&quot; feature that uses them isn&apos;t actually secure.
  194. I contacted PayPal support about the log in issue, though before they got back to me, I realized that the letter from PayPal was addressed to my real name, not my legal name.
  195. For idiotic policy reasons, my PayPal account is under my legal name.
  196. I double-checked the email, and sure enough, it was sent to the email address that I use for non-account transactions.
  197. After speaking with the support representative, they told me that the letter telling me that my statement is available is just a ploy to try to get me to &quot;upgrade&quot; my PayPal guest account into a full PayPal account.
  198. Unless I upgrade, I can&apos;t actually view the statement, so the claims that I have a statement ready for viewing are a blatant lie.
  199. </p>
  200. <p>
  201. All the while that I was waiting for responses from PayPal to each of my own responses to them, I was repeatedly trying to log into my account.
  202. Once in logged into my account, I browsed around a bit, making sure to check the page listing past transactions.
  203. I&apos;m not even sure why I did that though, seeing as there has never been any payment method associated with that account.
  204. While looking around, I spotted a link that I&apos;d looked for before, but had concluded did not exist: an account deletion link! I&apos;d done some Web searching even, but I only found information saying that for my account type, the only way to delete the account was to contact PayPal support and have them delete it.
  205. I actually spotted the link just as I was about to contact PayPal support again and try to get them to delete it, too.
  206. After clicking the link, PayPal tried to convince me not to delete the account about four times, then when that failed, PayPal &quot;limited&quot; my account, and they don&apos;t allow account holders to delete limited accounts.
  207. As soon as I switched pages to try to find the cause of the limitation, I received a notification telling me that the limitation had taken place.
  208. In other words, there&apos;s zero chance that the limitation had been there previously and I had just come in contact with it because I had tried to delete the account.
  209. There is no mistaking the fact that the account wasn&apos;t limited <strong>*until*</strong> I tried to delete it.
  210. To remove the account limitations, PayPal insists that I both provide some sort of proof of identity as well as give them unfettered access to my bank account.
  211. Fat chance! If you recall from last time that I dealt with this sort of problem with PayPal, and you probably don&apos;t because the pages of my journal from that period were lost due to <a href="/en/weblog/2015/03-March/07.xhtml">hard drive failure</a>, I outright refuse to hand PayPal the keys to any financial account of mine.
  212. Demanding identification crosses a line that they shouldn&apos;t cross, but I complied then and I complied now.
  213. However, last time, PayPal already had access to my credit card information.
  214. They had a way to charge me, but they were demanding access to my bank account anyway.
  215. There was no legitimate reason for them to have access to my credit union account (I had no bank account at the time).
  216. My only thought is that they must have been trying to steal money from my bank account.
  217. Nothing has changed, aside from the fact that this account has no credit card attached to it.
  218. I <strong>*will not*</strong> hand PayPal my credit union or bank credentials.
  219. I have contacted PayPal support once more, explaining the situation and explaining that I both provided my state-issued photo <abbr title="identification">ID</abbr> and refuse to provide access to my bank account.
  220. I&apos;m surprised that they talked to me at all on a Saturday though, and they probably won&apos;t get back to me until Monday on this issue.
  221. </p>
  222. <p>
  223. Doing a little research on euro coins, I learned that while the back of each euro coin of a specific denomination, <a href="https://en.wikipedia.org./wiki/Euro_coins#National_sides">the fronts of the coins vary from country to country</a>.
  224. While the coins are valid legal tender in all member nations of the euro area, each country is authorized to mint their own coins.
  225. Not only that, but each country chooses their own designs for the fronts of the coins that they mint.
  226. Interesting!
  227. </p>
  228. <p>
  229. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  230. </p>
  231. <hr/>
  232. <p>
  233. Copyright © 2016 Alex Yst;
  234. 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>.
  235. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  236. My address is in the source comments near the top of this document.
  237. This license also applies to embedded content such as images.
  238. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  239. </p>
  240. <p>
  241. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  242. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F11-November%2F12.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%2F11-November%2F12.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  243. </p>
  244. </body>
  245. </html>