Edition No. 3

What it is

A desktop screen recorder that captures your screen and webcam and produces a shareable link, in the mould of Loom. Its distinguishing trick is automatic zoom: it follows your cursor and pushes in on whatever you are clicking, without you editing a single keyframe.

What it is good for. Anyone selling something that is hard to describe in a sentence. Some ideas land in a video and die in a paragraph, and everything else in the marketing depends on someone understanding the product first. This is not about replacing an editing suite — it is about the twenty other recordings nobody opens an editing suite for: a reply to a support question, a feature teaser, a clip for a cold email. The auto-zoom removes the exact step that makes those feel cheap, and because the share link reports who watched and how far, a demo becomes a measurable marketing asset rather than a file.

What it is

A command-line tool that drives a headless browser to take screenshots of web pages, from a single URL or from a YAML file describing dozens of shots. Version 1.10 added video recording, so the same file can also produce short WebM clips of a scripted interaction.

What it is good for. Every marketing site quietly rots: you ship a UI change and the screenshots on your landing page, your docs and your README are suddenly of software that no longer exists. Nobody hand-fixes twenty screenshots, so they simply stay wrong, and a stale screenshot reads as an abandoned product to a first-time visitor. Describe the shots once in a YAML file and regenerating all of them is one command — which means it can run automatically whenever you deploy. It is also the cheapest way to get bilingual assets: point the same shot list at ?lang=ru and you have a complete Russian screenshot set for free.

What it is

A small Python package that reaches Microsoft Edge's online text-to-speech service without needing Edge, Windows or an API key. It returns MP3 audio plus word-boundary timings, and ships both a command-line tool and a Python API.

What it is good for. Anyone already paying per word for voiceover, which is the right call for the version that ships. The problem is that paying per draft is what stops the drafting: you write the script once, narrate it once, and never test a second phrasing of the intro. This makes the draft free. Narrate every version, listen back, cut the boring thirty seconds, and only then spend paid credit on the final cut — and do the same for a Russian edition, where the Microsoft voices are unusually good.

What it is

A web framework built for content-driven sites. It renders pages to plain static HTML by default and ships no JavaScript unless a component genuinely needs it, so pages arrive fast and complete.

What it is good for. This is the structural fix for the problem Unlighthouse (Edition 2) will report and cannot solve. A React single-page app hands a crawler an empty shell and a pile of JavaScript; Google sometimes copes, AI crawlers frequently do not, and Core Web Vitals suffer either way — on exactly the marketing pages that most need to rank. Astro flips it: the blog, the landing pages, any second-language pages and /llms.txt become static HTML at the edge of the domain, while the application itself stays React and unchanged at /app. It is also where programmatic SEO becomes possible — one template plus a list of use cases generates a hundred real, indexable pages.

What it does

Fider puts up a public board at an address you choose. Anyone who signs in can post an idea, vote on anybody else's, and reply in a threaded comment. The person running the board gives each post a status and writes an official response, which sends an email to everyone who voted and can also send a message to another system through a webhook. Each board gets its own title, welcome message, branding and shareable link, and search across posts. Posts can be tagged and grouped. Signing in is by a link emailed to you, with optional sign-in through Google, GitHub or Facebook; voting requires being signed in, which is deliberate — it is what stops one person voting fifty times — and it is also the main thing people grumble about. It is translated into several languages, and a multi-board mode serves separate boards on separate subdomains. It ships as a single program written in Go serving a browser interface, backed by PostgreSQL 12 or newer, distributed as a container. It will not run usefully without an outbound email provider — one of SMTP, Mailgun or Amazon SES is mandatory and the no-reply address has no default. It is not a help desk: there are no agents, queues, assignment, service-level targets, canned replies or private one-to-one conversations, because everything on it is public. It is not a live chat widget and not a customer-records system. There is no built-in roadmap board, no mobile app and no in-application widget — you send people a link.

Why it matters

Who it suits. Anyone shipping software to more than a few dozen people who is currently guessing what to build next, and who would rather have the argument in public than in a support inbox. It suits open-source maintainers particularly well, because the board doubles as a filter: an idea nobody votes for is an answer in itself. Skip it if what you actually need is a ticket queue with assignment and private threads — that is a different product — and skip it if you have no way to send email.

What people say. Independent editorial coverage of Fider is genuinely thin for a nine-year-old project, and we would rather say so than pad it. The one real hands-on account is by Isaac Johnson, a named cloud architect, at freshbrewed.science on 3 June 2025, and it is useful precisely because it is critical: his container kept crashing until he filled in the mail settings, he found the email verification for the first administrator "seems silly", the verification message never arrived and he had to dig the link out of his mail provider's logs, and he noted that the sign-in-by-email model "might be a challenge". His conclusion after moving it to Kubernetes with a mail provider and TLS was "Once in Kubernetes, it worked like a charm". He sells nothing and has no connection to the project. The second useful source is the project's own security record: advisory GHSA-wjrq-7x2x-9p48, published 5 October 2026, was reported by an outside researcher and describes unescaped user names and post titles landing misleading links in other people's notifications; it was patched the same day in version 0.38.2, with an honest note that notifications created before the upgrade are not rewritten. Fider also appears as a one-click template on several hosting platforms — Railway, Hostinger, Dokploy — which is evidence of distribution rather than quality, and every one of those companies makes money when you deploy through them.

