29.xhtml 9.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156
  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/02-February/29.xhtml" />
  27. <title>Ronsor Public License v2.5 &lt;https://y.st./en/weblog/2016/02-February/29.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/02-February/29.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/02-February/28.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2016/03-March/01.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>Ronsor Public License v2.5</h1>
  67. <p>Day 00359: Monday, 2016 February 29</p>
  68. </header>
  69. <p>
  70. Today is the day I was planning to buy a short domain originally.
  71. Thankfully, I made the purchase back when a short name was actually available.
  72. There are no more short names that are available in <abbr title="Domain Name System">DNS</abbr> spaces that are not run by registries that ask for telephone numbers from their customers.
  73. I thought that it would be fun to have a short domain purchased on a date that only occurs once every four years, but that&apos;s a stupid arbitrary reason to wait to register a domain.
  74. If I had waited, I would not have a short domain at all, or if I did, it wouldn&apos;t be in what i later discovered was my favorite name space.
  75. </p>
  76. <p>
  77. Mother&apos;s friend went home this morning.
  78. </p>
  79. <p>
  80. I&apos;ve been meaning to submit feedback for the local community college&apos;s online orientation, but I hadn&apos;t gotten around to it yet.
  81. Today, I emailed that in, on the final day that feedback would be accepted.
  82. I really wish I wasn&apos;t so far behind.
  83. It would have helped if I didn&apos;t spend yesterday taking a break.
  84. </p>
  85. <p>
  86. <a href="https://ronsor.net/">Ronsor</a> found out that his <code>&lt;form/&gt;</code> that submits to an email address is actually nonstandard, but works in many Web browsers.
  87. I didn&apos;t look into the standard myself, but it is kind of odd that it works.
  88. He also said that he&apos;s releasing his website under the Ronsor Public License v2.5, which is just the short text <q>Do whatever you want except take credit for it.
  89. I&apos;d like you to notify me if you redistribute my content, but it is not mandatory.</q>.
  90. It is now free, so when I finally catch up on everything that I need to get done, I will probably set up a mirror.
  91. I get the feeling that a certain someone pressured him into releasing it freely; it wasn&apos;t me.
  92. He also has his own <a href="https://ronsor.net/form.html">search engine</a>.
  93. It is possible to submit <abbr title="Uniform Resource Identifier">URI</abbr>s for inclusion, but this is done via email.
  94. I can&apos;t help but think that this means that he has to add <abbr title="Uniform Resource Identifier">URI</abbr>s manually.
  95. I try not to beg people to link to me, so I didn&apos;t send in my <abbr title="Uniform Resource Identifier">URI</abbr> for inclusion.
  96. </p>
  97. <p>
  98. Ronsor also tried to get me to start using <a href="https://github.com/cjdelisle/cjdns/">cjdns</a>.
  99. After looking into how it works, I was less than enthusiastic.
  100. Unlike <abbr title="The Onion Router">Tor</abbr>, there is no central authority; you can&apos;t just join the network.
  101. In fact, there is no one network.
  102. Instead, there are several independent networks, and to join any of them, you need to obtain permission from someone already on that network, at which point you connect your node to theirs.
  103. This introduces a number of issues.
  104. First of all, this is a trust-based networking model.
  105. I strongly feel that trust in any individual is a weak link.
  106. It either kills anonymity or involves taking the blame for people that you &quot;trusted&quot;, but didn&apos;t actually know.
  107. Second, when connecting to the network directly through their node, what happens if their node goes down? My assumption is that you lose access to the network until their node goes back up.
  108. There&apos;s no redundancy.
  109. Obviously, I cannot use this for anything serious, but Ronsor is my friend, so I expressed my concerns but tried to set it up anyway.
  110. I figured I could connect through cjdns to Ronsor&apos;s server like he wanted, but not use it for anything else.
  111. There is no package for cjdns in the Debian repositories, so I tried to compile it from source.
  112. I never could get it to successfully compile though.
  113. I just kept running into an error about the Node.js archive that the compilation script tried to download being corrupted:
  114. </p>
  115. <blockquote><pre>==&gt; Downloading http://nodejs.org/dist/v0.10.24/node-v0.10.24-linux-x64.tar.gz with wget...
  116. DONE!
  117. ==&gt; Verifying the checksum of the downloaded archive...
  118. ERROR: The downloaded file is damaged! Aborting</pre></blockquote>
  119. <p>
  120. My system&apos;s package of <a href="nodejs">Node.js</a> was too old, so the compilation script couldn&apos;t use it, and I tried downloading the archive myself and putting it in the source directory, but the compilation script didn&apos;t check for it there.
  121. I strongly suspect that it&apos;s failing to download the archive, not that the archive is actually damaged, but in either case, I&apos;m not sure why it&apos;s happening.
  122. There doesn&apos;t seem to be a reason that the download would fail or would come through damaged.
  123. I ended up giving up on this task for the day.
  124. </p>
  125. <p>
  126. I ended up at a restaurant today, so I ordered the only seemingly-vegan item on the menu.
  127. However, I&apos;ve learned from past experience at this restaurant that while the ingredients that they admit on the menu are included are vegan, the chefs add sour cream and cheese to the actual burrito.
  128. Yuck! So, I specifically asked that the sour cream and cheese be left off.
  129. However, they spaced it and added them anyway.
  130. I really feel bad having to have sent it back.
  131. It seems like such a waste of food.
  132. However, milk products literally give me a headache.
  133. It&apos;s not fair that I should get a headache just because they a) include extra ingredients that they don&apos;t mention on the menu and b) failed to leave them off when I asked that they be left off.
  134. </p>
  135. <hr/>
  136. <p>
  137. Copyright © 2016 Alex Yst;
  138. 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>.
  139. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  140. My address is in the source comments near the top of this document.
  141. This license also applies to embedded content such as images.
  142. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  143. </p>
  144. <p>
  145. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  146. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2016%2F02-February%2F29.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%2F02-February%2F29.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  147. </p>
  148. </body>
  149. </html>