25.xhtml 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192
  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/05-May/25.xhtml" />
  27. <title>Redacting unnecessary information from past journal entries &lt;https://y.st./en/weblog/2017/05-May/25.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/05-May/25.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/05-May/24.xhtml">&lt;Previous</a>
  60. <a rel="next" href="/en/weblog/2017/05-May/26.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>Redacting unnecessary information from past journal entries</h1>
  67. <p>Day 00810: Thursday, 2017 May 25</p>
  68. </header>
  69. <section id="general">
  70. <h2>General news</h2>
  71. <p>
  72. I took a trip to the Bring recycling centre to look for a dolly.
  73. However, they said they hoard dollies when they com in for use in the centre, so they don&apos;t actually sell them.
  74. Darn.
  75. </p>
  76. <p>
  77. The other day, I mentioned an experiment.
  78. I said I&apos;d explain more when the time came if it went well.
  79. This has been cancelled.
  80. The experiment itself is interesting, especially if it ends up working, but my mere participation in it reveals something I don&apos;t want broadcast on the Internet.
  81. In fact, I&apos;m going to need to go back through my past journal entries and redact some stuff for privacy.
  82. Sorry.
  83. There are a couple things I can think of offhand that&apos;ll be hard to redact without losing some events I want kept in.
  84. It&apos;ll be a challenge to preserve the good while taking back the personal details that don&apos;t actually matter.
  85. As time allows, I&apos;ll probably go back and read each journal entry, one by one, and carefully adjust them as needed.
  86. Most specifically, anything that draws attention to my sex will be removed or replaced.
  87. My body has a physical sex, it&apos;s true.
  88. However, this is the Internet and I&apos;m agendered.
  89. If you&apos;ve been following me this far, you probably have a pretty good idea of my physical sex, but if you&apos;re a new reader, my sex has become irrelevant now that I&apos;ve discovered my gender identity.
  90. If you look quickly, my old name (which is a huge hint as to my sex) is in my whois record, but once I have my new Social Security card and <abbr title="Department of Motor Vehicles">DMV</abbr> <abbr title="identification">ID</abbr> card in hand, I&apos;m updating my whois record as well.
  91. I&apos;m only leaving it alone for now in case I need to prove I&apos;m the domain name registrant for some reason.
  92. I shouldn&apos;t have to, but it&apos;s not worth the risk.
  93. If you&apos;re reading this, future me, you&apos;ve finished.
  94. Further entries make no mention or implication of my sex.
  95. </p>
  96. <p>
  97. I received a letter from the court today, addressed to my preferred name.
  98. My first thought was one of slight amusement.
  99. According to the court, my name change isn&apos;t final.
  100. I have to wait until fifteen days have passed since the judgement, then go back to the courthouse and finalise one last piece of paperwork.
  101. It&apos;s nice that they are using my new name, though you can surely understand why I thought they&apos;d use my old one for now.
  102. My amusement quickly turned to panic though.
  103. Why was the court writing to me?
  104. Did they decide to reverse the decision?
  105. Someone doesn&apos;t like my surname.
  106. That&apos;s it, isn&apos;t it?
  107. They&apos;ve forgotten that wye is sometimes a vowel in English, and have declared my name unpronounceable due to lack of vowels.
  108. They&apos;ve decided my name will cause undue confusion.
  109. The panic subsided though, as I realised once again that they addressed the letter to my preferred name.
  110. The court is calling me Alex Yst, so they must not have any particular reason to deny that name.
  111. As it turns out, the letter didn&apos;t have anything useful in it.
  112. Mainly, it was to alert me to the fact a name change judgement had been made on me.
  113. I was there though.
  114. As anticlimactic as it was, I saw it happen.
  115. Furthermore though, it talked about how I might have a lien put on my property until I paid back my debt to my creditor, if I&apos;d borrowed money to pay the court to process the case.
  116. Interesting.
  117. I paid in full from my own funds though.
  118. No creditor was involved, so no lien was placed.
  119. </p>
  120. <p>
  121. I was reading about identity today, and so many sources were bringing up the fact that an identity need not exist on paper.
  122. People use preferred names not matching their government-issued <abbr title="identification">ID</abbr>s all the time.
  123. This name change case shouldn&apos;t&apos;ve even been necessary.
  124. However, with all the identity lockdown stuff that goes on in this country, it&apos;s actually useful to have your preferred name on your <abbr title="identification">ID</abbr>.
  125. It shouldn&apos;t be.
  126. I certainly don&apos;t regret going to court for this.
  127. I just regret living in a world where going to court for this actually accomplished anything.
  128. Simply telling everyone I&apos;m Alex Yst should&apos;ve been enough.
  129. Identity is fluid, a single name doesn&apos;t always represent someone forever.
  130. For me, I doubt I&apos;ll need to switch names again.
  131. Unless something terrible happens and I lose <code>//y.st.</code>, &quot;Yst&quot; will always be my preferred surname.
  132. As long as some businesses default to using a middle initial in names instead of a full middle name or no middle name, I don&apos;t want a middle name at all.
  133. And as long as I reject the idiotic gender roles society imposes on us, I&apos;ll want a nice agendered name.
  134. &quot;Alex&quot; isn&apos;t the only option, but it fits the bill and sounds nice with my surname.
  135. But some other people&apos;s identities are fluid in ways different from my own identity&apos;s fluidity, ways that require a different name for a different occasion.
  136. </p>
  137. <p>
  138. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  139. </p>
  140. </section>
  141. <section id="mental">
  142. <h2>Mental health watch</h2>
  143. <p>
  144. I&apos;ve come to the conclusion that I&apos;m fine.
  145. Perfectly fine.
  146. I&apos;ve been panicking over nothing.
  147. These is absolutely nothing in my behaviours, the way I prefer to live, or in my personality that suggests I&apos;m undergoing a change or that I&apos;ll ever engage in romantic or sexual pairing.
  148. Whatever strange hormone flairs I&apos;m having right now are unnerving, to say the least, but it&apos;s unlikely they&apos;ll alter my core personality.
  149. I just need to relax.
  150. </p>
  151. </section>
  152. <section id="university">
  153. <h2>University life</h2>
  154. <p>
  155. Like last week, the <span title="Greek and Roman Civilization">HIST 1421</span> reading assignment this week is a bit unclear and without direct links to what we should read.
  156. If I understand correctly, the reading assignment is as follows:
  157. </p>
  158. <ul>
  159. <li>
  160. <a href="https://the-romans.co.uk/economy.htm">The Classics Pages: Antony Kamm&apos;s &apos;The Romans&apos;: 5.1 The economy and money</a>
  161. </li>
  162. <li>
  163. <a href="https://the-romans.co.uk/work.htm">The Classics Pages: Antony Kamm&apos;s &apos;The Romans&apos;: 5.2 Work</a>
  164. </li>
  165. </ul>
  166. <p>
  167. I finished the reading, but this reading assignment doesn&apos;t match with what is being asked of us in the written assignments for the week.
  168. I&apos;ll do some further reading tomorrow and see what I come up with.
  169. </p>
  170. </section>
  171. <hr/>
  172. <p>
  173. Copyright © 2017 Alex Yst;
  174. 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>.
  175. If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
  176. My address is in the source comments near the top of this document.
  177. This license also applies to embedded content such as images.
  178. For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
  179. </p>
  180. <p>
  181. <abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
  182. This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F05-May%2F25.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%2F05-May%2F25.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
  183. </p>
  184. </body>
  185. </html>