FEED Validator

for Atom and RSS and KML

Congratulations!

This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

line 32, column 0: content should not contain decoding attribute (24 occurrences) [help]
```
<a href="https://boredzo.org/blog ...
```
line 32, column 0: content should not contain loading attribute (23 occurrences) [help]
```
<a href="https://boredzo.org/blog ...
```
line 295, column 0: style attribute contains potentially dangerous content: image-rendering [help]
```
<a href="https://marchintosh.com/"><img decoding="async" lo ...
```

line 431, column 31: Two entries with the same value for atom:updated: 2024-04-07T05:07:45Z (8 occurrences) [help]

		<updated>2024-04-07T05:07:45Z</updated>
                               ^

Source: http://boredzo.org/blog/feed/atom/

<?xml version="1.0" encoding="UTF-8"?><feed
xmlns="http://www.w3.org/2005/Atom"
xmlns:thr="http://purl.org/syndication/thread/1.0"
xml:lang="en-US"
>
<title type="text">Idle Time</title>
<subtitle type="text">The personal weblog of Peter Hosey.</subtitle>
<updated>2025-02-04T22:14:15Z</updated>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog" />
<id>https://boredzo.org/blog/feed/atom</id>
<link rel="self" type="application/atom+xml" href="https://boredzo.org/blog/feed/atom" />
<generator uri="https://wordpress.org/" version="6.1.1">WordPress</generator>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Let the user help solve their own problem]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2025-01-14/let-the-user-help-solve-their-own-problem" />
<id>https://boredzo.org/blog/?p=2426</id>
<updated>2025-02-04T22:14:15Z</updated>
<published>2025-01-14T21:46:36Z</published>
<category scheme="https://boredzo.org/blog" term="Programming" />
<summary type="html"><![CDATA[I wish we had a maps app like Apple Maps or Google Maps that let you order up a travel itinerary using public transit between two points, and explicitly pick the transit routes involved. Or, ideally, multiple sets of routes, for comparison. Like, let’s say I’m in the Mission and I wanna get to the […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2025-01-14/let-the-user-help-solve-their-own-problem"><![CDATA[I wish we had a maps app like Apple Maps or Google Maps that let you order up a travel itinerary using public transit between two points, and explicitly pick the transit routes involved. Or, ideally, multiple sets of routes, for comparison.
<a href="https://boredzo.org/blog/wp-content/uploads/2025/01/sf-mission-and-soma.jpg"><img decoding="async" width="250" height="219" loading="lazy" alt="Map of San Francisco showing BART as a rainbow through the Mission before turning right to follow Market toward the Bay. Along the latter section, one block from Powell Station, a point of interest is marked for the Metreon shopping center." src="https://boredzo.org/blog/wp-content/uploads/2025/01/sf-mission-and-soma.jpg" /></a>
Like, let’s say I’m in the Mission and I wanna get to the Metreon. One of the existing apps might suggest the 14R rapid bus, which arrives in X minutes and takes Y minutes, or BART, which arrives in Z minutes and takes W minutes. But it might leave out alternatives like taking the 49 bus to Van Ness Station and then taking the Muni subway from there.
Sometimes all the app’s recommendations are reasonable, but sometimes there’s one or more options that might be preferable—and I don’t know how preferable if the app isn’t showing me when the next 49 arrives, so I can compare to the 7 minutes for a 14R or 9 minutes (including a short walk) for BART.
What I want is the ability to add a specific set of routes to include in consideration, or even to force an itinerary using those routes. Let me say “49, KLMN” and have it include that series of routes among my options for comparison.
<hr />
This is one instance of a general problem, which is products having only algorithmic solutions to the user’s needs, with no opportunity for the user to contribute to the solution.
The algorithmic-only model admits only one remedy: Improve the algorithm. But because no algorithm will ever be perfect, you’ll be playing this game of whac-a-mole forever.
This goes for the developer of each product, as well as for the user. I could try the same query in Apple Maps and Google Maps and the <a href="https://transitapp.com/">Transit app</a> and whatever else, but as long as they all work this way, all I’m doing is holding up different slices of Swiss cheese next to each other and comparing their holes.
When the user can contribute to the solution, then there’s a chance that they’ll have a better idea of how to meet their own needs.
And these aren’t mutually exclusive. You could use the user’s input to improve the algorithm’s suggestions.
Email spam filters have had this for decades. The “Report Spam” and “Not Spam” buttons help train the filter. And we still have them because the filter will never be perfect (not just because spam is always evolving).
For the transit routing example, it’s a more complex problem (not a simple ham-or-spam dichotomy) and there are privacy considerations. Even so, helping improve the routing algorithm for everyone could be something people could opt into.
If they decline, maybe the algorithm could use training supplements kept locally. The user who provided a suggestion could still benefit, even if they’ve declined to share that (potentially personal/identifying) data with others.
And even just the ability to add a route combination to the list, even if I have to do it every time, would be an improvement over not having that and being limited to whatever options the algorithm picks for me.
Don’t assume your algorithm has to solve everything all on its own. Let the user help. They’ll be happier with a solution they helped create, partly because it may be better for their specific needs, and partly because they got to be involved.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2025-01-14/let-the-user-help-solve-their-own-problem#comments" thr:count="3" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2025-01-14/let-the-user-help-solve-their-own-problem/feed/atom" thr:count="3" />
<thr:total>3</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Stuff I made this year]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2024-12-29/stuff-i-made-this-year" />
<id>https://boredzo.org/blog/?p=2421</id>
<updated>2024-12-30T05:30:46Z</updated>
<published>2024-12-30T05:29:44Z</published>
<category scheme="https://boredzo.org/blog" term="Life" />
<summary type="html"><![CDATA[It’s been a hell of a year, but it’s almost over. Since social media has gotten a lot more fragmented since Twitter died, probably a lot of folks haven’t seen the stuff I’ve only posted on my Mastodon or on my Cohost page (RIP). So here’s a round-up of most of what I made this […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2024-12-29/stuff-i-made-this-year"><![CDATA[It’s been a hell of a year, but it’s almost over.
Since social media has gotten a lot more fragmented since <a href="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter">Twitter died</a>, probably a lot of folks haven’t seen the stuff I’ve only posted on <a href="https://mastodon.social/@boredzo">my Mastodon</a> or on <a href="https://cohost.org/boredzo">my Cohost page</a> (RIP).
So here’s a round-up of most of what I made this year. I’ll likely import select posts from my Cohost archive (<a href="https://mastodon.social/@cohost/113699074947643844">download yours today!</a>—seriously, the site’s getting deleted in a couple days!) at some future time, but for now, they’ll stay on Cohost (and the Internet Archive’s mirror thereof).
If you’re wondering why March is so heavy in this list, it’s because of <a href="https://marchintosh.com/">#MARCHintosh</a>. Which is coming up again soon!
<ul>
<li>March: <a href="https://boredzo.org/blog/archives/2024-03-31/i-upgraded-my-ibook-g4-to-have-an-ssd">I upgraded my iBook G4 to have an SSD</a>, and took some notes on the process.</li>
<li>March: Improvements to <a href="https://github.com/boredzo/impluse-hfs">impluse</a>, my command-line tool for accessing the contents of vintage HFS volumes. For some highlights, see <a href="https://mastodon.social/@boredzo/112046773494367049">this toot</a>.</li>
<li>March: <a href="https://youtube.com/watch?v=iTNDm-LC_Js">A YouTube version of the Guided Tour of Macintosh Plus</a>, demonstrating the audio cassette and software program that were meant to be used together to learn how to use a GUI and a file-system. </li>
<li>March: <a href="https://youtube.com/watch?v=XKKUwlAHXf4">Tutorial on extracting icon resources to modern image formats using emulated Classic Mac OS</a></li>
<li>March: I discovered that <a href="https://mastodon.social/@boredzo/112129872179702803">you can move windows on a Mac using any edge</a>.</li>
<li>March–April: <a href="https://github.com/boredzo/csv_tools">Command-line tools for working with CSV files</a></li>
<li>July: <a href="https://cohost.org/boredzo-kitchen-diary/post/6834075-recipe-a-chocolate">A chocolate milkshake recipe equivalent to, if not better than, what’s sold in Ghirardelli chocolate shops</a> (that Cohost link will break soon; the recipe is also in my cookbook, listed below)</li>
<li>September: Overhauled my webpage on <a href="https://boredzo.org/postcards/">political postcarding</a>. It’s a bit of a seasonal item, only relevant in the months leading up to an election, but in those months, feel free to use this in your own postcarding efforts or send it to friends who are interested in easy ways to get out the vote.</li>
<li>September: Made an <a href="https://mastodon.social/@boredzo/113195108808392260">educational shitpost about trigonometry</a>.</li>
<li>October: Another election-season item, <a href="https://www.redbubble.com/i/pin/I-Voted-Early-pin-button-badge-by-votecards/165480192.2UH40">a button to advertise that you voted early</a>. Reusable, unlike a sticker!</li>
<li>October: <a href="https://boredzo.org/blog/archives/2024-10-27/skillet-handle-holder">Instructions on sewing a handle holder for a cast-iron skillet</a></li>
<li>November: As a sodium-conscious home cook, I looked up the sodium content of various brands of a couple of things I eat, and published those notes: <a href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins">Sodium content in frozen chicken tenderloins</a> and <a href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings">Sodium content in lemon-pepper seasonings</a></li>
<li>November: I wrote <a href="https://boredzo.itch.io/i-need-food">my first cookbook!</a></li>
<li>December: I wrote <a href="https://github.com/boredzo/get1resource">a command-line tool to extract resources from old Mac files</a> (including the System file, applications, many types of plug-ins or data files, and more).</li>
<li>December: I wrote <a href="https://github.com/boredzo/sort_du">a utility to sort the output of du -h by file size</a>. Then somebody pointed out that <a href="https://eozygodon.com/@yildo/113707657057117186">sort has a -h option that does the same thing</a>. A thousand times had I wished for it; 999 times had I looked and not found it. Now it exists—hooray! I thanked them in my reply, and have since archived this repo and will simply use sort -h henceforth.</li>
<li>December: Earlier in the year, I came up with an effective solution for storing my two kitchen knives (big knife and little knife) without damaging their edge. (This was motivated by my learning to sharpen them using whetstones.) This month, <a href="https://mastodon.social/@boredzo/113716365707638110">I improved that solution</a>.</li>
</ul>
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2024-12-29/stuff-i-made-this-year#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2024-12-29/stuff-i-made-this-year/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Sodium content in lemon-pepper seasonings]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings" />
<id>https://boredzo.org/blog/?p=2415</id>
<updated>2024-11-14T23:03:54Z</updated>
<published>2024-11-12T14:03:27Z</published>
<category scheme="https://boredzo.org/blog" term="Food" /><category scheme="https://boredzo.org/blog" term="blood pressure" /><category scheme="https://boredzo.org/blog" term="cooking" /><category scheme="https://boredzo.org/blog" term="food" /><category scheme="https://boredzo.org/blog" term="nutrition" /><category scheme="https://boredzo.org/blog" term="sodium" />
<summary type="html"><![CDATA[While I was writing the previous post about sodium in frozen chicken, it occurred to me that I should also include info on sodium in the lemon-pepper seasoning I often add to it, and eventually I decided to split that off into its own post. I have high blood pressure. Have had for years. I […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings"><![CDATA[While I was writing the previous post about <a href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins">sodium in frozen chicken</a>, it occurred to me that I should also include info on sodium in the lemon-pepper seasoning I often add to it, and eventually I decided to split that off into its own post.
I have high blood pressure. Have had for years. I take medication, but I’m also trying to reduce the sodium in my diet to limit how much it contributes.
It turns out that lemon-pepper seasonings, which I use frequently, are a significant contributor of sodium, as they all include salt (presumably sodium chloride) as one of their top two ingredients. Sigh.
There are salt-free options and I’m going to have to try some of them at some point. In the meantime, here are the sodium contents of all of the lemon-pepper seasoning products listed on Safeway’s website (minus the explicitly salt-free ones), plus the one currently in my kitchen, along with where “salt” is listed in the ingredients list.
These are all based on 1/4 teaspoon of seasoning, which ranges from 0.7 to 1 gram depending on brand. Most of these have either salt or pepper as the first ingredient; I’ve noted the exceptions.
<table>
<tr>
<th>Brand</th>
<th>Sodium content</th>
<th>Salt is listed…</th>
</tr>
<tr>
<td valign="top"><a href="https://www.safeway.com/shop/product-details.114150209.html">Lawry’s</a> The one I was using before my current jar</td>
<td valign="top">90 mg</td>
<td valign="top">2nd</td>
</tr>
<tr>
<td valign="top">Pacific Organic The one I’m currently using</td>
<td valign="top">140 mg</td>
<td valign="top">1st</td>
</tr>
<tr>
<td valign="top">Sunny Select (Save Mart)</td>
<td valign="top">140 mg</td>
<td valign="top">1st</td>
</tr>
<tr>
<td valign="top"><a href="https://www.safeway.com/shop/product-details.114150672.html">Signature Select (Safeway)</a></td>
<td>95 mg</td>
<td>2nd</td>
</tr>
<tr>
<td valign="top"><a href="https://www.safeway.com/shop/product-details.960512621.html">Kinder’s</a></td>
<td>105 mg</td>
<td>2nd (sugar is 1st, pepper 3rd)</td>
</tr>
<tr>
<td valign="top"><a href="https://www.safeway.com/shop/product-details.970033891.html">McCormick</a></td>
<td>180 mg</td>
<td>1st</td>
</tr>
<tr>
<td valign="top"><a href="https://www.safeway.com/shop/product-details.960163642.html">Scott’s</a></td>
<td>210 mg</td>
<td>1st (“spices” is 4th)</td>
</tr>
</table>
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Sodium content in frozen chicken tenderloins]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins" />
<id>https://boredzo.org/blog/?p=2413</id>
<updated>2024-11-12T14:03:49Z</updated>
<published>2024-11-12T14:02:38Z</published>
<category scheme="https://boredzo.org/blog" term="Food" /><category scheme="https://boredzo.org/blog" term="blood pressure" /><category scheme="https://boredzo.org/blog" term="chicken" /><category scheme="https://boredzo.org/blog" term="cooking" /><category scheme="https://boredzo.org/blog" term="food" /><category scheme="https://boredzo.org/blog" term="nutrition" /><category scheme="https://boredzo.org/blog" term="sodium" />
<summary type="html"><![CDATA[[Content note: This post is about meat used in cooking. If you don’t eat meat, this will be at best academic. If you’re opposed to the eating of meat, feel free to skip this post entirely.] I have high blood pressure. Have had for years. I take medication, but I’m also trying to reduce the […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins"><![CDATA[[Content note: This post is about meat used in cooking. If you don’t eat meat, this will be at best academic. If you’re opposed to the eating of meat, feel free to skip this post entirely.]
I have high blood pressure. Have had for years. I take medication, but I’m also trying to reduce the sodium in my diet to limit how much it contributes.
I also do a lot of home cooking, and many of my dinners involve a frozen chicken breast tenderloin. For one person, namely me, this is the perfect serving size of meat protein. Generally I grill it on my George Foreman grill with a dusting of <a href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-lemon-pepper-seasonings">lemon-pepper seasoning</a>.
Frozen chicken typically has some sort of brine solution added to it. I assume this helps the freezing process, or something. One consequence of this is that the sodium content of frozen chicken is greater than refrigerated chicken (which might be a reason for me to switch to refrigerated… hmmm) and also varies widely between brands.
I’m only going to be looking at tenderloins, since that’s what I buy. I’d guess that the ratios would be similar for a different cut—but if you buy a different cut and you care about sodium content, you should probably research the sodium content of your options for that cut yourself.
For most of these, I’ll link to the product online. One of them I don’t have an online product link for; the other, I’ll elaborate on after the table.
All of these are based on the nutrition facts label, which all of them give in terms of one 112-gram (4-ounce) tenderloin.
<table>
<tr>
<th>Brand</th>
<th>Sodium content</th>
</tr>
<tr>
<td>Signature Farms (Safeway)</td>
<td>190 mg</td>
</tr>
<tr>
<td>Trader Joe’s</td>
<td>75 mg</td>
</tr>
<tr>
<td valign="top"><a href="https://www.fosterfarms.com/product/always-natural-individually-frozen-breast-tenders/">Foster Farms</a></td>
<td width="60%">300 mg Note: Their website says 280 mg but I’m going by a bag I own.</td>
</tr>
<tr>
<td><a href="https://www.costcobusinessdelivery.com/kirkland-signature-chicken-tenderloins%2c-boneless-skinless%2c-6-lbs.product.100367403.html">Kirkland Signature</a></td>
<td>200 mg</td>
</tr>
<tr>
<td><a href="https://www.target.com/p/boneless-38-skinless-chicken-breast-tenderloins-frozen-40oz-good-38-gather-8482/-/A-14715976#lnk=sametab">Good & Gather (Target)</a></td>
<td>280 mg</td>
</tr>
<tr>
<td><a href="https://www.target.com/p/tyson-all-natural-chicken-tenderloins-frozen-40oz/-/A-14777760#lnk=sametab">Tyson</a></td>
<td>190 mg</td>
</tr>
<tr>
<td><a href="https://www.kroger.com/p/kroger-frozen-boneless-skinless-chicken-tenderloins/0001111000906">Kroger</a></td>
<td>180 mg</td>
</tr>
<tr>
<td><a href="https://www.walmart.com/ip/Great-Value-All-Natural-Chicken-Breast-Tenderloins-3-lb-Frozen/51259070">Great Value (Walmart)</a></td>
<td>190 mg</td>
</tr>
<tr>
<td><a href="https://www.perdue.com/products/perdue-individually-frozen-boneless-skinless-chicken-tenderloins/">Perdue</a></td>
<td>260 mg</td>
</tr>
</table>
The least was Trader Joe’s at 75 mg, and the greatest was Foster Farms at 300 mg (with Target just behind it at 280). Quite a range!
One thing I noticed is that nutrition facts published online may disagree with what’s printed on the bag. One example is noted above; another, bigger discrepancy is <a href="https://www.safeway.com/shop/product-details.960151171.html">Safeway’s listing</a> for store-brand frozen chicken tenderloins, which says that those contain 1,090 milligrams of sodium—five times the sodium content listed on the (differently-styled) Safeway-brand bag in my freezer now. That seems like it might be the wrong product’s nutrition facts.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2024-11-12/sodium-content-in-frozen-chicken-tenderloins/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Skillet handle holder]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2024-10-27/skillet-handle-holder" />
<id>https://boredzo.org/blog/?p=2409</id>
<updated>2024-10-27T20:12:03Z</updated>
<published>2024-10-27T20:06:43Z</published>
<category scheme="https://boredzo.org/blog" term="Projects" /><category scheme="https://boredzo.org/blog" term="Sewing" />
<summary type="html"><![CDATA[I modified a cotton pot-holder into a skillet handle holder.]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2024-10-27/skillet-handle-holder"><![CDATA[I cook with a couple of cast iron skillets—a 6-inch one and a 10-inch one—and, after each cooking session is complete, I wash the skillet so the fats and food bits left behind don’t set. In order to do this, I need to hold onto the handle—but by that point, the handle is very hot. Even with cast iron’s notoriously slow internal distribution of heat, the handle will still be 200°F or more.
My kitchen towel is often wet from hand-washing by that point, so I can’t very well use that as an insulator—the water will conduct the heat very efficiently. And I’m not stocking the kitchen with half a dozen towels at a time.
Pot-holders work, but it’s easy for a pot-holder to get misaligned and me to end up touching hot metal anyway. What I need is something I can slip onto the handle for that final cleaning step.
I’ve been using the Ove Glove, but wanted something easier to wash.<a href="#skillet_handle_holder_fn1_orig">*</a>
Lodge sells silicone pot handle covers, but I’d rather not spend $10 a pop for more plastic.
What I realized is that I can modify a pot-holder by folding it over and sewing it closed. So I bought a two-pack of black all-cotton pot-holders from Dollar Tree and got started.
<img decoding="async" width="500" height="375" alt="An unmodified black square pot-holder, with a loop for hanging at the middle of one edge, and a care label sewn in at the middle of another edge." src="https://boredzo.org/blog/wp-content/uploads/2024/10/IMG_1033-scaled.jpg">
The first step was to seam-rip all of the original bias tape away from the edge, exposing the edges of the pot-holder body. This binding also includes the loop that can be used to hang the pot-holder, and secures the label with the care instructions. I want to keep both of these in the new design.
I cut the original bias tape (from the end opposite the loop) to a length that I could put back on one edge, including both adjacent corners. This edge becomes the perimeter of the opening.
<img decoding="async" loading="lazy" width="500" height="375" alt="The pot-holder with its original bias tape removed, exposing the edge of the cotton batting inside. A length of the original bias tape has been clipped back onto one edge of the pot-holder, while another length of the bias tape lay alongside to show its one-inch width." src="https://boredzo.org/blog/wp-content/uploads/2024/10/IMG_1023-scaled.jpg">
Then I made some fresh bias tape from black cotton quilting fabric. I measured the length around one and a half sides of the pot-holder, which is the length of binding that will run from the open end down one side and along the closed end. The width is three inches, producing 1½-inch (36 mm) bias tape.
I don’t have a bias tape maker in that width (my widest one is 24 mm), so I had to apply the folds manually using pins and my ironing board. All-metal tailoring pins are helpful here because you can iron directly over them.
<img decoding="async" loading="lazy" width="500" height="375" alt="The inch-and-a-half black bias tape. One end of it is shown here against a small green cutting mat." src="https://boredzo.org/blog/wp-content/uploads/2024/10/IMG_1026-scaled.jpg"> 
I cut off the diagonal ends to leave a right-angle end before sewing.
The reason for the jumbo bias tape is that twice the thickness of the pot-holder is _thick_. I used a 100-diameter denim needle and reduced my presser foot pressure by two full turns, and my Singer Heavy Duty machine still struggled at times. And you can really tell where the cotton batting is being compressed by the lockstitch.
I decided to put the care label at the closed end. One thing I’d do differently: I think I’d prefer the label on the underside. The side I put the label on ends up facing up and tickling my palm when I’m holding the skillet with my left hand.
The loop also goes at the closed end, at the very end of the new bias tape. I cut it off from the original bias tape and stuck one end in under the new bias tape on each side.
<img decoding="async" loading="lazy" width="500" height="375" alt="The finished holder, shot at an oblique angle to show the opening in the foreground. At the far end is the care label and the loop." src="https://boredzo.org/blog/wp-content/uploads/2024/10/IMG_1030-scaled.jpg">
The finished product is very much a universal skillet handle holder, longer than either of my skillets’ handles; theoretically I could have trimmed it down to fit one of my skillets more exactly, and done the same with the other pot-holder to make one tailored for the other skillet. But I’m happy with this for now.
<img decoding="async" loading="lazy" width="500" height="375" alt="Holding my ten-inch skillet by the handle, which is encased in the cotton holder." src="https://boredzo.org/blog/wp-content/uploads/2024/10/IMG_1032-scaled.jpg">
* I had misremembered the Ove Glove as not being machine-washable, but I just looked up the care instructions and it is. Then I checked on the care label for the pot-holders and apparently those, despite being all-cotton, are “hand wash only”. Oops. (Neither can be tumble-dried.) When the time comes, I’ll probably machine-wash the pot-holder handle holder anyway and see what happens. <a href="#skillet_handle_holder_fn1_orig">↶</a>
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2024-10-27/skillet-handle-holder#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2024-10-27/skillet-handle-holder/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[I upgraded my iBook G4 to have an SSD]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2024-03-31/i-upgraded-my-ibook-g4-to-have-an-ssd" />
<id>https://boredzo.org/blog/?p=1896</id>
<updated>2024-12-30T05:56:00Z</updated>
<published>2024-03-31T22:32:35Z</published>
<category scheme="https://boredzo.org/blog" term="@Uncategorized" /><category scheme="https://boredzo.org/blog" term="MARCHintosh" />
<summary type="html"><![CDATA[I did take some notes which I’ll present below, but this isn’t a full how-to. I used iFixIt’s guide plus occasional reference to the official Apple Service Source repair guide (those are not strictly public but can be had from your favorite abandonware site). For this year’s #MARCHintosh, I decided to replace my iBook G4’s […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2024-03-31/i-upgraded-my-ibook-g4-to-have-an-ssd"><![CDATA[I did take some notes which I’ll present below, but this isn’t a full how-to. I used <a href="https://www.ifixit.com/Guide/iBook+G4+12-Inch+800+MHz-1.2+GHz+Hard+Drive+Replacement/166">iFixIt’s guide</a> plus occasional reference to the official Apple Service Source repair guide (those are not strictly public but can be had from your favorite abandonware site).
For this year’s <a href="https://marchintosh.com/">#MARCHintosh</a>, I decided to replace my iBook G4’s 30 GB spinning-rust hard drive with an SSD.
<a href="https://marchintosh.com/"><img decoding="async" loading="lazy" width="192" height="102" style="image-rendering: pixelated;" alt="The #Marchintosh logo, depicting a smiling compact Mac icon with a four-leaf clover and a stripe of six-color Apple rainbow." srcset="/blog/wp-content/uploads/2024/03/MARCHintoshLogo@1x.png, /blog/wp-content/uploads/2024/03/MARCHintoshLogo@2x.png 2x" src="/blog/wp-content/uploads/2024/03/MARCHintoshLogo@1x.png" /></a>
This was my second SSD upgrade, as I’d previously <a href="/cubehd">replaced my G4 Cube’s hard drive with an SSD</a>. (The pictures on that page show a hard drive because, before the SSD upgrade, I’d replaced the Cube’s hard drive with another hard drive, and that was what I originally documented on that page. Then, after that, when I decided to upgrade to an SSD, I used my own tutorial. iFixIt didn’t exist yet.)
I rather despise working on laptops, though this wasn’t as bad as I’d worried it would be. (Upgrading the memory in my Mac mini was harder. I pointedly did that as soon as the machine arrived so that it would be done and I’d never need to open the machine back up for the rest of its life.)
The thing that motivated me to go forward with it was that the iBook was absolutely filthy. It had been Mom’s, and she was a smoker in her life; she would routinely be smoking a cigarette and working on the computer, and getting so absorbed in the latter that ash would fall from her cigarette onto and into the computer. So I resolved to clean the disassembled parts as well as upgrade the storage.
For the cleaning, I mostly used paper towels wetted with diluted all-purpose cleaner. A couple small spots of deposited nail polish were resolved with cotton pads soaked with nail polish remover. It worked fine, at least so far—if I’ve started some chemical process of plastic deterioration, I don’t know it yet.
<img decoding="async" loading="lazy" width="504" height="378" alt="The iBook in question, closed, and visibly dirty even on the outside." src="/blog/wp-content/uploads/2024/03/IMG_7672@2x.jpg" srcset="/blog/wp-content/uploads/2024/03/IMG_7672@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7672@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7672@1x.jpg" /> 
Before cleaning.
<img decoding="async" loading="lazy" width="504" height="378" alt="The iBook in question, closed, now thoroughly cleaned and spiffy." srcset="/blog/wp-content/uploads/2024/03/IMG_7760@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7760@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7760@1x.jpg" /> 
After cleaning.
Once I decided the project was go, I also added in a memory upgrade, because it was less than $20 and I was already buying stuff from OWC for the operation anyway. The machine had 512 MB of RAM; now it has 1 GB. (Plus the 128 MB on the logic board.)
One key difference from the Cube upgrade: The iBook, being a laptop, doesn’t have as much space for the upgraded drive. The Cube had some wiggle room taken up by brackets; the iBook has basically none. In the Cube, I installed a standard-size SATA SSD plus a SATA-to-PATA adapter; in the iBook, that wouldn’t have fit.
So my first thought was an M.2 SSD, that being the form factor that today’s computers generally use. I ran into a problem: There are like three different signaling protocols that all run over the M.2 form factor, and M.2 correspondingly has three different keying combinations to guard against protocol mismatches (an incompatible SSD won’t physically fit, though an SSD that fits isn’t necessarily compatible). I noped out of trying to sort that out.
What I went with instead was mSATA. This form factor is kind of dying off as M.2 takes over, but Kingston still sells mSATA SSDs directly from their own website, and I found a suitable adapter on Amazon. (I buy from alternatives like Micro Center or direct from manufacturers whenever possible, but it wasn’t in this case. The manufacturer’s website links to their Amazon store.)
<img decoding="async" loading="lazy" width="606" height="340" alt="The two-and-a-half-inch spinning-rust hard drive, and the mSATA SSD in its IDE adapter, side by side in my hand." srcset="/blog/wp-content/uploads/2024/03/IMG_7735@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7735@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7735@1x.jpg" /> 
The old spinning-rust drive is 30 GB; the new SSD is 256 GB.

<h3>What’d I put in there?</h3>
Here’s the bill of materials I ended up with:
<ul>
<li><a href="https://shop.kingston.com/collections/solid-state-drives/products/kc600-ssd-1?variant=40836176576704">Kingston 256GB mSATA SSD</a> (you could go bigger, but I cheaped out)</li>
<li><a href="https://www.amazon.com/Ableconn-IIDE-MSAT-2-5-Inch-Converter-Aluminum/dp/B017VQT5YW/132-2787373-3000614">Ableconn mSATA to IDE adapter</a></li>
<li><a href="https://eshop.macsales.com/item/OWC/2700DDRS1GBA/">OWC 1 GB PC2700 RAM SO-DIMM</a> (the original Apple DIMM was PC2100, so this was a speed upgrade as well as a size upgrade)</li>
<li><a href="https://eshop.macsales.com/item/OWC/MS8U3SSD120/">OWC external FireWire SSD</a> to reinstall the OS from, since this machine can’t boot from USB and I don’t trust the internal optical drive to not eat the next disc I put in it</li>
</ul>
… and as I write this up now, I notice that OWC has now discontinued that last product. Did I buy the last one or something?
(It feels like OWC is moving away from selling products for older Macs, having now discontinued their last FireWire product AFAIK, and I’m bummed. At a time when the retro Mac community is resurgent, we can use every source for quality gear for our old Macs that we can get.)
For tools, I mostly used <a href="https://www.ifixit.com/products/essential-electronics-toolkit">one of iFixIt’s toolkits</a>, plus <a href="https://www.ifixit.com/products/precision-screw-extractor-set">the screw extractor set they sell</a>. I also found <a href="https://www.artsupplywarehouse.com/products/daylight-halo-table-magnifying-lamp%7CDAYU25200.html">a lighted magnifier</a> extremely helpful.
I also used <a href="https://coriolis-systems.com/">iPartition</a> to set up the external SSD with the Tiger and Leopard boot DVDs and various other things (including a copy I’d already made of the HDD).
<h3>Hiccups</h3>
<h4>Hiccup #1: The case of the borked screw</h4>
One of the three M2 (i.e., 2mm, i.e., really tiny) screws on the right side of the keyboard tray was visibly rusted and seemingly damaged. Trying to unscrew it (including a couple of attempts with the wrong size driver) damaged it further.
<img decoding="async" loading="lazy" width="504" height="283" alt="The inside of the keyboard tray. There are two screws in the rear and forward corners, and a third in the center. The forward screw has some visible rust on its head." srcset="/blog/wp-content/uploads/2024/03/IMG_7696@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7696@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7696@1x.jpg" /> 
This was after I’d already worked over that third screw a bunch. It was even more rust-covered at first.

I looked at a bunch of options and asked for ideas on Mastodon. A couple of people recommended precision screw extractors (much smaller and a different type than the kind you drill into a screw). I bought <a href="https://www.ifixit.com/products/precision-screw-extractor-set">the set that iFixIt sells</a>, which it turns out is <a href="https://www.centraltools.com/58-0675-4pc-screw-extractor-reversible-set.html">OEM’d by Moody Tools</a>.
The second extractor bit I tried, one of the smaller ones, worked perfectly, and drove the screw out as easily as the normal drivers did the undamaged screws. Thus I was unblocked and able to continue toward the hard drive.
I did encounter a second rusted screw near the latch mechanism. This I was able to clean with a few things, including a nylon-brush bit on a Dremel, without damaging the head. That screw came out and went back in with no further fuss.
<h4>Hiccup #2: The case of the stuck installer</h4>
After I got everything back together, the Tiger DVD wouldn’t boot. After either the verbose spew or the spinner, the OS switches to the normal GUI with a blue background, and should then show the Installer on that background—but it would get stuck at the blue background, with no window and no cursor.
On a whim, I tried Leopard (not a supported OS on this machine), and was pleasantly surprised to find that the iBook booted that DVD happily. Moreover, that it worked.
Leopard’s installer refused to install, of course, but it let me cancel and access the rest of the utilities—including Terminal, from which I was able to run <code>system_profiler</code>. Here, I figured, I could at least see whether any of my new hardware was showing up.
And the answer was no. Well, that was a let-down! The RAM slot read as empty (it definitely wasn’t), and querying the PATA bus hung.
I decided to try switching back to the original Apple DIMM, since it’s easier to get to the RAM than the hard drive. When I put the original DIMM back in, I noticed that it sat farther into the slot than the upgrade DIMM had been.
“HMMMMMM.”
So I popped it back out and re-upgraded the RAM. Sure enough, with a bit more attention to this detail, the new DIMM went into the slot exactly as far as the Apple DIMM had.
And when I booted the machine up again… everything worked. The new RAM showed up. PATA no longer hung.
“Hmm. PATA doesn’t hang anymore. Was that where Tiger was hanging?”
Yup! Or similar enough, anyway. It fixed the problem; Tiger’s installer was now unblocked.
<h4>Hiccup #3: The case of the 512 MB partition map</h4>
One of my goals for this machine is to try to cajole it into booting Mac OS 9 even though that isn’t supported, so I wanted to make sure to install the disk drivers that Mac OS 9 needs onto the SSD. This is an option in Disk Utility of that era… except it wasn’t showing up, presumably because this is a machine that (officially) can’t boot Mac OS 9 anyway, so why would it need that?
(The original hard drive had Mac OS 9 drivers installed. Maybe Panther was more permissive about that.)
Now, there is a second way to get Mac OS 9 drivers installed: <code>hdiutil create</code> has an option, <code>-layout 'UNIVERSAL HD'</code>, that sets up the image with a partition map containing a full set of Mac OS 9 drivers for every then-imaginable device interface, from SCSI to ATA to FireWire. (There is also <code>'UNIVERSAL CD'</code>, which gives a different set of drivers.)
So my plan was:
<ol>
<li>Create a RAM disk using <code>hdiutil create -nomount ram://262144</code> (that creates a 128 MB RAM disk), since I had nothing writable that I wasn’t about to obliterate (besides thumb drives), and I had plenty of RAM.</li>
<li>On the RAM disk, create a sparse disk image with the “UNIVERSAL HD” format and sized to the number of blocks <code>diskutil info</code> reported for the SSD.</li>
<li>Attach that disk image with <code>-nomount</code> so I can munge its contents directly.</li>
<li>Use <code>pdisk</code> to edit its partition map, specifically to create all the partitions I wanted.</li>
<li>Use <code>newfs_hfs</code> to format each of the partitions as HFS+J (or plain HFS+ in the case of the OS 9 partition).</li>
</ol>
Problem: Whenever I attached the sparse disk image, pdisk showed that the partition map was set for a 512 MB storage device, not a 256 GB storage device. It doesn’t offer any way to change that, even in the advanced options.
Solution: This was apparently a Tiger bug, because when I rebooted back into the Leopard DVD, the same series of steps worked perfectly.
So I had to do my partitioning and formatting in Leopard, then reboot back to the Tiger DVD to install the OS.
<h3>Results</h3>
Well, the first sign of success was that the Tiger installation—from the FireWire SSD to the IDE SSD—only took 15 minutes. If you’ve ever installed old Mac OS X from a CD or DVD to a spinning-rust drive, you’ll remember it definitely takes longer than that.
My informal test of the HDD’s speed before the operation showed about 30 MB/sec write speed (<code>dd if=/dev/zero bs=10485760 of=test</code>, followed by math to convert its output to MB/sec because Tiger’s <code>dd</code> doesn’t have <code>status=progress</code>). After the upgrade, I found out about <a href="http://xbench.com">Xbench</a>, and ran that, and it showed about 90 MB/sec write speed in most cases, which is basically saturating the UDMA100 interface. So, with the caveat that the methodologies of the two tests aren’t the same, I feel comfortable saying I tripled my throughput.
Tiger certainly feels way faster than ever before on this machine. The progress-bar portion of the boot process is now a tiny fraction of it, as the progress bar goes from 0 to 100% in about a second.
I’m very happy with the upgrade. I plan to see if I can convince the machine to boot from a Mac OS 9 partition (not a supported configuration—the machine came with a special version of Panther) or install Leopard (also not supported; this machine officially only supports Panther and Tiger plus Classic).
<h3>More photos</h3>
<h4>How dirty this thing was</h3>
<img decoding="async" loading="lazy" width="504" height="283" alt="Photo of the front edge of the machine. To the left of the latch release button, I haven't cleaned yet, and there's a visible beige patina. To the right of the button, my cleaning has revealed mostly-pristine-looking gray and white plastic." src="/blog/wp-content/uploads/2024/03/IMG_7685@1x.jpg" />
<img decoding="async" loading="lazy" width="504" height="353" alt="The underside of the machine. This surface is even filthier, with several brown streaks of unclear origin." src="/blog/wp-content/uploads/2024/03/IMG_7687@1x.jpg" />
<img decoding="async" loading="lazy" width="504" height="283" alt="The latch release mechanism, rife with dust bunnies. I used lots of canned air evicting them. I think I might have also resorted to a toothpick for some of it." src="/blog/wp-content/uploads/2024/03/IMG_7691@1x.jpg" />

<h4>Note #1: Drive bay shock bumpers</h4>
<img decoding="async" loading="lazy" width="504" height="283" alt="The IDE adapter (with mSATA SSD installed on the far side of it) sitting half-in the iBook's drive bay. Two black rubber washers are permanently affixed inside the drive bay, near the corners of the drive." srcset="/blog/wp-content/uploads/2024/03/IMG_7737@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7737@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7737@1x.jpg" /> 
Note the rubber bumpers inside the drive bay, inside the front of the machine. The heads of the screws on that side of the drive bracket (or the IDE adapter replacing it) rest inside these bumpers. There’s also a bracket with matching bumpers on the other side, which should be transferred from the old drive to the new one.
<h4>Note #2: Reinstalling the feet</h4>
The iBook’s feet have a design that ensures there’s only one way to reinstall them. You’ll need to pay attention to it when putting the feet back in, to ensure you don’t put them in crooked.
<img decoding="async" loading="lazy" width="504" height="283" alt="View through the lighted magnifier of one of the recesses where a foot is about to be reinstalled. There's a ridge on the inside of one quadrant of the recess." srcset="/blog/wp-content/uploads/2024/03/IMG_7740@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7740@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7740@1x.jpg" /> 
<img decoding="async" loading="lazy" width="504" height="283" alt="The metal ring that surrounds one foot, as seen from the underside that sits in the recess. There are three pillars from the outside-facing ring down to the bottom where the screw-hole is. One of those pillars has a lip carved out of it." srcset="/blog/wp-content/uploads/2024/03/IMG_7742@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7742@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7742@1x.jpg" /> 
The lip in this foot ring mates to the ridge in the recess. If the foot ring isn’t properly aligned, it won’t sit in the recess evenly. Don’t force it! Pull it out, look for the keying, and turn it so it’s correctly positioned.
<img decoding="async" loading="lazy" width="504" height="283" alt="Photo of the recess with the ring installed—so now we're viewing it from the exterior side rather than the interior side. Inside the ring is a well with three keys. Next to the ring, resting upside down, is the foot that will go into this ring; it has three grooves in its underside to match those keys." srcset="/blog/wp-content/uploads/2024/03/IMG_7745@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7745@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7745@1x.jpg" />
More keying. As before, pay attention and make sure you’re lined up, and back off and try again rather than trying to force it in.
<h4>Just for fun</h4>
<img decoding="async" loading="lazy" width="504" height="353" alt="The old spinning-rust hard drive. There's an air-pressure-equalization vent hole near one edge, and the label has a section that says “DO NOT COVER THIS HOLE”. I'm mischievously covering it with my fingertip." srcset="/blog/wp-content/uploads/2024/03/IMG_7732@1x.jpg, /blog/wp-content/uploads/2024/03/IMG_7732@2x.jpg 2x" src="/blog/wp-content/uploads/2024/03/IMG_7732@1x.jpg" />
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2024-03-31/i-upgraded-my-ibook-g4-to-have-an-ssd#comments" thr:count="6" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2024-03-31/i-upgraded-my-ibook-g4-to-have-an-ssd/feed/atom" thr:count="6" />
<thr:total>6</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[High-resolution Creative Commons badge]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-10-26/high-resolution-creative-commons-badge" />
<id>https://boredzo.org/blog/?p=1869</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-10-27T03:45:07Z</published>
<category scheme="https://boredzo.org/blog" term="Free stuff" /><category scheme="https://boredzo.org/blog" term="88x31" /><category scheme="https://boredzo.org/blog" term="Creative Commons" /><category scheme="https://boredzo.org/blog" term="hi-res" /><category scheme="https://boredzo.org/blog" term="hidpi" /><category scheme="https://boredzo.org/blog" term="Some Rights Reserved" /><category scheme="https://boredzo.org/blog" term="vector redraw" />
<summary type="html"><![CDATA[I noticed that the pointers tutorial‘s Creative Commons badge had gone missing. I guess they got tired of people hotlinking it. So I grabbed it from the Wayback Machine, and when I did, I noticed that it’s in the classic 88×31 format used by so many miniature promotional images. If the phrase “Netscape Now!” means […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-10-26/high-resolution-creative-commons-badge"><![CDATA[I noticed that <a href="/pointers">the pointers tutorial</a>‘s Creative Commons badge had gone missing. I guess they got tired of people hotlinking it.
So I grabbed it from the Wayback Machine, and when I did, I noticed that it’s in the classic 88×31 format used by so many miniature promotional images. If the phrase “Netscape Now!” means anything to you, you know what I’m talking about.
There’s been a growing trend of making <a href="https://cohost.org/rc/tagged/88x31">new 88×31 images</a>, some in higher resolutions for modern hi-DPI displays. So I thought I’d do one: redrawing the classic Creative Commons bug as a vector image that could be exported as SVG and as high-res PNG.
Here you go:
<table>
<tr>
<td style="text-align: center"><img decoding="async" loading="lazy" width="88" height="31" alt="The Creative Commons logo on a gray field, with “Some Rights Reserved” in white on black beneath it." src="https://boredzo.org/blog/wp-content/uploads/2023/10/CC-SomeRightsReserved-88x31@2x.png" /> 
The double-resolution PNG.</td>
<td style="text-align: center"><img decoding="async" loading="lazy" width="88" height="31" alt="The Creative Commons logo on a gray field, with “Some Rights Reserved” in white on black beneath it." src="https://boredzo.org/blog/wp-content/uploads/2023/10/CC-SomeRightsReserved-88x31.svg" /> 
The SVG.</td>
</tr>
</table>
I think the original image falls under the CC-BY (Attribution) 2.0 license that was then current. I’m happy to place these new images under <a href="https://creativecommons.org/licenses/by/2.0/">the same license</a> or <a href="https://creativecommons.org/licenses/by/4.0/">the newer 4.0 version</a>.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-10-26/high-resolution-creative-commons-badge#comments" thr:count="1" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-10-26/high-resolution-creative-commons-badge/feed/atom" thr:count="1" />
<thr:total>1</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[The third option: Novavax’s covid vaccine]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-10-24/novavax-covid-vaccine" />
<id>https://boredzo.org/blog/?p=1860</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-10-25T03:06:23Z</published>
<category scheme="https://boredzo.org/blog" term="Life" /><category scheme="https://boredzo.org/blog" term="covid-19" /><category scheme="https://boredzo.org/blog" term="get your vax" /><category scheme="https://boredzo.org/blog" term="Novavax" /><category scheme="https://boredzo.org/blog" term="vaccine" />
<summary type="html"><![CDATA[I’ve had four mRNA-based covid shots so far: Pfizer, Pfizer, Moderna, Pfizer. They’re great protection, of course, but I get harsh side effects from them—two or three days of alternating fever and chills. Not fun. Some folks take ’em just fine, and if you’ve never had an mRNA-based vaccine, I’d encourage you to try it […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-10-24/novavax-covid-vaccine"><![CDATA[I’ve had four mRNA-based covid shots so far: Pfizer, Pfizer, Moderna, Pfizer.
They’re great protection, of course, but I get harsh side effects from them—two or three days of alternating fever and chills. Not fun. Some folks take ’em just fine, and if you’ve never had an mRNA-based vaccine, I’d encourage you to try it at least once—my experience isn’t universal. But I always have a rough time.
I wanted to get this year’s covid shot back in September, which was the anniversary of my previous one, but I had to wait for availability to settle a bit since shots were hard to come by for several weeks, and I know folks who had appointments and then found out they’d been canceled on the day of due to shortage.
The longer that went on, the more I wanted to get my shot ASAP since we’ve already been in a covid surge for months by this point (per <a href="https://biobot.io/data/">wastewater data</a>) and we aren’t even to the holiday season yet.
<img decoding="async" loading="lazy" width="600" height="333" alt="Screenshot of Biobot's nationwide covid prevalence estimates for the past six months. It starts ramping up in July and has been fairly steady at high levels for the past two months. It's dipped a little bit this month but it's not down to anywhere near pre-July levels." src="https://boredzo.org/blog/wp-content/uploads/2023/10/BiobotWastewater20231024.png" /> Pictured here: Everyone I know, and everyone they know, who’s been coming down with covid over the last few months.
Then I heard that Costco has Novavax. (I later found out that Rite Aid also carries it. CVS might have it but apparently you can’t just book it through the website, you have to ask—weird.)
I went on <a href="https://www.costco.com/pharmacy/adult-immunization-program.html">Costco’s website</a> (which offers both Moderna and Novavax), made an appointment for what is now this past Saturday, and stocked up on my usual post-vax supplies: Gatorade, water in the fridge, clean laundry, and a few low-effort meals and snacks.
Saturday, I got the shot. No difficulty, and my insurance covered the cost—I paid $0.00.
Sunday, I spent the entire day feeling like I had a mild cold. No fever, no chills, just lots and lots of sleeping. Drank lots of water, some Gatorade, and even ate on my usual schedule.
Monday… I was fine. By Tuesday, I was back to 100%.
I spent one whole day with the symptoms of a mild cold.
This is a night and day difference from my experience with the Pfizer and Moderna vaccines. It’s more like my experience with a flu shot: sleep like a cat in a sunbeam for a day, then right back to normal.
<a href="https://www.science.org/content/article/should-you-pick-novavax-s-covid-19-shot-over-mrna-options">The efficacy of Novavax is comparable to the mRNA vaccines</a>—it might be a little lower, but close enough that the difference in post-vax experience makes it well worth the tradeoff. Doubly so if you’ve already had, or might get next time, an mRNA-based shot and want that “all of the above” protection.
If you also have a rough time with mRNA-based vaccines, try Novavax.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-10-24/novavax-covid-vaccine#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-10-24/novavax-covid-vaccine/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[If you don’t have RSI, ergonomics are for you]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-09-29/if-you-dont-have-rsi-ergonomics-are-for-you" />
<id>https://boredzo.org/blog/?p=1852</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-09-30T05:56:20Z</published>
<category scheme="https://boredzo.org/blog" term="@Uncategorized" />
<summary type="html"><![CDATA[This was originally posted as a tweet thread back in February 2022. For this Director’s Cut Extended Remix, I’ve added the photos and applied styling. I used my laptop as a laptop for about an hour yesterday and my wrists still hurt. It’s fading but slowly. So I guess I don’t get to do that […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-09-29/if-you-dont-have-rsi-ergonomics-are-for-you"><![CDATA[This was originally posted as a <a href="https://twitter.com/boredzo/status/1497400019137171456">tweet thread</a> back in February 2022. For this Director’s Cut Extended Remix, I’ve added the photos and applied styling.
I used my laptop as a laptop for about an hour yesterday and my wrists still hurt. It’s fading but slowly.
So I guess I don’t get to do that anymore. Split keyboard+vertical mouse or nothing.
<a href="https://boredzo.org/blog/wp-content/uploads/2023/09/Matias-Ergo-Pro.jpg.jpeg"><img decoding="async" loading="lazy" width="256" height="192" alt="My Matias Ergo Pro two-piece keyboard, splayed out on a lap desk sitting on my chair." src="https://boredzo.org/blog/wp-content/uploads/2023/09/Matias-Ergo-Pro.jpg.jpeg"></a><a href="https://boredzo.org/blog/wp-content/uploads/2023/09/Kensington-Pro-Fit-Ergo-Vertical-Wireless-mouse-scaled.jpg"><img decoding="async" loading="lazy" width="256" height="192" alt="My Kensington Pro Fit Ergo Vertical Wireless mouse, on a printed mousepad background on a cutting board on the (mostly flat) arm of my chair." src="https://boredzo.org/blog/wp-content/uploads/2023/09/Kensington-Pro-Fit-Ergo-Vertical-Wireless-mouse-scaled.jpg"></a>
2023 note: I’ve since replaced this keyboard with an <a href="https://ergodox-ez.com/">ErgoDox EZ</a>.
Maybe a split keyboard and vertical mouse seem like luxuries, because that’s their market position (the high end), but I promise you there’s nothing luxurious about this.
Really it’s more that there are keyboards and pointing devices that hurt people, and those that don’t.
<blockquote>But I use a one-piece keyboard and a regular mouse/trackball/trackpad and I’m fine!</blockquote>
Well, maybe. Or you’re not injured yet. Or not enough yet to notice without trying ergonomic hardware for a week and gauging the difference.
Ergo hardware can help you stay uninjured.
I cannot emphasize enough how important prevention is. How important it is to protect your hands before they’re injured.
You can’t un-injure them. You can only avoid injury… or not.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-09-29/if-you-dont-have-rsi-ergonomics-are-for-you#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-09-29/if-you-dont-have-rsi-ergonomics-are-for-you/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Minting a trillion-dollar coin is harder than you think]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-05-21/trillion-dollar-pitfalls" />
<id>https://boredzo.org/blog/?p=1848</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-05-22T05:15:35Z</published>
<category scheme="https://boredzo.org/blog" term="Politics" />
<summary type="html"><![CDATA[The trillion-dollar coin is an idea for one way that Democrats could get around Republican threats to throw the United States into default. (There are other options, including standing on the 14th Amendment clause that says “the public debt… shall not be questioned”.) The basic idea is this: The Department of the Treasury has the […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-05-21/trillion-dollar-pitfalls"><![CDATA[The <a href="https://en.wikipedia.org/wiki/Trillion-dollar_coin">trillion-dollar coin</a> is an idea for one way that Democrats could get around Republican threats to throw the United States into default. (There are <a href="https://indivisiblesf.org/call-scripts/2023/5/9/biden-stop-debt-ceiling-game">other options</a>, including standing on the 14th Amendment clause that says “the public debt… shall not be questioned”.)
The basic idea is this: The Department of the Treasury has the authority to direct the US Mint to produce a platinum coin at any denomination they see fit. The value of such a coin is its face value—that is to say, whatever it says it is. So when the Republicans start throwing around threats like “you need to cut off services to these groups of people or else the government is going to run out of money!!!”, as they have been, one option is to simply literally make more money—in enough of a quantity that it will pay for all the US Government’s expenditures for the next year or so and take a lot of the hostage-takers’ leverage away.
I’m not qualified to debate the policy or economics of it, and most likely, neither are you. But what I can do is think of any number of ways that someone—intentionally or otherwise—could fuck it up.
<h3>Mis-striking the coin</h3>
The last step of the process of producing a coin is called “striking” it. That’s the part where the design gets pressed into the faces of the (hitherto) blank.
Normally coin production is a mass-production process; <a href="https://www.usmint.gov/learn/production-process/coin-production">the country’s mints produce up to tens of thousands of coins per minute</a>. In this case, we’re talking about a one-off, so I don’t know whether they’d do the process differently or just run the machine for a very, very short amount of time.
Either way, it’s certainly possible for the coin to be mis-struck, or otherwise produced in a way that it is obviously defective. This has happened in a variety of ways to nearly every type of coin, and <a href="https://coinsite.com/us-error-coin-values/">normally, mis-struck or otherwise defective coins are worth significantly more than face value</a>.
What does that look like when the face value is $1,000,000,000,000?
Most likely, the mis-struck coin wouldn’t stay that way—they’d melt it down and try again. (After all, platinum ain’t cheap.) We might never know that there was a mis-struck trillion-dollar coin in existence for some short amount of time.
<h3>Composition</h3>
<a href="https://www.law.cornell.edu/uscode/text/31/5112">The specific section of the US Code that authorizes this stunt</a> says:
<blockquote>
The Secretary [of the Treasury] may mint and issue platinum bullion coins and proof platinum coins in accordance with such specifications, designs, varieties, quantities, denominations, and inscriptions as the Secretary, in the Secretary’s discretion, may prescribe from time to time.
</blockquote>
The trillion-dollar coin wouldn’t be a bullion coin, which is <a href="https://catalog.usmint.gov/coin-differences.html">a coin defined by its amount of some precious metal</a>—that would be a “this much platinum” coin, not a coin with a dollar denomination. So the trillion-dollar coin would be a proof coin.
The Mint regularly issues platinum proof coins, such as <a href="https://www.usmint.gov/coins/coin-medal-programs/american-eagle/2023-platinum-proof-freedom-of-the-press">this coin</a> for this year. That coin contains 1 ounce of platinum, and has a face value of $100, but is sold at a price dependent on the value of its platinum content, which is <a href="https://catalog.usmint.gov/on/demandware.static/-/Sites-USM-Library/default/dwfbfd15ca/images/PDFs/2023-Pricing-Grid.pdf">somewhere between $1,000 and $2,000</a>—ten to twenty times its face value.
So, for a trillion-dollar coin, how much platinum would they need? Does there need to be a particular ratio, or could they make a zinc coaster with 1 oz of platinum mixed in?
Or does it even matter? Could they make a 1-oz platinum coin, not much different from the ones they’re already making, and just add ten more zeroes across the back of it?
Speaking of which…
<h3>The design</h3>
There’s at least one <a href="https://www.flickr.com/photos/donkeyhotey/8349514053/">artistic rendering of what such a coin could look like</a>, but it’s just one artist’s conception and not an official rendering from the US Mint.
Presumably they’re not going to just type in “ONE TRILLION DOLLARS” in Impact and call it good. This is The Coin! It’s got to look like something.
On the flip side, this whole idea is an emergency measure. They’re not going to have time to go through the usual processes for coming up with new coin designs—not when the US Government could reach the statutory debt limit in… <a href="https://www.npr.org/2023/05/01/1173148677/debt-ceiling-limit-default-standoff">not even a couple of weeks at this point</a>.
Hopefully they’re coming up with a design now that they can have ready to go if and when it’s needed. (And make absolutely sure it has no typos in it.)
Of course, having the design ready to use at a moment’s notice gets into issues of…
<h3>Operational security</h3>
It’s easy to say “the Mint should do this” or “Treasury should do that” but it’s worth remembering that these are granfalloons, in the sense in which <a href="https://www.tinaja.com/ismm01.shtml">Don Lancaster used the term</a> (slightly different from Kurt Vonnegut’s original meaning):
<blockquote>
<h4>tactics secret—beware the granfalloon, my son</h4>
A granfalloon is any large bureaucratic figment of people’s imagination. For instance, there’s really no such thing as the Feds or the General Veeblefeltzer Corporation. There are a bunch of people out there that relate to each other, and there’s some structures, and some paper. In fact, there’s lots and lots of paper. The people sit in the structures and pass paper back and forth to each other and charge you to do so.
All these people, structures, and paper are real. But, nowhere can you point to the larger concept of “government” or “corporation” and say, “There it is, kiddies!” The monolithic, big “they” is all in your mind.
</blockquote>
If the Mint produces a trillion-dollar coin, it’s because people designed it and people fabricated it. If Treasury deposits the coin into the Federal Reserve, it’s because someone from Treasury personally visited the mint where the coin was struck, took possession of it, carried it to the Federal Reserve, and deposited it.
There are so many ways that could go wrong.
Every person involved in this would need to be vetted sixteen ways to Sunday. No foreign allegiances, no debts, not even a whiff of past criminal activity.
And you’d need a significant number of people. Nobody gets to go alone; you’d need multiple people monitoring each other, all with bodyguards, while also trying to remain as inconspicuous as possible and not look like they’re carrying the most valuable single object in the country.
Assuming, of course, that it remains a single object. I mentioned above that the production run would be a one-off. It would be supposed to be, at least—but as soon as the die exists, it’s theoretically possible to strike a second blank and make another trillion-dollar coin. Either a counterfeit, if it doesn’t actually contain the platinum, or a duplicate if it does.
You could argue that theft or counterfeiting are not actually as big of a concern with this project as they might be with, say, one-dollar coins. Supposing you stole the trillion-dollar coin, or struck a duplicate—what could you even do with it? Nobody will accept it as tender. No commercial bank or credit union will accept it in deposit; they’d immediately phone up the Secret Service and be like “yeah we found your coin”. What could you do, put it on eBay?
<h3>Small things, easily lost</h3>
Even barring any acts of malice or greed, what if the Custodian simply… lost it?
Coulda sworn it was in that pocket.
Did it fall out when I was paying for lunch?
Hope it didn’t roll into a storm drain…
But let’s say none of that happens and the Custodian makes it to the Federal Reserve with the solution to the debt ceiling crisis safely on their person.
Then what?
When you deposit hard currency—including coin—at your local banking institution, they put it in their drawer and mark up your account. From that point, the physical coins you left behind are then eligible to hand out to any other customer in service of a withdrawal, or to be transferred between tellers or between branches. They are fungible; the bank has hundreds or thousands of them and there is no particular reason to care about the location of any single one of them.
The trillion-dollar coin would be an extremely different situation.
To be fair, it is a (mostly) solved problem. <a href="https://www.newyorkfed.org/aboutthefed/goldvault.html">The New York Federal Reserve stores gold and other reserves</a> on behalf of various governments, including the US. It may also be that other Federal Reserve Banks around the country offer similar services. The trillion-dollar coin would likely end up at any of those locations.
Buuuut there are some differences.
First, it’s not a stack of gold bars. It’s a coin. Its value wouldn’t derive from its scrap metal value (as noted above, somewhere in the 1- to 2-kilobuck range) but from its denomination.
A stack of gold bars is hard to exfiltrate. Maybe a thief could remove a bar or two (if they somehow got past all the security) without anybody noticing. It’d be an extremely high-stakes game of Jenga. (Don’t ask me for tips; everything I know about this sort of crime I learned from heist movies, and I haven’t watched many heist movies.)
A coin is, well, a coin. People regularly carry dozens of them on their person without anyone noticing. When you go through a metal detector, you dump your coins into a pile in a little plastic tray and nobody looks at it.
Where would they even keep The Coin? Do they have little safety deposit boxes at the New York Fed?
That leads to the other problem: Keeping track of it.
Somewhere there needs to be a record of where, in the New York Fed or wherever else, the coin is kept. It needs to be in a place where (theoretically) someone from Treasury could retrieve it if there were ever a need to do so, not to mention a place that could be checked if there were suspicion of theft. Of course, that would also be sensitive information; you wouldn’t want anyone in the whole organization to be able to look up where the USG’s trillion dollars is.
Some of this is, again, solved problems or otherwise not worth worrying about. It’s a bank; not a normal bank but still a bank that (one hopes) has a means to keep even something as small as a single coin in a safe place, remember where that is, and guard access to both that location and the knowledge of it. And, as I mentioned above, theft is of limited concern for a coin that there is (or should be) only one of and that no place will accept.
<hr />
<h3>On a more serious note</h3>
None of this is to say that they shouldn’t do it; that’s more of a policy and economics question. Government works on hard problems all the time, and usually does better than we give it credit for. (Especially better than libertarians give it credit for.) Success is the expectation, and I’d argue it is actually the norm, but we don’t notice it and don’t appreciate it. Failure stands out, and certain actors are ideologically motivated to spotlight it. I’m more interested in anticipating failure as a means to ensuring success.
A lot of the difficulties I’ve outlined arise from the unique nature of this particular minting job. It’s a singular coin of exceptionally high face value. Processes that are normally routine become high-stakes; hazards that are normally negligible become serious concerns.
I really hope the folks at Treasury have thought about this more than the couple of hours I put into this blog post. Because with <a href="https://www.npr.org/2023/05/01/1173148677/debt-ceiling-limit-default-standoff">less than a couple weeks left of “extraordinary measures”</a>, if the Republicans keep trying to hold the country hostage by threatening to throw it into default, we might need this to go from “wild idea” to “thing we are actually doing” in a hot second.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-05-21/trillion-dollar-pitfalls#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-05-21/trillion-dollar-pitfalls/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Radical is relative]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-05-16/radical-is-relative" />
<id>https://boredzo.org/blog/?p=1846</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-05-16T18:48:56Z</published>
<category scheme="https://boredzo.org/blog" term="Politics" />
<summary type="html"><![CDATA[This was originally posted as a tweet thread in September 2019, back when Sen. Elizabeth Warren was a Presidential candidate advocating for a wealth tax. I have lightly edited it, mostly to account for the change in format plus a few other tweaks, but otherwise this is as I posted it then. I went looking […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-05-16/radical-is-relative"><![CDATA[This was originally posted as a <a href="https://twitter.com/boredzo/status/1176163659531206656">tweet thread</a> in September 2019, back when Sen. Elizabeth Warren was a Presidential candidate advocating for a wealth tax. I have lightly edited it, mostly to account for the change in format plus a few other tweaks, but otherwise this is as I posted it then.
<hr />
I went looking at <a href="https://web.archive.org/web/20190914183712/https://elizabethwarren.com/ultra-millionaire-tax/">Senator Warren’s wealth tax proposal</a>.
Two things.
First: Wealth taxed includes “residences, closely held businesses, assets held in trust, retirement assets, assets held by minor children, and personal property with a value of $50,000 or more”.
I was looking at this because I was wondering how much it would apply to (as an example) <a href="https://www.forbes.com/profile/jeff-bezos/">Jeff Bezos</a>. Bezos has a big pile of Amazon shares, but not a majority stake, so it’s not “closely held”. Not sure if any other criteria (e.g., trust) would cover it.
I like the wealth tax idea (though I’m sure it’ll get challenged in court if it ever happens) but want it to go farther: Include all stock directly held.
IMO, holding more than $50 million in stock should qualify you to start paying 2% of the overage as real money in tax.
Like, I would consider not wealth-taxing all stock to be a big loophole leaving a shit ton of money—and of “oh shit, gotta stop hoarding wealth” effects—on the table.
Bezos’s wealth-taxed net worth should be ~$110 billion [as of September 2019], not some number of millions.
Second: Senator Warren’s proposed wealth tax (somewhat famously but I probably shouldn’t neglect to mention it) kicks in at $50 million.
So imagine a thermometer. All them assets—your nine houses, $51,000 car, etc.—fill up the thermometer. If it doesn’t reach $50 million, you’re not wealth-taxed. But if it does pass $50 million, every dollar of total assets after that gets taxed 2%.
So if you have $50,000,000.00, you pay $0 tax—not $1 million.
If you have $50,000,001.00, you pay 2¢.
(Disclaimer: I am not a tax attorney.)
So both observations are why I think Senator Warren’s proposal is a moderate plan. A truly radical, socialist, wealth-redistributing proposal could go much farther!
I still like it. This isn’t an anti-Warren <del>thread</del> post by any means.
All’s I’m saying is: Fight for this, then fight for more.
<hr />
Always remember the frame of reference you evaluate something in.
In our society, billionaires are normal. Low income tax rates upon them: normal. $billion corps paying $0 tax: normal.
Senator Warren’s proposal seems radical because it is: It’s corrective action to a tilted economy.
It’s radical in the sense that it is a significant deviation from the status quo. A change. No more full speed ahead—here we turn left.
Repealing past tax cuts is also a change. But less radical.
A more expansive wealth tax? More radical.
Radical is a spectrum.
So reject the idea that “radical” is necessarily bad—radical is just change. What change? That’s what matters.
How much is warranted? How much is too much? How much is not enough?
How much should we fight for, how much should we accept, how much more should we fight for after?
Senator Warren’s wealth tax is radical. It is also moderate.
It is corrective action on a damaged economy. A change, and I think a necessary one.
It could go farther. It’s a good start.
I hope it gets enacted. And I hope it gets improved.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-05-16/radical-is-relative#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-05-16/radical-is-relative/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Moving away from algorithmic curation]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2023-04-24/moving-away-from-algorithmic-curation" />
<id>https://boredzo.org/blog/?p=1843</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2023-04-24T23:28:04Z</published>
<category scheme="https://boredzo.org/blog" term="Society" />
<summary type="html"><![CDATA[This was originally posted as a tweet thread back in November 2019, which is why it starts off with some suggestions about how best to use Twitter that are irrelevant now, since Twitter was killed by a dipshit billionaire with more money than sense and it took out the third-party clients in its death throes. […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2023-04-24/moving-away-from-algorithmic-curation"><![CDATA[This was originally posted as a <a href="https://twitter.com/boredzo/status/1198484860446203905">tweet thread</a> back in November 2019, which is why it starts off with some suggestions about how best to use Twitter that are irrelevant now, since <a href="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter">Twitter was killed by a dipshit billionaire with more money than sense</a> and it took out the third-party clients in its death throes. But the rest of the thread holds up and I felt it worth resurrecting.
<hr />
<ul>
<li>Tired: Helping Twitter refine its algorithmic profiling.</li>
<li>Wired: Switching to reverse-chronological timeline, as persistently as Twitter makes necessary.</li>
<li>Inspired (but admittedly not available to all): Switching to a good third-party client like Tweetbot or Twitterrific.</li>
</ul>
A few weeks ago, I saw a tweet from someone who’d switched to the algorithmic timeline experimentally and saw absolutely nothing about a then-current major news event that folks they followed had been tweeting about.
I still think about that.
It increasingly seems to me that the best things you can do with these services—recommendation engines, algorithmic timelines, and such—is (1) don’t use them when you can help it, and (2) lie to them at every opportunity.
Poison the well, and don’t drink from it.
I say this because we need to re-learn how to find each other, to recommend things ourselves, and to try each other’s personally-offered recommendations.
These are things that we should not give up to the control of companies, nor any other unknowable, unaccountable entity.
This also comes out of my thoughts about Twitter itself. And the degree to which social media has replaced RSS as our means of receiving fresh content.
It’s been good in some ways. Some of us have learned a lot, met new folks.
But we can’t depend on this.
We can’t depend on getting more of what we’ve expressed we want, if the algorithmic timeline can override that.
We can’t depend on discovering new things (and good ones, not bad ones) because the algorithm is unaccountable, built on profiling, and only seeking engagement.
A discovery algorithm’s job is to introduce people to things they don’t know they want or need.
How do you do this without introducing them to fascism, outrage fuel, shock content, or other trash? Without humans seeing that shit to screen it out?
How do you do this ethically?
Assuming the answer is “you can’t”, we then need to take up the mantle ourselves.
Spread positive things. Things you’ve made. Things you’ve learned. Skills, ideas, thoughts, actions.
This must include anti-fascism, the only other alternative being silent neutrality.
And we’ll need to use social media as best we can as long as we can, because of its amplifying nature, but we must also re-learn the other ways, the older ways. Online and off.
The old ways still work.
Print still works.
Person-to-person still works.
It’s gonna be hard to break dependency on social media, because of network effects and because of the addictive nature of it.
We probably need to start DMing each other email addresses, for a start.
And regularly contacting each other, Christmas-card style.
We’re going to need to make some changes in order to not keep heading down the same directions we’re currently going.
Not just “we” in the first person but “we” as in society. What “we” in the first person do must be chosen with that goal in mind.
I do hope, though, that whatever we ultimately replace social media with, it still has cats.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2023-04-24/moving-away-from-algorithmic-curation#comments" thr:count="3" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2023-04-24/moving-away-from-algorithmic-curation/feed/atom" thr:count="3" />
<thr:total>3</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Grieving Twitter]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter" />
<id>https://boredzo.org/blog/?p=1837</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2022-12-13T06:36:46Z</published>
<category scheme="https://boredzo.org/blog" term="@Uncategorized" />
<summary type="html"><![CDATA[Some have analogized Twitter to a sinking ship, while others have expressed anger that folks are leaving when Twitter has been so important—even life-saving—to so many. Thing is… Twitter (the company, and very likely the website) is a sinking ship. That much is indisputable at this point. It’s dying*. When you’re on a sinking ship, […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter"><![CDATA[Some have analogized Twitter to a sinking ship, while others have expressed anger that folks are leaving when Twitter has been so important—even life-saving—to so many.
Thing is… Twitter (the company, and very likely the website) is a sinking ship. That much is indisputable at this point. It’s dying<a id="fn_grievingtwttr_1_orig" href="#fn_grievingtwttr_1">*</a>.
When you’re on a sinking ship, you either sprout gills or swim for it (metaphorically). The ship is going down and you will be underwater unless you leave.
(You can decide for yourself what “underwater” means in the context of Twitter. In fact, I encourage you to: What is your red line? What conditions—including both destruction of things you got from Twitter and establishment of things you abhor—would cause you to leave?)
So folks have been leaving, mainly to Mastodon and some to Cohost; I’m not surprised by the skew toward Mastodon, since Mastodon is much more Twitter-like, whereas Cohost is more Tumblr-like. There’s also Post.news, which I haven’t looked deeply at since <a href="https://twitter.com/parismarx/status/1597008855652712449">they’ve been openly disinterested in making their website accessible</a>.
All of this means that Twitter (the community) is dead.
Not dying. Already dead.
A community is made of its people first, and the tools available to them second. The community that was pre-Musk Twitter is sundered; split between new websites with different tools, and the old website that is in its death throes. Many of the people have gone, and their tools have changed.
Both Mastodon and Cohost have Content Warnings, a tool created to meet the needs of people with PTSD and anxiety. Both have longer content limits (Cohost has no limit at all), to enable more expressivity. Both have better visibility control, to reduce context collapse. Both have no discovery algorithm, so you entirely control what you see—you see what folks you follow have published or boosted, and nothing else. Both have search for tags only, not full text, to thwart name-search brigades.
The change in people and the change in tools will create new communities, in all these places.
Twitter is already not the same place it was just a couple of months ago. It will never be that place again. (In some sense this is always true; you never cross the same river twice.) That threshold has been crossed; the Twitter we lost, is lost.
It’s not on Mastodon, either. Mastodon is technologically similar, but not the same, as I already listed off. The set of people is different, partly because of the people who joined it years ago and haven’t been part of Twitter for some time, and partly because not everybody’s come over yet (and some won’t, or have left). Some folks have been making different following decisions there than on Twitter, so the social graph is different.
Each is now a new community.
Mastodon is not the new Twitter; it is the closest extant thing to the old Twitter, but still different. On Twitter, what’s left of the old community remains (though, as I write this, further events have caused another wave of people to say “fuck this, I’m out”) and those who remain will ride the ship into the deep, until “sprout gills” becomes truly the only alternative to leaving.
Cohost is an entirely different thing, since even before its launch. It’s a good thing; I like it there. It is not trying to be Twitter, and in some ways it is trying not to be Twitter, and on both fronts it is succeeding.
And while I call each site a community, communities are rather smaller than that. Each community is many communities, with blurry edges. Maybe the Fediverse or Cohost or some other alternative wasn’t right for you the first time, or even the second, but maybe the right mix of people is there now, ready for you to find them. And some of us are on both, to varying degrees.
Mourn the communities we have lost, and choose what communities you’ll be part of.
* I would be remiss if I neglected to mention that Twitter is not simply dying as if by consumption; it is being murdered by a dipshit billionaire with more ego than sense. Twitter’s death was foul play. None of this had to happen; a billionaire did it to us. <a href="#fn_grievingtwttr_1_orig">↶</a>
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter#comments" thr:count="1" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2022-12-12/grieving-twitter/feed/atom" thr:count="1" />
<thr:total>1</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Props D and E (2022-10)]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2022-10-30/props-d-and-e-2022-10" />
<id>https://boredzo.org/blog/?p=1833</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2022-10-30T16:01:51Z</published>
<category scheme="https://boredzo.org/blog" term="Politics" />
<summary type="html"><![CDATA[If you aren’t a San Francisco voter, this post is going to be academic to you. I’ve filled out my entire ballot by this point, except for two of the local propositions, on which I’ve been dithering: Prop D and Prop E. The two are set against each other, and in fact one is a […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2022-10-30/props-d-and-e-2022-10"><![CDATA[If you aren’t a San Francisco voter, this post is going to be academic to you.
I’ve filled out my entire ballot by this point, except for two of the local propositions, on which I’ve been dithering: <a href="https://voterguide.sfelections.org/en/affordable-housing-–-initiative-petition">Prop D</a> and <a href="https://voterguide.sfelections.org/en/affordable-housing-–-board-supervisors">Prop E</a>.
The two are set against each other, and in fact one is a modification of the other. They’re similar enough that it’s possible to <a href="https://twitter.com/boredzo/status/1584779510213271552">diff them</a>, although doing that didn’t clarify as much as I’d hoped it would.
Part of the problem for me is that I know precious little about housing policy. I am neither a developer employee nor a tenant advocate. I’m just another San Francisco voter trying to make sense of this mess.
The resources I’ve been drawing upon are:
<ul>
<li><a href="https://voterguide.sfelections.org/en/local-ballot-measure-and-argument-information-0">The official San Francisco voter guide</a>, all the way down to the legal text of the measures (which is what I diffed)</li>
<li><a href="https://www.spur.org/news/2022-07-28/whats-real-difference-between-san-franciscos-two-affordable-housing-ballot-measures">SPUR’s detailed but overtly biased comparison</a> (SPUR being one of the sponsors of Prop D)</li>
<li><a href="https://www.theleaguesf.org/Nov_2022#PropDE">The League of Pissed-Off Voters’s less-detailed but contrary analysis</a></li>
</ul>
I really wish I had something like a Prop E version of SPUR’s article: a detailed, policy-wonk explanation of why E is better and will get housing built without screwing the low end of the market. Sadly, I have not found any such thing. The League’s argument is the best I’ve got on the Prop E side.
What I have is the following overall sense, and enough awareness of my own housing-policy ignorance to warn you that half of this might be wrong:
The shared goal of these propositions is to cut red tape. Housing development is often held up on a number of processes, including CEQA (California Environmental Quality Act) review and discretionary review by the Board of Supervisors.
The upside of these processes is that they’re used to drag developers kicking and screaming into building affordable housing so that the low end of the market—people who can’t afford market-rate housing—don’t get left out and priced out.
The downside of these processes is that the developers, as you might have gathered, don’t want to build affordable housing for people who can’t pay market rate, so they keep on dragging their feet, and if the process goes on long enough, sometimes they’ll sell out and profit off the appreciation of the land value rather than actually build any housing, setting everything back at square one.
(That downside is, from what I can tell, what YIMBYs refer to when they label Supervisors who vote down unaffordable housing projects as “anti-housing”. If you aren’t letting developers build whatever they want so it can <a href="https://twitter.com/katewillett/status/1584678773622177793">trickle down</a>, you must not want any housing to exist at all.)
What Props D and E have in common is, they both cut through some of that red tape to get affordable housing projects from plans on paper to shovels in ground faster. (D calls it “streamlining”; E calls it “acceleration”. I have no idea what that change was meant to signify.)
There we start to get into the differences.
Prop D cuts through more red tape than E does. In particular, E (the Board of Supervisors’ prop) leaves the Board’s discretionary review power intact. That then means, according to <a href="https://www.spur.org/news/2022-07-28/whats-real-difference-between-san-franciscos-two-affordable-housing-ballot-measures">SPUR’s comparison</a>, that these projects are subject to CEQA review.
It does seem to me that holding dense, multi-family housing up on CEQA review makes no fucking sense. SPUR notes that CEQA applies to housing in order to help curb sprawl, which does make sense, but dense urban housing getting caught in that seems like a bug worth fixing. The environmental impact is hopefully some people will get to live closer to where they work and take transit instead of highways. I consider taking CEQA review out of the way of building housing in cities to be a desirable goal.
Moreover, both props apply only to affordable housing projects (but not all the same ones; I’ll address that in a moment). Why should Prop E preserve discretionary review and thus CEQA review on <a href="https://codelibrary.amlegal.com/codes/san_francisco/latest/sf_planning/0-0-0-62348#JD_206.9">100% Affordable Housing Projects</a>? What’s to review? It should be a rubber stamp.
So the trade-off Prop E makes is that it leaves some pretty big knots of red tape still in place.
Prop D makes a different trade-off, which has become one of the principal arguments against it (it certainly features prominently in the League’s analysis): Prop D greatly expands the set of “affordable housing” that it would apply to, well beyond housing affordable to the low end of the market.
(The Voter Information Pamphlet’s <a href="https://voterguide.sfelections.org/en/affordable-housing-–-initiative-petition">summary of Prop D</a> and <a href="https://voterguide.sfelections.org/en/affordable-housing-–-board-supervisors">summary of Prop E</a> include breakdowns of what “affordable housing” projects they would “streamline”/“accelerate”.)
SPUR, one of the sponsors of the measure, is explicit about this as a goal in <a href="https://www.spur.org/news/2022-07-28/whats-real-difference-between-san-franciscos-two-affordable-housing-ballot-measures">their comparison</a>:
<blockquote>
Prop. D would expand the streamlining to include moderate and middle-income households. A 100% affordable project that provides an average affordability level of 120% of the Area Median Income (AMI) would be eligible for streamlining, compared to 80% AMI Income under state law. Under Prop. D, this would allow 100% affordable housing projects to also include some middle-income units for households making up to 140% of AMI.
</blockquote>
So the trade-off Prop D makes is that developers get to build “affordable housing” for a more profitable segment of the market, but that might mean people at the low end get screwed.
In summary:
<ul>
<li>Prop D cuts through more red tape, but has what might be an overly generous definition of “affordable housing”.</li>
<li>Prop E leaves Supervisorial power to hold up housing projects intact, but uses the existing, stricter definition of “100% affordable housing”.</li>
</ul>
Ultimately, what I want is something of a mix of the two. I want Prop E’s explicit effort to promote housing for the low end of the market that developers are eager to make Somebody Else’s Problem, but without Supervisorial review because why do you need it on projects that are already “100% affordable” by definition.
But that isn’t on the ballot, so I’m left with these choices:
<ul>
<li>Vote for Prop D and hope the trickle-down fallacy doesn’t screw poorer residents too hard.</li>
<li>Vote for Prop E and hope the developer lobby’s veiled threats that this will stop housing production don’t come to pass.</li>
<li>Vote for both of them, if I consider either one to be an improvement over the status quo. The perfect is the enemy of the good, so maybe it’s better to just pass one of them now. (If both pass, whichever one gets more votes wins.)</li>
<li>Vote against both of them, and hold out for my ideal proposition, which will definitely land on some future ballot through no action on my part.</li>
</ul>
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2022-10-30/props-d-and-e-2022-10#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2022-10-30/props-d-and-e-2022-10/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
<entry>
<author>
<name>Peter Hosey</name>
<uri>http://boredzo.org./</uri>
</author>
<title type="html"><![CDATA[Dash mini rice-cooker review]]></title>
<link rel="alternate" type="text/html" href="https://boredzo.org/blog/archives/2022-09-24/dash-mini-rice-cooker-review" />
<id>https://boredzo.org/blog/?p=1831</id>
<updated>2024-04-07T05:07:45Z</updated>
<published>2022-09-25T05:29:27Z</published>
<category scheme="https://boredzo.org/blog" term="Reviews" />
<summary type="html"><![CDATA[I originally wrote this review on the product listing on Target’s website, but unfortunately Target’s website isn’t really designed for reviews longer than a paragraph. So here’s the Director’s Cut. Ratings Overall: 3 out of 5 Design: 3 out of 5 Quality: 4 out of 5 Ease of use: 2 out of 5 Easy to […]]]></summary>
<content type="html" xml:base="https://boredzo.org/blog/archives/2022-09-24/dash-mini-rice-cooker-review"><![CDATA[I originally wrote this review on <a href="https://www.target.com/p/dash-2-cup-electric-mini-rice-cooker/-/A-87389843?preselect=85378064">the product listing on Target’s website</a>, but unfortunately Target’s website isn’t really designed for reviews longer than a paragraph. So here’s the Director’s Cut.
<h3>Ratings</h3>
<ul>
<li>Overall: 3 out of 5</li>
<li>Design: 3 out of 5</li>
<li>Quality: 4 out of 5</li>
<li>Ease of use: 2 out of 5</li>
<li>Easy to clean: 5 out of 5</li>
<li>Value: 4 out of 5</li>
</ul>
<h3>Pros:</h3>
<ul>
<li>Yup, it’s smol.</li>
<li>The lid and pot are dishwasher safe.</li>
<li>The pot is non-stick and indeed the rice did not stick.</li>
<li>Comes with a rice-measuring cup (160 ml) and rice paddle.</li>
</ul>
And it does make pretty good rice, assuming you get the ratio correct. If you like yours a little crispy on the bottom, this’ll do you well. If not… well, me either, but we’ll live.
<h3>Cons:</h3>
<ul>
<li>First thing out of the box, I had to repair the lid, which was assembled incorrectly. (The lid screw was drilled into the knob off-center. I unscrewed it and screwed it into the hole it was supposed to be in.)</li>
<li>The rice-making instructions are almost useless. Like most rice cookers, they tell you to measure the rice using the provided 160-ml cup. But then they give you the rice:water ratios in terms of US 240-ml cups! Treat them as ratios; for white rice, 160 ml of dry rice needs 200 ml of water. (You could use a regular measuring cup, or use the rice cup to measure 160 ml of water and then 40 more.)</li>
<li>The marks on the inside of the bowl are completely useless. They’re labeled as “0.5 cup” and “1 cup”. They’re actually 1.5 and 2 US cups! Pour in water up those lines and then pour it out into a 2-cup measuring cup and you’ll see. The “1 cup” line marks how much rice you’ll get from 1 rice-cup of dry rice—which is exactly no help when trying to measure the rice or the water in the first place. If you dump in water up to that line, it’ll be way too much. (Remember, the right amount of water for that much white rice is 200 ml. 2 US cups is 480 ml!) I knocked a star off of “Ease of use” for this.</li>
<li>The LEDs are surprisingly dim. In a bright kitchen, it’s hard to tell whether it’s on Cook or Warm.</li>
<li>There’s no on/off switch, so plugging it in immediately turns on Warm mode. Fairly typical of low-end rice cookers like this one. You may want to get a <a href="https://www.acehardware.com/switches/3189842">switch tap</a> if you’d like to leave it plugged in.</li>
</ul>
<h3>Conclusion</h3>
Soooo there’s a bit of homework. But once that’s all sorted, it works fine. Made decent rice.
Bonus tip that I didn’t mention in the Target review: Add one-quarter teaspoon of garlic salt to the rice+water for tasty garlic rice.
]]></content>
<link rel="replies" type="text/html" href="https://boredzo.org/blog/archives/2022-09-24/dash-mini-rice-cooker-review#comments" thr:count="0" />
<link rel="replies" type="application/atom+xml" href="https://boredzo.org/blog/archives/2022-09-24/dash-mini-rice-cooker-review/feed/atom" thr:count="0" />
<thr:total>0</thr:total>
</entry>
</feed>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

Download the "valid Atom 1.0" banner.
Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)
Add this HTML to your page (change the image src attribute if necessary):

<a href="http://www.feedvalidator.org/check.cgi?url=http%3A//boredzo.org/blog/feed/atom/"><img src="valid-atom.png" alt="[Valid Atom 1.0]" title="Validate my Atom 1.0 feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//boredzo.org/blog/feed/atom/

Home · About · News · Docs · Terms