EtherMail vs Wikilayer

Say goodbye to noisy chat applications with thousands of groups. Your single point of communication for web3 is here. Introducing EtherMail. Receive relevant content from the communities you belong to, directly into your inbox. Use your web3 wallet as an email, stay anonymous and secure. Save time by only reading relevant content that’s meant to reach you. No more spam or unwanted ads: get rewarded for seeing ads that resonate with you, or have an ad-free experience. Your Inbox, your rules. Enjoy a Gmail-like experience giving you traditional or fully anonymous and encrypted email-to-wallet and wallet-to-wallet communication. EtherMail is the smartest way to handle your email inbox, providing maximum phishing and spam protection. With EtherMail, you'll have one inbox to manage all your Web2 and Web3 mailing. You’re the reason we’ve created EtherMail. Help us shape the future of communications, and make your email more relevant, private, and secure. Be part of our awesome community - give us feedback, discuss/share ideas, and test new features. EtherMail is reimagining email for web3: A smart Web3 email Inbox to manage all your communications, seamlessly. Download now!

Wikilayer is a wiki that an AI assistant can read and edit on your behalf. You and your agent work on the same tree. The agent writes through MCP tools: it adds a node, rewrites one, moves a subtree, and reads back by outline instead of loading everything into its context. You read the result here, as ordinary pages. Every block has an address of its own. Rename it, rewrite it, move it under another parent, and links to it still land. Pages that lead to a block are listed under it, and nobody maintains that list by hand. History is kept per node, so a change to one paragraph is a change to one node, not to a whole document. WHAT PEOPLE KEEP HERE Personal notes: a second brain the agent reads selectively instead of holding a whole vault in context. Adding is a message in chat, not an app switch. Project memory: long-running context the agent writes and you audit. Hierarchy and full-text search across titles and bodies, without a separate vector store. Team workspace: decisions, context and meeting digests, written by the team and refactored by the agent. Public reference: guides, handbooks, fan wikis. Readers arrive from search and never touch the editing surface. VISIBILITY A wiki can be open to everyone, private to a team, or run on your own machine. Public wikis are crawlable the day you write them: server-rendered pages, Open Graph, sitemap, structured data, and addresses that survive a rename. WHAT IT IS NOT Not a block editor: bodies are plain markdown edited through MCP, not click-to-edit blocks, and the tree is hierarchical nodes rather than a relational document store. Not a real-time co-editor: each edit lands atomically, and conflicts resolve at write time rather than by merging keystrokes. Not an approval workflow: edits land on the live tree, and the audit trail is a snapshot of each node as it stood before the change. Bodies are markdown and the tools are MCP. Both are public formats, so a wiki reads out as plain documents whenever you want it somewhere else.