The easiest way to contribute is to:
- Use it: Make it more popular
- Fork it: Host an instance of Reverse on some domain - this helps it become more decentralized
- Open PRs: Reverse hasn't reached feature-parity with Twitter yet (and might not need to)
- The vision is something like 123movies, where the experience across different instances of the site is mostly the same, but maybe some hosts will choose to show ads, while others might charge $8/month to have a blue checkmark next to the user's name - variations like that. Fundamentally, the DRV protocol implements the peer-to-peer part - which keeps data across different deployed instances that have no communication with each other in sync - and through DRV200 content types are enforced. In these "contracts" peer-to-peer file storage is directed (posts are not stored in a database, other than a temporary queue cache, so you can deploy this serverless with no file system), and ownership transfers are recorded (like ERC721, but without any fees).
- Reverse can be further decentralized by forking & hosting Dereva and - through a PR - adding your instance URL to the
peersfile in order to be included in the blockchain network. Dereva extends DRV as an easily deployable service written in Node.js, which implements the contract standard and exposes a REST API. By using that API, Reverse is able to persist users and posts, which are ultimately stored on peer node hard drives.
