20.xhtml 9.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139
  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/20.xhtml" />
  27. <title>Yst Dawson fades and Alex Yst takes further form &lt;https://y.st./en/weblog/2017/03-March/20.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/20.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/19.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/03-March/21.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>Yst Dawson fades and Alex Yst takes further form</h1>
  67. <p>Day 00744: Monday, 2017 March 20</p>
  68. </header>
  69. <section id="general">
  70. <h2>General news</h2>
  71. <p>
  72. It seems my T-Mobile plan&apos;s still set to expire on me, despite my having added funds to the account.
  73. The dumbed-down interface T-Mobile requires tablet account-users (as opposed to smartphone account-users) doesn&apos;t have the option of starting up the plan that it&apos;s already on, either.
  74. I&apos;ll have to wait &apos;til tomorrow (is the line actually expiring at midnight this time?) when the line&apos;ll be fully down to try then.
  75. Of course, if I can&apos;t get it working, I&apos;ll pester T-Mobile support again. I paid them $30.75 <abbr title="United States Dollars">USD</abbr> yesterday, so they&apos;re either going to make sure I can get my account going or they&apos;re giving my money back.
  76. </p>
  77. <p>
  78. I tried to contact the cable company today to ask them more questions.
  79. Mostly, I want to know if the price will stay low after the first year without continued yearly service agreements and I <strong>*need*</strong> to know if I can set up an account without my Social Security number.
  80. Their live chat form seems to be busted today though.
  81. It was working the other day ...
  82. In any case, asking questions will have to wait.
  83. </p>
  84. <p>
  85. I forgot to mention, but the other day, Discover sent me a postal letter telling me the information about my authorized user, Yst Dawson, is incomplete and they want me to complete it.
  86. I can&apos;t perform any update without providing a Social Security number though.
  87. I&apos;m not looking to link a second identity to the account.
  88. I&apos;m not looking for a joint account, I&apos;m looking to authorize myself, under my preferred name, to spend my money!
  89. I can&apos;t update the name to reflect my own name change either.
  90. Anyway, I pulled up a live chat with a Discover representative today to try to get information about and resolve the issue.
  91. Long story short, Discover no longer has the option to add authorized users, as I already knew, and now only has the option to add partial-joint account holders with their identities tied to the account.
  92. Furthermore, if I don&apos;t downgrade Yst from being an authorized user to being a partial-joint account holder by adding their Social Security number (which is actually my own, but that name isn&apos;t tied to my Social Security number so they won&apos;t accept it), they&apos;re going to deactivate Yst&apos;s card on me.
  93. I&apos;m taking this opportunity to cut ties with Discover.
  94. My Discover card&apos;s cost me a lot of money in domain name fees for domain names that I haven&apos;t actually been able to use, so it&apos;ll be nice to have that liability eliminated anyway.
  95. As Discover&apos;s proven they won&apos;t always block transactions when they say they will, closing the account&apos;s the only way to be sure to put the domain name charges behind me.
  96. I haven&apos;t closed the account just yet though.
  97. It could be useful for a couple more things strictly because it&apos;s getting canceled soon.
  98. For example, if I manage to get my T-Mobile account fixed, I might be required to set up autopay again.
  99. However, I can set up autopay on the dying card, so autopay can never actually get through, and there&apos;s no risk to me or my money.
  100. I&apos;ll simply pay in person every month and T-Mobile&apos;ll only <strong>*think*</strong> they&apos;ll be able to charge me automatically if I forget.
  101. </p>
  102. <p>
  103. I spoke with a representative at Chase the other day to ask them about authorized users on their accounts.
  104. For chequing accounts, they require the authorized user come in in-person.
  105. It&apos;s not really possible for me to prove my real name yet though until I get it changed in court, which I&apos;ll likely do at some point.
  106. And once I <strong>*can*</strong> prove who I am, I&apos;ll no longer have any use for an &quot;authorized user&quot; card; I&apos;ll simply use a debit card from a credit union, most likely.
  107. As such, I can&apos;t get one of Chase&apos;s chequing accounts to fit my needs.
  108. Besides, if the authorized user has to prove their identity, they&apos;re not an authorized user at all; they&apos;re a partial- or full-joint account holder, which is exactly what I&apos;m <strong>*not*</strong> looking for.
  109. However, there&apos;s a difference in how they handle chequing account &quot;authorized users&quot; and credit card account authorized users; that is to say, the credit card accounts are actually <strong>*able*</strong> to have authorized users added.
  110. I thought I&apos;d have to wait to know if I was approved, but they actually let me know right away that I was approved, how much my line of credit&apos;s limit would be, and what interest rate they&apos;d charge.
  111. Both the card issued to my real name and the card issued to my birth name will arrive in the mail in about a week.
  112. Though I&apos;ll be canceling my Yst Dawson credit card, my Alex Yst card will be in my wallet probably before the next time I buy something online!
  113. </p>
  114. <p>
  115. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  116. </p>
  117. </section>
  118. <hr/>
  119. <p>
  120. Copyright © 2017 Alex Yst;
  121. 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>.
  122. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  123. My address is in the source comments near the top of this document.
  124. This license also applies to embedded content such as images.
  125. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  126. </p>
  127. <p>
  128. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  129. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F03-March%2F20.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%2F20.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  130. </p>
  131. </body>
  132. </html>