Anonymux has been running quietly for a while now — products shipping, clients onboarded, infrastructure built and rebuilt. There's been no shortage of things worth writing about. There just hasn't been anywhere to put them.
That changes today. This is the Anonymux blog.
Why bother
A few reasons, honestly. The practical one first: search. A static product site with no new content is nearly invisible to search engines after the initial crawl. A blog — even a sparse one, updated a few times a month — gives crawlers a reason to come back, and gives people searching for things you actually do a way to find you. That matters more as the product surface grows.
But the more useful reason is transparency. Anonymux is a small operation — one person, multiple products, a shared infrastructure model that most hosted services don't bother explaining. When something changes, when a policy gets updated, when a product ships — there's currently no place to say so formally. That creates a gap between what's actually happening and what any given user can know about it.
A blog is the lowest-friction way to close that gap without building something heavier.
It also creates a record. Legal notices, terms changes, privacy policy updates — these things should exist somewhere permanent, findable, and dated. This is that place.
What gets posted here
Five kinds of things:
When something ships or changes meaningfully — new endpoints, new features, breaking changes, deprecations.
New products, major launches, and milestones. Higher-signal than a routine update — things worth marking separately.
Policy updates, terms changes, legal notices. Formal and dated so there's a clear record.
Writing that's useful to people searching for things Anonymux products actually do — not keyword stuffing, just honest explainers.
Occasional longer pieces on building software, infrastructure decisions, and the thinking behind how Anonymux is put together.
How often will posts be?
There's no fixed posting schedule. Posts go up when there's something worth saying — a product ships, a policy changes, an infrastructure decision is interesting enough to document. That might mean two posts in a week, then nothing for a month. Quantity isn't the goal; having a reliable place to put things is.
The index at anonymux.org/blog is filterable by category, so if you only care about notices or only care about product updates, you don't have to scroll past everything else. An RSS feed is on the list — it'll be at /blog/feed.xml when it's ready.
Why RSS?
RSS is 25 years old and still the best way to follow a site without handing your attention to an algorithm. You subscribe to a feed URL, your reader polls it, and new posts show up in chronological order — no engagement scoring, no promoted content, no notification manipulation. It works the same whether the site has ten readers or ten thousand.
Most people rediscover RSS when they get tired of social media being the only way to follow things they care about. If you're not using a feed reader, FreshRSS (self-hostable feed aggregator) is typically a solid option. The Anonymux feed will be standard Atom — it should work with any reader.