I have been using Miniflux as my feed reader for a couple of years now. As mentioned in a previous note, I have customized it to add custom sorting for articles. In the last note I added sorting by similarity. In this note, I add another method to it: sorting by signal.

I have been using Miniflux as my feed reader for a couple of years now. As mentioned in a previous note, I have customized it to add custom sorting for articles. In the last note I added sorting by similarity. In this note, I add another method to it: sorting by signal.

What does Python have to do with Functional Programming? A LOT as it turns out. Come join us at an offline meetup for all Functional Programming and Python…

Showcase of the fonts used on abhinavsarkar.net.

Showcase of the fonts used on abhinavsarkar.net.

Jensen Huang, the NVIDIA CEO and wearer of the most midlife crisis looking leather jackets in the world, was on Ezra Klein’s podcast. Now I don’t really want you do go through all of what was being said in that recording/writeup. It’s painful. You feel your mental capabilities decaying with every minute of listening … […]

For years I used compfuck, my little Brainfuck-to-Carp compiler, to explain the shape of a Futamura projection, even though I knew it wasn’t quite…

How does the math library's trigonometric function work?

Complexity has to live somewhere; but it does not have to live everywhere.

The unification-fd package by wren gayle romano is the de-facto standard way to do unification in Haskell. You’d use it if you need to implement type inference for your DSL, for example.

_I wrote this post for a prompt given during ourlocal Indieweb club meeting: “Write about non-negotiables in your personal space.”_ My MacBook Pro is my digital personal space on which I spend hours every day. Absence of some particular tools and capabilities is a deal breaker for me now, even if I switch to a different laptop or OS. First, I require a tiling window manager to use anything at all on my laptop. I don’t want to bother with moving windows around, fixing overlaps, changing their sizes etc. The window manager should do these for me and should be drivable by keyboard shortcuts. Currently I use Amethyst on macOS. Next, I want to configure my machine programmatically instead of going around tweaking hundreds of knobs. Not only is it cumbersome, but fairly non-reproducible too. Another reason I want this is to be able to easily move my configurations over time to newer machines I get. Currently I use nix-darwin and home-manager for this purpose. Since I write a lot of text (code and prose), a fast editor is indispensable for me. It has to be configurable too, because I like to adapt it to my liking. The editor for code should support popular programming languages and color schemes. Currently I use Zed and Bear. A fast editor must be accompanied by a fast terminal. Again, it needs to have good configurability, but I generally don’t require many external plugins. I mostly use default layouts, and do not require scriptability. Currently I use Ghostty. Dark mode support is must have for all applications I use. In 2026, if your app doesn’t support dark mode, I’ll drag it to the trash bin without batting a single eyelash. I spend a lot of time looking at code, so I like having nice looking and highly legible monospace fonts. My current favourites are Pragmata Pro, Fira Mono and Jetbrains Mono. As a programmer, I use CLI tools all the time. So I definitely value them enough to get to know them and make informed choices. I like my tools to be fast, feature-full, easy to learn, and composable with other tools. I list many of the tools I use in this post I wrote a few years ago: Software I use on my MacBook. * * * I may be forgetting a few more, but I think this covers the most important ones. If you have any questions or comments, please leave a comment below. If you liked this post, please share it. Thanks for reading!

_I wrote this post for a prompt given during ourlocal Indieweb club meeting: “Write about non-negotiables in your personal space.”_ My MacBook Pro is my digital personal space on which I spend hours every day. Absence of some particular tools and capabilities is a deal breaker for me now, even if I switch to a different laptop or OS. First, I require a tiling window manager to use anything at all on my laptop. I don’t want to bother with moving windows around, fixing overlaps, changing their sizes etc. The window manager should do these for me and should be drivable by keyboard shortcuts. Currently I use Amethyst on macOS. Next, I want to configure my machine programmatically instead of going around tweaking hundreds of knobs. Not only is it cumbersome, but fairly non-reproducible too. Another reason I want this is to be able to easily move my configurations over time to newer machines I get. Currently I use nix-darwin and home-manager for this purpose. Since I write a lot of text (code and prose), a fast editor is indispensable for me. It has to be configurable too, because I like to adapt it to my liking. The editor for code should support popular programming languages and color schemes. Currently I use Zed and Bear. A fast editor must be accompanied by a fast terminal. Again, it needs to have good configurability, but I generally don’t require many external plugins. I mostly use default layouts, and do not require scriptability. Currently I use Ghostty. Dark mode support is must have for all applications I use. In 2026, if your app doesn’t support dark mode, I’ll drag it to the trash bin without batting a single eyelash. I spend a lot of time looking at code, so I like having nice looking and highly legible monospace fonts. My current favourites are Pragmata Pro, Fira Mono and Jetbrains Mono. As a programmer, I use CLI tools all the time. So I definitely value them enough to get to know them and make informed choices. I like my tools to be fast, feature-full, easy to learn, and composable with other tools. I list many of the tools I use in this post I wrote a few years ago: Software I use on my MacBook. * * * I may be forgetting a few more, but I think this covers the most important ones. If you have any questions or comments, please leave a comment below. If you liked this post, please share it. Thanks for reading!

