23.xhtml 5.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  1. <?php
  2. /**
  3. * <https://y.st./>
  4. * Copyright © 2015 Alex Yst <mailto:copyright@y.st>
  5. *
  6. * This program is free software: you can redistribute it and/or modify
  7. * it under the terms of the GNU General Public License as published by
  8. * the Free Software Foundation, either version 3 of the License, or
  9. * (at your option) any later version.
  10. *
  11. * This program is distributed in the hope that it will be useful,
  12. * but WITHOUT ANY WARRANTY; without even the implied warranty of
  13. * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  14. * GNU General Public License for more details.
  15. *
  16. * You should have received a copy of the GNU General Public License
  17. * along with this program. If not, see <https://www.gnu.org./licenses/>.
  18. **/
  19. $xhtml = array(
  20. 'title' => 'Major website work',
  21. 'body' => <<<END
  22. <p>
  23. I was looking at Lo-Fi is Sci-Fi&apos;s music files and found that the artist listed in the meta data is not Lo-Fi is Sci-Fi, but Chris Zabriske! At least, that is the case for three out of four of the albums.
  24. I kind of wonder if this has any significance.
  25. For example, are these files from before Chris uploaded them to Bandcamp? Bandcamp would have modified the meta data and set the artist string to &quot;Lo-Fi is Sci-Fi&quot;.
  26. If that is the case, would these perhaps be the files that had been uploaded? If that is the case, higher-quality copies might not exist.
  27. The $a[FLAC] and Vorbis files might have been converted from the $a[MP3]s, resulting in needless bloat in the case of the $a[FLAC] files and quality loss in the case of the Vorbis files.
  28. Lo-Fi is Sci-Fi was a {$a['lo-fi']} band, so I would not put it past them to record in a lossy file type.
  29. </p>
  30. <p>
  31. I tried to find all links in this weblog containing the text &quot;/domain_research/#&quot; so that I could fix them to point to the correct page, but strangely enough, <code>grep</code> was not returning any results for where they were.
  32. At first, I thought that special characters were being interpreted in my input string or something, but after several experiments, I do not believe that to be the case.
  33. My weblog literally has no matches for that string, so there is nothing for me to fix on that front.
  34. </p>
  35. <p>
  36. Some people on $a[IRC] told me that I should discontinue use of timestamps in $a[PHP] and use <a href="https://secure.php.net/manual/en/book.datetime.php"><code>DateTime</code></a> objects instead.
  37. By the time that they had sugested doing that though, I had already built my new navigation helper function using timestamps.
  38. As my deadline for website cleanup completion is creeping ever closer, I will not fix my function for the time being.
  39. I will continue working on visible parts of the website and work on improving the back end source code later.
  40. </p>
  41. <p>
  42. Next, I moved the navigation bar to a separate file and added support for including an arbitrary number of navigation bars to any given page.
  43. This allows me to do two things.
  44. Most importantly, it allows me to include sub-navigation options for the weblog pages by adding a second navigation bar with forward and back hyperlinks, but it also allows me to remove the English navigation bar that was present on the &quot;choose a language&quot; page.
  45. Fixing all the pages on the site to take advantage of this functionality was a pain though, and until the pages were fixed, the navigation bar had been removed entirely, so it could not exactly wait for another day.
  46. </p>
  47. <p>
  48. It was a good thing that I had added support for arbitrary numbers of navigation bars too, as while I was finishing up coding the secondary navigation bar, I decided that it might be a good idea to add three more navigation bars to weblog entries, though I may or may not implement that.
  49. The three navigation bars would allow jumping to any year, any month in the current year, and any day in the current month.
  50. However, this may just be added bloat.
  51. First of all, these links (aside from the day-in-month links) Would link to lesser navigation pages that are kind of obsolete due to the presence of the main weblog index page.
  52. Second, the main weblog index page is linked to on every page of this site, so it would be cleaner just to keep that as the only weblog navigation link, aside from those that link to the first, last, previous, and next entries within the weblog.
  53. The again, perhaps my mult-navigarion bar idea was not so good.
  54. The navigation bar used by a given page can pull in other navigation bars from its own code as needed.
  55. Then again, having an arbitrary number of navigation bars gives me a clean way to have zero on the language selection page.
  56. </p>
  57. <p>
  58. I tried naming my $a[Tor] relay &quot;authorednansyxluonion&quot;, but $a[Tor] did not like the length of the name and shut down on me, costing me my uptime rating again.
  59. It did accept the name <code>authorednansyxlu</code> though.
  60. It seems that at some point, my relay stopped being considered stable, either because of this down time or the one where I tried relaying an onion to another onion, as I had been told that that was possible.
  61. </p>
  62. <p>
  63. My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
  64. </p>
  65. END
  66. );