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:
Christomatt
2026-01-27 01:27:15 +01:00
parent 6b8eeb6814
commit eb63194c56
49 changed files with 1173 additions and 3559 deletions
+3 -30
View File
@@ -2,15 +2,13 @@
* Account Moved Notification API
*
* Called by the new node to notify the old node that an account has migrated.
* The old node then marks the account as moved and broadcasts Move activity to followers.
* The old node then marks the account as moved.
*/
import { NextRequest, NextResponse } from 'next/server';
import { db, users, follows } from '@/db';
import { eq } from 'drizzle-orm';
import * as crypto from 'crypto';
import { createMoveActivity } from '@/lib/activitypub/activities';
import { signRequest } from '@/lib/activitypub/signatures';
interface MoveNotification {
oldHandle: string;
@@ -75,37 +73,12 @@ export async function POST(req: NextRequest) {
},
});
const nodeDomain = process.env.NEXT_PUBLIC_NODE_DOMAIN || 'localhost:3000';
const oldActorUrl = `https://${nodeDomain}/users/${user.handle}`;
// Create Move activity with DID extension
const moveActivity = createMoveActivity(
user,
oldActorUrl,
newActorUrl,
nodeDomain
);
// Broadcast Move activity to all followers
// In a production system, this would be queued
let notifiedCount = 0;
for (const follow of userFollowers) {
try {
// For local Synapsis followers, we could update directly
// For remote followers, we'd send the Move activity
// For now, we'll just count them
notifiedCount++;
} catch (error) {
console.error('Failed to notify follower:', error);
}
}
console.log(`Account ${oldHandle} marked as moved to ${newActorUrl}. Notified ${notifiedCount} followers.`);
console.log(`Account ${oldHandle} marked as moved to ${newActorUrl}. ${userFollowers.length} followers.`);
return NextResponse.json({
success: true,
message: 'Account marked as moved',
followersNotified: notifiedCount,
followersNotified: userFollowers.length,
});
} catch (error) {