The Register of British Slave-traders compiles and presents information on all known slave-traders in Britain who invested in the trafficking of captive Africans from 1563 to 1807.

Comments

Over the years, this website has accumulated many interesting and atypical features and pages. Most visitors either browse the homepage or land on individual posts from syndications and social media, and never click around enough to notice and experience all the intriguing things scattered around the website. So I decided to jot some of them down in this note1.

Decades of consistency, lost in an update.

How to avoid space leaks on lazy setting How to avoid space leaks on lazy setting Table of Contents 1. A classification of...

Default browser presentations have converged to mostly obsolete the venerable resets of yore. That does not mean they converged to an ideal place. Like my beloved Emacs, several defaults that are popular to change, but persist for backward compatibility. This layer is for fixing those. I want this layer to be unopinionated, but what’s unopinionated tends to be a matter of opinion. It should at least be fit for reuse as a low-priority layer on other projects. Download the complete `cromulent-better-defaults.css` layer. ## Logical properties # Logical properties and values are favored over the traditional physical properties. I write almost exclusively in left-to-right languages, but I’m a sucker for linguistics and fun abstractions. ## Border box sizing # `border-box` sizing includes the padding and margin of a box in its width and height, which substantially simplifies layout calculations. MIT *, *::before, *::after { box-sizing: border-box; } The simplified box sizing also simplifies the modal dialog dimensions, from which we no longer need to subtract 6 pixels for the border. MIT dialog:modal { max-inline-size: calc(100% - 2em); max-block-size: calc(100% - 2em); } ## Body height # We want the body to take 100% of the viewport to keep footers at the bottom or to vertically center, `vh` is common here. `vb` refers to the block axis rather than the height, and the `s` stands for small viewport. MIT body { min-block-size: 100svb; } ## Replaced elements # Replaced elements have “natural dimensions” that are “outside the scope of the CSS formatting model.” Those dimensions tend to flow better as block elements. `max-inline-size` doesn’t refer to `inline` display, which we just overrode, but is a logical property that constrains the width in horizontal writing mode and the height in vertical. `block-size` refers to the other dimension, which we want auto-scaled to maintain the replaced element’s aspect ratio when `max-inline-size` shrinks it. MIT audio, canvas, embed, iframe, img, input[type="image"], object, video, svg { display: block; max-inline-size: 100%; block-size: auto; } ## Indentation # Several elements default to a `margin-inline-start` in `px` for indentation. I prefer font-relative `ch`, or the width of the character `0`. MIT blockquote, figure, dd { margin-inline: 4ch; } Other elements use `padding-inline-start`. MIT menu, ol, ul { padding-inline: 4ch; } ## Text wrapping # Headers and header-likes are typically short. They look best when the lines are balanced to a similar length. MIT h1, h2, h3, h4, h5, h6, hgroup, summary, dt, th, caption { text-wrap: balance; } Longer-form elements can be improved with pretty wrapping. MIT p, li, dd, blockquote, figcaption { text-wrap: pretty; } ## Form fonts # Form elements’ fonts are often overridden by the user agent, and it’s fashionable to reset them to inherit from the parent element. I actually think it’s an ideal case for `system-ui`. MIT button, input, select, textarea { font-family: system-ui; font-size: inherit; } ## Specific elements # ### `<address>` # `<address>` is a useful semantic element, but there’s no reason to render it as italics. MIT address { font-style: normal; } ### `<hr>` # Default `<hr>` representations aren’t as diverse as they used to be, but they bring in a border style (`inset`) and color (`gray`) that don’t quite fit elsewhere. MIT hr { border: 0; border-block-start: 1px solid currentColor; } ### `<hgroup>` # `<hgroup>` is a relatively obscure element that allows “secondary content”, or subheadings. They will be smaller than the main heading, but maintaining the bold helps associate them with the primary heading. MIT hgroup p { font-weight: bold; } ### `<textarea>` # Allow the user to see more text, but gently protect them from dragging it into a horizontally scrolling hellscape. MIT textarea { resize: vertical; }

Comments

