<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title>Ronsome</title>
		<link>http://ronso.me/</link>
		<description>I'm Hudson Valley native, Ron Newsome, Jr.</description>
		<author>Ron Newsome, Jr.</author>
		<pubDate>Fri, 29 Jun 2007 03:05:56 GMT</pubDate>
		<image>
			<url>http://ronso.me/images/icons/ronsome.com256.png</url>
			<title>Ronsome</title>
			<link>http://ronso.me/</link>
		</image>

		<item>
			<title>Writing, Legitimately</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/5</guid>
			<link>http://ronso.me/blogposts/writing-legitimately</link>
			<description>
					<![CDATA[ <p>Now and again, I bump into an aspiring novelist who claims to be working on a book that he or she hopes to publish. Invariably, I suggest that <a href="http://kdp.amazon.com">self-publishing</a> on Amazon might be the way to go, and I almost always get the same response: &quot;Well, I might do that eventually, but first I want to be accepted by a <em>legitimate publisher</em>.&quot; </p>
<p>Never mind the fact that <a href="http://www.nytimes.com/2011/03/25/books/amanda-hocking-sells-book-series-to-st-martins-press.html">some authors have done pretty well</a> by self-publishing, particularly with <a href="http://phx.corporate-ir.net/phoenix.zhtml?c=176060&amp;p=irol-newsArticle&amp;ID=1565581&amp;highlight=">digital books</a>. I think it should be obvious that good writing legitimizes itself.</p> ]]>
			</description>
			<pubDate>Jul 7 2013</pubDate>
			<category>writing, publishing</category>
		</item>

		<item>
			<title>Hulu Minus</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/6</guid>
			<link>http://ronso.me/blogposts/hulu-minus</link>
			<description>
					<![CDATA[ <p>So, Hulu's owners are scrambling to get new licensing deals in place, in order to facilitate a sale. Does that mean the new owners will be bound by the same inane non-PC device policy that currently exists?</p>
<p>I'm sure this has been mentioned before, but Hulu's policy of allowing all of its content to be played for free on PCs (where PC means any computer running a traditional desktop OS), while other devices only get access to limited content feels twisted. That limited content, of course comes at a premium—a premium to the tune of a $7.99 per month subscription.</p>
<p>I'm about to give up, and cancel Hulu Plus. While the idea of watching TV shows on a 40 inch screen on my own schedule remains appealing, there are a number of factors working against the service. First, all of the shows that I'm paying for are readily available for free if I watch them on my PC. Second, it seems like the vast majority of shows that I actually want to watch are only available via PC. Hulu Plus just doesn't seem like it adds enough value to warrant a premium over the basic service.</p>
<p>Hulu needs to do something about it's horrible Hulu Plus device policy. Maybe add an intermediate tier? Add more commercials? Obviously, there's no reasonable explanation for Hulu to restrict streaming to TVs and other internet-connected devices.</p> ]]>
			</description>
			<pubDate>Jun 4 2012</pubDate>
			<category>content, tv</category>
		</item>

		<item>
			<title>What Was Race</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/8</guid>
			<link>http://ronso.me/blogposts/what-was-race</link>
			<description>
					<![CDATA[ <p>Over in the New York Times Opinion Pages <a href="http://opinionator.blogs.nytimes.com/2012/04/01/in-arizona-censoring-questions-about-race/#">Linda Martín Alcoff talks about critical race theory</a> and Arizona officials' efforts to prevent it from being taught in public schools. She does a credible job of explaining what critical race theory is, and why Arizona legislators might be against it, but in doing so, she veers into a minor discussion of what race is. She even goes so far as to touch upon the pseudo-science historically used to support the idea of race (while emphasizing its lack of biological validity).</p>
<p>The fact is that &quot;race&quot; has lost validity as a term to differentiate between biologically distinct people. For most people race is completely interchangeable with ethnicity. &quot;Racisim&quot; has become the catch-all for any kind of cultural, religious, or ethnic bias. While Alcoff refers to herself as a &quot;racial realist&quot; having &quot;defended the reality of race throughout [her] work,&quot; she might as well call herself an ethnic realist. In the end, while the idea of race remains sociologically important, it shouldn't be biologically significant.</p> ]]>
			</description>
			<pubDate>Apr 4 2012</pubDate>
			<category>race, culture</category>
		</item>

		<item>
			<title>Wakeup Call</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/9</guid>
			<link>http://ronso.me/blogposts/wakeup-call</link>
			<description>
					<![CDATA[ <p>This morning a spammer managed to invite me to a phishing scheme via Google Calendar. For some reason Google added the event to my calendar and set a notification, <em>even though I never indicated that I was attending</em>. As a result, I got an unwanted 6am wakeup call on a Sunday when my smartphone alerted me to the impending event.</p> ]]>
			</description>
			<pubDate>Jun 30 2013</pubDate>
			<category>calendar, google, phishing</category>
		</item>

		<item>
			<title>Standing Out</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/11</guid>
			<link>http://ronso.me/blogposts/standing-out</link>
			<description>
					<![CDATA[ <p>We all know the story: Web devs begin misusing UAs, so browser vendors mangle them beyond recognition
in the hopes that devs can't block them from their sites.</p>
<p>Well here we are in 2013, and everybody knows that <a href="https://developer.mozilla.org/en-US/docs/Browser_detection_using_the_user_agent" title="Browser detection using the user agent">using feature detection is the way to write browser
specific code</a>. Maybe browser vendors are leery of breaking the web, but they should be able to come up
with a standard implementation of the UA string. It should be trivial, really. There are only three or
four important pieces of information traditionally included anyway: OS, vendor, browser, version number,
and perhaps device type (mobile, etc.). The UA for <a href="http://google.com/chrome">Chrome</a> on my <a href="http://google.com/nexus/4">Nexus 4</a> includes references to Mozilla,
Safari, Gecko, KHTML, and AppleWebkit, but makes no mention of the actual vendor (Google).
How about this?</p>
<pre><code>Android 4.2.2; Google Chrome 27.0; mobile</code></pre>
<p>How hard is that?</p> ]]>
			</description>
			<pubDate>Jun 28 2013</pubDate>
			<category>browsers</category>
		</item>

		<item>
			<title>Introducing Popbox</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/13</guid>
			<link>http://ronso.me/blogposts/introducing-popbox</link>
			<description>
					<![CDATA[ <p><a href="/projects/Popbox">Popbox</a> is a lightweight, unobtrusive script for displaying images in a Web page. Written entirely in JavaScript and CSS, Popbox weighs in at just 3.7 kb, and relies on no external dependencies. Popbox was designed as a smaller, simpler replacement for other image presentation scripts such as <a href="http://www.huddletogether.com/projects/lightbox/">Lightbox</a>, <a href="http://www.digitalia.be/software/slimbox">Slimbox</a>, and <a href="http://www.cabel.name/2008/02/fancyzoom-10.html">FancyZoom</a>.</p>
<p>All CSS and images are contained in the JS file, so setup is a snap.
All you have to download is the script. Include the script in the head of your document, and add <code>rel="popbox"</code> to links you want to open with Popbox.</p>
<p>Popbox has been tested on Firefox 3+, Safari 3+, Chrome 1.0, Opera 9+, and IE 7+.</p>
<p>Popbox is free software released under a Creative Commons license.</p>
<p><a href="/js/popbox.js">Download popbox.js</a> | <a href="/css/popbox.css">Download CSS</a></p> ]]>
			</description>
			<pubDate>Dec 23 2012</pubDate>
			<category>js, css, image, tools</category>
		</item>

		<item>
			<title>A Consumer's Guide to Useless Product Reviews</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/14</guid>
			<link>http://ronso.me/blogposts/a-consumers-guide-to-useless-product-reviews</link>
			<description>
					<![CDATA[ <p>While shopping and reading user product reviews on Amazon, I decided to come up with my own guide detailing how to write a proper review. You're welcome.</p>
<p><strong>Forget performance.</strong> The last thing a person wants to see when perusing consumer product reviews is whether or not a product works. Whether the item does what the manufacturer claims, or fails spectacularly, if you're going to mention that information, be sure to bring it up last. Better yet, put it in a lengthy footnote. Really, you don't have to mention performance at all. It's a well-documented fact that long, vague, repetitive reviews rate higher than those that are insightful and succinct.*</p>
<p><strong>Be effusive.</strong> Whether or not you like the product, say so as frequently as possible. Verbal abuse and vacuous praise are both signs of a thoughtful, stable person. For bonus points fit in a tired cliche or two (double points for the phrases &quot;works like a charm&quot; and &quot;piece of s#@t&quot;).</p>
<p><strong>State the obvious.</strong> Remember, the whole point of reading other people's reviews is to find out things about a product that you could easily learn without owning it. If you think an item is overpriced, say so. If you're reviewing electronics, write an in-depth explanation of the underlying technology. If you don't have a good grasp of how the thing works, all the better, the reader is certainly as ignorant as you are. Besides, credibility is overrated. By the same token, there's no need to include relevant information in your review. People like surprises.</p>
<p>One last thing: <strong>Whether or not a product is labeled for a particular use is irrelevant.</strong> The customer is ALWAYS right. Products should do whatever you want them to. It is perfectly reasonable for the manufacturer, the retailer, and state and local governments to be able to read your mind, and make sure your every need and comfort are met. The reader realizes this, and cares deeply about your needs, so don't be shy about venting your frustrations.</p>
<p>So, go ahead, write your review. We couldn't possibly care more.</p>
<p><small>*Not a well-documented fact.</small></p> ]]>
			</description>
			<pubDate>Dec 4 2012</pubDate>
			<category>reviews, shopping</category>
		</item>

		<item>
			<title>Five Stars</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/16</guid>
			<link>http://ronso.me/blogposts/five-stars</link>
			<description>
					<![CDATA[ <p>Too many five-star ratings systems label two stars as &quot;OK&quot; and three stars as &quot;liked it&quot;. That kind of system offers three degrees of approval and one degree of disapproval (and one degree of ambivalence). My rating system looks like this:</p>
<table width="100%">
<tr><td>A favorite, highly recommended</td><td>★★★★★</td></tr>
<tr><td>Pretty good, recommended</td><td>★★★★</td></tr>
<tr><td>Not bad, but not recommended</td><td>★★★</td></tr>
<tr><td>Pretty bad, not recommended</td><td>★★</td></tr>
<tr><td>Awful, recommended against</td><td>★</td></tr>
</table> ]]>
			</description>
			<pubDate>Jul 4 2012</pubDate>
			<category>ratings, reviews</category>
		</item>

		<item>
			<title>Content Builders of All Stripes</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/17</guid>
			<link>http://ronso.me/blogposts/content-builders-of-all-stripes</link>
			<description>
					<![CDATA[ <p>Over on <a href="http://stuntbox.com/">Stuntbox</a> David Sleight has another <a href="http://stuntbox.com/blog/2012/03/content-archipelago-ascendant/">smart post</a> on content consumption and delivery. As he says, &quot;...the future of media tends towards access...meet a user wherever they are with the content they want....&quot; It's a discussion you can't get away from, whether you're talking about Flash and HTML5 or <a href="http://theoatmeal.com/comics/game_of_thrones">HBO and &quot;Game of Thrones&quot;</a>.</p> ]]>
			</description>
			<pubDate>Apr 2 2012</pubDate>
			<category>content, format</category>
		</item>

		<item>
			<title>Omnibox</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/18</guid>
			<link>http://ronso.me/blogposts/omnibox</link>
			<description>
					<![CDATA[ <p>The Chrome Omnibox is terrible. Firefox gets it right with the Awesomebar. As far as I can tell, there is no rhyme or reason to the way Chrome offers suggestions. Putting aside the aggressive search suggestions, which I understand (it <em>is</em> a Google browser after all), Chrome is awful when it comes to matching URLs and titles from my history.</p> ]]>
			</description>
			<pubDate>Aug 4 2013</pubDate>
			<category>browser, firefox, chrome</category>
		</item>

		<item>
			<title>JUMP vs. Next</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/19</guid>
			<link>http://ronso.me/blogposts/jump-vs-next</link>
			<description>
					<![CDATA[ <p>Android Central has a nice, little breakdown of how AT&amp;T (and other telcos) plan to continue to squeeze profits from a saturated market: <a href="http://feedproxy.google.com/~r/androidcentral/~3/7FbKWtIi4bw/story01.htm">T-Mobile and AT&amp;T: JUMP to your Next phone purchase--or don't</a>.</p> ]]>
			</description>
			<pubDate>Jul 17 2013</pubDate>
			<category>att, tmobile, phone, cell</category>
		</item>

		<item>
			<title>Disregarding Privacy</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/23</guid>
			<link>http://ronso.me/blogposts/disregarding-privacy</link>
			<description>
					<![CDATA[ <p>There has been quite a bit of <a href="http://stuntbox.com/blog/2013/08/chrome-password-security/">shock</a> and <a href="http://www.wired.com/threatlevel/2013/08/chrome-password-manager/">consternation</a> over Chrome's <a href="http://blog.elliottkember.com/chromes-insane-password-security-strategy">poorly implemented password manager</a>, but frankly, I'm no more than a little surprised. Over the past few years Google has taken a <a href="http://techcrunch.com/2010/02/12/google-buzz-privacy/">disturbingly</a> <a href="http://www.theregister.co.uk/2013/03/10/google_to_settle_with_us_states_over_wi_spy/">lax</a> <a href="http://www.pcmag.com/article2/0,2817,2411916,00.asp">stance</a> on user privacy.</p>
<p>After reading <em><a href="http://en.wikipedia.org/wiki/In_the_Plex">In the Plex</a></em>, Steven Levy's in-depth look at what makes Google tick, it's easy to see how a group of engineers focused on creating new (and profitable) ways of using mountains of stored data could overlook the little, old issue of user privacy.</p> ]]>
			</description>
			<pubDate>Aug 8 2013</pubDate>
			<category>privacy, passwords, chrome, google</category>
		</item>

		<item>
			<title>Something's Not Right</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/25</guid>
			<link>http://ronso.me/blogposts/somethings-not-right</link>
			<description>
					<![CDATA[ <div>
<p><strong>Google</strong>: Something's not right.</p>

<p><strong>Me</strong>: Care to elaborate?</p>

<p><strong>Google</strong>: We're having trouble contacting our servers. We're going to keep trying.</p>

<p><strong>Me</strong>: Well, sure, that'll fix everything.</p>
</div> ]]>
			</description>
			<pubDate>Aug 15 2013</pubDate>
			<category>gmail, google</category>
		</item>

		<item>
			<title>Don't Blame the Messager</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/27</guid>
			<link>http://ronso.me/blogposts/dont-blame-the-messager</link>
			<description>
					<![CDATA[ <p><a href="http://arstechnica.com/tech-policy/2013/08/texting-drivers-in-nj-you-might-be-liable-for-their-car-crash/">Ars Technica reports</a> that if you text drivers in New Jersey, you might be liable for their car crash. The thing is, simply receiving a text <del>is not</del> shouldn't be a distraction. A person doesn't become distracted until he chooses to read the text. To suggest that the sender might share some of the responsibility for a crash is ridiculous.</p> ]]>
			</description>
			<pubDate>Aug 30 2013</pubDate>
			<category>texting, blame, law</category>
		</item>

		<item>
			<title>Good Rules</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/29</guid>
			<link>http://ronso.me/blogposts/good-rules</link>
			<description>
					<![CDATA[ <p>If no one knows the reason behind a rule, it probably isn't a good rule, and no, &quot;because we've always done it that way&quot; does not qualify as a reason. That isn't to say it's a <em>bad</em> rule—it just isn't a <em>good</em> one.</p> ]]>
			</description>
			<pubDate>Jun 22 2014</pubDate>
			<category>rules</category>
		</item>

		<item>
			<title>Fizzle</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/30</guid>
			<link>http://ronso.me/blogposts/fizzle</link>
			<description>
					<![CDATA[ <p>Well, it happened again. A certain <a href="http://www.cbsnews.com/news/blizzard-2015-may-be-falling-short-of-predictions/">monster storm</a> was supposed to hit the Northeast, and in some areas fell short of predictions. Now, incredibly, some people are complaining because the storm <em>wasn't as bad as promised</em>. Some feel inconvenienced because roads were closed. Some are disappointed because there just wasn't enough snow(?!). Worst of all are the folks who are angry because the weatherman got it wrong. Again.</p>
<p>Every time I talk to one of <em>those</em> people I have to grit my teeth and smile as they tell me how incompetent weather forecasters are. Predicting the weather is hard, and <strong>most of the time these guys get it right</strong>. Seriously, forecasts in the Northeast predicted a snowstorm, and we got...snow. The fact that we're even given an approximation of snow in inches is a bonus.</p>
<p>So, if you don't have confidence in the weatherman, that's fine. Next time he predicts a blizzard, pack your sunblock and head to the beach. Just don't complain to me how he's always wrong.</p> ]]>
			</description>
			<pubDate>Jan 28 2015</pubDate>
			<category>weather</category>
		</item>

		<item>
			<title>Maple Snow</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/31</guid>
			<link>http://ronso.me/blogposts/maple-snow</link>
			<description>
					<![CDATA[ <p>The maple tree in the front yard is weeping which is weird enough, but some of the drops are so small, and its so cold outside that there is actually snow coming out of it.</p> ]]>
			</description>
			<pubDate>Mar 29 2015</pubDate>
			<category>nature</category>
		</item>

		<item>
			<title>It's Different, I Hate It</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/32</guid>
			<link>http://ronso.me/blogposts/its-different-i-hate-it</link>
			<description>
					<![CDATA[ <p>Wow, people really hate <a href="http://lifehacker.com">Lifehacker</a>'s <a href="http://product.kinja.com/updating-kinjas-design-1727969613/1727975818?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+lifehacker%2Ffull+%28Lifehacker%29">redesign</a>. The complaints about the size of the font are particularly interesting because 16px is the browser default for fonts (at least it is in Chrome and it was in Firefox, last time I checked). The complaints about the font face being difficult to read are also curious. Having viewed the site on four different screens of varying sizes and resolutions, I don't see the problem.</p> ]]>
			</description>
			<pubDate>Sep 1 2015</pubDate>
			<category>design</category>
		</item>

		<item>
			<title>Happy New Year</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/33</guid>
			<link>http://ronso.me/blogposts/happy-new-year</link>
			<description>
					<![CDATA[ <p>Every year the sheaf of papers tacked to the bulletin board falls down at some point  because a push pin is not intended to support a small book, and every year we inexplicably put it back up again.</p> ]]>
			</description>
			<pubDate>Dec 29 2015</pubDate>
			<category></category>
		</item>

		<item>
			<title>Light Show</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/35</guid>
			<link>http://ronso.me/blogposts/light-show</link>
			<description>
					<![CDATA[ <p>Sitting outside watching the shadows on the ground as the clouds move across the sun. It's like sitting in a room when a little kid discovers the dimmer switch.</p> ]]>
			</description>
			<pubDate>Apr 16 2017</pubDate>
			<category>nature</category>
		</item>

		<item>
			<title>New Toy</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/36</guid>
			<link>http://ronso.me/blogposts/new-toy</link>
			<description>
					<![CDATA[ <p>At dawn you can hear the relay that controls the automatically activated night vision light in the WyzeCam snapping on and off like the ticking of a clock. Well, that is if your clock ticks more and more urgently, the closer it gets to actual sunup.</p> ]]>
			</description>
			<pubDate>Apr 11 2018</pubDate>
			<category>WyzeCam, camera, smarthome, technology</category>
		</item>

		<item>
			<title>Using Multiple Accounts with  Mutt and MSMTP</title>
			<guid isPermaLink="true">http://ronso.me/blogposts/37</guid>
			<link>http://ronso.me/blogposts/using-multiple-accounts-with-mutt-and-msmtp</link>
			<description>
					<![CDATA[ <p>A few months ago I set out to find a command line email client that could handle system emails from web servers better than the default &quot;mail&quot; command. It didn't take me long to settle on <a href="http://www.mutt.org/">Mutt</a>. I've been using it now for several months, and I quite like it. In fact, I prefer it by far to the <a href="https://www.gmail.com/">Gmail web client</a>. With a little help from Google I tracked down several guides to getting Mutt working with Gmail (and <a href="http://msmtp.sourceforge.net/">MSTP</a>). I even found a blog post detailing how one intrepid Mutt enthusiast managed to <a href="https://pbrisbin.com/posts/two_accounts_in_mutt/">get multiple Gmail accounts working</a> with his configuration. However, after perusing this article, and fiddling with my own configuration a little bit, I've settled on a simpler way.</p>
<p>Rather than try to cram two account configurations into a single file, I've created two separate config files, plus two scripts that allow Mutt to use the appropriate file. In my case, I have a config for Gmail, and another one for my own domain.</p>
<p>First, I created a folder with the two config files (I won't include my configurations here, others have covered the subject in depth elsewhere):</p>
<pre><code>mkdir -p ~/Documents/.mailconfigs/; cd ~/Documents/.mailconfigs/
nano gmail.com.muttrc gmail.com.msmtprc ronsome.net.muttrc ronsome.net.msmtprc</code></pre>
<p>The trick to making this work is in the simple bash scripts I created. </p>
<p>For Gmail:</p>
<pre><code>sudo nano /usr/local/bin/gmail</code></pre>
<p>And enter:</p>
<pre><code>rm ~/.muttrc
rm ~/.msmtprc
ln -s ~/Documents/.mailconfigs/gmail.com.muttrc ~/.muttrc
ln -s ~/Documents/.mailconfigs/gmail.com.msmtprc ~/.msmtprc</code></pre>
<p>The other is similar; simply replace &quot;gmail.com&quot; with &quot;ronsome.net&quot;. now I can type <code>gmail</code>, and Mutt will start with my Gmail config, or I can enter <code>ronsome.net</code> to begin with the other one.</p> ]]>
			</description>
			<pubDate>Jul 2 2018</pubDate>
			<category>email, gmail, mutt</category>
		</item>
	</channel>
</rss>
