The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,862 other subscribers

The Lunduke Journal on X: “Another classic UNIX system has died. The final version of HP-UX has, as of 3 days ago, officially hit “obsolescence” and is no longer supported… “

Posted by jpluimers on 2026/01/04

Another classic UNIX system has died.

The final version of HP-UX has, as of 3 days ago, officially hit “obsolescence” and is no longer supported.

While most versions of HP-UX had hit “end of life” some years back, version 11i v3 (specifically for Itanium servers) was still supported.  At least… until the clock struck midnight on New Year’s Eve.

HP-UX joins the likes of IRIX (support ended in 2013).

Luckily there are still a few classic style UNIX systems in production… but the list is growing smaller with each passing year.

https://x.com/LundukeJournal/status/2007699486039027954

Posted in Uncategorized | Leave a Comment »

Goudtekens Nederland via NU.nl

Posted by jpluimers on 2026/01/02

Goudtekens (meer algemeen gehaltemerken of keurteken) in Nederland via [Wayback/Archive] Goudprijs piekt, dus tijd om je (oma’s) juwelenkist te verzilveren | Slimmer leven | NU.nl: Read the rest of this entry »

Posted in LifeHacker, Power User | Leave a Comment »

Het tekenen van de Eindrekening en verantwoording » Zumpolle Advocaten

Posted by jpluimers on 2026/01/02

Voor mijn link-archief:

Het ondertekenen van de Eindrekening en verantwoording is een vorm van décharge en dat houdt in dat de oude bewindvoerder door de nieuwe bewindvoerder gevrijwaard wordt van aansprakelijkheid voor het gevoerde bewind.

[Wayback/Archive] Het tekenen van de Eindrekening en verantwoording » Zumpolle Advocaten

–jeroen

Posted in About, LifeHacker, Personal, Power User | Leave a Comment »

GitHub – spotDL/spotify-downloader: Download your Spotify playlists and songs along with album art and metadata (from YouTube if a match is found).

Posted by jpluimers on 2026/01/01

Need to check the matching algorithm of [Wayback/Archive] GitHub – spotDL/spotify-downloader: Download your Spotify playlists and songs along with album art and metadata (from YouTube if a match is found).

I wanted to download [Wayback/Archive] The Incredits – song and lyrics by Michael Giacchino | Spotify for music practice, but then found Michael listed it on his YouTube channel twice:

A bit later I also found [Wayback/Archive] The Incredits – Transcription (with original score) – YouTube with [Wayback/Archive] The Incredits Sheet Music for Piano, Trombone, Tuba, Flute piccolo & more instruments (Symphony Orchestra) | MuseScore.com

Via [Wayback/Archive] Youtube-dl supports Spotify. How to use it? : youtubedl.

--jeroen

Posted in Development, ffmpeg, Media, Media Streaming, Power User, Python, Scripting, SocialMedia, Software Development, Spotify, YouTube, youtube-dl | Leave a Comment »

ssl – Why was 398 days chosen for TLS expiration? – Stack Overflow

Posted by jpluimers on 2026/01/01

Cool, since I switched to Let’s Encrypt a long while ago, I missed that various tools now require TLS expiration be no longer than 398 days away (and preferably even 397 days).

So I also missed the reason for that specific number of days. [Wayback/Archive] ssl – Why was 398 days chosen for TLS expiration? – Stack Overflow (thanks [Wayback/Archive] stevendesu and [Wayback/Archive] user10063)

answers it:

366+31+1 = 398 days

It equals one leap year + one month + “a little room to handle the messiness of dates.”

then posts a lot of quotes from references to the history on how that reason came to be. I have archived and listed the links below.

Most of the discussion was during a very hectic time in life: after a single sided bad accident my mentally retarded brother was in and assisting him during his recovery period, I developed cancer and had extensive treatments against it. All the more reason for missing all this:

Read the rest of this entry »

Posted in Communications Development, Development, Encryption, https, HTTPS/TLS security, Internet protocol suite, Let's Encrypt (letsencrypt/certbot), Power User, Security, TCP, TLS | Tagged: , | Leave a Comment »

It died, but longer ladders will be there: 12ft – Wikipedia

Posted by jpluimers on 2025/12/31

