Like others, I used to use StatusNet back when it powered identi.ca, and abandoned it when they switched to pump.io and everything broke.<p>I considered running my own StatusNet&#x2F;GNUSocial&#x2F;pump.io instance, or even writing an OStatus plugin for the CMS I used to run my site on, but have come to the realisation that such software isn&#x27;t the right path for federation.<p>If I were running a popular site with many users, e.g. a forum, then such features might be nice to add. But hosting my own multi-user, dynamic, OAuth-based Web app just for myself is crazy; especially when the only other thing my server hosts is a static HTML site (I had the same realisation that a multi-user, dynamic CMS Web app was also insecure overkill). In fact, I never used to use the identi.ca Web site anyway; I used the XMPP bot until it got turned off, then switched to RSS feeds and a custom posting command ( <a href="http:&#x2F;&#x2F;chriswarbo.net&#x2F;git&#x2F;warbo-utilities&#x2F;branches&#x2F;master&#x2F;web&#x2F;status" rel="nofollow">http:&#x2F;&#x2F;chriswarbo.net&#x2F;git&#x2F;warbo-utilities&#x2F;branches&#x2F;master&#x2F;we...</a> )<p>Unfortunately I&#x27;ve not seen a simple, single-user, no-authentication-required, non-Web-app (preferably commandline) implementation of these protocols (OStatus, Salmon, webmention, etc.) which I could use alongside a standalone, untrusted API endpoint on my server.<p>I spotted some IndieWeb links on HN a few weeks ago and some of what they say resonates with me, e.g. <a href="https:&#x2F;&#x2F;indiewebcamp.com&#x2F;monoculture" rel="nofollow">https:&#x2F;&#x2F;indiewebcamp.com&#x2F;monoculture</a> Unfortunately, some of their technology seems heavily focused on non-federated, non-FOSS walled gardens which I don&#x27;t want to be part of (e.g. IndieAuth can use a Google account, a GitHub account, a Twitter account, etc. It claims to support email, but that seems to have died since Mozilla Persona shut down)