diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..918de83
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,6 @@
+_site
+.sass-cache
+.jekyll-cache
+.jekyll-metadata
+vendor
+Gemfile.lock
diff --git a/404.html b/404.html
new file mode 100644
index 0000000..3a16ab5
--- /dev/null
+++ b/404.html
@@ -0,0 +1,25 @@
+---
+permalink: /404.html
+layout: page
+---
+
+
+
+
+
404
+
+
Page not found :(
+
The requested page could not be found.
+
diff --git a/CNAME b/CNAME
deleted file mode 100644
index 41d0bef..0000000
--- a/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-holgr.com
\ No newline at end of file
diff --git a/Gemfile b/Gemfile
new file mode 100644
index 0000000..fec23cb
--- /dev/null
+++ b/Gemfile
@@ -0,0 +1,33 @@
+source "https://rubygems.org"
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+# bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+#gem "jekyll", "~> 4.4.1"
+# This is the default theme for new Jekyll sites. You may change this to anything you like.
+gem "minima", "~> 2.5"
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+gem "github-pages", "~> 232", group: :jekyll_plugins
+# If you have any plugins, put them here!
+group :jekyll_plugins do
+ gem "jekyll-feed", "~> 0.12"
+end
+
+# Windows and JRuby does not include zoneinfo files, so bundle the tzinfo-data gem
+# and associated library.
+platforms :mingw, :x64_mingw, :mswin, :jruby do
+ gem "tzinfo", ">= 1", "< 3"
+ gem "tzinfo-data"
+end
+
+# Performance-booster for watching directories on Windows
+gem "wdm", "~> 0.1", :platforms => [:mingw, :x64_mingw, :mswin]
+
+# Lock `http_parser.rb` gem to `v0.6.x` on JRuby builds since newer versions of the gem
+# do not have a Java counterpart.
+gem "http_parser.rb", "~> 0.6.0", :platforms => [:jruby]
diff --git a/LICENSE b/LICENSE
deleted file mode 100644
index 8f71f43..0000000
--- a/LICENSE
+++ /dev/null
@@ -1,202 +0,0 @@
- Apache License
- Version 2.0, January 2004
- http://www.apache.org/licenses/
-
- TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
- 1. Definitions.
-
- "License" shall mean the terms and conditions for use, reproduction,
- and distribution as defined by Sections 1 through 9 of this document.
-
- "Licensor" shall mean the copyright owner or entity authorized by
- the copyright owner that is granting the License.
-
- "Legal Entity" shall mean the union of the acting entity and all
- other entities that control, are controlled by, or are under common
- control with that entity. For the purposes of this definition,
- "control" means (i) the power, direct or indirect, to cause the
- direction or management of such entity, whether by contract or
- otherwise, or (ii) ownership of fifty percent (50%) or more of the
- outstanding shares, or (iii) beneficial ownership of such entity.
-
- "You" (or "Your") shall mean an individual or Legal Entity
- exercising permissions granted by this License.
-
- "Source" form shall mean the preferred form for making modifications,
- including but not limited to software source code, documentation
- source, and configuration files.
-
- "Object" form shall mean any form resulting from mechanical
- transformation or translation of a Source form, including but
- not limited to compiled object code, generated documentation,
- and conversions to other media types.
-
- "Work" shall mean the work of authorship, whether in Source or
- Object form, made available under the License, as indicated by a
- copyright notice that is included in or attached to the work
- (an example is provided in the Appendix below).
-
- "Derivative Works" shall mean any work, whether in Source or Object
- form, that is based on (or derived from) the Work and for which the
- editorial revisions, annotations, elaborations, or other modifications
- represent, as a whole, an original work of authorship. For the purposes
- of this License, Derivative Works shall not include works that remain
- separable from, or merely link (or bind by name) to the interfaces of,
- the Work and Derivative Works thereof.
-
- "Contribution" shall mean any work of authorship, including
- the original version of the Work and any modifications or additions
- to that Work or Derivative Works thereof, that is intentionally
- submitted to Licensor for inclusion in the Work by the copyright owner
- or by an individual or Legal Entity authorized to submit on behalf of
- the copyright owner. For the purposes of this definition, "submitted"
- means any form of electronic, verbal, or written communication sent
- to the Licensor or its representatives, including but not limited to
- communication on electronic mailing lists, source code control systems,
- and issue tracking systems that are managed by, or on behalf of, the
- Licensor for the purpose of discussing and improving the Work, but
- excluding communication that is conspicuously marked or otherwise
- designated in writing by the copyright owner as "Not a Contribution."
-
- "Contributor" shall mean Licensor and any individual or Legal Entity
- on behalf of whom a Contribution has been received by Licensor and
- subsequently incorporated within the Work.
-
- 2. Grant of Copyright License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- copyright license to reproduce, prepare Derivative Works of,
- publicly display, publicly perform, sublicense, and distribute the
- Work and such Derivative Works in Source or Object form.
-
- 3. Grant of Patent License. Subject to the terms and conditions of
- this License, each Contributor hereby grants to You a perpetual,
- worldwide, non-exclusive, no-charge, royalty-free, irrevocable
- (except as stated in this section) patent license to make, have made,
- use, offer to sell, sell, import, and otherwise transfer the Work,
- where such license applies only to those patent claims licensable
- by such Contributor that are necessarily infringed by their
- Contribution(s) alone or by combination of their Contribution(s)
- with the Work to which such Contribution(s) was submitted. If You
- institute patent litigation against any entity (including a
- cross-claim or counterclaim in a lawsuit) alleging that the Work
- or a Contribution incorporated within the Work constitutes direct
- or contributory patent infringement, then any patent licenses
- granted to You under this License for that Work shall terminate
- as of the date such litigation is filed.
-
- 4. Redistribution. You may reproduce and distribute copies of the
- Work or Derivative Works thereof in any medium, with or without
- modifications, and in Source or Object form, provided that You
- meet the following conditions:
-
- (a) You must give any other recipients of the Work or
- Derivative Works a copy of this License; and
-
- (b) You must cause any modified files to carry prominent notices
- stating that You changed the files; and
-
- (c) You must retain, in the Source form of any Derivative Works
- that You distribute, all copyright, patent, trademark, and
- attribution notices from the Source form of the Work,
- excluding those notices that do not pertain to any part of
- the Derivative Works; and
-
- (d) If the Work includes a "NOTICE" text file as part of its
- distribution, then any Derivative Works that You distribute must
- include a readable copy of the attribution notices contained
- within such NOTICE file, excluding those notices that do not
- pertain to any part of the Derivative Works, in at least one
- of the following places: within a NOTICE text file distributed
- as part of the Derivative Works; within the Source form or
- documentation, if provided along with the Derivative Works; or,
- within a display generated by the Derivative Works, if and
- wherever such third-party notices normally appear. The contents
- of the NOTICE file are for informational purposes only and
- do not modify the License. You may add Your own attribution
- notices within Derivative Works that You distribute, alongside
- or as an addendum to the NOTICE text from the Work, provided
- that such additional attribution notices cannot be construed
- as modifying the License.
-
- You may add Your own copyright statement to Your modifications and
- may provide additional or different license terms and conditions
- for use, reproduction, or distribution of Your modifications, or
- for any such Derivative Works as a whole, provided Your use,
- reproduction, and distribution of the Work otherwise complies with
- the conditions stated in this License.
-
- 5. Submission of Contributions. Unless You explicitly state otherwise,
- any Contribution intentionally submitted for inclusion in the Work
- by You to the Licensor shall be under the terms and conditions of
- this License, without any additional terms or conditions.
- Notwithstanding the above, nothing herein shall supersede or modify
- the terms of any separate license agreement you may have executed
- with Licensor regarding such Contributions.
-
- 6. Trademarks. This License does not grant permission to use the trade
- names, trademarks, service marks, or product names of the Licensor,
- except as required for reasonable and customary use in describing the
- origin of the Work and reproducing the content of the NOTICE file.
-
- 7. Disclaimer of Warranty. Unless required by applicable law or
- agreed to in writing, Licensor provides the Work (and each
- Contributor provides its Contributions) on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
- implied, including, without limitation, any warranties or conditions
- of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
- PARTICULAR PURPOSE. You are solely responsible for determining the
- appropriateness of using or redistributing the Work and assume any
- risks associated with Your exercise of permissions under this License.
-
- 8. Limitation of Liability. In no event and under no legal theory,
- whether in tort (including negligence), contract, or otherwise,
- unless required by applicable law (such as deliberate and grossly
- negligent acts) or agreed to in writing, shall any Contributor be
- liable to You for damages, including any direct, indirect, special,
- incidental, or consequential damages of any character arising as a
- result of this License or out of the use or inability to use the
- Work (including but not limited to damages for loss of goodwill,
- work stoppage, computer failure or malfunction, or any and all
- other commercial damages or losses), even if such Contributor
- has been advised of the possibility of such damages.
-
- 9. Accepting Warranty or Additional Liability. While redistributing
- the Work or Derivative Works thereof, You may choose to offer,
- and charge a fee for, acceptance of support, warranty, indemnity,
- or other liability obligations and/or rights consistent with this
- License. However, in accepting such obligations, You may act only
- on Your own behalf and on Your sole responsibility, not on behalf
- of any other Contributor, and only if You agree to indemnify,
- defend, and hold each Contributor harmless for any liability
- incurred by, or claims asserted against, such Contributor by reason
- of your accepting any such warranty or additional liability.
-
- END OF TERMS AND CONDITIONS
-
- APPENDIX: How to apply the Apache License to your work.
-
- To apply the Apache License to your work, attach the following
- boilerplate notice, with the fields enclosed by brackets "{}"
- replaced with your own identifying information. (Don't include
- the brackets!) The text should be enclosed in the appropriate
- comment syntax for the file format. We also recommend that a
- file or class name and description of purpose be included on the
- same "printed page" as the copyright notice for easier
- identification within third-party archives.
-
- Copyright {yyyy} {name of copyright owner}
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-
diff --git a/README.md b/README.md
deleted file mode 100644
index 788ab24..0000000
--- a/README.md
+++ /dev/null
@@ -1,2 +0,0 @@
-# holgr.github.io
-GitHub Page
diff --git a/_config.yml b/_config.yml
new file mode 100644
index 0000000..aedc440
--- /dev/null
+++ b/_config.yml
@@ -0,0 +1,63 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely edit after that. If you find
+# yourself editing this file very often, consider using Jekyll's data files
+# feature for the data you need to update frequently.
+#
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'bundle exec jekyll serve'. If you change this file, please restart the server process.
+#
+# If you need help with YAML syntax, here are some quick references for you:
+# https://learn-the-web.algonquindesign.ca/topics/markdown-yaml-cheat-sheet/#yaml
+# https://learnxinyminutes.com/docs/yaml/
+#
+# Site settings
+# These are used to personalize your new site. If you look in the HTML files,
+# you will see them accessed via {{ site.title }}, {{ site.email }}, and so on.
+# You can create any custom variable you would like, and they will be accessible
+# in the templates via {{ site.myvariable }}.
+
+title: holgr.com
+email: holger@eilhard.net
+description: >- # this means to ignore newlines until "baseurl:"
+ This is my site. Welcome. There should be some clever text here, but I don't know yet, what it should say. Maybe later.
+baseurl: "/blog" # the subpath of your site, e.g. /blog
+url: "https://holgr.com" # the base hostname & protocol for your site, e.g. http://example.com
+#twitter_username: jekyllrb
+#github_username: jekyll
+show_excerpts: true
+excerpt_separator: ""
+
+minima:
+ social_links:
+ - platform: mastodon
+ user_url: "https://mastodon.social/@holgr"
+ - platform: bluesky
+ user_url: "https://bsky.app/profile/holgr.com"
+
+# Build settings
+theme: minima
+plugins:
+ - jekyll-feed
+
+
+# Exclude from processing.
+# The following items will not be processed, by default.
+# Any item listed under the `exclude:` key here will be automatically added to
+# the internal "default list".
+#
+# Excluded items can be processed by explicitly listing the directories or
+# their entries' file path in the `include:` list.
+#
+# exclude:
+# - .sass-cache/
+# - .jekyll-cache/
+# - gemfiles/
+# - Gemfile
+# - Gemfile.lock
+# - node_modules/
+# - vendor/bundle/
+# - vendor/cache/
+# - vendor/gems/
+# - vendor/ruby/
diff --git a/_drafts/2025-02-07-welcome-to-jekyll.md b/_drafts/2025-02-07-welcome-to-jekyll.md
new file mode 100644
index 0000000..de73701
--- /dev/null
+++ b/_drafts/2025-02-07-welcome-to-jekyll.md
@@ -0,0 +1,29 @@
+---
+layout: post
+title: "Welcome to Jekyll!"
+date: 2025-02-07 17:14:09 -0800
+categories: jekyll update
+---
+You’ll find this post in your `_posts` directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run `jekyll serve`, which launches a web server and auto-regenerates your site when a file is updated.
+
+Jekyll requires blog post files to be named according to the following format:
+
+`YEAR-MONTH-DAY-title.MARKUP`
+
+Where `YEAR` is a four-digit number, `MONTH` and `DAY` are both two-digit numbers, and `MARKUP` is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.
+
+Jekyll also offers powerful support for code snippets:
+
+{% highlight ruby %}
+def print_hi(name)
+ puts "Hi, #{name}"
+end
+print_hi('Tom')
+#=> prints 'Hi, Tom' to STDOUT.
+{% endhighlight %}
+
+Check out the [Jekyll docs][jekyll-docs] for more info on how to get the most out of Jekyll. File all bugs/feature requests at [Jekyll’s GitHub repo][jekyll-gh]. If you have questions, you can ask them on [Jekyll Talk][jekyll-talk].
+
+[jekyll-docs]: https://jekyllrb.com/docs/home
+[jekyll-gh]: https://github.com/jekyll/jekyll
+[jekyll-talk]: https://talk.jekyllrb.com/
diff --git a/_includes/footer.html b/_includes/footer.html
new file mode 100644
index 0000000..c064fac
--- /dev/null
+++ b/_includes/footer.html
@@ -0,0 +1,28 @@
+
+
+
diff --git a/_layouts/default.html b/_layouts/default.html
new file mode 100644
index 0000000..58e141b
--- /dev/null
+++ b/_layouts/default.html
@@ -0,0 +1,20 @@
+
+
+
+ {%- include head.html -%}
+
+
+
+ {%- include header.html -%}
+
+
+
+ {{ content }}
+
+
+
+ {%- include footer.html -%}
+
+
+
+
diff --git a/_layouts/home.html b/_layouts/home.html
new file mode 100644
index 0000000..0ea7778
--- /dev/null
+++ b/_layouts/home.html
@@ -0,0 +1,33 @@
+---
+layout: default
+---
+
+
+ {%- if page.title -%}
+
{{ page.title }}
+ {%- endif -%}
+
+ {{ content }}
+
+ {%- if site.posts.size > 0 -%}
+
{{ page.list_title | default: "Posts" }}
+
+ {%- for post in site.posts -%}
+ -
+ {%- assign date_format = site.minima.date_format | default: "%b %-d, %Y" -%}
+ {{ post.date | date: date_format }}
+
+ {%- if site.show_excerpts -%}
+ {{ post.excerpt }}
+ {%- endif -%}
+
+ {%- endfor -%}
+
+
+ {%- endif -%}
+
+
diff --git a/_layouts/page.html b/_layouts/page.html
new file mode 100644
index 0000000..01e4b2a
--- /dev/null
+++ b/_layouts/page.html
@@ -0,0 +1,14 @@
+---
+layout: default
+---
+
+
+
+
+
+ {{ content }}
+
+
+
diff --git a/_layouts/post.html b/_layouts/post.html
new file mode 100644
index 0000000..032d85b
--- /dev/null
+++ b/_layouts/post.html
@@ -0,0 +1,23 @@
+---
+layout: default
+---
+
+
+
+
+
+ {{ content }}
+
+
+
+
diff --git a/_posts/2022-12-18-links-for-reasons.md b/_posts/2022-12-18-links-for-reasons.md
new file mode 100644
index 0000000..2335c0b
--- /dev/null
+++ b/_posts/2022-12-18-links-for-reasons.md
@@ -0,0 +1,30 @@
+---
+id: 5735
+title: 'Links – For Reasons'
+date: '2022-12-18T15:07:18-08:00'
+author: 'Holger Eilhard'
+layout: post
+guid: 'https://holgr.com/?p=5735'
+permalink: /blog/links-for-reasons/
+---
+
+It's been quite some time, but I thought it'd be nice to add some info here with other places where you can find me. Especially since you're now – on some sites – [no longer allowed](https://help.twitter.com/en/rules-and-policies/social-platforms-policy) to link to your other accounts. It's really only a handful:
+
+- Mastodon: [mastodon.social/@holgr](https://mastodon.social/@holgr)
+- SupportDiffs on Mastodon: [mastodon.online/@supportdiffs](https://mastodon.online/@supportdiffs)
+- GitHub: [holgr](https://github.com/holgr)
+
+I wouldn't be surprised if there'll be a poll in a few hours asking people if Twitter's dumb rule of the day should be revoked. And then 24 hours later it'll be scrapped and/or people will be let back in.
+
+That's his modus operandi nowadays:
+- Let someone publish a new idiotic rule and immediately ban some famous people
+- Wait a bit for people to get upset and talk about him and his stupid rule
+- Come up [with a poll](https://twitter.com/elonmusk/status/1603600001057185792)
+- Optional: [redo the poll](https://twitter.com/elonmusk/status/1603609278664712192) because he didn't like the outcome of the first poll
+- Let people back on the site (if they delete their tweets, even if they're linking to publicly available information that is being [broadcast through the air](https://en.wikipedia.org/wiki/Automatic_Dependent_Surveillance–Broadcast))
+- Post how Twitter „[is 🔥🔥🔥🔥](https://twitter.com/elonmusk/status/1603659604906213376)“
+- Rinse, repeat
+
+More and more people are figuring out that the only way to stop this is to stop giving him (and his 44 billion dollar website) attention and leave Twitter.
+
+Update: The policy ([here on archive.org](https://web.archive.org/web/20221218173806/https://help.twitter.com/en/rules-and-policies/social-platforms-policy)) lasted only a few hours.
\ No newline at end of file
diff --git a/_posts/2024-03-08-macos-sonoma-theres-a-process-stealing-your-window-focus.md b/_posts/2024-03-08-macos-sonoma-theres-a-process-stealing-your-window-focus.md
new file mode 100644
index 0000000..4afdfce
--- /dev/null
+++ b/_posts/2024-03-08-macos-sonoma-theres-a-process-stealing-your-window-focus.md
@@ -0,0 +1,30 @@
+---
+id: 5798
+title: "macOS Sonoma: There's a process stealing your windows' focus"
+date: '2024-03-08T19:17:40-08:00'
+author: 'Holger Eilhard'
+layout: post
+guid: 'https://holgr.com/?p=5798'
+permalink: /blog/macos-sonoma-theres-a-process-stealing-your-window-focus/
+---
+
+Sean Harding finally put [into words](https://www.threads.net/@seanharding/post/C4RT42-rqD3) an issue that I've witnessed for a while now on macOS Sonoma.
+
+This is it:
+> Weird MacOS thing: the window I am working in will sometimes lose focus (without the app losing focus). Suddenly, and without any obvious cause. It will be as if no window has focus. Sometimes happens as often as every few minutes, sometimes doesn't happen for a long time. I can’t figure out any common variable. But it can be very disruptive.
+Has anyone else seen this? Any ideas?
+
+I've [adjusted the Python script](https://gist.github.com/holgr/59f8df7f81aa2b74d67e0ab95e2fd28a) mentioned in the thread to work with Python 3.x that you can get with [Homebrew](https://brew.sh) for example.
+
+
+This is what the output looks like:
+```> python3.11 find_focus_stealer.py
+2024-03-08 17:20:34: iTerm2 [/Applications/iTerm.app]
+2024-03-08 17:20:37: Safari [/System/Volumes/Preboot/Cryptexes/App/System/Applications/Safari.app]
+2024-03-08 17:25:17: CoreServicesUIAgent [/System/Library/CoreServices/CoreServicesUIAgent.app]
+2024-03-08 17:25:51: Safari [/System/Volumes/Preboot/Cryptexes/App/System/Applications/Safari.app]
+2024-03-08 17:25:52: iTerm2 [/Applications/iTerm.app]```
+
+So it looks like Apple's own `CoreServicesUIAgent` is the problem. Who's going to file the Radar that will immediately be ignored by the time it's submitted?
+
+Update 2024-07-03: Ever since removing Carrot Weather from my Mac this issue has gone away. I'm still certain it's some bug in the underlying macOS, but if this happens to you, check there first.
\ No newline at end of file
diff --git a/about.md b/about.md
new file mode 100644
index 0000000..f376e25
--- /dev/null
+++ b/about.md
@@ -0,0 +1,7 @@
+---
+layout: page
+title: About
+permalink: /about/
+---
+
+Hi, my name is Holger. Welcome to my site.
\ No newline at end of file
diff --git a/index.html b/index.html
deleted file mode 100644
index e69de29..0000000
diff --git a/index.md b/index.md
new file mode 100644
index 0000000..0671507
--- /dev/null
+++ b/index.md
@@ -0,0 +1,6 @@
+---
+# Feel free to add content and custom Front Matter to this file.
+# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
+
+layout: home
+---