23.xhtml 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235
  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/23.xhtml" />
  27. <title>Verizon is invading my mother&apos;s privacy again. &lt;https://y.st./en/weblog/2016/10-October/23.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/23.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/22.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/10-October/24.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>Verizon is invading my mother&apos;s privacy again.</h1>
  67. <p>Day 00596: Sunday, 2016 October 23</p>
  68. </header>
  69. <img src="/img/CC_BY-SA_4.0/y.st./weblog/2016/10/23.jpg" alt="Red gazebo" class="weblog-header-image" width="811" height="480" />
  70. <p>
  71. Current countdowns:
  72. </p>
  73. <ul>
  74. <li>249 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. Website cleanup &quot;to do&quot; list:
  80. </p>
  81. <ul>
  82. <li>Remove numeric <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> entities; these pages are written in Unicode, non-<abbr title="American Standard Code for Information Interchange">ASCII</abbr> characters can be used directly.</li>
  83. <li>Find and tag any references to <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> tags in my journal pages.</li>
  84. <li>Find and tag any references to functions, classes, and constants that can be <code>grep</code>ed for; look for backslashes and empty parentheses.</li>
  85. </ul>
  86. <p>
  87. <a href="https://marcwithac.bandcamp.com/">Marc With a C</a> seems to have written a few days ago, but I missed it because I&apos;m not as active on Twitter as I could be.
  88. My copy of CARK has been mailed, and has some stickers thrown in.
  89. That&apos;s an interesting bonus, I&apos;m curious to see what those look like.
  90. Furthermore, due to the recent hurricane, things didn&apos;t fall into place with the cassette sale as planned.
  91. Some people couldn&apos;t make it into the shop the day before the sale, which Marc says hindered the email sales.
  92. However, the remainder of the unsold tapes will be put on sale in December.
  93. They won&apos;t go to waste! Assuming that this isn&apos;t another telephone-based sale, I&apos;ll try to spread the word when that happens.
  94. </p>
  95. <p>
  96. I really, really, really should have worked on schoolwork today, but I didn&apos;t.
  97. I started the day writing yesterday&apos;s journal entry, due to having gotten home late this morning and not having time to write it yesterday, and I was going to work on my homework after that.
  98. I&apos;m still feeling a bit mentally tired though from the lack of sleep yesterday, so I instead went with my mother to run errands.
  99. </p>
  100. <p>
  101. First, we went to an estate sale.
  102. They didn&apos;t really have anything interesting there, but it was in a nice-looking neighborhood.
  103. Several large trees dotted the area, so the houses had been there a while.
  104. </p>
  105. <p>
  106. Next, we went to the Verizon store, which seemed to be our main errand.
  107. My mother gets some discount on their Verizon service for being an educator.
  108. Even so, their Verizon bill is through the roof and they should really consider again switching to a better service provider.
  109. However, they just locked themself in with another two-year contract, so they won&apos;t be switching any time soon.
  110. In any case, my mother&apos;s had this discount for a while, but Verizon was demanding that my mother reverify their status as a schoolteacher.
  111. They wanted my mother to upload a photograph or scan of their pay stub.
  112. Of course, my mother didn&apos;t want to do this because the pay stub has so much personal information.
  113. That&apos;s the thing with postpaid mobile service though.
  114. You pay them a higher fee than prepaid customers pay, and you do it for the privilege of handing over your personal information that they don&apos;t honestly need.
  115. The representative online said that my mother could black out all the numbers first, but when my mother asked to submit only the part of the pay stub that verified who their employer is, the representative insisted that that wouldn&apos;t be acceptable.
  116. My mother didn&apos;t want an image of their pay stub on file, so we went into the Verizon store in person to handle verification there.
  117. The person at the door greeted us and asked what we needed help with, then we waited for about half an hour.
  118. At that point, that same person that had checked us in came to help, but said that the only way that the verification process could be completed was online.
  119. Why couldn&apos;t they have told us that when they checked us in? It seemed like the person had just blown us off as well.
  120. Once out the door, I asked if they had thought that we&apos;d been blown off as well, and they&apos;d been thinking the same thing, so we headed back in to complain.
  121. It turns out that they have no complaint-handling system though, which seems very strange.
  122. How do you keep customers if you won&apos;t hear them out when there&apos;s a problem? After a bit, the manager was brought in, and they handled the verification process.
  123. My mother was annoyed that they refused to work on the situation before seeing photo <abbr title="identification">ID</abbr>, as they&apos;d left theirs out in the van and didn&apos;t want to go back out for it, then when the manager took care of the situation, they did so by photographing the pay stub and sending it in online.
  124. In other words, visiting the store in-person hadn&apos;t accomplished anything over completing the process online themself.
  125. I swear, mobile carriers walk all over postpaid customers, demanding personal information that they have no business having.
  126. Why does anyone pay more for such unacceptable treatment?
  127. </p>
  128. <p>
  129. Next, we went to a store to pick up balloons.
  130. My mother&apos;s been granted a $100 <abbr title="United States Dollars">USD</abbr> budget for they year by their employer to use for school supplies.
  131. They can use it for whatever school-related expense that they want to, provided that they keep and submit the receipts.
  132. Apparently, they&apos;re working on a butterfly unit with their students, and are going to have them work on papier-mâché butterflies.
  133. These long balloons that they bought, which are the kind you&apos;d see used for balloon modeling, will serve as the bodies of the butterflies.
  134. </p>
  135. <p>
  136. We stopped for a bite to eat at Carl&apos;s Junior, where we each got an order of their nachos sans meat (mine also without dairy products).
  137. They&apos;ve made the orders about a third of the size that they were until recently though, but the price hasn&apos;t changed! That&apos;s a rip-off.
  138. On the positive side though, the bottoms of their new containers are labeled as compostable.
  139. I&apos;m always happy to see progress made in a more environmentally-friendly direction!
  140. </p>
  141. <p>
  142. Next, we stopped at the laundromat to dry my mother&apos;s laundry from yesterday.
  143. I hung my clothing up to dry at home, but my mother doesn&apos;t have that luxury.
  144. They need to look nice for work, but hang drying leads to wrinkles in the fabric.
  145. I brought my laptop along on our errands in case there was time to work on my reading assignments while we were there, but I didn&apos;t end up doing that.
  146. </p>
  147. <p>
  148. Lastly, we headed to the storage unit to look for a stockpile of wire coat hangers that my mother has.
  149. We couldn&apos;t find them there, but we did remove several other items from the unit which my mother will take to their classroom tomorrow.
  150. Some of it doesn&apos;t exactly belong there, but it&apos;s school-related, and removing it from the storage unit frees up space to get other things in.
  151. </p>
  152. <p>
  153. We stopped by home, but only briefly.
  154. We headed back out, this time, to the forest.
  155. My mother feels better if they get some time in the woods, so we went out to gather bullet shells.
  156. I didn&apos;t really feel like gathering shells though, so I mostly slacked off on that.
  157. Instead, I looked at plants and fungi.
  158. I ended up finding three chanterelles, which my mother harvested.
  159. We later took a walk down a very nice trail, mostly visible only by the lack of moss.
  160. The forest floor in that area was mostly covered in the stuff, with several mushrooms and a few ferns scattered throughout, but the trail was well-traversed enough to have killed the moss.
  161. Strange-looking mushrooms abounded, though they weren&apos;t very photogenic.
  162. Being a bright white against a darker background, the camera interpreted the mushroom as a source of light and overcorrected in all the wrong ways.
  163. </p>
  164. <p>
  165. My GT-i9300 used to have the option to allow access to the camera from the lock screen.
  166. As I really didn&apos;t use the camera much, I disabled that.
  167. However, I&apos;ve been using my GT-i9100M&apos;s camera daily over the past two weeks, so I&apos;ve been trying to enable that feature on this device.
  168. It was enabled by default on the GT-i9300, and the setting for it seems to also be enabled by default on the GT-i9100M.
  169. However, the camera isn&apos;t accessible from the device&apos;s lock screen.
  170. I still haven&apos;t managed to figure out how to fix this, but while going through various settings, I found a new camera mode that might be useful to me.
  171. I&apos;ve been scaling the photographs that I take, because they&apos;re far too large to post on this minimalistic website, then cropping them, because I prefer an aspect ratio with greater width.
  172. My device&apos;s camera has a <abbr title="Video Graphics Array">VGA</abbr> mode though, that eliminates the need for scaling.
  173. The images are already nice and small! Even better, <abbr title="Wide Video Graphics Array">WVGA</abbr> mode likewise produces small photographs, but also provides a nice, wide view.
  174. I&apos;ll try out <abbr title="Wide Video Graphics Array">WVGA</abbr> mode tomorrow and see how well that works for me.
  175. I&apos;m hoping that this will not only make things easier, but will also provide a standard size and aspect ratio for my photographs.
  176. Initially, I started cropping my images due to a mistake that I made.
  177. I held my camera in the wrong orientation all day on the <a href="/en/weblog/2016/10-October/09.xhtml">ninth</a>, when I started this daily photography thing.
  178. I had stupidly assumed that my camera took square photographs and I wanted them all to be right-side up.
  179. That resulted in images that were taller than they were wide though, which I really didn&apos;t like for use as webpage header images.
  180. I scales the image that I chose to use that day both to reduce blur and to reduce file size, then cropped it to look more like a landscape-orientation photograph.
  181. As I was cropping the image, I had to chose an aspect ratio.
  182. I could have calculated what the original aspect ratio was, then apply it in the other direction, but instead, I just chose a simple aspect ratio that looked nice: 3:2.
  183. I applied this same ratio to my later photographs through cropping, despite having held my camera correctly when taking them.
  184. This was partially for consistency, but partially because the original aspect ratio, while not square, was too close to being square.
  185. I liked the aspect ratio of that first photograph that I&apos;d cropped.
  186. This new camera mode though provides an even-wider aspect ratio, so it continues to look nice, and I&apos;m hoping that the smaller size will likewise automatically reduce blur.
  187. </p>
  188. <p>
  189. Speaking of photographs, my mother had me copy their photographs from their iPhone to their desktop computer.
  190. Oddly enough, the device appears to communicate using <abbr title="Media Transfer Protocol">MTP</abbr>, but I think that it&apos;s some sort of nonstandard version of <abbr title="Media Transfer Protocol">MTP</abbr>.
  191. The device refuses to send the photographs to my laptop, though I think that it sends them all to my mother&apos;s desktop.
  192. Furthermore, the device presents a greatly-different directory structure to my laptop than their desktop.
  193. On their desktop, only the <code>/DCIM/</code> directory is visible.
  194. This directory contains four subdirectories, all of which contain photographs.
  195. However, my laptop sees things very differently.
  196. For starters, I can see a lot more than just the <code>/DCIM/</code> directory.
  197. It looks like a regular home directory on a desktop machine or a Replicant/Android device.
  198. For that reason, I think that my laptop is seeing a more clear view of what&apos;s really on there.
  199. Secondly, the <code>/DCIM/</code> directory contains many more directories than just the four containing photographs.
  200. Most of these are empty.
  201. Strangest of all though, the names of the subdirectories that contain the photographs as seen by my mother&apos;s desktop machine refer to directories that on my laptop, appear to be empty directories.
  202. Instead, different;y-named subdirectories appear to contain the photographs.
  203. I&apos;m not sure what sort of nonsense the iPhone is pulling, but it&apos;s probably something stupid that Apple came up with to try to be &quot;better&quot; at the cost of compatibility.
  204. </p>
  205. <p>
  206. While writing up this journal entry, I realized that going back to work at the pizza place isn&apos;t as simple as it sounds.
  207. Even if they hire me, they have required uniforms, and they only give you two.
  208. I don&apos;t have a working washing machine! I&apos;ll need to go to the expensive laundromat every two days if I get this job back.
  209. I&apos;ll have to see what my mother thinks about that situation tomorrow.
  210. </p>
  211. <p>
  212. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  213. </p>
  214. <hr/>
  215. <p>
  216. Copyright © 2016 Alex Yst;
  217. 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>.
  218. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  219. My address is in the source comments near the top of this document.
  220. This license also applies to embedded content such as images.
  221. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  222. </p>
  223. <p>
  224. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  225. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F10-October%2F23.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%2F23.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  226. </p>
  227. </body>
  228. </html>