<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: 0907</title><link>https://news.ycombinator.com/user?id=0907</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Fri, 10 Apr 2026 04:42:37 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=0907" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by 0907 in "Bitmap fonts make computers feel like computers again"]]></title><description><![CDATA[
<p>I've dabbled a few times in writing bitmap font parsers for both technically constrained and artistic projects. There is a reason that design has resolved to the same few cliches, because expectability, latent understanding, and 'obviousness' reduces onboarding curve and fatigue. It's a cognitive accessibility issue before you even get to legitimate accessibility concerns. Render a .F16 at anything larger than 16px in a modern application and you're introducing issues which are solved, quantitatively and qualitatively, by vector graphics and antialiasing. There's an optimistic naivety which is nice to have, but misunderstands design as a conduit for informed action vs design as an aesthetic function independent of intent is legitimately dangerous if you're doing anything other than building narrative products emulating older tech.</p>
]]></description><pubDate>Thu, 09 Apr 2026 20:31:33 +0000</pubDate><link>https://news.ycombinator.com/item?id=47709516</link><dc:creator>0907</dc:creator><comments>https://news.ycombinator.com/item?id=47709516</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47709516</guid></item><item><title><![CDATA[New comment by 0907 in "Show HN: Hackerbrief – Top posts on Hacker News summarized daily"]]></title><description><![CDATA[
<p>Something I've been tinkering on for the last few weeks is absent.dev[1], was working towards getting the guts to share this on HN but there's a few things I want to polish first. This is the MVP, but it will essentially be moving towards what you're suggesting, much more customisable news aggregation and more importantly, where <i>you</i> consume it. Feed agnostic, channel agnostic, in the form(s) you want (longform, shortform, summary, tl;dr etc). You can check the clustering logic on the digest[2].<p>1. <a href="https://absent.dev/" rel="nofollow">https://absent.dev/</a>
2. <a href="https://absent.dev/episode/ABS-0014/clusters" rel="nofollow">https://absent.dev/episode/ABS-0014/clusters</a></p>
]]></description><pubDate>Mon, 16 Mar 2026 14:00:39 +0000</pubDate><link>https://news.ycombinator.com/item?id=47399158</link><dc:creator>0907</dc:creator><comments>https://news.ycombinator.com/item?id=47399158</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=47399158</guid></item><item><title><![CDATA[New comment by 0907 in "Components will kill pages"]]></title><description><![CDATA[
<p>I think that the inverse thesis is true, you make websites more accessible (a11y, wgac, aria labels etc) for humans, then the interaction heuristics are clearer for agents functioning off browser-use or similar. If a screen reader can understand your site, then an agent can. Reinventing the wheel to facilitate the current state of agents makes the web worse for everyone, it's not a preemptive move, it's actually a decline in almost objective and measurable quality, and potentially one which removes access to the internet by people who just want to.. use the internet.</p>
]]></description><pubDate>Thu, 12 Feb 2026 00:13:30 +0000</pubDate><link>https://news.ycombinator.com/item?id=46983120</link><dc:creator>0907</dc:creator><comments>https://news.ycombinator.com/item?id=46983120</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46983120</guid></item></channel></rss>