ResearchHub product update — 1/22/22
Automating the editor program, improving ResearchHub’s homepage, and developing open-source infrastructure
The past couple of weeks we have been focused on shipping tools for our editor program. Here are all the features we are planning for it!
Editor Program
- Editor Dashboard — We released an editor dashboard internally to show the activity of all of our editors. Soon, we will release this to the leaderboards as well, so anyone can take a look at all of our editors and how they’re doing.
- Automated Editor payouts (expected to launch next week) — Starting in February, Editors will receive RSC every day in an automated fashion.
- Automated editor notifications (expected to launch next week ) — Whenever activity (comment, post, hypothesis, or paper upload) happens in an editor's hub, we will ping each editor with a notification. Editors can change their notification preferences between every action, a 3-hour rollup of all actions, or a daily rollup of all actions. In addition, whenever editors are not active for a full week, we will automatically send out emails to remind them to engage with their community.
- After a certain period of inactivity, the editor will be automatically removed from the editor program and will have to reapply.
Homepage Improvements
Over the past couple of weeks, we have also made some big improvements to our homepage.
- Added tags to denote document type (Post / Paper / Hypothesis)
- Added a hub selector to mobile devices
- Updated the filters to be more condensed
ResearchCoin Distribution
We are also working on improving the RSC reward algorithm. Our plan is to distribute 50mm RSC each year to the community via the DAO. Currently, all rewards are in increments of 1 RSC per upvote, but that will change as we sync our rewards with the 50mm distribution.
Open Source
ResearchHub’s codebase is open-sourced, but the OS version is lagging behind our production code on researchhub.com by about one month. We have two closed internal repos, but we have been working hard this week to consolidate these into one open-source version that will be in sync with production and updated in real-time.
In addition, we have set up a bounty program so that anyone can contribute new code to ResearchHub and be rewarded for their time and effort with RSC.
If you are an OS developer and love our mission, stop by our community Slack and join the #open-source-dev channel to stay in the loop.
If you are interested in contributing to ResearchHub’s mission of accelerating the pace of scientific research — join us by signing up at https://www.researchhub.com/
