Jae's Blog

About half an hour ago, Servo re-affirmed their ban of LLM tools laid out in their contribution policies:

Contributions must not include content generated by large language models or other probabilistic tools, including but not limited to Copilot or ChatGPT. This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project.

This is honestly great to hear, as it cements the longevity of the project, avoiding the many headaches associated with AI code generation amongst others.

A little known feature of Git is that you can have conditions, for instance, to have a work and personal name and email.

First, the ~/.gitconfig file:

[includeIf "gitdir:~/src/personal/"]
  path = ~/.gitconfig.personal

[includeIf "gitdir:~/src/work/"]
  path = ~/.gitconfig.work
Code language: PHP (php)

After specifying this, you can then create two files, ~/.gitconfig.personal and ~/.gitconfig.work, containing:

[user]
    email = email@something.com
    name = MyName

and

[user]
    email = jae@consoso.com
    name = Very serious business person

Now, when you are in ~/src/personal/, the personal email and name will be used, and when in ~/src/work/, the work one will be.

Previously, I’ve shared about EUVD, the European Vulnerability Database.

Turns out in the wake of the whole CVE debacle, a bunch of other initiatives were also announced!

• OWASP’s unified framework, this one aims to be a bit more decentralized from what I’ve seen in the article
• GCVE (Global CVE Allocation System), this one as well seems to be a bit more decentralized than before

As more alternatives pile up, this paints a good outlook for the future, shall CVE go definitely down the drain.

The motto of “vibe” coders really is “let the thing do it, don’t check anything ever” because the whole cohort of Cursor users (an IDE with built-in LLMs) really believed a support bot that came up with a fake policy.

Shortly afterward, several users publicly announced their subscription cancellations on Reddit, citing the non-existent policy as their reason. “I literally just cancelled my sub,” wrote the original Reddit poster, adding that their workplace was now “purging it completely.” Others joined in: “Yep, I’m canceling as well, this is asinine.” Soon after, moderators locked the Reddit thread and removed the original post.

This is maybe too much on the nose when talking about LLM users. Vibes-based support is apparently a thing nowadays as well.

You can find the full article on ArsTechnica: https://arstechnica.com/ai/2025/04/cursor-ai-support-bot-invents-fake-policy-and-triggers-user-uproar/

Being currently assigned to the issue about ARM support for Resonite headlesses (GH-2555), time for an update since there hasn’t been one in some time.

First off, everything is looking great, current status being:

• 6 PRs are currently open (FreeImage, Opus, Crunch, Assimp, MSDFGen, RNNoise)
• 1 PR has been merged 🎉 (Brotli)
• 1 repo is missing (Freetype)

This marks the first ARM-related PR being reviewed and merged into an official repository, being the PR #1 on the Brotli repo, which bundled Windows, Linux x64 and Linux ARM CI/CD builds.

As a reminder, I am currently providing a complete package of all libraries built directly for ARM on my website.

Next steps would be to:

• Get an official fork of the Freetype repository (requested on 2025/04/09)
• Create a container image bundling my libraries and a way to download the headless easily on ARM machines
• Get all the current PRs reviewed and merged

The second one is more important as distribution is probably the biggest issue for complete ARM support of the headless, SteamCMD not supporting this architecture.

I am very confident to say that we will reach official support very soon, given how well this has been going so far.

My plans after this feature is shipped is to work on the macOS support (GH-1412) as it’s also marked as “community help wanted”.

A friend sent me a link to an interesting blog post talking about making an Open-Source DMR radio using a LimeSDR board and GNU Radio.

Digital Mobile Radio (DMR) is a mobile radio standard created by ETSI, which is very popular within the amateur radio community. […]
A very basic DMR modem (receiver and transmitter), capable of voice calls, that could emulate a subscriber radio using a SDR transceiver as the radio interface is described in this page.
While this modem is just a proof-of-concept interpretation of the DMR standard with no real use-case, there exists at least one open source project which proposes to create an open source DMR transceiver.

You can see the full blog post over there: https://qradiolink.org/open-source-DMR-transceiver-implementation.html

A little known feature of Steam is that it offers RSS feeds for any app/game/whatever shared using it.

The URL is also very simple to use:

https://store.steampowered.com/feeds/news/app/$AppIDCode language: JavaScript (javascript)

You can then replace $AppID by the application ID of your game.

For instance, if we want to monitor Resonite, app ID 2519830, you will need the following URL:

https://store.steampowered.com/feeds/news/app/2519830Code language: JavaScript (javascript)

There, super easy!

At some point, I had some issues converting some files with ffmpeg, most particularly videos on my Fedora install.

Turns out fixing this is really easy with the help of RPMFusion.

If you haven’t enabled it at the system installation, you can do that really easily via a single command which will install the free and nonfree variants of the repository:

sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpmCode language: JavaScript (javascript)

Now, you can just swap ffmpeg for the RPMFusion one like so:

sudo dnf swap ffmpeg-free ffmpeg --allowerasing

This will install a bunch of codecs and replace the regular build of ffmpeg by a more permissive one (in terms of what you can do, not licensing).

Keep in mind that if you want to keep your system free (as in freedom), you might not want to do this.

I’ve recently discovered that the EU has their own vulnerability database: EUVD.

As noted by the message on top of the page:

This website is currently in its beta phase. We appreciate your collaboration in reporting any inaccurate or incomplete information via the link below “Provide feedback”.

The site is still in a really early stage, but hopefully it gains a bit more traction as the future of other vulnerability databases is uncertain (for instance, with CVE almost dying abruptly due to a contract ending).

As of now, there also are no feeds (RSS more particularly) to watch this database, so hopefully this will be added soon.

Enabling DNSSEC on systemd-resolved is quite easy.

First, let’s go in /etc/systemd/resolved.conf.d/main.conf and add/modify the file like so:

[Resolve]
DNSSEC=true
Code language: JavaScript (javascript)

For good measure, you can also enable DoT (DNS Over TLS) in there, which you can use with something like DNS0.

Restart systemd-resolved using systemctl restart systemd-resolved and voilà.

Now, if you type something like resolvectl query j4.lc, you should get an answer like so:

j4.lc: 95.217.179.88                           -- link: enp6s0
       2a12:4946:9900:f00::f00                 -- link: enp6s0

-- Information acquired via protocol DNS in 141.7ms.
-- Data is authenticated: yes; Data was acquired via local or encrypted transport: yes
-- Data from: network
Code language: CSS (css)

On the contrary, if you try to query a domain which has an invalid signature, for instance with resolvectl query badsig.go.dnscheck.tools, you will get:

badsig.go.dnscheck.tools: resolve call failed: All attempts to contact name servers or networks failed
Code language: CSS (css)

Do note some domains might stop resolving because of this, in which case, contact their admin so they can correct the issue.

Also, on my side, resolution hangs rather than displaying a proper error, which seems to be something like this bug (or maybe another, haven’t looked too much into this yet) on the systemd issue tracker.