<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>@octylFractal</title><description>The internet home of Octavia Togami / @octylFractal</description><link>https://octyl.net/</link><item><title>Tiny Astronomical Changes</title><link>https://octyl.net/2026/06/14/tiny-astronomical-changes/</link><guid isPermaLink="true">https://octyl.net/2026/06/14/tiny-astronomical-changes/</guid><pubDate>Sun, 14 Jun 2026 03:26:51 GMT</pubDate><content:encoded>&lt;p&gt;&lt;a href=&quot;/2026/05/29/pretty-patterns-2/&quot;&gt;As foretold&lt;/a&gt;, I have moved my site to use a new static site generator. After looking at a lot of
different options, and seriously considering writing my own, I ended up using &lt;a href=&quot;https://astro.build/&quot;&gt;Astro&lt;/a&gt;. It’s open-source, has good IDE
support for &lt;code&gt;.astro&lt;/code&gt; files (I really wish IntelliJ’s MDX support was better so I could use that…), and allows me to
use JavaScript for the more dynamically generated content on my site. The idea of shipping certain islands of
interactivity without needing to require it for the whole site is also really interesting, and I might take advantage of
that in the future.&lt;/p&gt;
&lt;p&gt;The bulk of the changes are backend-only, the site remains mostly the same. I did make some tiny adjustments that I had
been holding off on, because they were pretty tied to how Jekyll worked. Hopefully nothing you will notice :)&lt;/p&gt;</content:encoded></item><item><title>Switching Fonts Again</title><link>https://octyl.net/2026/06/07/switching-fonts-again/</link><guid isPermaLink="true">https://octyl.net/2026/06/07/switching-fonts-again/</guid><pubDate>Sun, 07 Jun 2026 08:42:47 GMT</pubDate><content:encoded>&lt;p&gt;While proof-reading the last post, I realized I didn’t really like the serif font I was using, “Libre Baskerville”.
When I originally chose it, there were few lengthy posts and I didn’t have a good comparison to make. Now that I have
another long post, I evaluated many fonts in my current poor reading conditions, and settled on “Noto Serif”. It really
feels like a generic pick to me, but I found it difficult to pick out another readable serif font at 16px. Lots of
other good candidates failed because I didn’t like a particular way a word would be rendered by it. Noto won out as the
best overall.&lt;/p&gt;
&lt;p&gt;But to be honest… I’ll probably change it again, when I have more time.&lt;/p&gt;</content:encoded></item><item><title>The End of the GitHub Era</title><link>https://octyl.net/2026/06/07/the-end-of-the-github-era/</link><guid isPermaLink="true">https://octyl.net/2026/06/07/the-end-of-the-github-era/</guid><pubDate>Sun, 07 Jun 2026 07:47:23 GMT</pubDate><content:encoded>&lt;p&gt;Well, I return sooner than expected (see last post). GitHub has finally placed the final straw on my metaphorical
camel, and broken its back, by sending me an email about GitHub Copilot CLI… with no unsubscribe link.&lt;/p&gt;
&lt;p&gt;I did not sign up for marketing emails and actively work to keep them out of my inbox by whatever means necessary.
This unsolicited notice has finally convinced me that GitHub as it currently stands is no longer somewhere that I wish
to promote by continuing to push my code to its platform. This is a relatively minor event overall, but I had already
been considering dropping GitHub as I find the site more and more non-functional for my day-to-day usage. I haven’t
been affected much by the downtime yet, but I am continually affected by their code viewer introducing weird jank by its
nature of being &lt;code&gt;&amp;#x3C;canvas&gt;&lt;/code&gt; based now, resulting in misaligned text, copying issues, problems jumping to lines, and more.&lt;/p&gt;
&lt;p&gt;It worries me that they had a search downtime so severe that issues and PRs could not be properly searched for multiple
days. The &lt;a href=&quot;https://en.wikipedia.org/wiki/Single-page_application&quot;&gt;SPA&lt;/a&gt; nature of the site continually breaks my back button and history, and recently it has started failing to
load new pages completely, requiring me to manually refresh the page to force it to actually make a normal web request
and get the full page state. This entirely defeats the point of even having an SPA in the first place.&lt;/p&gt;
&lt;p&gt;I haven’t kept a good record of everything that annoys me about GitHub, and I’m sure there’s more I don’t remember.
But hopefully, this shows that the email I got is just the latest in a long-standing decline in quality at GitHub.&lt;/p&gt;
&lt;h3 id=&quot;where-im-going-next&quot;&gt;Where I’m going next&lt;/h3&gt;
&lt;p&gt;I need to balance a few different concerns when selecting where to host my code. In approximate order of importance:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;code&gt;Transferrable&lt;/code&gt;. I should be able to export my data, for the inevitable future migration.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Open Source&lt;/code&gt;. The project should be open source, so it’s at least possible for me to use the exported data in the
original form.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Social&lt;/code&gt;. Others should be able to easily file issues and make PRs, with minimal friction.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Sustainable&lt;/code&gt;. The company or person hosting it must have a sound plan for keeping financial incentives away from the
project, so it is less likely to be cost-cut to death. In practice, this means it should be a non-profit corporation or
public service; or self-hosted.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;Vibe&lt;/code&gt;. I should like the vibe of people working on and owning it. This is pretty subjective of course.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;With these in mind, here are the options I considered.&lt;/p&gt;
&lt;h4 id=&quot;tangled&quot;&gt;Tangled&lt;/h4&gt;
&lt;p&gt;&lt;a href=&quot;https://tangled.org/&quot;&gt;Tangled&lt;/a&gt; is something I recalled going around BlueSky last year. They are &lt;code&gt;Open Source&lt;/code&gt;, and their AT Protocol base
means that it can be considered &lt;code&gt;Transferrable&lt;/code&gt; and &lt;code&gt;Social&lt;/code&gt; as well. However, they fail my &lt;code&gt;Vibe&lt;/code&gt; check by having some
of their primary discussion platforms be Discord and X. I’d like to reduce my reliance on these platforms due to their
closed nature (both proprietary and having &lt;a href=&quot;https://en.wiktionary.org/wiki/login_wall&quot;&gt;login walls&lt;/a&gt;). They also fail at being &lt;code&gt;Sustainable&lt;/code&gt;, as they are &lt;a href=&quot;https://blog.tangled.org/seed/&quot;&gt;funded by
VC money&lt;/a&gt;. At some point, those investors will want a return, and I’ve seen what happens then many times
over. So I discarded Tangled as an option.&lt;/p&gt;
&lt;h4 id=&quot;radicle&quot;&gt;Radicle&lt;/h4&gt;
&lt;p&gt;I’d also heard about &lt;a href=&quot;https://radicle.dev/&quot;&gt;Radicle&lt;/a&gt; a little bit. They are again &lt;code&gt;Open Source&lt;/code&gt; and, due to being decentralized entirely, also
&lt;code&gt;Transferrable&lt;/code&gt;. However, the current state of it is that all operations must be performed by CLI or their Desktop app.
This severely limits how &lt;code&gt;Social&lt;/code&gt; it is, as it’s much more involved for someone to even file an issue on my project.
Their &lt;code&gt;Vibe&lt;/code&gt; is a little bit uncertain for me. In terms of communication, they do still have a presence on X, but the
primary development communication occurs on Zulip, which I like. Their primary funding comes from Radworks, which
appears to be some kind of variant on a &lt;a href=&quot;https://en.wikipedia.org/wiki/Decentralized_autonomous_organization&quot;&gt;DAO&lt;/a&gt;. I’ve heard some good arguments against these, essentially that because it
still has to interact with the traditional expectations of other entities, someone will always be holding the power to
make changes without going through the formal on-chain process, making it not much different from a normal organization
but with a lot more overhead. For example, someone has to own the domain and DNS for it, and whoever has access to that
can make whatever changes they want.&lt;/p&gt;
&lt;p&gt;However, the Radicle devs seem to be &lt;a href=&quot;https://radicle.zulipchat.com/#narrow/channel/392584-Feedback/topic/Lobste.2Ers/near/564200355&quot;&gt;considering moving away from this&lt;/a&gt; as their primary funding. I’m
also still not sure myself if I consider it a problem. Radworks seems to be somewhat aware that they are not entirely
bound to the blockchain, and explicitly have some off-chain mechanisms. And Radicle itself is actually owned by the
non-profit &lt;a href=&quot;https://betterinternet.foundation/&quot;&gt;Better Internet Foundation&lt;/a&gt;. Overall, I’m not sure how I feel about them being &lt;code&gt;Sustainable&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;If Radicle had a usable web interface and some more time to build trust that Radworks is sustainable, I would likely
pick them. I really like the ideas, but it seems they still need some more time to cook.&lt;/p&gt;
&lt;h4 id=&quot;self-hosting&quot;&gt;Self-hosting&lt;/h4&gt;
&lt;p&gt;Self-hosting, to me, is the ultimate &lt;code&gt;Transferrable&lt;/code&gt; and &lt;code&gt;Sustainable&lt;/code&gt; option, as I would only shut down the service if
I did not need it any more. Due to my preferences, anything I picked would obviously also be &lt;code&gt;Open Source&lt;/code&gt;, and
obviously I like my own &lt;code&gt;Vibe&lt;/code&gt;. But the one way that this currently fails is &lt;code&gt;Social&lt;/code&gt;. The established options that are
self-hostable (Radicle again, Forgejo, GitLab, etc.) all would still require users to either use weird interfaces or
to sign up for an account on my personal instance. I consider that unacceptable friction. I would really like it if
there was an option for federated or decentralized &lt;a href=&quot;https://en.wikipedia.org/wiki/Forge_(software)&quot;&gt;forges&lt;/a&gt;, but it’s just not there yet as far as I can tell.&lt;/p&gt;
&lt;p&gt;I unfortunately must discard this option.&lt;/p&gt;
&lt;h4 id=&quot;gitlab&quot;&gt;GitLab&lt;/h4&gt;
&lt;p&gt;I did not spend much time looking at GitLab as I’ve previously tried using it, and found that I really did not like how
the website felt. I just don’t like the &lt;code&gt;Vibe&lt;/code&gt;, and for me, that was enough to barely consider it.&lt;/p&gt;
&lt;h4 id=&quot;codeberg&quot;&gt;Codeberg&lt;/h4&gt;
&lt;p&gt;We now come to &lt;a href=&quot;https://codeberg.org/&quot;&gt;Codeberg&lt;/a&gt;. Based on the &lt;code&gt;Open Source&lt;/code&gt; &lt;a href=&quot;https://forgejo.org/&quot;&gt;Forgejo&lt;/a&gt;, they even advertise on their docs that you can migrate
from their instance to another Forgejo instance using the same migration tools they offer, easily making it
&lt;code&gt;Transferrable&lt;/code&gt; as well. I’ve seen a lot of projects moving here, and they already have a sizable userbase, making it a
pretty good &lt;code&gt;Social&lt;/code&gt; contender. As a non-profit with a decent donation record, they look pretty &lt;code&gt;Sustainable&lt;/code&gt;. And
finally, I do like their &lt;code&gt;Vibe&lt;/code&gt;. They even kept the &lt;a href=&quot;https://anubis.techaro.lol/&quot;&gt;Anubis&lt;/a&gt; mascot on!&lt;/p&gt;
&lt;p&gt;So clearly, I’m going to start moving over to Codeberg. My account is at the typical &lt;a href=&quot;https://codeberg.org/octylFractal&quot;&gt;octylFractal&lt;/a&gt;.
I won’t be moving over existing repositories en-masse, but whenever I update one, I will be copying it to Codeberg
first and archiving the GitHub original with a notice. I’ve started with this very site, which used to live at
&lt;a href=&quot;https://github.com/octylFractal/octylFractal.github.io&quot;&gt;https://github.com/octylFractal/octylFractal.github.io&lt;/a&gt;, and now lives at
&lt;a href=&quot;https://codeberg.org/octylFractal/octylsite&quot;&gt;https://codeberg.org/octylFractal/octylsite&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Let’s keep fighting the &lt;a href=&quot;https://en.wikipedia.org/wiki/Enshittification&quot;&gt;enshittification&lt;/a&gt; of the online web as best we can; by making conscious choices to use
better things where we can.&lt;/p&gt;</content:encoded></item><item><title>Pretty Patterns 2</title><link>https://octyl.net/2026/05/29/pretty-patterns-2/</link><guid isPermaLink="true">https://octyl.net/2026/05/29/pretty-patterns-2/</guid><pubDate>Fri, 29 May 2026 06:11:22 GMT</pubDate><content:encoded>&lt;p&gt;&lt;em&gt;If pretty patterns are so good, why didn’t they make pretty patterns 2?&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Well, I have now. Instead of loading a prebaked PNG and tiling it, the pattern is now generated procedurally wherever
I need it, during the static site generation. It bakes an SVG that is then repeated to fill the sidebar background.
The advantage of this is a lot smaller file size, and since it can be trivially inlined, it saves an extra request
and no longer flickers so badly when navigating. It also fits the vibe I was going for a lot more.&lt;/p&gt;
&lt;p&gt;The implementation does make me think about retiring Jekyll though. I really would like to be able to write with,
y’know, actual functions ‘n’ stuff. Jekyll is also getting quite slow with how complex my Liquid usage is.
I would probably switch to a custom system that uses JSX/TypeScript and emits a static site from that, with
extension points. Why that over Java? Because JSX is well-integrated for writing HTML.&lt;/p&gt;
&lt;p&gt;That’s all for now. See you in another two years :)&lt;/p&gt;</content:encoded></item><item><title>PipeWire has built-in VBAN support!</title><link>https://octyl.net/2024/11/05/pipewire-built-in-vban/</link><guid isPermaLink="true">https://octyl.net/2024/11/05/pipewire-built-in-vban/</guid><pubDate>Tue, 05 Nov 2024 23:30:19 GMT</pubDate><content:encoded>&lt;p&gt;Updated Feb 02 2025.&lt;/p&gt;
&lt;h3 id=&quot;rip-audio-bicycle-2022-2024&quot;&gt;RIP &lt;code&gt;audio-bicycle&lt;/code&gt;, 2022-2024&lt;/h3&gt;
&lt;p&gt;I recently went to make some changes to my old project, audio-bicycle, but I found that it was no longer necessary!
PipeWire now has built-in VBAN support (&lt;a href=&quot;https://docs.pipewire.org/page_module_vban_send.html&quot;&gt;send&lt;/a&gt;, &lt;a href=&quot;https://docs.pipewire.org/page_module_vban_recv.html&quot;&gt;recv&lt;/a&gt;), and this works well enough for me that I no longer need
audio-bicycle. I’m kind of sad to see it go, but its name will live on in the configuration of my new setup.&lt;/p&gt;
&lt;p&gt;However, there were a few gotchas I encountered while setting this up. For context, my configuration is designed to
take outgoing audio from my Linux desktop running PipeWire, and send it to my Windows machine running VoiceMeeter to
be output on the speakers. The Windows machine also sends microphone audio back to the Linux machine, for use in voice
calls. I like to listen to music while I work, so I need a completely clean signal with no noise.&lt;/p&gt;
&lt;h3 id=&quot;audio-rate-and-format&quot;&gt;Audio Rate and Format&lt;/h3&gt;
&lt;p&gt;The defaults for the VBAN modules are not very good, picking 44100 Hz rate and S16LE format. This requires remixing
from my 48000 Hz S24LE audio, which introduces some artifacts. I recommend checking what you’re using with &lt;code&gt;pw-top&lt;/code&gt;
and setting the VBAN modules to match, or at least transferring S24LE audio. Here’s the settings I used on each module:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;audio.format = &quot;S24LE&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;audio.rate = 48000&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;del&gt;You should also make sure that VoiceMeeter is configured to use the same settings on its sending side, as PipeWire will
not check or do any conversion for you :(.&lt;/del&gt; [2025-17-02] I believe this is no longer the case as of
&lt;a href=&quot;https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1a5514e5cf406284f3f7e9466ac630eb64004af3&quot;&gt;this commit&lt;/a&gt;, but
I don’t think it’s released anywhere yet.&lt;/p&gt;
&lt;h3 id=&quot;latency&quot;&gt;Latency&lt;/h3&gt;
&lt;p&gt;PipeWire’s VBAN modules also pick very high latency numbers, presumably because they expect to be used over the
internet. I adjusted these down for the very low latency I have on my local network:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;# For send and recv, keeps a smaller buffer.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;sess.latency.msec = 2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;# For send only, minimizes the time between packets&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;sess.min-ptime = 1&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;miscellaneous&quot;&gt;Miscellaneous&lt;/h3&gt;
&lt;p&gt;&lt;del&gt;I needed to increase the quantum in order to prevent certain applications from not having enough buffer, like &lt;code&gt;mpv&lt;/code&gt;.
Putting &lt;code&gt;node.force-quantum = 512&lt;/code&gt; on each module’s stream seemed to be enough, but this is likely
environment-dependent.&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;&lt;del&gt;Finally, I had to set &lt;code&gt;node.always-process = true&lt;/code&gt; on both modules to ensure that the audio was always being sent and
received. This is because the modules will stop processing audio if there is no stream connected otherwise, and this
can cause noise when starting a new stream. This made noticeable pops when starting music or skipping tracks, which
was very annoying. I assume the same could occur with the microphone, but I haven’t tested it. The cost of ~3% of one
CPU core is worth it to me to avoid this noise.&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;[2025-17-02] None of this is necessary now, due to many improvements in Pipewire. It’s working fine on 1.2.7.&lt;/p&gt;
&lt;p&gt;For reference, here’s my final configuration file &lt;code&gt;01-audio-bicycle.conf&lt;/code&gt;:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;context.modules = [&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        name = libpipewire-module-vban-recv&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        args = {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            source.ip = 10.190.229.127&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            sess.latency.msec = 10&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            sess.name = &quot;audio-bicycle&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            audio.format = &quot;S24LE&quot; # [2025-17-02] This and `audio.rate` might not be necessary soon.&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            audio.rate = 48000&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            stream.props = {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                media.class = &quot;Audio/Source&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                node.name = &quot;VBAN Mic&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                node.description = &quot;VBAN Mic&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    {&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        name = libpipewire-module-vban-send&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        args = { &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            source.ip = 10.190.229.127&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            destination.ip = 10.190.229.105&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            sess.min-ptime = 1&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            sess.latency.msec = 2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            sess.name = &quot;audio-bicycle&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            audio.format = &quot;S24LE&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            audio.rate = 48000&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            stream.props = { &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                media.class = &quot;Audio/Sink&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                node.name = &quot;VBAN Speakers&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;                node.description = &quot;VBAN Speakers&quot;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;            }   &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;        }   &lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    }&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;]&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;</content:encoded></item><item><title>Minor Site Design Adjustments</title><link>https://octyl.net/2024/11/05/site-design-adjustments/</link><guid isPermaLink="true">https://octyl.net/2024/11/05/site-design-adjustments/</guid><pubDate>Tue, 05 Nov 2024 23:20:20 GMT</pubDate><content:encoded>&lt;p&gt;I’ve removed the monospace formatting of some parts of the site to make it easier to read, notably the navbar and post
text. I noticed while writing the next blog post that the monospace font was making the text difficult to read,
but I still prefer to have the other pages in monospace as I think it looks nice. I also changed the font from Lato
to Libre Baskerville which looks better at 16px.&lt;/p&gt;
&lt;p&gt;There was also a ton of adjustments to improve mobile behavior.&lt;/p&gt;</content:encoded></item><item><title>Pretty Patterns and Soft Shadows</title><link>https://octyl.net/2024/07/21/pretty-patterns-and-soft-shadows/</link><guid isPermaLink="true">https://octyl.net/2024/07/21/pretty-patterns-and-soft-shadows/</guid><pubDate>Sun, 21 Jul 2024 03:42:08 GMT</pubDate><content:encoded>&lt;p&gt;On a whim, I felt like adding additional texture to the left and right sides of the site where no main content is
present. I originally was going to integrate something from &lt;a href=&quot;https://css-doodle.com/&quot;&gt;&amp;#x3C;css-doodle/&gt;&lt;/a&gt; but I
could not figure out how to make the patterns I wanted statically, as I don’t want to require JavaScript to view the
site as intended (&lt;del&gt;I’m aware that on small screens, it is required to use the navbar. If you have suggestions for this,
please let me know!&lt;/del&gt; Edit Aug 08 2024: I’ve done a hacky fix for this). So instead, I searched around and found this
&lt;a href=&quot;https://bg.siteorigin.com/&quot;&gt;“Background Image Generator”&lt;/a&gt; and selected a pattern that I thought looked nice.&lt;/p&gt;
&lt;p&gt;In order to ensure it meshes with the existing page, the new patterns have shadows around the edges. I also added a
shadow around the navbar and footer to make them stand above the content. I’m quite happy with the results, and I hope
you enjoy them as well!&lt;/p&gt;</content:encoded></item><item><title>Projects Page</title><link>https://octyl.net/2024/07/16/projects-page/</link><guid isPermaLink="true">https://octyl.net/2024/07/16/projects-page/</guid><pubDate>Tue, 16 Jul 2024 02:52:17 GMT</pubDate><content:encoded>&lt;p&gt;I’ve added a new &lt;a href=&quot;/projects&quot;&gt;Projects&lt;/a&gt; page to the site. It showcases the projects I find the most valuable or
interesting, and that actually work well. I hope you find them useful!&lt;/p&gt;</content:encoded></item><item><title>Yet Another Site Refresh</title><link>https://octyl.net/2024/02/16/yet-another-site-refresh/</link><guid isPermaLink="true">https://octyl.net/2024/02/16/yet-another-site-refresh/</guid><pubDate>Fri, 16 Feb 2024 04:47:30 GMT</pubDate><content:encoded>&lt;p&gt;The content on this site has again been updated to reflect an approximation of my current self.
Mostly this is an update to Bootstrap (5.3.2) and a move away from any third-party sites, to entirely self-hosted
content. I’ve disliked relying on them due to the potential for them to disappear, and the fact that they can
affect my uptime (though this site is still primarily hosted on GitHub Pages, so it’s not entirely self-hosted).&lt;/p&gt;</content:encoded></item><item><title>Site Refresh</title><link>https://octyl.net/2022/12/10/site-refresh/</link><guid isPermaLink="true">https://octyl.net/2022/12/10/site-refresh/</guid><pubDate>Sat, 10 Dec 2022 18:49:58 GMT</pubDate><content:encoded>&lt;p&gt;I’ve gone through and given the site a slightly different theme, to better fit how I want to represent myself. I’ve also
used &lt;a href=&quot;https://wave.webaim.org/&quot;&gt;WAVE&lt;/a&gt; to improve the accessibility of the site, so it should be top-notch. Let me know if you find any improvements
I could make in this area. I really enjoy how WAVE works and recommend it for any accessibility work you do.&lt;/p&gt;
&lt;p&gt;As usual, I’ve also updated some dependencies to the latest version as of writing: Bootstrap (5.2.3), Jekyll (4.3.1),
and Jekyll Feed (0.16.0).&lt;/p&gt;</content:encoded></item><item><title>RSS Feed Added</title><link>https://octyl.net/2022/09/05/rss-feed/</link><guid isPermaLink="true">https://octyl.net/2022/09/05/rss-feed/</guid><pubDate>Mon, 05 Sep 2022 19:18:54 GMT</pubDate><content:encoded>&lt;p&gt;At the request of an anonymous reader, I’ve added an RSS feed for my blog posts. It’s linked from the
&lt;a href=&quot;/blog/&quot;&gt;main blog index&lt;/a&gt;, as well as each individual post. You can see it on this one in the bottom-right, it looks
like this: &lt;a href=&quot;#&quot; class=&quot;btn btn-primary&quot;&gt;&lt;span class=&quot;fa-solid fa-rss&quot; title=&quot;Atom/RSS Feed&quot;&gt;&lt;/span&gt;&lt;/a&gt;&lt;/p&gt;</content:encoded></item><item><title>GitHub Pages + Jekyll 4 with Github Actions!</title><link>https://octyl.net/2022/09/05/github-actions-jekyll/</link><guid isPermaLink="true">https://octyl.net/2022/09/05/github-actions-jekyll/</guid><pubDate>Mon, 05 Sep 2022 17:20:26 GMT</pubDate><content:encoded>&lt;p&gt;I’ve been wondering for a while why the GitHub Pages gem hadn’t been updated to Jekyll 4, which contains many
changes that I’ve really wanted in the past. It turns out that GitHub has a new &lt;a href=&quot;https://github.blog/2022-08-10-github-pages-now-uses-actions-by-default/&quot;&gt;GitHub Actions workflow&lt;/a&gt; that is
intended to replace the black-box pipeline that was the default, allowing for using other static site generators
or really any arbitrary code to produce a Pages site. I’m really excited for this change, and hope to experiement
with other ways of creating sites besides Jekyll in the future.&lt;/p&gt;
&lt;p&gt;However, this site doesn’t have any good reason to switch to another generator right now, so I’ve simply updated it to
use the new Actions workflow and updated to Jekyll 4. A preliminary check of the site appears to show no issues, but
please let me know if you find any!&lt;/p&gt;</content:encoded></item><item><title>downloadanykey.com</title><link>https://octyl.net/2021/11/13/downloadanykey/</link><guid isPermaLink="true">https://octyl.net/2021/11/13/downloadanykey/</guid><pubDate>Sat, 13 Nov 2021 07:37:40 GMT</pubDate><content:encoded>&lt;p&gt;I’ve written a new site, a riff on &lt;a href=&quot;https://downloadmoreram.com/&quot;&gt;https://downloadmoreram.com/&lt;/a&gt;, entitled &lt;a href=&quot;https://downloadanykey.com/&quot;&gt;“Download Any
Key!”&lt;/a&gt;. This new site was a fun way for me to learn some new skills, like deploying a
&lt;a href=&quot;http://dnslink.io/&quot;&gt;DNSLink&lt;/a&gt;-based site and Blender. As hinted, this site &lt;em&gt;is&lt;/em&gt; IPFS-enabled, so it should theoretically
last until the failure of the IPFS network, though currently with a small reliance on the DNS system as well. I hope to
add more content to this in the future, and am open to PRs if you have some creative ideas!&lt;/p&gt;
&lt;p&gt;The site’s source is available at &lt;a href=&quot;https://github.com/octylFractal/downloadanykey.com&quot;&gt;https://github.com/octylFractal/downloadanykey.com&lt;/a&gt;.&lt;/p&gt;</content:encoded></item><item><title>Bootstrap 5, et. al</title><link>https://octyl.net/2021/07/21/bootstrap-5/</link><guid isPermaLink="true">https://octyl.net/2021/07/21/bootstrap-5/</guid><pubDate>Wed, 21 Jul 2021 07:12:36 GMT</pubDate><content:encoded>&lt;p&gt;I’ve updated the site to Bootstrap 5, as well as updating some other dependencies. Let me know if anything seems broken.&lt;/p&gt;</content:encoded></item><item><title>Blog Navigation + Other Improvements!</title><link>https://octyl.net/2020/02/23/blog-navigation/</link><guid isPermaLink="true">https://octyl.net/2020/02/23/blog-navigation/</guid><pubDate>Sun, 23 Feb 2020 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I’ve updated the blog to include navigation, between the now &lt;em&gt;two&lt;/em&gt; posts!&lt;/p&gt;
&lt;p&gt;Additionally, publish date and title information is visibly shown.&lt;/p&gt;</content:encoded></item><item><title>A New Site</title><link>https://octyl.net/2020/01/28/a-new-site/</link><guid isPermaLink="true">https://octyl.net/2020/01/28/a-new-site/</guid><pubDate>Tue, 28 Jan 2020 22:53:36 GMT</pubDate><content:encoded>&lt;p&gt;Hello, and welcome to the new bio / internet home for Octavia Togami, i.e. &lt;strong&gt;me&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;I don’t intend to update this very often, but at least the content is semi-relevant again :).&lt;/p&gt;</content:encoded></item></channel></rss>