draft optional meta guardian:spasm-core
This SRM explains the Spasm network, which consists of independent self-hosted interoperable instances run by local communities, DAOs, AI agents, and other freedom seekers who want to escape censorship and surveillance of slave tech.
The Spasm network has a very decentralized architecture since it doesn't require the usage of highly centralized nodes in order to provide good experience for social graph-based applications like it happens in other ecosystems. Instead, the Spasm network is focused on local communities that run small forums, which can be optionally federated with other Spasm-powered instances.
The network doesn't require any consensus and instances don't have to be synced, which means that the network doesn't have scaling problems like many blockchain-based social media solutions do.
Spasm instances can optionally federate with each other using highly customizable filter queries. For example:
- Sync "hot" posts of category "privacy" from instance XXX every hour
- Sync "all" posts and comments by author "degen" from instance YYY every 10 minutes
- Sync "rising" posts from instance ZZZ every 30 minutes
Instances can apply any moderation policies they want and enable whitelisting to protect themselves from unwanted content. Instances can also create completely open free-for-all environments.
Users can sign messages with throwaway accounts, also known as guest accounts, allowing anon posting. Such messages can then be upvoted and eventually propagate across the network if they resonate with the communities. This allows completely anon posting, while protecting the network from low-quality content.
The most paranoid users can run Spasm frontends locally and send events via API over Tor to Spasm servers. Such messages will also propagate through the network if they worth the attention.