**Location:** Lincoln, Nebraska, USA **Employment type:** Volunteer **Term:** Permanent **Compensation:** $0 **Reports to:** The community **Direct reports:** None **Start date:** Immediate We’re looking for a passionate, self-directed engineer to take full ownership of one of the most widely deployed libraries in the ecosystem. This is a rare opportunity to make a real impact on software that millions of developers depend on every single day. If you thrive on autonomy, love working in the open, and want to wear many hats in a fast-paced environment, we’d love to hear from you. **About the role** As Senior Open Source Maintainer you will be the primary technical owner and public face of the project. You’ll drive the roadmap, ship releases, support a global user base, and champion the project across the wider industry. This is a highly visible individual contributor role with enormous scope. No two days are the same, and you’ll have full autonomy to decide how you spend your time. **What you’ll do** * Own the technical roadmap and long-term architectural direction * Review and merge contributions from a diverse, global community of open source developers * Triage and prioritise the issue tracker and feature request backlog * Maintain comprehensive documentation, examples, migration guides, and API references * Ensure project websites and documentation meet current accessibility standards * Cut releases across all supported major version lines and write the release notes * Own the CI pipeline, release automation, and package publishing infrastructure * Keep dependencies current and promptly action automated update pull requests * Support users on GitHub, Discord, Slack, Stack Overflow, Mastodon, Bluesky, and email * Ensure compatibility across all current runtimes, operating systems, and architectures * Preserve backwards compatibility, including widely relied-upon undocumented behaviour * Coordinate release timing with downstream distributions, registries, and redistributors **You’ll also** * Participate in the on-call rotation for incidents at downstream production deployments * Support enterprise consumers where project issues block business-critical systems * Define and communicate support, deprecation, and end-of-life policies for all release lines * Provide migration guidance to adopters upgrading from end-of-life releases * Coordinate advisories, CVE records, disclosure timelines, and researcher credits * Ship embargoed CVE patches across all supported version lines within the disclosure window * Produce SBOMs, VEX statements, and signed provenance attestations for every release * Maintain reproducible builds and independently verifiable release artifacts * Complete supplier security assessments and questionnaires for enterprise consumers * Remediate findings from OpenSSF Scorecard, dependency scanners, and compliance platforms **As well as** * Review high volumes of contributions from AI coding agents and automated refactoring tools * Triage vulnerability reports generated by commercial AI security scanners * Champion the project at international conferences, on podcasts, and across social media * Moderate all community spaces and enforce the Code of Conduct * Engage constructively with feedback shared on social media and public forums * Represent the project in working groups, standards bodies, and regulatory consultations * Prepare grant applications and quarterly reports for current and prospective funders * Administer domains, trademarks, signing keys, cloud accounts, and social media * Advise enterprise legal teams on licensing, patent, warranty, and export control matters * Own the succession plan: identify, recruit, and onboard your replacement **How we’ll measure success** * GitHub stars * Time to first response on issues and pull requests * Release cadence and mean time to patch for disclosed vulnerabilities * Open issue and stale pull request backlog * Dependency freshness * OpenSSF Scorecard result and other automated project scoring * Community sentiment across public channels * Downstream adoption * Bus factor **What we’re looking for** * 8+ years of professional software engineering experience * Deep expertise in one systems language and professional proficiency in at least four others * Written communication pitched to audiences from first-time contributors to Fortune 500 CISOs * Consistent release cadence with minimal dependency churn and no breaking changes * Comfortable across engineering, support, security, community, marketing, finance, and legal * Balances contributors, enterprises, security researchers, regulators, and automated systems * Comfortable receiving direct public feedback and turning it into improvements * Availability overlapping core business hours in AMER, EMEA, and APAC * Able to respond to time-sensitive security matters outside normal working hours * Provides own hardware, reliable internet, and test environments for all supported platforms **Nice to have** * Prior experience in technical writing, developer relations, or community management * Experience migrating existing codebases to memory-safe languages * Working knowledge of licence compatibility and international trademark registration * Grant writing and nonprofit financial reporting experience * Media training * An established personal audience on at least one major social platform * Conversational proficiency in a second and third language * A second job **What we offer** * 100% remote, work from anywhere in the world * Complete flexibility over your working hours * High-impact work depended on by startups and Fortune 500 companies alike * Exceptional visibility and personal brand building opportunities * Regular speaking slots at leading industry events * The opportunity to develop close working relationships with several national CERTs * A passionate, highly engaged global user community * GitHub Sponsors enabled on the repository **How to apply** Please submit a CV, a link to your GitHub profile, and a short cover letter telling us what ownership means to you. Our interview process consists of a recruiter screen, a technical interview, a system design round, a take-home exercise, and a final community panel. If you don’t meet every requirement listed above, we’d still encourage you to apply. We are committed to building a diverse and inclusive community and welcome applicants from all backgrounds. This position will remain open until filled. Due to the volume of applications received, we are unable to respond to every candidate individually. _This role is not eligible for relocation assistance or visa sponsorship._