Verdict. The most complete product in this edition, and the reason it earns a second outing: nine years old, code pushed the day before this was written, a release five days before that whose headline content is two externally reported security fixes plus a hardening pass, and 31 open issues against 4,572 stars — a tracker somebody is grooming rather than abandoning. Run it for an evening and the hard part is the mail provider, not the software. Four practical warnings. Encryption is off by default and the program binds every network interface on port 3000, with the documented container mapping that to port 80, so put a proxy in front. Signups are open by default. The docker-compose.yml in the repository is a development file full of hardcoded passwords — do not deploy it. And there is no latest tag on its container registry, so pin a version. The closest alternatives are logchimp/logchimp and clearflask/clearflask; the second is Apache-2.0 rather than AGPL, which matters if the network clause is a problem.

What it is

A self-hosted platform for feature flags and A/B experiments, with a statistics engine that reads results directly from your own data warehouse. It has SDKs for React and Python among two dozen others.

What it is good for. Worth being straight about this one, because it is the entry most likely to waste time if taken at face value. The experimentation half is not yet useful on a small site: reaching statistical significance on a landing-page test needs thousands of visitors, and running underpowered tests is worse than running none because you will act on noise. The flag half, though, is worth it today — shipping a half-finished feature behind a flag that only the team can see means you stop maintaining long-lived branches, and turning a broken feature off becomes a toggle rather than a redeploy at midnight. Install it for the flags, get the habit, and let the experiments become useful later.

What it is

A clean, typed Python wrapper around the YouTube Data API. It covers channels, playlists, videos, comments and search, handles OAuth, and returns proper objects instead of raw dictionaries.

What it is good for. YouTube Studio tells you about today. It is poor at telling you about trends, useless for tracking anyone else, and it cannot do a chore across forty videos at once. With this, three jobs become scripts you write once with Claude Code and forget: pull every video from a list of channels teaching similar tools and diff it weekly, so a competitor's new topic arrives as a notification rather than a discovery three months late; snapshot your own titles, views and descriptions into PostgreSQL nightly, so you can see which bilingual pairing outperforms; and rewrite the link block in every description in one pass when a URL changes.

What it is

A self-hosted platform-as-a-service you install on your own server: push-to-deploy from Git, automatic HTTPS certificates, environment variables, logs and scheduled database backups, all from a web interface.

What it is good for. This is the wildcard, and it is here because of arithmetic. Across three editions the radar has now suggested a dozen self-hosted services, and each one installed is another container to renew a certificate for, another database to remember to back up, another thing that fails silently at 3am. That burden lands entirely on one person who would rather be doing marketing. Coolify collapses it into one screen — deploys, TLS, logs and, crucially, scheduled Postgres backups you configure once. The honest caveat is that it becomes a single point of failure, so do not migrate the main application into it first. Put the next thing you deploy behind it, live with it for a fortnight, and move the important things only once you trust it.

What it is

A document parser from IBM Research, now under the LF AI & Data Foundation, that converts PDF, DOCX, PPTX, XLSX, HTML and images into clean structured Markdown. It preserves reading order, headings and table structure, and runs locally on CPU.

What it is good for. A tool that promises to handle "chat, discussion or document" only makes the document half real when someone can drop a 90-page PDF on the page and get a map back. That is the moment the addressable audience changes shape: not just people with long AI conversations, but anyone holding a research report, a contract, a set of meeting minutes or a textbook chapter. Docling is the shortest credible path there, and because it runs on CPU locally, no document ever leaves the machine doing the work — a real selling point for anyone considering pasting something confidential. Its Markdown output feeds straight into Chonkie (Edition 2).

What it is

A topic-modelling library that embeds documents, clusters them, and labels each cluster with the words that distinguish it. It supports hierarchical topics, topics over time, and swapping in your own embedding model.

What it is good for. This is the economic counterweight to GraphRAG from Edition 1. GraphRAG produces a beautiful nested hierarchy and charges thousands of LLM calls per document to do it — fine as a premium tier and ruinous as the default path for a free trial. BERTopic reaches a comparable structure by clustering embeddings, so the marginal cost of mapping a conversation is CPU time rather than API spend. Its hierarchical mode gives you the parent/child structure a drill-in UI needs, and its topics-over-time view is close to a feature in itself. Pair it with model2vec (Edition 1) as the embedding backend and the whole thing fits comfortably on a small VPS.

What it is

A React graph-visualisation library that renders nodes and edges in WebGL, with fifteen or more built-in layouts, clustering, path-finding and both 2D and 3D modes. It is built for graphs too large to draw as HTML elements.

What it is good for. React Flow from Edition 1 is the right canvas for a readable detail view, and it starts to struggle somewhere past a thousand or two visible nodes because every node is a real DOM element. A 500-message thread with nested subtopics reaches that. Reagraph is the answer to that specific ceiling rather than a replacement: WebGL draws the whole constellation at once, the user picks a cluster, and you hand off to React Flow for the readable drill-in. Worth noting that the repository ships a CLAUDE.md, which means Claude Code has maintainer-written guidance for it.

What it is

A library that extracts hundreds of statistical features from time-series windows — trends, autocorrelations, entropy, peak counts and far more — then runs hypothesis tests to discard the ones with no relationship to your target.

What it is good for. Anyone hunting trading strategies runs out of imagination before they run out of data. Hand-picking indicator combinations means you test the twenty ideas you happened to think of, so the result depends on the ideas rather than on the data. This inverts it: cut three years of price history into windows, label each by what price did next, extract everything, and let the statistical filter tell you which properties actually carry signal. It complements STUMPY from Edition 1 rather than competing — STUMPY finds shapes that repeat, tsfresh finds properties that predict — and whatever survives either search should go straight to backtesting.py (Edition 2) before you believe a word of it.