You can enable default federation in the admin panel, which has several lists of pre-configured instances and filters focused on topics like crypto, privacy, tech, or politics. By default, your instance checks these lists once an hour for "rising" posts and comments. You can also enable custom federation links, which can include other Spasm instances as well as regular RSS feeds, since Spasm's agnostic architecture supports various protocols, private keys, and even unsigned legacy RSS posts. Custom federation allows you to use different filters and update frequencies for each source. The custom federation list is public, so you can see an example at this instance, which has a lot of RSS sources: https://degenrocket.space/admin If you want to keep your federation list hidden, then you can configure it through an environment variable.

To prepare Spasm for an increasingly hostile environment amid regulators' relentless push for more dystopian restrictions on open source software, we're diversifying infrastructure. All Spasm git repos are now mirrored across multiple platforms to increase resilience and censorship-resistance. Self-hosted Forgejo https://git.spasm.network/spasm-network Slave tech platforms: https://codeberg.org/spasm-network https://github.com/spasm-network --- All Spasm commits have been cryptographically signed with GPG since day one to guarantee security. You can verify commits against these keys: https://git.spasm.network/degenrocket.gpg https://codeberg.org/degenrocket.gpg https://github.com/degenrocket.gpg --- Ready to unplug yourself and your community from slave tech? Launch Spasm under three minutes with Docker/Podman: [Forgejo](https://git.spasm.network/spasm-network/spasm-docker) [Codeberg](https://codeberg.org/spasm-network/spasm-docker) [Github](https://github.com/spasm-network/spasm-docker) Deploy Spasm on a new VPS with one script: [Forgejo](https://git.spasm.network/spasm-network/spasm-ansible) [Codeberg](https://codeberg.org/spasm-network/spasm-ansible) [Github](https://github.com/spasm-network/spasm-ansible)

You can now launch your Spasm forum on a new VPS with just [one script](https://github.com/spasm-network/spasm-ansible), which handles everything automatically: industry-standard hardening, app installation with Podman, and auto-updates. Enjoy a fully autonomous setup that requires zero server maintenance. As regulators continue tightening their grip on slave tech platforms, Spasm equips you with the best tools to escape walled gardens and reclaim your right to the freedoms of association and speech.

For the past five years, running a Spasm instance required messing around with environment variables, but not anymore. The web admin panel has been fully reworked in the effort to simplify the process of setting up a Spasm forum. You can now customize your entire instance with soy GUI using just a private key. Spasm doesn't utilize any account-based slave architecture with cookies or other outdated tech. Instead, all administrative events are directly signed with a private key, just like any other message within the Spasm ecosystem. No accounts, no cookies, no web2 bullshit. Make changes. Sign. Done. You can view the new panel live at various instances, e.g.: https://forum.spasm.network/admin Managing a forum through direct signing demonstrates Spasm's potential beyond social media. It can serve as a foundational infrastructure for diverse applications, from decentralized GitHub and NPM to podcasting platforms, streaming services, gaming ecosystems, and more. You want to integrate your web3 solution into Spasm as a module? You're welcome to do that because Spasm is not the full tech stack; it's the robust base layer for web3. In fact, independent teams have already built alternative Spasm frontends with unique architectures. The future is direct signing of all online interactions, and Spasm is the most advanced protocol to lead this transition. Think of Spasm as the 'https' of web3. No more fake web3 logins. No more slave tech. Only direct signing. Only self-custody. Only freedom.