FialkaApp/fialka-mailbox

This is a nascent, zero-star project with no adoption signal, forks, or development velocity. While the README pitch is compelling (self-hosted, E2E encrypted, Tor-native, metadata-free), the execution appears to be in very early stages or freshly initialized. The zero metrics across all dimensions suggest either a just-published repo or abandoned/stalled development. The core concept—encrypted relay with zero server-side decryption—is a known pattern (seen in Signal Server, ProtonMail relay architecture, Briar, etc.). Defensibility is minimal: the moat would depend entirely on ecosystem adoption within the Fialka community, which is itself a niche protocol. Frontier risk is low because encrypted relay infrastructure is not a priority for major labs—they either build proprietary messaging systems or deprecate centralized relays entirely. No technical depth, community, or switching costs are evident yet. The Raspberry Pi targeting and Tor integration show thoughtful design for privacy use cases, but without evidence of a working implementation, users, or differentiation from standard encrypted relay patterns, this scores as a tutorial/experiment. If it gains 50+ stars, active PRs, and real Fialka network adoption, the score could rise to 4-5, but currently it is defenseless and easily replicable by any team building encrypted messaging infrastructure.