I built this because I was frustrated with the fragmentation of the internet. I love the depth of the Open Web (RSS blogs, news sites), but I also believe in the censorship resistance of the Sovereign Web (Nostr). Switching between Reeder and Damus felt like moving between two disconnected worlds.
EchoDeck is a "Dual-Core" social reader that attempts to bridge this gap.
*The Architecture:*
We use a hybrid approach to solve accessibility and performance:
1. *The Bridge:* We aggregate RSS feeds server-side (solving CORS/privacy issues) and normalize them into Nostr-compatible events. This lets you "Zap" (tip) a blog post via Lightning, just like a social post.
2. *The Tunnel:* To ensure access for users in restrictive regions (like behind the GFW), we deploy edge relay proxies that obfuscate WebSocket traffic, allowing connection to global relays without VPNs.
3. *The Stack:* Built with Next.js 14 (App Router), Shadcn/UI, and a custom Zustand store to handle the high-frequency "waterfall" of WebSocket events without re-render fatigue.
*The "Proof of Engagement" Experiment:*
To prevent spam and ensure high-quality initial growth, I've implemented a gamified invite system.
- New users start with 0 invites.
- You must complete "Quests" (e.g., Subscribe to 3 RSS feeds, Publish 1 Note) to unlock invite codes.
- This creates a "Proof of Engagement" layer—only active users can grow the network.
*Genesis Codes for HN:*
We are in Closed Beta. Here are 10 "Tier 0" Genesis Codes specifically for the HN community. These grant immediate invite privileges so you can bring your friends.
JoeyPro•1h ago
I’m the builder behind EchoDeck.
I built this because I was frustrated with the fragmentation of the internet. I love the depth of the Open Web (RSS blogs, news sites), but I also believe in the censorship resistance of the Sovereign Web (Nostr). Switching between Reeder and Damus felt like moving between two disconnected worlds.
EchoDeck is a "Dual-Core" social reader that attempts to bridge this gap.
*The Architecture:* We use a hybrid approach to solve accessibility and performance: 1. *The Bridge:* We aggregate RSS feeds server-side (solving CORS/privacy issues) and normalize them into Nostr-compatible events. This lets you "Zap" (tip) a blog post via Lightning, just like a social post. 2. *The Tunnel:* To ensure access for users in restrictive regions (like behind the GFW), we deploy edge relay proxies that obfuscate WebSocket traffic, allowing connection to global relays without VPNs. 3. *The Stack:* Built with Next.js 14 (App Router), Shadcn/UI, and a custom Zustand store to handle the high-frequency "waterfall" of WebSocket events without re-render fatigue.
*The "Proof of Engagement" Experiment:* To prevent spam and ensure high-quality initial growth, I've implemented a gamified invite system. - New users start with 0 invites. - You must complete "Quests" (e.g., Subscribe to 3 RSS feeds, Publish 1 Note) to unlock invite codes. - This creates a "Proof of Engagement" layer—only active users can grow the network.
*Genesis Codes for HN:* We are in Closed Beta. Here are 10 "Tier 0" Genesis Codes specifically for the HN community. These grant immediate invite privileges so you can bring your friends.
ECHO-GEN-38DBJ6 ECHO-GEN-38VEHE ECHO-GEN-3MZBUE ECHO-GEN-3QZGN2 ECHO-GEN-4WQV7Y ECHO-GEN-4ZDN53 ECHO-GEN-4ZGFEN ECHO-GEN-5UDBAF ECHO-GEN-6BK8W3 ECHO-GEN-6C4V2D
If these run out, check out the repo or DM me your npub, and I’ll mint a fresh one for you.
github community:https://github.com/Zhaoyi0526/EchoDeck-Community
I’d love to hear your feedback on the "Hybrid" architecture approach!