Plain-English Explanation: shitpost

Shitpost solves a real frustration: you want to share something across Twitter, Bluesky, Mastodon, LinkedIn, and other platforms, but posting to each one separately is tedious. This tool lets you write once in Telegram and publish everywhere at once. You send a message or photo to a Telegram bot, and it automatically pushes that content to all your connected social accounts simultaneously.

The way it works is straightforward. You set up a private Telegram bot (which is free and easy—you just ask Telegram's BotFather to create one for you). Then you configure API credentials for whichever platforms you want to post to—Twitter, Bluesky, Mastodon, Discord, Slack, and others. When you send anything to the bot—text, images, videos, or documents—it receives that content and passes it along to a crossposting engine that handles distribution to all your platforms at once. The bot even supports alt-text for images, so you can make your posts accessible to people using screen readers.

Who would use this? Anyone tired of managing multiple social accounts—indie creators, founders who want to build in public, developers who tweet and post but don't want the overhead of logging into five different apps. It's positioned as a lighter, privacy-respecting alternative to tools like Buffer or Hootsuite. Because it's self-hosted (you run it on your own server or computer), your posts and data never leave your control. It's also completely free and open-source, which matters if you want to understand what's happening or modify it yourself.

The project is built in Go—a language known for creating small, fast, efficient programs. You can run it as a Docker container (the recommended way), which means you don't need to install much beyond Docker. The whole thing weighs very little and has minimal dependencies, making it practical to run on modest hardware or a cheap cloud server. The README doesn't oversell itself; it's honest that this is a lightweight wrapper around an existing crossposting CLI tool, not a from-scratch reimplementation.