In short
Harbor is an open-source, distributed social network built on the Polycentric protocol.
REACTAWSGCP
π About the job
Harbor is an open-source, distributed social network built on the Polycentric protocol. Users own their identity and data, publish to multiple independent servers, and stay resilient even if individual servers go offline. We are now building the next major capability: large-file media (videos, music, and other owned content) distributed peer-to-peer as torrents so it remains available without depending on any single host.
We are looking for a developer to design and implement the high-performance P2P / torrent-based media layer that will power this for Harbor.
\n
β Responsibilities
β Design and build the core peer-to-peer media distribution system for Harbor, using BitTorrent-style protocols (and related techniques) for large file storage and retrieval
β Implement or integrate DHT, tracker, peer discovery, piece selection, and swarm management logic in Rust
β Ensure seamless integration with the Polycentric protocol so media remains content-addressed, cryptographically signed, and available across independent servers/peers
β Optimize for reliability, bandwidth efficiency, and censorship resistance at scale (handling large files, high peer churn, and sparse availability)
β Collaborate with the distributed team on architecture decisions around networking, data models, and performance
β Contribute to the open-source community around decentralized storage and social systems
π―Requirements
πΉStrong production experience with systems languages (Rust, C++, etc.).
πΉHands-on experience building distributed or peer-to-peer systems (BitTorrent, IPFS, libp2p, or similar)
πΉSolid understanding of cryptographic primitives (signing, verification, content addressing, hashing)
πΉExperience with high-performance networking, concurrency, and reliable backend systems
πΉAbility to work autonomously in a remote, asynchronous team
πΉGenuine interest in decentralized systems, censorship-resistant publishing, and user-owned data
πΉDesirable
πΉExperience with BitTorrent internals (DHT/Kademlia, piece selection strategies, magnet links, trackers, or WebTorrent)
πΉFamiliarity with IPFS, content-addressed storage, or other next-generation P2P data networks
πΉCompiling Rust to WebAssembly for cross-platform clients
πΉExperience with PostgreSQL (or similar) for metadata/indexing alongside the P2P layer
πΉBackground in recommendation systems, search/indexing, or mobile/frontend (React Native) is a plus but secondary to the distributed systems work
πCloud or infrastructure experience (AWS, GCP, etc.)