[ Jump to content ]


delivered in beta

In the end of April 2009 I started using Twitter—and today, after almost 14 years, in the end of January 2023 I deleted my account. I had great times with Twitter and with the people on there, made friends and I still have a lot of good memories. But over the last years the platform changed and I only used it sporadicly and mostly passively. After the takeover by Elon Musk the platform went into a direction I am no longer comfortable with. So I’m leaving, saying:

This post # 006 of 100 Days To Offload.

Beim Aufräumen meines Archives fand ich einen Radiobeitrag von November 2012 wieder: Eine Biographie über Martin Scorsese anlässlich seines 70. Geburtstags. Auf der Suche nach etwas mehr Kontext zur Audio-Datei fand ich nicht den original Beitrag von 2012, aber entdeckte, dass der Deutschlandfunk (Dlf) den Beitrag zu Martin Scorseses 80. Geburtstag im November 2022 erneut veröffentlichte:

Film als Passion: Über Marin Scorsese:

Martin Charles Scorsese, geboren am 17. November 1942 in Queens, New York City, ist ein US-amerikanischer Regisseur, Drehbuchautor, Filmproduzent und Schauspieler. Er gehört zu den einflussreichsten und bedeutendsten Regisseuren des zeitgenössischen amerikanischen Kinos. Mit respektvoller Ironie nennt man ihn einen „hardcore Cineasten“. Für Martin  Scorsese ist die Filmgeschichte seine Passion. Er führt ein Leben für den und mit dem Film. Als eifriger Sammler von Filmkopien und -plakaten sucht er die geliebten Werke zu bewahren, als geschickter Lobbyist die Restaurierung gefährdeter Titel zu sichern. Als enthusiastischer Filmessayist stellt er den Zuschauern seine Perspektiven auf die Historie der amerikanischen und der italienischen Kinematographie vor, die ihn besonders geprägt haben. Diese Sendung würdigte Martin Scorsese aus Anlass seines 70. Geburtstags, die wir nun zum 80. Geburtstag noch einmal wiederholen.

This post is # 005 of 100 Days To Offload.

I’m a data hoarder of sorts. In the last decade I’ve collected a lot of stuff and that must be sorted and cleaned up. Over the years I tried different sorting structures but it never worked out for me. But currently, I have a pretty solid system and over the last year I’m sorting everything in. And I’ll give you a glimpse into my archives by writing about some of it.

This post is # 004 of 100 Days To Offload.

ClassicPress 1.5.0 was released a few days ago with support for PHP 8. And this solves a lot of problems I had on this blog in the last few month: On the homepage was the title “Archive” visible, which should not be visible; and on my archive page nothing was shown at all—except for the title; and all I’ve got was mysterious error messages in the logs … Guess I should have better looked at the requirements (which are now, btw, a bit outdated), than I would have seen that I was using the wrong PHP version. Lesson learned.

So now I can start tinkering on this blog again and not try to hunt this weird behavior of ClassicPress.

This post is # 003 of 100 Days To Offload.

Just some days ago I saw a video of Linus Tech Tips about battery-draining standby modes of Windows laptops (and sometimes MacBooks).

Now I came across Sleep Aid (via Michael Tsai), a macOS tool to diagnose and solve standby aka. sleeping issues on Macs. From the blog post Hot Bag MacBook about it:

Have you ever travelled somewhere to find that your MacBook is nice and warm, with next to no battery left? If so, these are the common causes of a “Hot Bag MacBook” that we’ve found so far.

This could be handy.

This post is # 002 of 100 Days To Offload.

100 Days To Offload:

The whole point of #100DaysToOffload is to challenge you to publish 100 posts on your personal blog in a year.

Posts don’t need to be long-form, deep, meaningful, or even that well written. If there are spelling and grammar mistakes, or even if there’s no real point to the post, so what? What’s important is that you’re writing about the things you want to write about.

Your posts could be how-to guides, or links to another post you have found interesting. They could include your own thoughts about that post, or a response to it. It could be a simple update about what you have done that day. Tell us about your dog, your cat, your fish tank, or whatever hobbies you have. Someone will find it interesting.

Just. Write.

A few days ago I stumbled upon this: Writing 100 blog posts on my blog in 365 days—can’t be that hard, right?! Challenge accepted.

This post is # 001 of 100 Days To Offload.

