<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>notes from /dev/null - blog</title><link href="http://yummymelon.com/devnull/" rel="alternate"/><link href="http://yummymelon.com/devnull/feeds/tags/blog.atom.xml" rel="self"/><id>http://yummymelon.com/devnull/</id><updated>2025-03-23T14:20:00-07:00</updated><entry><title>NFDN Finally Supporting OS Appearance Changes</title><link href="http://yummymelon.com/devnull/finally-supporting-os-appearance-changes.html" rel="alternate"/><published>2025-03-23T14:20:00-07:00</published><updated>2025-03-23T14:20:00-07:00</updated><author><name>Charles Choi</name></author><id>tag:yummymelon.com,2025-03-23:/devnull/finally-supporting-os-appearance-changes.html</id><summary type="html">&lt;p&gt;Better late than never. This blog now supports OS appearance changes.&lt;/p&gt;</summary><content type="html">&lt;p&gt;Finally got around to updating this blog to support &lt;a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme"&gt;OS appearance changes&lt;/a&gt;. Pleasantly surprised that the CSS was not difficult to figure out nor that much  to do. Looking at my Org &lt;code&gt;TODO&lt;/code&gt; timestamp for this task, it was back in&lt;code&gt;[2023-10-26 Thu 15:20]&lt;/code&gt;when I really wanted this to happen. Better late than never, I suppose.&lt;/p&gt;
&lt;p&gt;Side note - Mobile Safari (both iPhone and iPad) is stubborn in not refreshing updated CSS files. To force this, go to Settings › Apps › Safari › Advanced › Website Data. When there do the following:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Search for yummymelon.com&lt;/li&gt;
&lt;li&gt;Press the &lt;code&gt;Edit&lt;/code&gt; button.&lt;/li&gt;
&lt;li&gt;Delete yummymelon.com data.&lt;/li&gt;
&lt;li&gt;Press the &lt;code&gt;Done&lt;/code&gt; button.&lt;/li&gt;
&lt;li&gt;Kill running Safari app (Swipe up, Select Safari, Swipe Up).&lt;/li&gt;
&lt;li&gt;Restart Safari.&lt;/li&gt;
&lt;li&gt;Open &lt;a href="http://yummymelon.com/devnull/"&gt;http://yummymelon.com/devnull/&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;</content><category term="misc"/><category term="blog"/></entry><entry><title>Going back to feeds</title><link href="http://yummymelon.com/devnull/going-back-to-feeds.html" rel="alternate"/><published>2023-06-13T23:20:00-07:00</published><updated>2023-06-13T23:20:00-07:00</updated><author><name>Charles Choi</name></author><id>tag:yummymelon.com,2023-06-13:/devnull/going-back-to-feeds.html</id><summary type="html">&lt;p&gt;Reddit's on-going self-inflicted wound has got me revisiting feeds.&lt;/p&gt;</summary><content type="html">&lt;p&gt;With the turmoil going on at Reddit starting from their stance on 3&lt;sup&gt;rd&lt;/sup&gt; party mobile clients, I'm taking this as an opportunity to shed even more of my &lt;a href="http://yummymelon.com/devnull/taking-a-break-from-twitter.html"&gt;social media consumption&lt;/a&gt;. On all my devices I have logged out of Reddit and deleted their mobile clients and browser bookmarks too. &lt;/p&gt;
&lt;p&gt;For me, one of the larger conveniences of aggregating sites like Reddit was the one-stop shopping for interesting posts/articles on the web. But leaving editorial to the madness of crowds (as it's been for the past decade or so) has definitely shown its limitations. Going back to reading from syndication feeds (aka RSS/ATOM) and forcing the curation back on me seems like the right thing to do. Maybe I'll change my mind later, but I've no interest in joining some federated clone of Reddit to replace it.&lt;/p&gt;
&lt;p&gt;With my newfound embrace of feeds from all over the web, I figured it was time to revamp this blog's feeds as well.&lt;/p&gt;
&lt;p&gt;Go to the following page, &lt;a href="http://yummymelon.com/devnull/tags.html"&gt;Feed &amp;amp; Tags&lt;/a&gt;, to get the feed link for all posts from this blog, as well as separate feeds per metadata tag used by each blog post. The &lt;strong&gt;Feed &amp;amp; Tags&lt;/strong&gt; link is at the bottom of every page on this blog as well.&lt;/p&gt;
&lt;p&gt;Looking forward to seeing how well this works over time. Will return to this topic at the end of 2023. &lt;/p&gt;</content><category term="misc"/><category term="blog"/><category term="social media"/><category term="feeds"/></entry><entry><title>Static Blog Generation: 9 Weeks In</title><link href="http://yummymelon.com/devnull/static-blog-generation-9-weeks-in.html" rel="alternate"/><published>2013-04-28T16:49:00-07:00</published><updated>2013-04-28T16:49:00-07:00</updated><author><name>Charles Choi</name></author><id>tag:yummymelon.com,2013-04-28:/devnull/static-blog-generation-9-weeks-in.html</id><summary type="html">&lt;p&gt;Thoughts after 9 weeks of using Pelican to statically generate a blog.&lt;/p&gt;</summary><content type="html">&lt;p&gt;9 weeks in using &lt;a href="http://getpelican.com"&gt;Pelican&lt;/a&gt; to generate my blog and so far I dig it: I've been able to write more and write better with it.&lt;/p&gt;
&lt;p&gt;Thinking about why, the reasons come down to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Being able to define and automate your own workflows.&lt;/li&gt;
&lt;li&gt;Being able to use Markdown to format your source files.&lt;/li&gt;
&lt;li&gt;Easy customization (especially if you have a background in Python, templating and web development).&lt;/li&gt;
&lt;li&gt;Using source code control (git in my case) to manage/sanity check what you post.&lt;/li&gt;
&lt;li&gt;It's fast. Having worked with Python web frameworks like Zope (and Plone later on), TurboGears, and Django, it's easy to get stuff initially up and running but the price you pay is slow run-time performance, especially for content that doesn't need to be dynamic in the first place. Not all content needs to be stashed in a database.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Static blog generation with a tool like Pelican is not for everybody: you really need to be comfortable with working like a software developer. But if you're already there then you'll likely find yourself pleased with it.&lt;/p&gt;</content><category term="misc"/><category term="Software"/><category term="Blog"/><category term="Pelican"/></entry></feed>