From 12ft – Wikipedia:

On July 17, 2025, the News Media Alliance reported that it had taken down the website.

It’s impossible to enjoy the content of online media by paying (for instance because payment systems are not compatible, but also because those media often have region blocks), so this is to longer ladders (and understanding how ladders work):

Read the rest of this entry »

Posted in archive.is / archive.today, Cloud, Containers, Development, Docker, HTML, HTML5, Infrastructure, Internet, InternetArchive, JavaScript/ECMAScript, LifeHacker, Power User, Python, Scripting, Software Development, WayBack machine, Web Development | Leave a Comment »

list-style-type none “No item marker is shown”. – CSS: Cascading Style Sheets | MDN

Posted by jpluimers on 2025/12/31

Note that for removing the bullet-type, it does not matter if it is an ordered or unordered list.

Via [Wayback/Archive] html list type none – Google Search.

–jeroen

Posted in CSS, Development, HTML, Software Development, Web Development | Leave a Comment »

Bedrijf failliet: stalling deelscooters kost gemeente zeker zes ton

Posted by jpluimers on 2025/12/30

Bij disruption (Hallo Uber, Amazon, Zorgcowboys!) komen de kosten uiteindelijk vrijwel altijd op de maatschappij terecht.

Ook nu weer: [Wayback/Archive] Bedrijf failliet: stalling deelscooters kost gemeente zeker zes ton

De gemeente Hollands Kroon dreigt voor ruim 600.000 euro het schip in te gaan door het ruimen van zo’n 4000 scooters van het failliete deelscooterbedrijf Go Sharing. De Noord-Hollandse gemeente probeert de schade te verhalen op het bedrijf. Maar omdat Go Sharing enkele malen van eigenaar wisselde en in november failliet ging, is de kans op succes gering.

--jeroen

Posted in Uncategorized | Leave a Comment »

python – Some gists on github have very many forks. How can I find the most recently active and/or heavily modified? – Stack Overflow

Posted by jpluimers on 2025/12/30

Interesting read: there is even an API for it (which you need to be logged on for in order not to get a rate limit): [Wayback/Archive] python – Some gists on github have very many forks. How can I find the most recently active and/or heavily modified? – Stack Overflow

Thanks [Wayback/Archive] Michael Goldshteyn, [Wayback/Archive] rob006, [Wayback/Archive] Chankey Pathak and [Wayback/Archive] ikwyl6 for solving this both for gists and regular github repositories:

Read the rest of this entry »

Posted in Development, DVCS - Distributed Version Control, gist, git, GitHub, Software Development, Source Code Management | Leave a Comment »

Structure and Interpretation of Test Cases • Kevlin Henney • GOTO 2022 – YouTube (hello Leap Years!)

Posted by jpluimers on 2025/12/30

Any session by Kevlin is great, so this is definitely recommended watching: [Wayback/Archive] Structure and Interpretation of Test Cases • Kevlin Henney • GOTO 2022 – YouTube

Via [Wayback/Archive] Ifeora Okechukwu on Twitter: “On the structure and interpretation of test cases: by @KevlinHenney Awesome talk!!! “.

A few takeaways:

  • Kevlin uses the same Leap Year case as I have taught since the mid 1990’s: I like the way we both approach software development, though I can still learn a lot from Kevlin.
  • Non-programmers understand more than you might expect, just like you can get much more from a foreign news paper than you would think at first thought
  • You should know how to draw a Venn diagram with 4 sets allowing *all* combinations of those (search for “Venn’s four-set diagram using ellipses” in the link on the left)
  • Kevlin shows these 4 sets:
    • Common cases
    • Simple cases
    • Boundary cases
    • Edge cases

    The first two and last two sound similar. They aren’t.

  • Wrinkles and various levels of code coverage: don’t fool yourself as that is easy to do
  • The way of thinking is “thorough” (note from self: AI is not thorough, it is statistics)
  • Calendars are difficult (and depending a lot on the period and region their usage are valid for) – I already knew that, but it was good to be reminded off; see presentations by Jon Skeet for more information on it, see the blog tag Jon Skeet, or for instance these links:

Read the rest of this entry »

Posted in Development, Software Development, Testing | Leave a Comment »