26.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  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/07-July/26.xhtml" />
  27. <title>Tutanota premium accounts are now available &lt;https://y.st./en/weblog/2015/07-July/26.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/07-July/26.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/07-July/25.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2015/07-July/27.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>Tutanota premium accounts are now available</h1>
  67. <p>Day 00141: Sunday, 2015 July 26</p>
  68. </header>
  69. <p>
  70. I found information on how to set um my keyboard to <a href="http://en.esperanto.org.nz/how-to-learn-esperanto/how-to-type-esperanto-characters/linux">type Esperanto Characters</a>.
  71. The good news is that it works and I can now type all letter characters used in Esperanto with ease.
  72. The bad news is that the change borked my quote and double quote key.
  73. The key with a Windows logo had previously been useless, but it now acts as a modifier key.
  74. Holding it, I can type whichever Esperanto character I needed an accent on, and it will apply the correct one.
  75. However, the single quote key now also acts as a modifier, altering the next key I hit to have a standard accent, one not used in Esperanto.
  76. If I remember to hold the Windows key when I press the single quote key, I can override this.
  77. But now comes the stupid part.
  78. The double quote (shift + single quote) is taken up as well and need the Windows key to be pressed to override it, but pressing this three-key combination does not always work.
  79. About half the time, no character is generated when I try to type a double quote.
  80. I can seem to find a pattern to when it works and not either.
  81. It&apos;s also worth noting that the &quot;¢&quot; and &quot;€&quot; symbols are also now accessible by combining the Windows key, &quot;e&quot; key, and for the &quot;¢&quot; symbol, the shift key.
  82. </p>
  83. <p>
  84. In case the page at the <abbr title="Uniform Resource Identifier">URI</abbr> linked to above goes dead, the way to activate this functionality is to first run <code>setxkbmap -layout &quot;us&quot; -variant &quot;alt-intl&quot; -option &quot;lv3:lwin_switch,esperanto:qwerty&quot;</code> on the command line to make it take effect right away, then add it to one of the files that is run upon every log in, such as <code>~/.bash_aliases</code>, to make it persist after restarting or logging out.
  85. </p>
  86. <p>
  87. I worked on Minetyst a little and got a few of the images made.
  88. The most notable was the clay image.
  89. I was trying to draw desert sand but it came out horribly.
  90. The pattern was not sand-like at all, but it was almost perfect for clay.
  91. I modified the pattern a little, and messed with the colors a lot, and made the image pretty usable for use in clay nodes.
  92. </p>
  93. <p>
  94. Before I had heard about Esperanto, I had wanted to learn Lojban.
  95. I don know what made Esperanto seem more appealing, but it made me switch plans.
  96. However, Lojban is still out there and I&apos;m not really sure which is a better language.
  97. I tried to find comparisons of the two languages, but nothing about the things I care about such as lack of ambiguity.
  98. It seems both have a rigid structure that makes them very well built, syntacticly-speaking, but that&apos;s about all I could find.
  99. Learning a language is of no use though if there is no one else that uses that language though.
  100. Esperanto is a common enough language that it has it&apos;s own two-letter <abbr title="International Organisation for Standardisation">ISO</abbr> 639‑1 language code, a status reserved for &quot;major&quot; languages.
  101. I decided that I would check on Lojban&apos;s status, and if it had an <abbr title="International Organisation for Standardisation">ISO</abbr> 639‑1 language code, I would continue trying to figure out which to learn first, then probably move on to the other.
  102. However, if Lojban had not been assigned such a code, I would write it off for the time being.
  103. I only have so much time and I need to put my efforts to where they will actually be useful.
  104. As it turns out, Lojban is not common enough for such a code, so I won be learning it for now.
  105. That&apos;s not to say that Lojban isn&apos;t to say Lojban isn&apos;t a great language, only that it hasn&apos;t picked up as much momentum as Esperanto yet.
  106. </p>
  107. <p>
  108. I decided to log into my Tutanota account today to delete it.
  109. I never use that email account as it&apos;s such a pain to use.
  110. Tutanota&apos;s end-to-end encryption requires special software to use, but the software has a number of limitations.
  111. First, the only option for a desktop client is Outlook Express with the Tutanota plugin.
  112. Really? The only email client that can be used is proprietary? As for the Android application, its source code is available, but the application is available only in three places: Google Play, the Amazon Store, and a webpage blocked by CloudFlare.
  113. Google and Amazon refuse to allow you to download applications except through their own proprietary software, so you can&apos;t download the Tutanota application from them without using proprietary software.
  114. As for the webpage, it&apos;s blocked by CloudFlare, so <abbr title="The Onion Router">Tor</abbr> users such as myself are stuck.
  115. There is simply no way to win.
  116. The final option is to use the Web interface, but that means having your Web browser constantly open to that page, which is a pain.
  117. Tutanota mail is not a feasible option in its current state.
  118. </p>
  119. <p>
  120. The plan was to log in to the account and delete it using the provided form, which asks for feedback as to why you are deleting it.
  121. I would explain the situation, then come back once things at Tutanota are better fleshed out.
  122. However, it seems that two weeks ago, they sent me an email that I missed due to checking mail being a pain.
  123. It said that premium accounts are now available, and for a limited time, if you open one, you get five gigabytes of extra storage space.
  124. I wrote back and asked if the offer was still good and if catch-all addresses are offered if you bring your own domain.
  125. If the offer is still valid and catch-all addresses are offered, I&apos;ll get a premium account now while the extra storage space is being offered and wait out the issues while they get ironed out.
  126. If catch-all addresses are not implemented, Tutanota won&apos;t meet my needs and I don&apos;t need an account at my domain.
  127. The mail host used for my domain must use a catch-all address.
  128. In this case, I&apos;ll still delete my account and wait for the accessibility issues to be worked out.
  129. Once ready, I&apos;ll use a gratis Tutanota account for my secondary email address that needs to be disconnected from my domain.
  130. Finally, if the offer is no longer valid, there is no longer any rush to set up the account.
  131. I might as well not pay for the time I won&apos;t be able to fully use it, and I&apos;ll delete the account and wait for the accessibility issues to be fixed before getting the premium account.
  132. </p>
  133. <p>
  134. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  135. </p>
  136. <hr/>
  137. <p>
  138. Copyright © 2015 Alex Yst;
  139. 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>.
  140. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  141. My address is in the source comments near the top of this document.
  142. This license also applies to embedded content such as images.
  143. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  144. </p>
  145. <p>
  146. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  147. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2015%2F07-July%2F26.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%2F07-July%2F26.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  148. </p>
  149. </body>
  150. </html>