June 2025 updateHEADmaster

6 files changed, 149 insertions, 44 deletions

diff --git a/_posts/june_08_2025.org b/_posts/june_08_2025.org
new file mode 100644
index 0000000..0a9bc8f
--- /dev/null
+++ b/_posts/june_08_2025.org
@@ -0,0 +1,25 @@
+:PROPERTIES:
+:ID:       c397a1c8-5980-419d-88d4-a3c9782343d5
+:END:
+#+TITLE: Update June 08, 2025
+#+DATE: <2025-06-08 Sun 15:30>
+#+filetags: :update:
+
+* What have I been up to?
+Another month has gone by, so I guess it's time to see what I've been up to.
+
+Canonical hosted our company's sprint in Frankfurt, Germany during the month of May. It was a very productive time for the whole team. I always enjoy seeing everyone in person, talking through big issues face-to-face, and exploring a new city. I also got to spend some time in Zurich, Switzerland before the sprint began. Zurich is pretty awesome 🏔️!
+
+In miracle-wm, I have been going down quite the rabbit-hole🐇! What began as a plan to fix the remaining warnings in the source code has snowballed into me implemnenting the rest of the IPC mechanism and testing the entire thing. This has been no small feat, as both sway and i3 implement a _lot_ of different commands, and a failure to implement any one of them often leads to half-broken clients. I've had to make some "executive" decisions to ignore parts of the protocol that I deem irrelevant now (especially many of the X-specific bits), but it is a mostly compatible implementation. The good news is that I've nearly completed this journey and should be ready to release version ~0.6.0~ some time in the middle of June.
+
+Miracle is getting closer-and-closer to my vision of it every day. The only problem right now is finding the bandwidth to implement everything that I have in my head :)
+
+On the Mir side of things, I am still implementing the magnifier glass accessibility feature from before, but with a much-improved technical direction that we arrived at during our time in Frankfurt. Unfortunately, this required a quick detour to properly implement the ~overlay_cursor~ flag of [[https://wayland.app/protocols/wlr-screencopy-unstable-v1#zwlr_screencopy_manager_v1:request:capture_output:arg:overlay_cursor][zwlr_screencopy_manager_v1::capture_output_region]], as both screencopy and magnification rely on this same code path. The good news is that I'm quite close on this and it should be landing in full any day now 🤞
+
+I also fixed [[https://github.com/canonical/mir/pull/3968][this very breaking bug]] that was actively preventing miracle from rendering on my second monitor, so that's good.
+
+On addition to these two projects, I am also reinvolving myself in the Flutter multi-window work. For those who don't know, we're trying to make it so that the Flutter toolkit can render to multiple surfaces. This is no small feat, as Flutter was originally written with the assumption that only a single "view" would ever be drawn too. However we've managed to make some great progress on it thus far, and we're very excited to land the first pull request imminently with the help of the folks over a Google!
+
+I hope you're having a great and productive summer 😎
+
+
diff --git a/_posts/sitemap.org b/_posts/sitemap.org
index bd0f976..4cef4e1 100644
--- a/_posts/sitemap.org
+++ b/_posts/sitemap.org
@@ -1,11 +1,15 @@
 #+TITLE: Matthew's Blog Posts
 
-#+DATE: 2025-05-22 at 09:02
+#+DATE: 2025-06-08 at 15:35
 
 #+HTML_LINK_HOME: /
 
 #+HTML_LINK_UP: /
 
+- [[file:june_08_2025.org][Update June 08, 2025]] created on June 08, 2025
+  #+begin_sitemap_tag
+  update
+  #+end_sitemap_tag
 - [[file:may_06_2025.org][Update May 06, 2025]] created on May 06, 2025
   #+begin_sitemap_tag
   update
diff --git a/posts/hello.html b/posts/hello.html
index 7a62e80..ec10db2 100644
--- a/posts/hello.html
+++ b/posts/hello.html
@@ -26,9 +26,9 @@
   </div>
 </div>
 <div id="content" class="content">
-<div id="outline-container-orgc6f1d20" class="outline-2">
-<h2 id="orgc6f1d20">TLDR</h2>
-<div class="outline-text-2" id="text-orgc6f1d20">
+<div id="outline-container-orgbec5765" class="outline-2">
+<h2 id="orgbec5765">TLDR</h2>
+<div class="outline-text-2" id="text-orgbec5765">
 <ul class="org-ul">
 <li>Create a new folder</li>
 <li>Put <a href="https://raw.githubusercontent.com/mattkae/matthewkosarek-xyz/master/index.css">index.css</a>, <a href="https://raw.githubusercontent.com/mattkae/matthewkosarek-xyz/master/publish.el">publish.el</a>, and <a href="https://github.com/mattkae/matthewkosarek-xyz/blob/master/publish.sh">publish.sh</a> in the folder</li>
@@ -42,9 +42,9 @@
 </ul>
 </div>
 </div>
-<div id="outline-container-orgf0fd8f0" class="outline-2">
-<h2 id="orgf0fd8f0">Introduction</h2>
-<div class="outline-text-2" id="text-orgf0fd8f0">
+<div id="outline-container-orgb717615" class="outline-2">
+<h2 id="orgb717615">Introduction</h2>
+<div class="outline-text-2" id="text-orgb717615">
 <p>
 I've recently fallen in love with <code>org-mode</code>, specifically when I use it with <a href="https://www.orgroam.com/">org-roam</a>. I find the whole workflow of creating, tagging, and - later on - searching for information on my computer to be very elegant. On top of that, now that I have the time, I want to begin writing blog posts to better work out my thoughts. With both of these things in mind, I am again turning to the universal tool for human prospering: <code>org-mode</code>. This time, I want to see how it can help me turn a simple org file into a blog post on my website. My requirements are:
 </p>
@@ -67,9 +67,9 @@ And that's pretty much it for now. Without further ado, let's jump into getting
 </p>
 </div>
 </div>
-<div id="outline-container-orgc203944" class="outline-2">
-<h2 id="orgc203944">Basic HTML File</h2>
-<div class="outline-text-2" id="text-orgc203944">
+<div id="outline-container-org1ccbbae" class="outline-2">
+<h2 id="org1ccbbae">Basic HTML File</h2>
+<div class="outline-text-2" id="text-org1ccbbae">
 <p>
 As a pilot, we are going to use this org file that I am currently writing (<code>hello.org</code>) as our guinea pig. The goal is to have this org file be our very first blog post.
 </p>
@@ -109,9 +109,9 @@ We then do a <code>chmod +x publish.sh</code> to make it an executable and run i
 </p>
 </div>
 </div>
-<div id="outline-container-orgb5be820" class="outline-2">
-<h2 id="orgb5be820">Disabling features that we don't want</h2>
-<div class="outline-text-2" id="text-orgb5be820">
+<div id="outline-container-orga8b7149" class="outline-2">
+<h2 id="orga8b7149">Disabling features that we don't want</h2>
+<div class="outline-text-2" id="text-orga8b7149">
 <p>
 The next thing will be to remove some of the generated items that I didn't ask for, namely the table of contents, author, section numbers, creation time stamp, and the validation link.
 </p>
@@ -140,9 +140,9 @@ The next thing will be to remove some of the generated items that I didn't ask f
 </div>
 </div>
 </div>
-<div id="outline-container-org8316009" class="outline-2">
-<h2 id="org8316009">Styling &amp; Code Highlighting</h2>
-<div class="outline-text-2" id="text-org8316009">
+<div id="outline-container-org0d2b040" class="outline-2">
+<h2 id="org0d2b040">Styling &amp; Code Highlighting</h2>
+<div class="outline-text-2" id="text-org0d2b040">
 <p>
 Next thing on our list is custom styling. This can be achieved by first installing the <code>htmlize</code> package from <code>melpa</code> / <code>elpa</code>.  The EmacsWiki describes this as "a package for exporting the contents of an Emacs buffer to HTML while respecting display properties such as colors, fonts, underlining, invisibility, etc" (<a href="https://www.emacswiki.org/emacs/Htmlize">reference</a>). If used "out-of-the-box", the buffer will be exported to HTML with all of the styles inlined (e.g. if you underline something in your org file, you will generate a <code>&lt;span style="text-decoration: underline"&gt;...&lt;/span&gt;</code>).  However, we are more interested in styling everything by ourselves: we don't want <code>htmlize</code> making assumptions about what underlining means to us! Luckily, <code>htmlize</code> gives us the option to export with class names instead of inline styles so that we can specify each style for ourselves.
 </p>
@@ -312,9 +312,9 @@ If we run the publish again, we can see that we have full styling on our code sn
 </p>
 </div>
 </div>
-<div id="outline-container-org227c647" class="outline-2">
-<h2 id="org227c647">Images</h2>
-<div class="outline-text-2" id="text-org227c647">
+<div id="outline-container-org338b6ac" class="outline-2">
+<h2 id="org338b6ac">Images</h2>
+<div class="outline-text-2" id="text-org338b6ac">
 <p>
 Our first two criteria have been met! Next on the list is solving images. As an example, let's use this <a href="file:///_posts/assets/squirrel.jpg">squirrel image</a> that I found online with an open source license. The ideal situation would be:
 </p>
@@ -359,16 +359,16 @@ So what's the fix here? Well, we have two options, but I am going to go with the
 That's all there is to it! There are simpler ways as well, but that should do it:
 </p>
 
-<div id="org567fa83" class="figure">
+<div id="org70c1fa6" class="figure">
 <p><img src="/_posts/assets/squirrel.jpg" alt="squirrel.jpg" width="300" />
 </p>
 <p><span class="figure-number">Figure 1: </span>A Cute Squirrel</p>
 </div>
 </div>
 </div>
-<div id="outline-container-orgf513ceb" class="outline-2">
-<h2 id="orgf513ceb">Creation Date</h2>
-<div class="outline-text-2" id="text-orgf513ceb">
+<div id="outline-container-org396f39b" class="outline-2">
+<h2 id="org396f39b">Creation Date</h2>
+<div class="outline-text-2" id="text-org396f39b">
 <p>
 Let's add the creation date below the title next. To start, we will modify the publish command to remove the title (<code>:with-title nil</code>) and, in its place, show a preamble bit of HTML that contains a formatted <code>div</code> with the title and the "last modified" span.z
 </p>
@@ -427,9 +427,9 @@ Note that the downside of this is that the created date will change whenever you
 </p>
 </div>
 </div>
-<div id="outline-container-org9eb5e7e" class="outline-2">
-<h2 id="org9eb5e7e">Generating the Directory</h2>
-<div class="outline-text-2" id="text-org9eb5e7e">
+<div id="outline-container-orgb732174" class="outline-2">
+<h2 id="orgb732174">Generating the Directory</h2>
+<div class="outline-text-2" id="text-orgb732174">
 <p>
 For every org file in my <code>_posts</code> folder, I would like to create a link to the generated HTML file at the <code>/posts.html</code> page of my website. You can think of this as the "directory" of all posts. My criteria is:
 </p>
@@ -489,9 +489,9 @@ If you open the <code>sitemap.html</code> file in your browser, you will see a b
 From here, you may customize it however you like.  The following are my customizations.
 </p>
 </div>
-<div id="outline-container-org17e71ed" class="outline-3">
-<h3 id="org17e71ed">Sitemap Title</h3>
-<div class="outline-text-3" id="text-org17e71ed">
+<div id="outline-container-org7ed3bbf" class="outline-3">
+<h3 id="org7ed3bbf">Sitemap Title</h3>
+<div class="outline-text-3" id="text-org7ed3bbf">
 <p>
 I changed the title to "Matthew's Blog Posts".
 </p>
@@ -513,9 +513,9 @@ I changed the title to "Matthew's Blog Posts".
 </div>
 </div>
 </div>
-<div id="outline-container-orgc81a45b" class="outline-3">
-<h3 id="orgc81a45b">Format blog entries in the list</h3>
-<div class="outline-text-3" id="text-orgc81a45b">
+<div id="outline-container-org5647f3c" class="outline-3">
+<h3 id="org5647f3c">Format blog entries in the list</h3>
+<div class="outline-text-3" id="text-org5647f3c">
 <p>
 I like to include the creation date on the blog posts. To do this, we can use <code>org-publish-find-property</code> to find the date property of the org file. Afterward, we can format a string that  includes our formatted timestamp and the <code>org-publish-sitemap-default-entry</code>, which is just a link with the title of the post.
 </p>
@@ -536,9 +536,9 @@ I like to include the creation date on the blog posts. To do this, we can use <c
 </div>
 </div>
 </div>
-<div id="outline-container-org1c07067" class="outline-2">
-<h2 id="org1c07067">Tags &amp; Filtering</h2>
-<div class="outline-text-2" id="text-org1c07067">
+<div id="outline-container-org10b4190" class="outline-2">
+<h2 id="org10b4190">Tags &amp; Filtering</h2>
+<div class="outline-text-2" id="text-org10b4190">
 <p>
 I use <a href="https://www.orgroam.com/">Org-roam</a> for all of my note-taking and, in the next blog post, I plan to demonstrate how I will hook up my Org-roam note-taking workflow to my blogging. In the meantime, just know that we can add tags to the top of our org files like this:
 </p>
@@ -758,9 +758,9 @@ Finally, let's append the following to <code>posts/posts.css</code> so that our
 </div>
 </div>
 </div>
-<div id="outline-container-org8a7a547" class="outline-2">
-<h2 id="org8a7a547">Conclusion</h2>
-<div class="outline-text-2" id="text-org8a7a547">
+<div id="outline-container-org32ee7b9" class="outline-2">
+<h2 id="org32ee7b9">Conclusion</h2>
+<div class="outline-text-2" id="text-org32ee7b9">
 <p>
 There are many more customizations that I plan to do on this system in the future, but I plan to leave this for now so that I can actually get to some blogging. I will proofread and fix my mistakes as time goes on, but this should be a good jumping off point for anyone interested in using org for their own blogging system.
 </p>
diff --git a/posts/june_08_2025.html b/posts/june_08_2025.html
new file mode 100644
index 0000000..3683395
--- /dev/null
+++ b/posts/june_08_2025.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+<meta name="viewport" content="width=device-width, initial-scale=1" />
+<title>Update June 08, 2025</title>
+<meta name="generator" content="Org Mode" />
+
+<link rel="stylesheet" href="/index.css" />
+<link rel="stylesheet" href="/posts/post.css" />
+<link rel="shortcut icon" href="/favicon/favicon.ico" type="image/x-icon">
+<script src='/posts/post.js'></script>
+</head>
+<body>
+<div id="org-div-home-and-up">
+ <a accesskey="h" href="/posts/sitemap.html"> UP </a>
+ <a accesskey="H" href="/"> HOME </a>
+</div><div id="preamble" class="status">
+
+  <div class="org-article-title">
+    <h1>Update June 08, 2025</h1>
+    <span>Last modified: 2025-06-08 Sun 15:30</span>
+    <span><a href="/posts/feed.xml">RSS Feed</a></span>
+  </div>
+</div>
+<div id="content" class="content">
+<div id="outline-container-orgd1fe380" class="outline-2">
+<h2 id="orgd1fe380">What have I been up to?</h2>
+<div class="outline-text-2" id="text-orgd1fe380">
+<p>
+Another month has gone by, so I guess it's time to see what I've been up to.
+</p>
+
+<p>
+Canonical hosted our company's sprint in Frankfurt, Germany during the month of May. It was a very productive time for the whole team. I always enjoy seeing everyone in person, talking through big issues face-to-face, and exploring a new city. I also got to spend some time in Zurich, Switzerland before the sprint began. Zurich is pretty awesome 🏔️!
+</p>
+
+<p>
+In miracle-wm, I have been going down quite the rabbit-hole🐇! What began as a plan to fix the remaining warnings in the source code has snowballed into me implemnenting the rest of the IPC mechanism and testing the entire thing. This has been no small feat, as both sway and i3 implement a <span class="underline">lot</span> of different commands, and a failure to implement any one of them often leads to half-broken clients. I've had to make some "executive" decisions to ignore parts of the protocol that I deem irrelevant now (especially many of the X-specific bits), but it is a mostly compatible implementation. The good news is that I've nearly completed this journey and should be ready to release version <code>0.6.0</code> some time in the middle of June.
+</p>
+
+<p>
+Miracle is getting closer-and-closer to my vision of it every day. The only problem right now is finding the bandwidth to implement everything that I have in my head :)
+</p>
+
+<p>
+On the Mir side of things, I am still implementing the magnifier glass accessibility feature from before, but with a much-improved technical direction that we arrived at during our time in Frankfurt. Unfortunately, this required a quick detour to properly implement the <code>overlay_cursor</code> flag of <a href="https://wayland.app/protocols/wlr-screencopy-unstable-v1#zwlr_screencopy_manager_v1:request:capture_output:arg:overlay_cursor">zwlr<sub>screencopy</sub><sub>manager</sub><sub>v1</sub>::capture<sub>output</sub><sub>region</sub></a>, as both screencopy and magnification rely on this same code path. The good news is that I'm quite close on this and it should be landing in full any day now 🤞
+</p>
+
+<p>
+I also fixed <a href="https://github.com/canonical/mir/pull/3968">this very breaking bug</a> that was actively preventing miracle from rendering on my second monitor, so that's good.
+</p>
+
+<p>
+On addition to these two projects, I am also reinvolving myself in the Flutter multi-window work. For those who don't know, we're trying to make it so that the Flutter toolkit can render to multiple surfaces. This is no small feat, as Flutter was originally written with the assumption that only a single "view" would ever be drawn too. However we've managed to make some great progress on it thus far, and we're very excited to land the first pull request imminently with the help of the folks over a Google!
+</p>
+
+<p>
+I hope you're having a great and productive summer 😎
+</p>
+</div>
+</div>
+</div>
+</body>
+</html>
diff --git a/posts/may_06_2025.html b/posts/may_06_2025.html
index 713eb17..52854f8 100644
--- a/posts/may_06_2025.html
+++ b/posts/may_06_2025.html
@@ -26,9 +26,9 @@
   </div>
 </div>
 <div id="content" class="content">
-<div id="outline-container-org00fb593" class="outline-2">
-<h2 id="org00fb593">What have I been up to?</h2>
-<div class="outline-text-2" id="text-org00fb593">
+<div id="outline-container-org539b8c9" class="outline-2">
+<h2 id="org539b8c9">What have I been up to?</h2>
+<div class="outline-text-2" id="text-org539b8c9">
 <p>
 I've been meaning to do these little blog-post type updates for a while, and I figured now is as good a time as any. So let's start :)
 </p>
diff --git a/posts/sitemap.html b/posts/sitemap.html
index 680b7c8..f6e05fe 100644
--- a/posts/sitemap.html
+++ b/posts/sitemap.html
@@ -21,16 +21,25 @@
 
   <div class="org-article-title">
     <h1>Matthew's Blog Posts</h1>
-    <span>Last modified: 2025-05-22 at 09:02</span>
+    <span>Last modified: 2025-06-08 at 15:35</span>
     <span><a href="/posts/feed.xml">RSS Feed</a></span>
   </div>
 </div>
 <div id="content" class="content">
 <ul class="org-ul">
 <li><p>
+<a href="june_08_2025.html">Update June 08, 2025</a> created on June 08, 2025
+</p>
+<div class="sitemap_tag" id="org0a77fe2">
+<p>
+update
+</p>
+
+</div></li>
+<li><p>
 <a href="may_06_2025.html">Update May 06, 2025</a> created on May 06, 2025
 </p>
-<div class="sitemap_tag" id="org7a48767">
+<div class="sitemap_tag" id="org32d887f">
 <p>
 update
 </p>
@@ -39,7 +48,7 @@ update
 <li><p>
 <a href="hello.html">Hello, Org</a> created on June 20, 2023
 </p>
-<div class="sitemap_tag" id="orgf3799b7">
+<div class="sitemap_tag" id="org5c1e10a">
 <p>
 technology,home
 </p>