[Feedback Request] Decentralized P2P Collaboration with Fileverse

Fileverse tl;dr

Fileverse is a decentralized alternative to Google Docs, offering secure, peer-to-peer document collaboration without centralized servers or logins. Users can identify themselves with ENS or stay anonymous, with all communication encrypted. Fileverse operates entirely on IPFS, ensuring service continuity even if its team disbands. It automatically creates a multi-signature (multi-sig) account for document sharing, making it ideal for DAOs needing trustless collaboration.

Proposal

Consider adopting dDocs, a decentralized document editing tool with mobile-native support, split-screen functionality, and markdown compatibility. Below are some example use cases:

  1. Facilitate community contributions to the ENS DAO Newsletter, including reporting on developer updates, events, and other noteworthy topics.
  2. Track and manage collaborations within and across different Working Groups using the Kanban feature.
  3. Promote a transparent and collaborative environment for critical documentation, such as bylaws.

Example: dDocs can create a shared document with separate sections for each stakeholder group to input their concerns and suggestions. The platform’s version control and multi-signature (multi-sig) approval process ensures that changes are only finalized after all relevant parties have reviewed and consented, maintaining alignment and trust across the organization.

Try it out!

I’ve created a dDocs collaboration for the ENS DAO Newsletter. The developer community, delegates, and other DAO stakeholders can freely access this document to report any updates of interest for potential inclusion in the newsletter. I will routinely check the contributor wall for updates moving forward.

—

Your feedback means the world to me, many thanks! :pray:

cc. @Momonosukke @file-seeder

Resources:

8 Likes

Just dropping my two cent: I’ve followed the development of Fileverse for a long time after meeting one of the founders. I think it’s a great product and they’ve made an immense amount of progress. It would be great to see web3 orgs dogfooding web3 products, especially ones like this that are mature replacements for centralized alternatives.

5 Likes

Though I don’t work as a part of a WG in ENS adopting ddocs would be a nice step forward as a kind of dog-fooding for the industry.

Even if you guys end up not totally adopting it, any feedback you give to them would be helpful I suppose.

4 Likes

This is a great idea:

  1. The product is good. The user interface is easy to navigate, and the overall experience is nice. I also appreciate the little details like the counters.
  2. In a decentralized ecosystem, it’s important to use tools that are transparent and privacy-focused. Staying true to the principles of decentralization.
  3. It’s a great way to bring visibility to projects that have received DAO support. This is especially valuable when you’re just starting out.
3 Likes

This is a good suggestion.

The truth is we stay pretty lean with DAO Tooling from a collaboration perspective. We really only use Discourse for comms and wikis, and HackMD for collaboration on markdown docs like proposals or forum posts (h/t to Obsidian as well, iykyk)

We could certainly try to use ddocs instead of HackMD since ddocs supports markdown pretty well. The sharing and identity verification would be superior to HackMD. I’ll make a commitment to lead with ddocs as an option whenever possible.

Thanks for the suggestion @lefterisjp

3 Likes