03.xhtml 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261
  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/09-September/03.xhtml" />
  27. <title>I can no longer trust my mobile for now &lt;https://y.st./en/weblog/2016/09-September/03.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/09-September/03.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/09-September/02.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/09-September/04.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>I can no longer trust my mobile for now</h1>
  67. <p>Day 00546: Saturday, 2016 September 03</p>
  68. </header>
  69. <p>
  70. Current countdowns:
  71. </p>
  72. <ul>
  73. <li>20 unfinished weblog entries in <a href="/en/weblog/2016/07-July/">July</a></li>
  74. <li>16 days until mobile voice/<abbr title="Short Message Service">SMS</abbr> service with my current carrier ends</li>
  75. <li>46 days until mobile data service with my current carrier ends</li>
  76. <li>43 days until my old domain registrar can no longer counter my charge dispute</li>
  77. </ul>
  78. <p>
  79. Vanessa and our mother came home today.
  80. It seems that they didn&apos;t have any success in finding a place to live, and as such, Vanessa is not yet registered in school.
  81. Vanessa seems to be being strong for our mother, though I&apos;m almost certain that this turn of events is bothering them.
  82. </p>
  83. <p>
  84. I forgot to mention that NotABug has come back up, only a day after it went down.
  85. Perhaps it was just scheduled maintenance that I simply didn&apos;t know about.
  86. I tend to panic more and quicker than I should.
  87. The last time that I had a Git host running on free software though (Gitorious), they got bought out by a company (GitLab) that scrapped the free service in favor of their existing proprietary service.
  88. It&apos;s worth noting that GitLab does offer a free version of their software, but they don&apos;t <strong>*host repositories*</strong> using it.
  89. If I had the means to host my own repositories, GitLab software might be an option, but repositories hosted by the GitLab company are hosted using the proprietary version of the software.
  90. At the moment, I know of only two free Git hosts that don&apos;t come with restrictions that I don&apos;t feel like dealing with: <a href="https://notabug.org./">NotABug.org</a> and <a href="https://git.vola7ileiax4ueow.onion/">Volatile Git</a>.
  91. Fearing disk damage, service discontinuation, and company buyout, I like having a bit of redundancy.
  92. Losing either of these two Git hosts would be quite unfortunate.
  93. </p>
  94. <p>
  95. Cyrus located the source of the bad scent.
  96. It wasn&apos;t the sink after all, but a bag of rotten potatoes.
  97. I never could smell it, but at least that&apos;s cleaned up now.
  98. </p>
  99. <p>
  100. My mother is quite inconsiderate when it comes to my mobile Internet connection, which we&apos;ve both been having to use.
  101. They asked to use it while I was trying to study, used it for a bit, then took a nap without returning my mobile to me.
  102. I couldn&apos;t continue studying because I had no Internet connection, but they weren&apos;t even using it! This isn&apos;t really going to work out well, especially once we get moved.
  103. Out of desperation, I&apos;ve done something that I never wanted to do: I&apos;ve <a href="https://code.paulk.fr./article16/missing-proprietary-firmwares-in-android-systems">installed proprietary firmware on my Replicant</a>.
  104. Paul K has a script that makes the task easy, and after looking at both the code and the file system of the device before the noxious firmware was added, it looks like removing it will be easy.
  105. With a root shell, I only need to delete <a href="file:///system/vendor/firmware/">one directory</a>, which didn&apos;t exist before, but now contains all the firmware.
  106. With this firmware, I was able to get a Wi-Fi hotspot going, so we no longer have to use a wired tether.
  107. We can both use the Internet at the same time.
  108. The catch, of course, is that I can no longer trust my device.
  109. </p>
  110. <p>
  111. It&apos;s worth noting that as installing the nonfree firmwares would compromise the system, I was considering just giving up and installing CyanogenMod.
  112. However, in explaining what firmware was to Vanessa, I realized that this was a bad idea.
  113. By instead installing the firmwares on Replicant, I could keep at least the code running on the main processor free - or so I thought.
  114. However, after installing them, my mobile forgot the <abbr title="Access Point Name">APN</abbr> needed to connect to the Internet! I tried re-entering that information, but the mobile still didn&apos;t have it.
  115. I entered another <abbr title="Access Point Name">APN</abbr>, this one just quick and bogus.
  116. This <abbr title="Access Point Name">APN</abbr> too didn&apos;t show up.
  117. I rebooted the device, and all three showed up.
  118. I tried deleting the bogus <abbr title="Access Point Name">APN</abbr> and one of the identical-yet-working <abbr title="Access Point Name">APN</abbr>s, but neither would accept deletion and rebooting again didn&apos;t help.
  119. I ended up using the <abbr title="Access Point Name">APN</abbr> reset option, which deleted all three, but then the device wouldn&apos;t allow me to add new <abbr title="Access Point Name">APN</abbr>s for several reboots.
  120. I don&apos;t know what the issue is, but somehow, the firmwares are not only acting in their hardware components, but screwing with the main system as well.
  121. I suppose that this is my punishment for using nonfree firmwares.
  122. I can&apos;t wait until we&apos;re in a situation where we no longer need them.
  123. </p>
  124. <p>
  125. The process was taking longer than I&apos;d quoted to my mother, so I explained that I was having difficulties and that the shady software that I&apos;d had to install to make this work was causing problems.
  126. I didn&apos;t explain why I was calling the software shady (I consider all proprietary software to be shady), as my mother would only argue pointlessly about it.
  127. It&apos;s better to just leave them in the dark if they&apos;re going to be a pain about things.
  128. </p>
  129. <p>
  130. I was going to try to install <abbr title="The Onion Router">Tor</abbr> on my mother&apos;s machine, as they&apos;d already agreed to allow me to install a proxy if it got the Internet connection working.
  131. Originally, we couldn&apos;t get <abbr title="Domain Name System">DNS</abbr> to resolve over the tethered connection, so the <abbr title="The Onion Router">Tor</abbr> Browser Bundle had allowed us to have the remote <abbr title="The Onion Router">Tor</abbr> servers resolve the <abbr title="Domain Name System">DNS</abbr> for us.
  132. That is no longer an issue, though my carrier could still yell at me and revoke my account if they find out that we&apos;re tethering.
  133. <abbr title="The Onion Router">Tor</abbr> on the desktop machine wouldn&apos;t fix the fact that the <abbr title="time to live">TTL</abbr> of packets wasn&apos;t at quite the right number, but it would eliminate all cleartext communications through the device, fixing the problem of &quot;incorrect&quot; User-Agent header strings.
  134. Before I could get the software transfered to my mother&apos;s machine though, I realized that it didn&apos;t matter.
  135. In hotspot mode, random strangers might get on the network, and they wouldn&apos;t be using <abbr title="The Onion Router">Tor</abbr>.
  136. If my carrier is going to catch me, there is nothing that I can do about it now.
  137. Putting a password on the Wi-Fi access point is possible, but it&apos;s not a nice thing to do.
  138. Wi-Fi access points should always be open.
  139. </p>
  140. <p>
  141. Cyrus found a video of <a href="http://professorshyguy.com/">Professor Shyguy</a>&apos;s <a href="https://professorshyguy.bandcamp.com/track/science-life-abcs">
  142. Science, Life, &amp; ABCs</a>.
  143. While the video is not free (likely due to an oversight, as the song itself is under <abbr title="Creative Commons Attribution-ShareAlike">CC BY-SA</abbr> 3.0), it contains all of the lyrics! I&apos;ll probably transcribe them here in my journal when I have time, as I&apos;ve been looking for a lyric sheet on that song for quite some time.
  144. Also though, the video explains the word choice in the song a bit.
  145. In the first verse, every word starts with a letter of the alphabet, from a to zee.
  146. In the second verse, it goes backwards.
  147. Every word starts with a letter from zee to a.
  148. The third verse&apos;s rules were a bit too challenging for Professor Shyguy to even work with, so while it mostly follows a pattern of each word representing two letters (the first letter of both the first and second syllable), it has a few exceptions.
  149. I had no idea that that much effort went into that song! Then again, I&apos;ve been unable to make out the lyrics because of how fast Shyguy sings, so I didn&apos;t stand a chance.
  150. This might be the world&apos;s only awesome alphabet song though.
  151. Well, maybe that&apos;s going a bit far, but it&apos;s certainly the only awesome alphabet song that I&apos;ve personally heard.
  152. </p>
  153. <p>
  154. My state-issued <abbr title="identification">ID</abbr> card arrived in the mail today.
  155. It&apos;s a bit ahead of schedule, but considering that this is the second time that they shipped it and it didn&apos;t arrive at all the first time, it&apos;s also way late.
  156. I&apos;m still not amused with the <abbr title="Department of Motor Vehicles">DMV</abbr>, but at least I have mu <abbr title="identification">ID</abbr> card now.
  157. </p>
  158. <p>
  159. Also in the mail, I received a letter meant for <a href="https://opalrwf4mzmlfmag.onion/">wowaname</a>.
  160. My understanding is that someone wrote some hacky code using the domain name <a href="https://afsadgsdcgdcfgefcasfcascfsadf.com./"><code>//afsadgsdcgdcfgefcasfcascfsadf.com.</code></a>, assuming that this domain name would never be registered.
  161. However, of course, that&apos;s a stupid assumption, no matter how ridiculous the domain name is.
  162. Instead, domains under the <code>//invalid.</code> <abbr title="Top Level Domain">TLD</abbr> should be used.
  163. Wowaname decided to show them their folly by registering the domain name that their code assumed not to exist.
  164. I don&apos;t know if this resulted in any issues for them, but wowaname now owns that domain.
  165. The letter that I received today was from a domain registrar, requesting that wowaname transfer the domain to their registration services, as well as register two more ridiculous domain names: <code>//afsadgsdcgdcfgefcasfcascfsadf.net.</code> and <code>//afsadgsdcgdcfgefcasfcascfsadf.org.</code>.
  166. Clearly, this was some sort of automated mailing.
  167. If any human had looked at this domain name, they wouldn&apos;t be asking wowaname to register two more nonsense domains.
  168. As wowaname&apos;s whois privacy provider though, it&apos;s my job to pass that information on to wowaname in case they actually do want it, so I got in touch and let them know.
  169. However, upon hearing the news, wowaname informed me that the company must be using cached data, as they no longer use my name and address for their domain registrations.
  170. They&apos;ve found a new solution that they think will work, without compromising their own privacy.
  171. I wish them luck in their endeavors, and hopefully no one will hassle them like last time.
  172. </p>
  173. <p>
  174. It looks like the quiz today doesn&apos;t count toward my grade.
  175. Having done fairly well on it though has increased my confidence a bit though.
  176. I&apos;ve absorbed at least some of the reading from yesterday.
  177. I&apos;ve asked about the missing discussion assignment in one course and posted on the discussion board in the other.
  178. The discussion questions were unrelated to one another a bit, so my post looks a bit more scattered than it really is:
  179. </p>
  180. <blockquote>
  181. <p>
  182. Unfortunately, I feel that the role of many higher education institutions, especially in the United States, has become to hoard knowledge.
  183. Schools actively seek patents, which are legally-imposed monopolies on vague ideas (Electronic Frontier Foundation, n.d.).
  184. If you invent something new, but it&apos;s too similar to something &quot;protected&quot; by a patent, you can get sued.
  185. Likewise, if you improve upon someone else&apos;s design, you can get sued! With these monopolies in place, competition is snuffed out, and even the patent holders have no real incentive to try to produce their goods more efficiently, as there is no competition to try to beat.
  186. </p>
  187. <p>
  188. In the past, educational institutions were actually about education.
  189. This knowledge-hording doesn&apos;t seem to have been as prevalent.
  190. This may partially be the fault of the students.
  191. Students are choosing to attend more for-profit schools than they used to (Online Universities, 2012), and knowledge-hording can be quite profitable in the short term.
  192. In the long term though, patents are a hindrance to innovation (Electronic Frontier Foundation, n.d.) and only serve to slow us down.
  193. </p>
  194. <p>
  195. I&apos;m not sure what is meant by &quot;student profiles&quot;.
  196. My best guess would be student demographics, so unless someone wants to correct me, I&apos;m going to assume that that&apos;s the case.
  197. It seems that student diversity has grown quite a bit.
  198. The main people getting an education in the past were rich white males, but now educated women outnumber educated men, poor people can be educated too, and while Caucasians still outnumber other races in educational institution (in the United States, anyway), other races are starting to join in as well (Online Universities, 2012).
  199. Students these days are also more likely to be older or disabled than in the past.
  200. </p>
  201. <p>
  202. Ways of learning have greatly changed.
  203. In my parents&apos; day, computers were just barely coming into existence.
  204. They were huge, room-sized machines.
  205. People didn&apos;t keep such things in their houses, and instead, it was mostly the schools that had them.
  206. Research was conducted in libraries using books found via a card catalog system.
  207. I&apos;m not sure if the Internet existed yet, but if so, it was likely still confined to use in places of research in education, so it couldn&apos;t be used from home.
  208. These days, even in brick and mortar schools, students often conduct research online, both on campus and at home.
  209. There&apos;s much less thumbing through physical databases, as we can simply ask our favorite search engines to return results from their enormous databases, which they do almost instantly.
  210. We have access to even more learning materials than before, and those materials are usually easier to find than in the past.
  211. </p>
  212. <p>
  213. If I were to establish my own university, its mission would be to spread the idea that information and knowledge should be available to and usable by everyone.
  214. If we all shared our knowledge and worked together instead of against one another, we&apos;d advance much more quickly as a society.
  215. Not only would there be no need to reinvent old wheels from scratch, previous designs could be improved in both subtle and drastic ways, allowing incremental improvements to benefit everyone.
  216. Schools should be a place of learning; a place where knowledge is set free.
  217. </p>
  218. <p>
  219. References:
  220. </p>
  221. <p>
  222. Electronic Frontier Foundation.
  223. (n.d.).
  224. How Patents Hinder Innovation (Graphic) | Electronic Frontier Foundation.
  225. Retrieved from https://www.eff.org/issues/how-patents-hinder-innovation
  226. </p>
  227. <p>
  228. Electronic Frontier Foundation.
  229. (n.d.).
  230. Patents | Electronic Frontier Foundation.
  231. Retrieved from https://www.eff.org/patent
  232. </p>
  233. <p>
  234. Online Universities.
  235. (2012, September 17).
  236. 20 Amazing Changes in College Demographics - Online Universities.
  237. Retrieved from http://onlineuniversities.com./blog/2012/09/20-amazing-changes-college-demographics/
  238. </p>
  239. </blockquote>
  240. <hr/>
  241. <p>
  242. Copyright © 2016 Alex Yst;
  243. 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>.
  244. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  245. My address is in the source comments near the top of this document.
  246. This license also applies to embedded content such as images.
  247. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  248. </p>
  249. <p>
  250. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  251. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F09-September%2F03.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%2F09-September%2F03.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  252. </p>
  253. </body>
  254. </html>