10.xhtml 22 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332
  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/10.xhtml" />
  27. <title>I got into my old email account! &lt;https://y.st./en/weblog/2016/09-September/10.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/10.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/09.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/09-September/11.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 got into my old email account!</h1>
  67. <p>Day 00553: Saturday, 2016 September 10</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>9 days until mobile voice/<abbr title="Short Message Service">SMS</abbr> service with my current carrier ends</li>
  75. <li>39 days until mobile data service with my current carrier ends</li>
  76. <li>36 days until my old domain registrar can no longer counter my charge dispute</li>
  77. </ul>
  78. <p>
  79. I found something really strange today when I went back to examine the mobile device that we&apos;re using as a Wi-Fi hotspot.
  80. One at a time, I disabled the remaining applications that could be disabled, checking the Internet connectivity each time.
  81. Strangely enough, the connection never dropped.
  82. After disabling everything, I even tried rebooting the device to clear any lingering processes.
  83. However, the mobile&apos;s radio still functions normally.
  84. So why couldn&apos;t the device connect to the Internet yesterday? I&apos;m so confused.
  85. On another note, it seems that it&apos;s possible to disable Google Play Services after all, it just can&apos;t be done from the application list.
  86. Instead, one must open the application drawer and try to disable Google Settings from there.
  87. Google Settings seems to be a pseudo-application controlled by Google Play Services, so disabling it disables both.
  88. </p>
  89. <p>
  90. I was going through my oldest Android device, as I apparently didn&apos;t wipe it.
  91. Wanting that data cleared, I thought it best to make sure that I wasn&apos;t deleting anything important.
  92. Strangely, I found the two-factor authentication option from my old domain registrar that I&apos;m having issues with in the Google Authenticator application! The stuff in this device really was old! I decided to check out the <a href="apt:keepassx">KeePassX</a> database on the device to see if it contained my old domain account password (as I could end my issues with them really quickly if I could get that password), but it wasn&apos;t in there.
  93. Indeed, the KeePassX database on the device predates my current domain, but I must not have kept that database up to date.
  94. Sadly, ti the best of my knowledge, nothing in that database is of any use any more.
  95. I&apos;ve downloaded a copy to my laptop just in case though.
  96. However, it isn&apos;t possible for me to recover the shared key from the Google Authenticator application, and that information likewise isn&apos;t present in the database.
  97. I also found a copy of my old offline journal from the time period that my Gluglug machine died on me and I had only my mobile to do any computing on.
  98. This journal has since been integrated with my online journal, so it was fine to delete this offline copy.
  99. </p>
  100. <p>
  101. As I continued through the device, I found that K-9 mail was still attached to two of my past email accounts! Neither of these email accounts had credentials in the password database and one of them has long since been expired.
  102. The other, however, is the email account used with my old domain registrar! I can&apos;t seem to figure out how to get K-9 to cough up the password so that I can make note of it, so if I had cleared this device&apos;s data without the proper preparation, I&apos;d have lost that account forever.
  103. The first step, of course, was to reset the email account&apos;s password, which strangely, involved sending the password reset link to the very inbox that I was supposedly locked out of.
  104. I received the reset link on the mobile, forwarded it to my current email address, and opened it on my laptop.
  105. I reset the password, then reset my two-factor authentication token, putting both into the old password database.
  106. Next, I reset my old domain account password.
  107. However, after resetting it, the domain registrar wouldn&apos;t accept my new password! I don&apos;t know what their problem is.
  108. Now, they&apos;ve locked my old account and claim that I need to perform another password reset to get my account back.
  109. However, they are no longer sending me the password reset emails that they claim to, or at least they somehow aren&apos;t getting through.
  110. </p>
  111. <p>
  112. The readings in <span title="Online Education Strategies">UNIV 1001</span> were mostly just links to resources to help locate sources to cite, information on how to properly read a scholarly paper, and information on plagiarism, all of which I&apos;ve already gone over at my old school, so reading through it again was quick.
  113. There was one page on academic misconduct though, which was useful for coming up with ideas for my discussion responce for the week, which was supposed to mention forms of unethical behavior that could occur at a university, as well as examples of types of plagiarism.
  114. Also of note, the assignment required making a promise to uphold each individual part of University of the People&apos;s code of conduct and and code of academic integrity, as well as how we plan to carry through with that (which should explain the strange section of assertions in the middle of the below post).
  115. </p>
  116. <blockquote>
  117. <p>
  118. One example of plagiarism would be to copy a passage from a source, barely change it at all, and not cite that source (Princeton University, 2016) Slight rewording does not count as paraphrasing, and even if it did, it doesn&apos;t get you out of citing your work.
  119. Another example would be a passage in which each sentence was paraphrased individually, but in which the passage as a whole reads about the same (Princeton University, 2016).
  120. Instead, when using information contained within a full passage of the source work, the passage must be paraphrased in its entirety.
  121. That is to say, not only must you use your own word choice, but also your own sentence structure, sentence order, and paragraph structure (Princeton University, 2016).
  122. Again, this still requires a citation.
  123. If the source material&apos;s original phrasing is too important to be parted with, one can always include the exact wording, but it must be placed withing quotation marks in addition to including the always-mandatory citation.
  124. </p>
  125. <p>
  126. While ideas should never be thought of as property, plagiarism can be detrimental to one&apos;s academics or career.
  127. Even if it wasn&apos;t, proper citation of sources is both polite to the author of your source and provides your own readers with a chance to know where you got your ideas, giving them the same chance of learning from the work that you had.
  128. Plagiarism can destroy your reputation as a student or a professional.
  129. For students, plagiarism can lead to a black mark on their academic record (Turnitin, LLC, n.d.).
  130. Not only could their current school expel them, prospective future schools might not even admit them! For career holders, reputation loss due to plagiarism can result in inability to publish, job loss, and/or an inability to be hired (Turnitin, LLC, n.d.).
  131. Plagiarism isn&apos;t only detrimental for reasons related to loss of reputation and the consequences of said lost reputation though.
  132. Plagiarism is considered a violation of copyright law.
  133. Despite ideas not being property (Lenford, 2006) and monopolies being unethical (HG.org, n.d.), copyright gives authors a legally-imposed monopoly on that which they have said.
  134. Violating one of these monopolies by committing plagiarism can result in legal repercussions, such as jail time or being sued by the holder of that copyright (Turnitin, LLC, n.d.).
  135. </p>
  136. <p>
  137. I will not engage in offensive, harassing, or hostile behavior.
  138. I always try to keep the feelings of others in mind when communicating.
  139. I will always submit only original work created by myself.
  140. I will never attempt to pass another&apos;s work off as my own.
  141. I will also avoid resubmitting work that I&apos;ve previously submitted, unless a particular course requires otherwise (such as a cumulative assignment).
  142. I will not plagiarize.
  143. If I legitimately don&apos;t have a source to cite, I will find sources that back up my ideas and cite them.
  144. This will both help show that I&apos;m not the only one thinking these things and prevent people from thinking that I&apos;ve plagiarized things that I haven&apos;t.
  145. I will not make up data or cite sources that I haven&apos;t even read.
  146. I will not misrepresent my personal situation or attempt to gain special treatment.
  147. I will not aid another student in violating the code of conduct or code of academic integrity laid out by University of the People.
  148. </p>
  149. <p>
  150. The main unethical behavior that I&apos;ve heard about occurring in universities is cheating on tests (University of California Berkley, n.d.).
  151. However, I&apos;ve also heard about people buying essays and handing them in instead of doing the work themselves.
  152. Honestly, it isn&apos;t difficult to find essay-selling services (DuckDuckGo, n.d.).
  153. Another unethical behavior that&apos;s carried out in universities, and one that most people probably don&apos;t think about when they think about unethical behavior at universities, is taking out patents.
  154. When students, professors, or any other people at a university patent ideas, it become illegal for people to use those ideas.
  155. Universities should be about spreading knowledge to all that seek it, not keeping it away from the masses via the patent system.
  156. What&apos;s worse is that many of the discoveries patented by universities are made using federal funds (World Intellectual Property Organization, n.d.).
  157. This means that the public is paying for this research to be done, yet the public is unable to make use of the fruits of the labor that they funded! If you ask me, that is one of the most unethical things that happen withing the walls of a university.
  158. </p>
  159. <p>
  160. References:
  161. </p>
  162. <p>
  163. DuckDuckGo.
  164. (n.d.).
  165. buying essays at DuckDuckGo.
  166. Retrieved September 10, 2016, from https://duckduckgo.com/html/?q=buying+essays
  167. </p>
  168. <p>
  169. HG.org.
  170. (n.d.).
  171. What Are Monopolies and Why Are They Bad? - HG.org.
  172. Retrieved from https://www.hg.org/article.asp?id=31592
  173. </p>
  174. <p>
  175. Lenford, J.
  176. (2006, April 4).
  177. Right to Create: Are Ideas &quot;Property?&quot;.
  178. Retrieved from https://righttocreate.blogspot.nl./2006/04/are-ideas-property.html
  179. </p>
  180. <p>
  181. Princeton University.
  182. (2016, August).
  183. Examples of Plagiarism - Academic Integrity at Princeton University.
  184. Retrieved from https://www.princeton.edu./pr/pub/integrity/pages/plagiarism/
  185. </p>
  186. <p>
  187. Turnitin, LLC.
  188. (n.d.).
  189. 6 Consequences of Plagiarism.
  190. Retrieved from https://www.ithenticate.com./resources/6-consequences-of-plagiarism
  191. </p>
  192. <p>
  193. University of California Berkley.
  194. (n.d.).
  195. Academic Misconduct: Cheating, Plagiarism, and Other Forms | GSI Teaching &amp; Resource Center.
  196. Retrieved from http://gsi.berkeley.edu./gsi-guide-contents/academic-misconduct-intro/
  197. </p>
  198. <p>
  199. World Intellectual Property Organization.
  200. (n.d.).
  201. Academic Patenting: How universities and public research organizations are using their intellectual property to boost research and spur innovative start-ups.
  202. Retrieved from http://www.wipo.int./sme/en/documents/academic_patenting.html
  203. </p>
  204. </blockquote>
  205. <p>
  206. I&apos;m considering writing my own <abbr title="American Psychological Association">APA</abbr> citation generator in JavaScript.
  207. It&apos;s a bit tiresome to keep looking up citation generators to make sure that my citations are formatted correctly, and if I have one on my own website, I&apos;ll know right where to find it without a Web search.
  208. Why use JavaScript and not something server-side that can be used in Web browsers that don&apos;t have JavaScript enabled, you ask? Well, the reasons are twofold.
  209. First, I don&apos;t have permission to use server-side scripting with my current Web host.
  210. I&apos;ll eventually be self-hosted again, or so I hope, but what if I end up having to host with another again in the future? JavaScript should work with any decent Web host simply because to the Web server, it&apos;s a static file to be sent to the client.
  211. It doesn&apos;t even need to be executed.
  212. Secondly, and more importantly, running a citation generator on my server would be a form of <abbr title="Service as a Software Substitute">SaaSS</abbr>.
  213. I don&apos;t want to provide <abbr title="Service as a Software Substitute">SaaSS</abbr>.
  214. With a JavaScript application, you are running all the computations on your own machine.
  215. Furthermore, if you never want to visit my website again, you could even easily download the JavaScript and <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> page to your local machine and run it whenever you like without ever seeing me again.
  216. It&apos;s not my goal to try to bribe you into visiting me if you don&apos;t want to drop by.
  217. </p>
  218. <p>
  219. So when will I be writing this citation generator? Well, it&apos;ll be a while.
  220. I&apos;m currently very busy with school, moving, catching up with my journal writing, and dealing with two troublesome companies that are being a thorn in my side, among other things.
  221. I&apos;ll get to it when I can, assuming that I still have an interest in building it at that time.
  222. Then again, having that citation generator on hand could save me some time rather quickly, so I might decide to build it sooner rather than later.
  223. </p>
  224. <p>
  225. Taking a break from education for a bit, I checked my email and found that I&apos;d received a letter from Patreon yesterday.
  226. For privacy, I&apos;ve redacted the support representative&apos;s name.
  227. </p>
  228. <blockquote>
  229. <p>
  230. [REDACTED], Sep 9, 3:03 PM PDT
  231. </p>
  232. <p>
  233. Hello Yst,
  234. </p>
  235. <p>
  236. Thanks for reaching out about this.
  237. I&apos;ve spoken with our security team to get insight on this.
  238. </p>
  239. <p>
  240. We support Tor and the objectives of its mission.
  241. However, fixing this issue you&apos;ve highlighted will require us to make large infrastructural changes to how Patreon works.
  242. </p>
  243. <p>
  244. While we understand there are a lot of false positives with Cloudflare - it does protect us against malicious traffic.
  245. </p>
  246. <p>
  247. Again, so sorry for your frustrations here.
  248. A lot of us internally use Tor.
  249. We hope to fix this but unfortunately this is a long-term fix and not something we can resolve in the short-term.
  250. </p>
  251. <p>
  252. If you would like us to remove your active pledges so that you aren&apos;t charged in the future, please let me know and I can delete them for you today.
  253. </p>
  254. <p>
  255. Regards,
  256. </p>
  257. <p>
  258. [REDACTED]
  259. </p>
  260. </blockquote>
  261. <p>
  262. They want me to wait a bit, they say.
  263. It&apos;s not a quick and easy fix, they say.
  264. I don&apos;t think that this support representative understands that I&apos;ve been waiting for quite a while.
  265. I&apos;ve been patient, and unless they have an estimated deadline for a fix, I&apos;m done being patient.
  266. Being patient with Pateron has now cost me some musical stylings of <a href="https://marcwithac.bandcamp.com/">Marc With a C</a> and <a href="http://professorshyguy.com/">Professor Shyguy</a>.
  267. These are tracks that I might never get another chance to obtain! Accordingly, I responded as so:
  268. </p>
  269. <blockquote>
  270. <p>
  271. Greetings, [REDACTED]!
  272. </p>
  273. <p>
  274. I&apos;m not sure why a large infrastructure change would be needed, at least right away.
  275. It would be very nice to eventually not be dealing with CloudFlare CAPTCHAs every time that I visit the website, but one exceedingly simple change would fix the login page issue.
  276. Simply moving the JavaScript files needed by the login page to the same domain used by the login page itself would prevent the second, invisible, unsolvable CAPTCHA.
  277. </p>
  278. <p>
  279. You say that it will be a while before this is fixed.
  280. Do you have any estimation of how long this will take? It&apos;s already taken about six months (as I complained about this issue back in March).
  281. According to my records, my initial complaint, which I sent to the wrong department, was on 2016-03-23, while my first complaint to actual Patreon support was on 2016-03-25.
  282. I&apos;ve been locked out of my account for about half a year now, yet nothing has been done yet.
  283. </p>
  284. <p>
  285. It wasn&apos;t until a few days ago that I even started complaining again, so honestly, I wasn&apos;t asking you to resolve it in the short term, but this is getting ridiculous.
  286. How long are you saying that this wait will continue? I feel like by setting this aside and waiting several months for a fix, I allowed this issue to be forgotten.
  287. Should I have written in with a complaint every week to keep the issue from being ignored?
  288. </p>
  289. <p>
  290. If you have some sort of expected wait period, I&apos;ll check back at about the time that you expect to be finished, but otherwise, maybe I should start writing in every week after all.
  291. </p>
  292. <p>
  293. ~ Yst Dawson
  294. </p>
  295. </blockquote>
  296. <p>
  297. Let&apos;s see how they respond to that.
  298. I&apos;ve been more than patient, now it&apos;s time for them to get moving on that fix.
  299. I&apos;m a paying customer and I&apos;ve been locked out of my account for six months!
  300. </p>
  301. <p>
  302. Getting back to my schoolwork, I started doing research about free software business models and worked on constructing my paper.
  303. I likely won&apos;t post any spoilers until I turn the paper in, but I want this paper to be well-researched and convincing, while still meeting the conditions laid out in the assignment.
  304. I&apos;ve put together an initial draft, but it still needs work.
  305. Much to my surprise, finding information on free software business models was much easier than I&apos;d imagined.
  306. </p>
  307. <p>
  308. I had fully intended to get back to <span title="Globalization">POLS 1503</span>&apos;s readings today, but today was a busy day, so that didn&apos;t happen.
  309. I&apos;ll crack down and get to work on that tomorrow.
  310. </p>
  311. <hr/>
  312. <p>
  313. Copyright © 2016 Alex Yst;
  314. 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>.
  315. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  316. My address is in the source comments near the top of this document.
  317. This license also applies to embedded content such as images.
  318. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  319. </p>
  320. <p>
  321. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  322. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F09-September%2F10.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%2F10.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  323. </p>
  324. </body>
  325. </html>