Screenshot of the intersection of two Instagram story ads: the first is for Adobe Creative Cloud, the second for Affinity 2.0

The ad targeting of Instagram is on point again.

Update 11.12.2022: Das Buch hat ein:e neue:n Besitzer:in gefunden.

Cover von Adobe Flash CS5: Das umfassende Handbuch

Geöffneter Buchrücken mit DVD von Adobe Flash CS5: Das umfassende Handbuch

Verschenke mein Fachbuch Adobe Flash CS5: Das umfassende Handbuch aus dem Verlag Galileo Design (heute: Rheinwerk-Verlag) von 2010, inkl. DVD. Ohne Mängel, nur der Buchumschlag hat Gebrauchsspuren.

Ich kaufte es mir Ende 2011 für die Vorbereitung meiner Kurse für angehende Online-Redakteure, die etwas über Flash lernen sollten – heute taugt es nur noch für das moderne Antiquariat.

Das Buch kann sehr gerne bei mir in Wuppertal abgeholt werden. Versand ist auch möglich, wenn die Versandkosten in Höhe von 6,99 € (Paket bis 5 kg) übernommen werden. Anschreiben!

Bibliographische Informationen: Nick Weschkalnies & Sven Gasser: Adobe Flash CS5: Das umfassende Handbuch. Galileo Design, Bonn, 2010. ISBN-13: 978-383621-564-0. DNB: #1001391713.

Auch online bei: ebay, ebay Kleinanzeigen, nebenan.de

A lot has changed over the last decade on the web—and so has WordPress: WordPress has started as a simple blogging tool and has grown into a widely used CMS with a simple interface for (new) users and a huge ecosystem of extensions, themes and developers. That’s great—and a reason why I still use it for other projects and at work—but WordPress has outgrown my needs for a simple blogging tool that I want for my blog. And now, with WordPress 6.0 around the corner, it’s time to switch to ClassicPress. ClassicPress is a fork of WordPress 4.9—or: the pre-Gutenberg era—and so exactly what I want my blogging tool to be: simple.

Lately I had a tough time to figure out how to serve a Unity3D WebGL export via AWS CloudFront from an AWS S3 origin after updating to Unity3D 2020.01 with it’s new WebGL loader. I don’t describe how to connect AWS CloudFront to serve files from AWS S3—Andrew Welch does this neatly in his tutorial (one can skip the last step about Craft CMS, though)—I focus on the special configuration the Unity3D files need.

The new WebGL loader

The new WebGL loader requires that certain files are served in a specific way, contrary to the default web-server configurations.
From the forums:

When hosting such a build on a server, the following http headers should be added to the server responses in order to make the build load correctly:

  • .gz files should be served with a Content-Encoding: gzip response header.
  • .br files should be served with a Content-Encoding: br response header.
  • .wasm, .wasm.gz or .wasm.br files should be served with a Content-Type: application/wasm response header.
  • .js, .js.gz or .js.br files should be served with a Content-Type: application/javascript response header.

The Apache configuration example makes it even clearer:

<IfModule mod_mime.c>
# The following lines are required for builds without decompression fallback, compressed with gzip
RemoveType .gz
AddEncoding gzip .gz
AddType application/octet-stream .data.gz
AddType application/wasm .wasm.gz
AddType application/javascript .js.gz
AddType application/octet-stream .symbols.json.gz

# The following lines are required for builds without decompression fallback, compressed with brotli
RemoveType .br
RemoveLanguage .br
AddEncoding br .br
AddType application/octet-stream .data.br
AddType application/wasm .wasm.br
AddType application/javascript .js.br
AddType application/octet-stream .symbols.json.br

# The following line improves loading performance for uncompressed builds
AddType application/wasm .wasm


The easiest way to serve the Unity3D WebGL files via AWS CloudFront from an AWS S3 origin with the correct configuration is to set the correct Content-Type and Content-Encoding in the S3 bucket. Then CloudFront serves them to the user with the correct configuration directly.

To achieve this, one can set the correct metadata of the files via the AWS S3 management console: Select the file, open the “Actions” menu, select “Change metadata”, set the metadata in the opening pop-over on the right-hand side.

Screenshot: AWS S3 console with opened edit view for file metadata

At one point I wrote a small helper script in Python, using boto3, to set the correct metadata after I uploaded the files manually: