refactor: Migrate from ActivityPub federation to native Swarm network
- Remove ActivityPub infrastructure (webfinger, nodeinfo, inbox, activities, signatures) - Implement native peer-to-peer Swarm network with gossip protocol - Replace federated timeline with Swarm timeline aggregating posts from all nodes - Migrate direct messaging to end-to-end encrypted Swarm Chat system - Update user interactions (follow, like, repost) to use Swarm protocol - Add cryptographic key management for DID-based identity system - Remove server-bound identity model in favor of portable DID identities - Update documentation to reflect Swarm architecture and capabilities - Add debug utilities and chat testing tools for Swarm network - Refactor database schema to support distributed user directory - Update bot framework to work with Swarm network interactions - Simplify API routes to use Swarm protocol instead of ActivityPub - This transition enables true peer-to-peer communication, instant interactions, and encrypted messaging while maintaining sovereign identity through DIDs
This commit is contained in:
+5
-5
@@ -9,7 +9,7 @@ A real-time, end-to-end encrypted chat system built exclusively for the Synapsis
|
||||
- **Real-Time Delivery**: Messages delivered instantly via swarm inbox
|
||||
- **Read Receipts**: See when messages are delivered and read
|
||||
- **Typing Indicators**: Know when someone is typing (coming soon)
|
||||
- **No ActivityPub Limitations**: Built specifically for swarm, not constrained by AP spec
|
||||
- **Native Swarm Protocol**: Built specifically for the swarm network
|
||||
|
||||
## Architecture
|
||||
|
||||
@@ -141,14 +141,14 @@ Test the chat system:
|
||||
4. Send a message
|
||||
5. Check the other account's `/chat` page
|
||||
|
||||
## Differences from ActivityPub DMs
|
||||
## Why Swarm Chat?
|
||||
|
||||
Traditional ActivityPub direct messages are just posts with limited visibility. Swarm Chat is superior:
|
||||
Swarm Chat was built from the ground up for the Synapsis network:
|
||||
|
||||
- **True E2E Encryption**: Not possible with ActivityPub
|
||||
- **True E2E Encryption**: Messages encrypted with recipient's public key
|
||||
- **Real-Time**: Direct delivery, no polling required
|
||||
- **Proper Chat UX**: Conversations, read receipts, typing indicators
|
||||
- **Lightweight**: No heavyweight ActivityPub overhead
|
||||
- **Lightweight**: Simple JSON protocol
|
||||
- **Swarm-Native**: Built for the swarm, not retrofitted
|
||||
|
||||
## Contributing
|
||||
|
||||
Reference in New Issue
Block a user