You remember when your blog, your photos, and your notes all lived on one site you controlled, and people could follow you with RSS instead of an algorithm? That idea never died. It just picked up Webmentions, Micropub, and ActivityPub along the way.
Idno (idno/idno) is the open-source engine behind that movement today. About 1,100 GitHub stars, PHP 8.3+, Apache 2.0 for the core, and a history that longtime indie web folks still call Known. Homepage and docs: idno.co and docs.idno.co. Tagline on the repo: a social publishing platform, not a brochure CMS.
What it actually does
Idno is a personal (or small-community) site where posts, bookmarks, photos, and status updates share one profile. You publish on your domain. People follow you. Plugins extend syndication, indie web protocols, and presentation. The README still ships Bootstrap, Webmention client code, microformats parsers, and media tools because this project grew up alongside the IndieWeb crowd, not inside a SaaS growth team.
Under the hood you install with composer create-project idno/idno or clone Git and run composer install. You need a supported database (check current docs; MongoDB libraries are in the stack). PHP 8.3 is the floor now, which is stricter than the PHP 7 era when Known first went viral on shared hosts.
ActivityPub is the part that trips people up. Follow acceptance, delivering posts to remote followers, and update/delete propagation go through an asynchronous event queue. Turn it on in config.ini with event_queue = 'AsynchronousQueue', then run idno.php service-event-queue under systemd (or cron --once on cheap hosting). Without that worker, ActivityPub events pile up in the database and federated servers never see your updates. That is not optional if you care about the fediverse side.
Why self-host?
Tumblr, Medium, and Threads want your writing in their garden. Idno wants your writing on your hostname. Self-hosting means your export is a database backup, not a support ticket. You choose who registers. You wire your own SMTP. You accept the maintenance cost of PHP, Composer, queue workers, and TLS certificates.
For Canadian creators and small newsrooms, the pitch is familiar: content and account metadata live on infrastructure you can point to in a privacy review. You are not betting a decade of posts on a US platform pivoting to video.
How it compares to our other posts
Ghost is the polished newsletter and membership machine. Ech0 is a younger Go microblog. Haven is invite-only family sharing. Idno sits in indie web territory: your site is the hub, protocols talk to the wider web, and you are expected to run background workers if you federate. HTMLy stays flat-file simple; Idno embraces plugins, events, and federation.
Who should run it
Good fit: indie bloggers who want ActivityPub or Webmentions on their own domain; researchers and educators teaching POSSE; developers comfortable with Composer, queue workers, and occasional plugin debugging.
Skip it: teams that need WooCommerce or enterprise SSO out of the box; anyone on PHP 8.1 shared hosting that cannot run a long-lived worker; founders who want zero-ops and Ghost(Pro) simplicity.
Hosting in Canada
Plan a VPS, not the cheapest shared plan. Idno wants PHP 8.3, Composer dependencies, a real database, and ideally systemd for the queue worker. A CloudBox in Toronto or Cambridge gives you room for nginx, TLS, backups, and the async pipeline without cron gymnastics. Keep the database and uploaded media in Canada if residency language matters to your readers.
Bottom line
Idno is self-hosted social publishing for the indie web: your domain, your posts, federation when you earn it by running the queue. Install with Composer, enable the async worker before you tout ActivityPub, and treat it like infrastructure you own, not a toy PHP blog.
Talk with Swift Host if you want Idno on a Canadian VPS with PHP, workers, and backups handled sensibly. We are in St. Albert and actually answer the phone.