05.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164
  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 © 2015 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/2015/10-October/05.xhtml" />
  27. <title>Net neutrality is still in peril &lt;https://y.st./en/weblog/2015/10-October/05.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/2015/10-October/05.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/2015/10-October/04.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2015/10-October/06.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>Net neutrality is still in peril</h1>
  67. <p>Day 00212: Monday, 2015 October 05</p>
  68. </header>
  69. <p>
  70. According to an email I received today, Jeb Bush says he&apos;ll gut net neutrality if he is elected, despite the fact that republicans and democrats are in agreement that net neutrality needs to be preserved.
  71. I was going to likely vote for whatever third party candidate ran for office because I don&apos;t like the democrats or the republicans, but now I&apos;m going to vote for the democratic candidate.
  72. I can&apos;t honestly expect the third-party candidate to win, so I had better put my vote toward trying to make Jeb Bush lose.
  73. </p>
  74. <p>
  75. Before leaving the house, I tried again to get a regular expression onion generator that would spit out only onions composed of English words.
  76. This time, I tried writing a <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> script that held the regular expression so eschalot wouldn&apos;t have to.
  77. The <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> script was supposed to ask eschalot for whatever the first onion it could generate, then the onion would be examined in <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> before deciding whether or not to write it to disk before generating a new one.
  78. However, it seems that my regular expression is too large for <abbr title="PHP: Hypertext Preprocessor">PHP</abbr> as well.
  79. I may or may not try porting this to other languages and trying to run it there.
  80. </p>
  81. <p>
  82. I walked some resumes down to the local mall today, though it seems most places didn&apos;t want them.
  83. Instead, they wanted me to apply online.
  84. I did manage to get a couple handed out though, and I got a list of places to apply online.
  85. I&apos;ll start on those applications tomorrow.
  86. I also have a sort-of-interview set up for Wednesday, so maybe I&apos;ll get lucky and that will go well.
  87. </p>
  88. <p>
  89. After returning home, I waited for a refrigerator delivery.
  90. We now have a full-sized refrigerator! We&apos;ve been working with a miniature refrigerator for the past month, which has been a bit of a pain.
  91. </p>
  92. <p>
  93. I found four working <abbr title="Top Level Domain">TLD</abbr>s for use without a telephone number today.
  94. The first was <a href="/en/URI_research/ccTLDs.xhtml#tk">Tokelau</a>&apos;s registry.
  95. This registry appears to be run by Freenom, but unlike the other registries run by Freenom, the Tokelau registry has it&apos;s own registration forms in addition to the ones on the Freenom website.
  96. If you register through the Freenom website, registration requires a telephone number, but if you register through the Tokelau registry&apos;s website, registration does not require a telephone number.
  97. </p>
  98. <p>
  99. The next registry belongs to the <a href="/en/URI_research/ccTLDs.xhtml#sl">Republic of Sierra Leone</a>.
  100. This registry&apos;s registration page requires that the telephone number field be filled out, but it accepts arbitrary strings in this field as well as actual telephone numbers.
  101. Simply filling the field out with the string &quot;no telephone number available&quot; will suffice.
  102. </p>
  103. <p>
  104. The third registry does things a little strangely.
  105. This registry, owned by the <a href="/en/URI_research/ccTLDs.xhtml#pr">Commonwealth of Puerto Rico</a>, has registration broken into a few different website visits.
  106. First, you visit the website and begin registration by entering your email address.
  107. You are then sent an email to confirm your address, with a link back to the registration website.
  108. Next, you fill out your whois information.
  109. A telephone number claims to be required, but you can use an arbitrary string such as &quot;no telephone number available&quot; here as well.
  110. Upon submission of the form, you are presented with a message that your application will be reviewed, and you will be sent an email with payment instructions upon acceptance.
  111. I assume this email will link back to the registry website, instigating the third and final Web-based part of the registration.
  112. I feel bad having the reviewers review my application when I have no intent to purchase.
  113. I submitted the form thinking that I would next be presented with a payment page, at which point I could cancel the registration, having verified that the form accepted the lack of a telephone number.
  114. </p>
  115. <p>
  116. Finally, I looked into the registry of the <a href="/en/URI_research/ccTLDs.xhtml#pn">Pitcairn Group of Islands</a>.
  117. This registry is the weirdest I&apos;ve seen, as far as whois contact information gathering.
  118. Instead of having several fields asking for various pieces of contact information, this registry&apos;s registration form has simply one text area labeled &quot;Your contact details&quot;.
  119. That&apos;s all! It has no specifics as to what it is asking for.
  120. If you want to put in just your email address, that would technically be correct.
  121. If you want to put in your email address in addition to your postal address, that is also fine.
  122. If you want to be obtuse, you could put only a fax number and make it so almost no non-business would have a way to reach you.
  123. You could even put a Twitter account there as the way you want to be reached! The possibilities are endless, and I&apos;m not sure what they are really after, though they probably want at least a postal address and email address.
  124. </p>
  125. <p>
  126. eNom has taken down <a href="http://wowana.me/">wowaname</a>&apos;s <abbr title="generic top-level domain">gTLD</abbr>-based domain without notice and despite me having proved the address in the whois record is valid.
  127. The only thing I can think is that my email got caught in the spam filter or something, so wowaname forwarded it to eNom.
  128. The domain loss has caused <a href="ircs://irc.volatile.ch:6697/">Volatile</a> to fall apart a bit, as it was dependent on that host name for some of the connections.
  129. </p>
  130. <p>
  131. After thinking about it a bit, wowaname came to the conclusion that she may be under attack from some unknown disruptive party.
  132. Three accounts have been giving her trouble now, all at around the same time.
  133. eNom has revoked her domain after hassling her, her Twitter account has been revoked, and Riseup was hassling her about some email she sent.
  134. I don&apos;t recall if Riseup revoked her account or she quit using it out of fear that it would soon be revoked, but that account is now down as well.
  135. I&apos;d have to agree: the timing is just too suspicious to be three isolated incidents.
  136. Someone isn&apos;t happy with wowaname.
  137. She does have a tendency to needlessly provoke people too, so it really could be anyone as far as I know.
  138. I really hope the domain ends up back in her possession, though I have no idea how to find out who is the cause of all this mess.
  139. </p>
  140. <p>
  141. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  142. </p>
  143. <hr/>
  144. <p>
  145. Copyright © 2015 Alex Yst;
  146. 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>.
  147. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  148. My address is in the source comments near the top of this document.
  149. This license also applies to embedded content such as images.
  150. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  151. </p>
  152. <p>
  153. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  154. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F10-October%2F05.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%2F2015%2F10-October%2F05.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  155. </p>
  156. </body>
  157. </html>