14.xhtml 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216
  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/08-August/14.xhtml" />
  27. <title>My old domain registrar is trying to steal my money and I sold out to Google Voice. &lt;https://y.st./en/weblog/2016/08-August/14.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/08-August/14.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/08-August/13.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/08-August/15.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 old domain registrar is trying to steal my money and I sold out to Google Voice.</h1>
  67. <p>Day 00526: Sunday, 2016 August 14</p>
  68. </header>
  69. <p>
  70. It&apos;s too late to cancel the FreedomPop order now; they&apos;ve shipped it.
  71. FreedomPop still hasn&apos;t responded to me though.
  72. </p>
  73. <p>
  74. While power washing the porch, I decided that I should at least try to scoot the large, heavy pond filter to another section of the porch, power wash under it, then scoot it back.
  75. While attempting to do that, I found that water was being sloshed out of a hole on the side.
  76. Why was the filter full of water? No wonder it was so heavy! We&apos;ve never actually used that filter as far as I know, so I&apos;m guessing that the water inside is somehow rainwater.
  77. The lid on top should have kept the rain out though, so I&apos;m not sure why the thing is full.
  78. After dumping it out, the filter became much easier to move.
  79. Furthermore, it doesn&apos;t appear to be an actual filter, but just the shell of one.
  80. We certainly wouldn&apos;t have intentionally filled it with water without an actual filter being present in there.
  81. I should have completely power washed the porch today, but I ended up arguing with my old domain registrar all day.
  82. I could have worked on washing the porch between messages to them, but I was far too stressed by them to get hardly anything done.
  83. </p>
  84. <p>
  85. Because of <a href="/en/weblog/2015/03-March/07.xhtml">the incident</a>, I lost all of my passwords to every account that I had anywhere online.
  86. Knowing that I wouldn&apos;t be able to get back into any accounts that had automatic payments set up, I had Discover mark my card as lost and send me a new one.
  87. My intent was that anyone with my old credit card number wouldn&apos;t be able to continue charging me and they&apos;d have to allow the services that they provided me to expire.
  88. However, that, as I learned today, did not go as planned.
  89. Apparently, credit cards have a feature that allows a merchant to set up reoccurring payments without holding onto the credit card information.
  90. Therefor, when the credit card information changes, it doesn&apos;t have any effect on the future charges.
  91. My old domain registrar has been charging me for domain renewals on three domain names that I can&apos;t even access! I noticed the latest charge, which occurred a couple of days ago, because I was checking for a refund from PayPal/eBay.
  92. I tried talking to my old domain registrar to try to get them to stop charging me (by turning off automatic renewals) and if possible, refund only the domain that they charged me for two days ago.
  93. I didn&apos;t even ask for a refund on the other two domains.
  94. However, they outright refuse to turn off automatic renewal unless I provide a notarized letter verifying my identity.
  95. This is insane.
  96. They refuse to accept state-issued photo <abbr title="identification">ID</abbr> because they think that it can be forged, but they somehow don&apos;t think that this notarized letter can be forged.
  97. I refuse to create further identifying documents though; United States citizens already have way too many identifying documents.
  98. They fail to grasp the fact that I have access to the credit card statement too.
  99. Even if the domain names are somehow not mine, the credit card <strong>*is*</strong>, and I am not okay with them continuing to charge it.
  100. I offered to send them my credit card statement to prove that the card is mine, and even said that maybe they should disable automatic renewals, but send an email to the email address that they have on file warning the domain holder that automatic renewals have been disabled and that they may re-enable them with a different credit card if they so choose.
  101. No dice.
  102. While the domain registrar is trying to screw me over, it&apos;s not the fault of the representative that I dealt with.
  103. Besides, it&apos;s hard to be angry with polite people.
  104. I made sure to let them know that I was aware that this was the fault of the company that they work for, not their own fault, and said that I hoped that I hadn&apos;t caused them too much frustration.
  105. Next, I headed on over to speak with Discover.
  106. </p>
  107. <p>
  108. My only choice as I see it is to file a charge dispute through Discover.
  109. Even the representative from the domain name company admitted that I was well within my rights to do so.
  110. In a best-case scenario, this dispute with prevent further charges and might even result in a refund for one or more of the three charges over the past year.
  111. In a worst-case scenario, all that i have to do is cancel my Discover card.
  112. While I greatly hope that Discover does their job and revokes authorization for continued charges from the domain name company, the fact is, if the account is gone, no further charges can be made.
  113. My Discover card is the best credit card that I&apos;ve ever had (though I admit I&apos;ve only had two), so I&apos;d hate to lose it, but it&apos;s also true that getting the card involved use of a telephone back before I started refusing to use a telephone number as a personal identifier.
  114. Simply put, I shouldn&apos;t even have a Discover card because obtaining a Discover card required telephone service.
  115. If I do end up having to lose my Discover card, in a way, it would only be the correction of a mistake, not the loss that it would feel like.
  116. It would feel like a loss though; I was able to get a card under my preferred name (as opposed to my legal name) through Discover, so without that card, online purchases (and anything that automatically renews) may never be the same.
  117. It sounds like the charge dispute will work though.
  118. I explained the situation to a Discover representative, and they said that they are going to give the domain company a full fifteen days before acting, but on 2016-08-30, they said that they will get back to me and initiate the dispute if still necessary.
  119. I let Hover know of Discover&apos;s decision in case it would make any difference, and am anxiously awaiting the thirtieth of the month.
  120. </p>
  121. <p>
  122. I finished my university readings for the week and moved on to work on the discussion assignment.
  123. Much to my surprise and delight though, there wasn&apos;t a discussion assignment this week and it sounds like there won&apos;t be any at all during the orientation.
  124. Discussion assignments are bad enough when they&apos;re graded, but when you&apos;re not even going to get credit for them, it seems like even more of a waste of effort.
  125. Don&apos;t get me wrong, I&apos;ll put in the effort, but I never learn anything from the discussion assignments.
  126. Basically, the whole class just sits around reciting what we all already learned throughout the week.
  127. I&apos;m not sure what anyone else is gaining from this or what we&apos;re expected to accomplish, but it just seems like lost time and unfruitful effort.
  128. Perhaps it actually helps certain people learn though.
  129. </p>
  130. <p>
  131. This week&apos;s assignment was simply to fill out our university profiles, which are visible to the other students.
  132. Uploading a photograph of oneself was listed as a requirement of the assignment, but as the assignment isn&apos;t graded, I just skipped that part.
  133. There&apos;s no reason that anyone needs a photograph of me.
  134. I did complete all other listed requirements though.
  135. It seems that there will be a graded journal entry each week too, though not during orientation.
  136. I suppose that I&apos;ll probably quote those in this journal, as it&apos;s my real one, and there&apos;s no reason to have a fragmented journal setup.
  137. With the only asignment done, I&apos;m done with the orientation for the week.
  138. School weeks at this university are measured from Thursday to Wednesday, so it&apos;ll be a few days before the next readings and assignment.
  139. </p>
  140. <p>
  141. I finally got around to fixing the <abbr title="Domain Name System">DNS</abbr>-leaking issue in my mail client.
  142. My plan was to replace the client with one that didnt&apos; leak, but that didn&apos;t end up happening.
  143. I went to the people of <a href="ircs://irc.oftc.net.:9967/%23Tor">#tor</a> for advice, asking what <abbr title="Pretty Good Privacy">PGP</abbr>-enabled mail clients that they knew of without <abbr title="Domain Name System">DNS</abbr> leakage.
  144. They said that the only one that they knew of was actually <a href="apt:icedove">Thunderbird</a>, but only with the <a href="apt:xul-ext-torbirdy">TorBirdy</a> extension installed.
  145. I don&apos;t even need to switch mail clients again! I went to the Thunderbird extension repository to find TorBirdy, but the description said that if one is running Debian, they should install it through <a href="apt:aptitude">Debian&apos;s package manager</a>, so that&apos;s what I did.
  146. For some reason though, the preferences were all in Arabic! I asked in #Tor how to switch the language of the plugin to English or Esperanto, and they told me about a bug in that version of the software.
  147. Purging the Debian repository version and installing from the Thunderbird repository as originally planned fixed the problem.
  148. </p>
  149. <p>
  150. My mother can&apos;t stand that my telephone number changes and claims that using the <abbr title="Short Message Service">SMS</abbr> gateways is too difficult.
  151. On my end, the email end, I could understand that complaint.
  152. To use the <abbr title="Short Message Service">SMS</abbr> gateways, I need to first figure out what carrier a number is even serviced by, then locate the appropriate gateway to use.
  153. It&apos;s a pain, but it&apos;s worth it to use an email address as my own handle instead of merely a ten-/eleven-digit number.
  154. However, on their end, the mobile end, all that they have to do is send to my email address.
  155. There&apos;s no lookups and no effort.
  156. It&apos;s just as easy as sending messages to a telephone number.
  157. However, with my mother&apos;s data usage going through the roof without Wi-Fi access around to keep it down, I was able to do something that I&apos;ve wanted to do for a long time: disable that blasted iMessage service on their iPhone.
  158. The iPhone by default sends messages using up data instead of using standard <abbr title="Short Message Service">SMS</abbr> messaging.
  159. Furthermore, because of a bug in Verizon&apos;s service, Verizon iPhones using iMessage don&apos;t work very well with the <abbr title="Short Message Service">SMS</abbr> gateways.
  160. Anything going to of from a Verizon iPhone through the <abbr title="Short Message Service">SMS</abbr> gateway will come out on the other side as an attachment instead of an easy-to-read basic message.
  161. I suspect that turning off iMessage and turning on <abbr title="Short Message Service">SMS</abbr> messaging will fix that.
  162. However, I also disabled <abbr title="Multimedia Messaging Service">MMS</abbr> messaging because it too uses the data connection.
  163. Without <abbr title="Multimedia Messaging Service">MMS</abbr> messaging, the iPhone refuses to send to send messages to an email address, as it doesn&apos;t want to send them via <abbr title="Short Message Service">SMS</abbr>.
  164. If I&apos;m being honest, Replicant has this same antifeature.
  165. A basic flip telephone can send to an email address using basic <abbr title="Short Message Service">SMS</abbr>, but somehow these more-capable mobile devices can&apos;t.
  166. I actually suspected that this might happen though, so I tried to contact my mother yesterday.
  167. My message of course got through, but they couldn&apos;t reply.
  168. Now, they have a legitimate excuse for not wanting to use the <abbr title="Short Message Service">SMS</abbr> gateway: they can only receive messages, not send them.
  169. With regular <abbr title="Short Message Service">SMS</abbr> messaging out of the question (as my mother complains about my ever-changing telephone number) and <abbr title="Short Message Service">SMS</abbr> gateway out of the question (because of the buggy software stack that demands that the data connection be used), I searched for an <abbr title="Short Message Service">SMS</abbr> forwarding service.
  170. I asked if anyone know of one on <a href="ircs://sbuk7aqcxkoyipwv.onion:49152/%23Android">#Android</a>, and they told me to use Google Voice.
  171. I dreaded that answer, but it was honestly the one that I expected.
  172. The problem with Google Voice is that it requires a Google account to use.
  173. The problem with Google accounts is of course that Google demands a telephone number, regardless of if you plan to make use of any of their telephone-related services.
  174. In this case though, I was trying to get Google to forward <abbr title="Short Message Service">SMS</abbr> to another number, so there was no point in trying to avoid handing over the number, or so I thought.
  175. </p>
  176. <p>
  177. As it turns out, Google Voice is in many ways a better service than what I was looking for.
  178. I was able to set it up to not forward to a telephone number, but instead, forward to my new Google email inbox.
  179. I can even reply to the email and the reply will be sent to the sender of the initial <abbr title="Short Message Service">SMS</abbr> message! The main catch is simple though.
  180. While clearly no telephone number to forward to is needed in this setup, Google demands that a forwarding telephone number be supplied, though it can be disabled.
  181. If the forwarding number is deleted, the Google number is also deleted and it seems to be impossible to recover.
  182. No new forwarding number can be added if there is no Google number, but without a forwarding number, Google won&apos;t allow there to be a Google number.
  183. This telephone-free setup requires a blasted telephone number that has been verified by Google! Thankfully, my telephone number will be expiring in about two months, after which, Google won&apos;t have a telephone number that reaches me.
  184. Furthermore, whenever I have the chance, I&apos;ll add any telephone number that I can (as long as it&apos;s not my number or won&apos;t be my number for much longer) to the account to further dilute their information.
  185. Also, use of Google Voice is in desperation here, but now that I have the account, that doesn&apos;t mean that I can use it for anything else.
  186. Because the account had me verify a telephone number, regardless of the fact that that number won&apos;t reach me for much longer, I cannot use the account for any other Google service.
  187. This account must remain isolated in every possible way.
  188. As a further catch, the main benefit of Google Voice (being able to make it look like I&apos;m sending from a telephone number instead of an email address) is it&apos;s second-to-main drawback as well (the main one being that a verified telephone number is needed to set up the account).
  189. If my messages appear to come from a telephone number, they don&apos;t appear to be coming from my email address.
  190. I should only use this account to contact people that I for some reason cannot reach via the <abbr title="Short Message Service">SMS</abbr> gateways, with the exception of my mother, whom I can reach but they cannot reach me.
  191. </p>
  192. <p>
  193. It sounds like my mother will be coming home tomorrow.
  194. </p>
  195. <hr/>
  196. <p>
  197. Copyright © 2016 Alex Yst;
  198. 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>.
  199. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  200. My address is in the source comments near the top of this document.
  201. This license also applies to embedded content such as images.
  202. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  203. </p>
  204. <p>
  205. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  206. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F08-August%2F14.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%2F08-August%2F14.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  207. </p>
  208. </body>
  209. </html>