19.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185
  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 © 2017 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/2017/06-June/19.xhtml" />
  27. <title>How did the Free Software Foundation find me!? &lt;https://y.st./en/weblog/2017/06-June/19.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/2017/06-June/19.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/2017/06-June/18.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/06-June/20.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>How did the Free Software Foundation find me!?</h1>
  67. <p>Day 00835: Monday, 2017 June 19</p>
  68. </header>
  69. <section id="general">
  70. <h2>General news</h2>
  71. <p>
  72. How did the Free Software Foundation find me!?
  73. I stopped donating to them at least three years ago, have since moved thrice, and have never given them this address.
  74. Now, I receive a letter in the mail begging for another donation.
  75. They don&apos;t seem to have my current name, only my birth name.
  76. I don&apos;t recall ever giving them that either, but whatever; they can have that.
  77. I need to figure out how they&apos;re tracking me though.
  78. </p>
  79. <p>
  80. I forgot to update my whois records to reflect my legal name change.
  81. I&apos;ve done this now today though, so everything should now be in order.
  82. </p>
  83. <p>
  84. I finally finished unpacking my clothing into my closet.
  85. It&apos;s been pretty low on my priority list, but I finally got around to it so I could deal with my sock situation.
  86. I&apos;ve also thrown out all my pairs of underwear that have holes at the waistband and replaced them.
  87. I still have some with small holes elsewhere, but those seem much less likely to quickly continue degrading.
  88. As for my sock situation I mentioned ...
  89. I was considering throwing out all my socks and replacing them with two styles of socks; one black, one white.
  90. It&apos;d be so easy to match socks then, I wouldn&apos;t even need to worry about slightly-mismatched socks ever again.
  91. I decided against that plan by the end of the day though.
  92. It&apos;d be a huge waste, and then I&apos;d be stuck with no variety anyway.
  93. I just need to get a bunch of those sock clips that keep socks sorted even in the wash.
  94. I wonder where I can find those ...
  95. Speaking of socks, I think that&apos;s what I&apos;ll put in that crate my neighbour gave me.
  96. First though, I&apos;ll need to get those clips and sort out any socks with holes in them.
  97. Every sock in the crate will be clipped to a mate, and any without a mate will be thrown out.
  98. I&apos;ve moved several times in the recent past, so there&apos;s a high probability those sock mates are gone for good.
  99. </p>
  100. <p>
  101. I was shown the website of another agendered person with a self-chosen name and a short domain name: <a href="https://s.ai/">Sai</a>.
  102. Unlike me though, they chose &quot;Sai&quot; as their only name, while I chose &quot;Yst&quot; as my surname.
  103. I don&apos;t want to stand out too much, at least not for now.
  104. I identify by the name &quot;Yst&quot; much more then by &quot;Alex&quot; or &quot;Alex Yst&quot;, but the name &quot;Alex&quot; helps me not look like a total nut job.
  105. At least, that&apos;s my intent.
  106. Maybe one day, I&apos;ll change my name again and drop the &quot;Alex&quot; ... but for now, I&apos;m contented with the way things are now.
  107. That said, I&apos;ve got a lot of possible nicknames if I keep &quot;Alex&quot;, some of which are pretty nice, such as &quot;Lexi&quot; and &quot;Xander&quot;.
  108. I also don&apos;t want to totally lose my identity if something horrible happens and I lose my domain somehow.
  109. As it is now, I&apos;d only lose the meaning of half my name, so I&apos;d only have to replace half my name.
  110. If something terrible happens, it could be useful having my name be partially decoupled from my domain name, but at the same time, my domain name is a huge part of who I am and I don&apos;t want my personal name and my domain name to be completely decoupled.
  111. </p>
  112. <p>
  113. I used to be a little off-put when I was given items personalised with my name.
  114. However, I&apos;m starting to realise that was only because I hated my name.
  115. Now, I enjoy seeing things with my name on them, even if they&apos;re not my things.
  116. It&apos;s hard to describe the feeling, but the closest I can come at the moment is that it amuses me slightly.
  117. </p>
  118. <p>
  119. I was thinking about my login name at University of the People today.
  120. Instead of using something memorable, they have us log in using our student numbers.
  121. It seems impersonal, but at the same time, the alternative would probably be to log in using a derivative of our legal names.
  122. Had the system been set up that way, I&apos;d likely be stuck logging in using my birth name, even now.
  123. That&apos;d really suck.
  124. </p>
  125. <p>
  126. One of my coworkers asked me if I&apos;ve ever experienced a &quot;ghost burn&quot; before.
  127. Um ... a what?
  128. It turns out they were referring to the phenomenon of touching the table and being burnt by it despite no obvious heat source.
  129. I can&apos;t seem to find any legitimacy to the term, but it&apos;s caused by setting a hot pan on the table and later removing it, forgetting that it had been set there.
  130. The pan heats the table, then you burn yourself on the table.
  131. I&apos;ve done that loads of times, though I didn&apos;t have a name for it.
  132. &quot;Ghost burn&quot; does sound pretty cool though, so I&apos;m just going to go with that.
  133. </p>
  134. <p>
  135. One of my bosses grabbed the three keys dangling around my neck, looking them over.
  136. They said &quot;apartment key, mail key, ...&quot; and just sort of trailed off, not sure what the third key was.
  137. It&apos;s just the laundry room key, but I told them it was the key to my heart.
  138. They said that they&apos;d get someone to steal it from me, so I replied that I&apos;d change the locks.
  139. They said you can&apos;t change the locks on your heart, so I retorted that I know a good heart surgeon slash lock smith.
  140. They didn&apos;t have much to say on the matter after that, but admitted that those are hard to come by.
  141. </p>
  142. <p>
  143. My coworker whose shift I covered about a week ago was grateful.
  144. They apparently needed the day off to study for a big test, and passed it.
  145. The offered me a haircut for my trouble or a caffeinated beverage, but I passed.
  146. I&apos;m growing my hair out now, and I don&apos;t drink caffeine.
  147. Besides, their gratitude is enough.
  148. Well, that and the money I made just for picking up those extra hours.
  149. </p>
  150. <p>
  151. One of my other coworkers said they&apos;re jealous of my surname.
  152. I told them they could have it too if they want to go to court for it.
  153. They don&apos;t want to pay the court fees though, and I don&apos;t blame them.
  154. More than getting my new name, I wanted to be rid of the birth name name I hated, so it was worth it for me.
  155. It&apos;s not something that&apos;s worth it for everyone.
  156. It turns out my coworker also liked my birth surname too.
  157. I guess that name wasn&apos;t terrible, it was just my given and middle names I didn&apos;t like.
  158. Still, if I was going to pay the court fees, take the time to figure out how to change my name, and go through the stress of changing my name legally for the first time ... I might as well get the most out of it.
  159. </p>
  160. <p>
  161. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  162. </p>
  163. </section>
  164. <hr/>
  165. <p>
  166. Copyright © 2017 Alex Yst;
  167. 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>.
  168. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  169. My address is in the source comments near the top of this document.
  170. This license also applies to embedded content such as images.
  171. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  172. </p>
  173. <p>
  174. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  175. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F06-June%2F19.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%2F2017%2F06-June%2F19.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  176. </p>
  177. </body>
  178. </html>