<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ThinkPad X1 Carbon Gen 10 (Carbon Fiber + Magnesium) on Jaspers Archive</title><link>https://jas.pe/gear/thinkpad-x1-carbon-gen-10/</link><description>Recent content in ThinkPad X1 Carbon Gen 10 (Carbon Fiber + Magnesium) on Jaspers Archive</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 24 Jul 2026 03:06:42 +0000</lastBuildDate><atom:link href="https://jas.pe/gear/thinkpad-x1-carbon-gen-10/index.xml" rel="self" type="application/rss+xml"/><item><title>NotifPWA</title><link>https://jas.pe/posts/notifpwa/</link><pubDate>Fri, 24 Jul 2026 03:06:42 +0000</pubDate><guid>https://jas.pe/posts/notifpwa/</guid><description>&lt;p&gt;I ran into this issue that notifications could not easily be sent to my phone. I wanted something like &lt;code&gt;ntfy&lt;/code&gt;, but self-hosted to keep my infrastructure mine.
The issue with self-hosting &lt;code&gt;ntfy&lt;/code&gt; is that push-notifications do not work &lt;em&gt;(as of 24/07/2026)&lt;/em&gt; on iOS, because Apple™ loves doing things &lt;em&gt;differently&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://support.apple.com/en-au/101566"&gt;&lt;code&gt;iOS 16.4+&lt;/code&gt; supports Web Notifications as long as the site is a PWA&lt;/a&gt;. This is something I can use.&lt;/p&gt;
&lt;h1 id="what-is-a-pwa"&gt;
 &lt;a href="#what-is-a-pwa" class="heading-anchor"&gt;What is a &amp;ldquo;PWA&amp;rdquo;?&lt;/a&gt;
&lt;/h1&gt;
&lt;p&gt;A &amp;ldquo;&lt;em&gt;PWA&lt;/em&gt;&amp;rdquo; is similar to an App, it can be used like an app, added to the home screen, and offer other platform specific benefits, without getting into the nitty-gritty:
You can use it as if it is an app, built for the platform you are on. What makes it different though is that traditionally websites are experienced more as a place you can visit, other than a place you have. A website doesn&amp;rsquo;t (typically) have a presence on the user&amp;rsquo;s device, instead it is requested / accessed by a browser.&lt;/p&gt;</description></item><item><title>chatto.ts: Strictly typed Chatto Framework</title><link>https://jas.pe/posts/chatto.ts/</link><pubDate>Thu, 16 Jul 2026 01:19:59 +0000</pubDate><guid>https://jas.pe/posts/chatto.ts/</guid><description>&lt;p&gt;Last week, I was doing my usual browsing of &lt;a href="https://news.ycombinator.com"&gt;ycombinator&lt;/a&gt;, when I came across a post that read &lt;a href="https://news.ycombinator.com/item?id=48833116"&gt;Chatto is now open source&lt;/a&gt;, which caught my attention, especially because the post (at the time of writing) had over 1100 points, so I had to look at what all the fuss was about.&lt;/p&gt;
&lt;p&gt;I checked out the post, and it was immediately filled with &lt;em&gt;incredible- if true&lt;/em&gt; claims, such as &lt;strong&gt;&amp;ldquo;extremely easy to self-host&amp;rdquo;&lt;/strong&gt;, &lt;strong&gt;&amp;ldquo;very light on resources&amp;rdquo;&lt;/strong&gt;, &lt;strong&gt;&amp;ldquo;snappiest frontend that you’ve ever used in an app like this&amp;rdquo;&lt;/strong&gt;, &lt;strong&gt;&amp;ldquo;fully encrypted at rest&amp;rdquo;&lt;/strong&gt;, and &lt;strong&gt;&amp;ldquo;voice and video calls&amp;rdquo;&lt;/strong&gt;.
Now this wouldn&amp;rsquo;t be the first time something like this pops up and it ends up being a lot less than what you would&amp;rsquo;ve wanted, or a garbled mess of AI slop that does not work in the slightest.&lt;/p&gt;</description></item><item><title>Moving to Hugo</title><link>https://jas.pe/posts/hugo/</link><pubDate>Tue, 23 Jun 2026 15:16:49 +0800</pubDate><guid>https://jas.pe/posts/hugo/</guid><description>&lt;h1 id="why"&gt;
 &lt;a href="#why" class="heading-anchor"&gt;Why?&lt;/a&gt;
&lt;/h1&gt;
&lt;h2 id="the-beginning-of-trouble"&gt;
 &lt;a href="#the-beginning-of-trouble" class="heading-anchor"&gt;The beginning of trouble&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;On my previous site, I had written my own frontmatter interpreter to make blogging easy.
I did not like the complexity or feel that existing options like wordpress provided, and I did not Google much longer than 30 seconds to see if the tool I was looking for already existed.
So I had coded one, from scratch&amp;hellip; That went predictably horribly and I had to continually make changes just to accomodate new features I didn&amp;rsquo;t think of initially.&lt;/p&gt;</description></item></channel></rss>