There are, however, plenty of tools that convert markdown to HTML, and VB6 is able to display that.
So all you need is something that runs in your build system to convert the markdown to HTML and you're golden.
According to https://metacpan.org/release/BOBTFISH/Text-Markdown-1.000031/source/Makefile.PL, perl's Text::Markdown runs on perl 5.8. I would be very surprised if you couldn't get that to run on Windows 98?
But then, big amount of yak shaving, that.
Ik zag onlangs een weerstation op de Shelly website:
https://www.shelly.com/products/ecowitt-ws90-7-in-1-weather-station
Ik heb er zelf geen ervaring mee, maar heb wél ervaring met andere Shelly-producten. Hun protocol werkt zonder cloud en kan rechtstreeks (lokaal) in home assistant geduwd worden. Dat geeft je meteen open data?
While cleaning a storage room, our staff found this tape containing #UNIX v4 from Bell Labs, circa 1973
Apparently no other complete copies are known to exist: https://gunkies.org/wiki/UNIX_Fourth_Edition
We have arranged to deliver it to the Computer History Museum
Might be required for a tag that needs to send data back to a station which it's driving past at whatever the legal speed limit is in the relevant jurisdiction?
Why do people write a wall of text when a simple "hey, Fedora 43 is out, can you provide packages?" would have sufficed?
I will never understand that.
I moved to South Africa in 2019, having lived for 40 years in Belgium before that.
Belgium has DST, South Africa does not.
Before the move, I thought the DST change affected me for about a week or so.
I now know that it actually affects me the whole year round. My daily rhythm has stabilized over the past few years. I consistently wake up with the Sun now, which I could never do before the move.
DST is a terrible idea.
I tend to just configure my git remotes to not accept pushes to the main branch, only merges. After that it's just a matter of simple git history editing.
Fun fact: the reason it was dropped from later versions of Windows was because it made a number of assumptions that were not true in 64-bit Windows and it was deemed too expensive to port.
Also I found a download somewhere and can confirm it works just fine under wine on Linux 😉
Ik woon in Zuid Afrika en heb al jaaaren een desktop sip-telefoon aangesloten bij 3starsnet (grandstream hardware)
Zijn sindsdien wel overgenomen en heten nu anders, maar werkt gewoon goed, ook met andere sip providers.
I'm fine with dropping RHEL9 and OpenSUSE <15 from our supported distributions 🤷
Is there a workaround for this that you're aware of? Other than "generate RSA keys instead", which technically we could do but which I'd like to avoid if at all possible.
[wouter@rhel rpm-gpg]$ sudo rpm --import RPM-GPG-KEY-BEID-RELEASE
[wouter@rhel rpm-gpg]$ sudo rpm --import RPM-GPG-KEY-BEID-RELEASE-2025
fout: RPM-GPG-KEY-BEID-RELEASE-2025: key 1 import failed.
[wouter@rhel rpm-gpg]$ sudo rpm --import RPM-GPG-KEY-BEID-CONTINUOUS
The only differences are that -2025 is recent and ECDSA NIST P-384, the other two are over 10 years old and need to be rotated, and are RSA.
Does RPM not support ECDSA for code signatures? Or am I doing something wrong?