distribute() is a project designed by Vlambeer's Rami Ismail. After creating his popular presskit() tool, he wondered about other automatable challenges developers and press face while communicating. Distribution of (p)review copies ended at the top of that list, and thus work on distribute() began.
distribute() would not have been possible without the help and support of the following people:
Any press request with the verified icon is a verified and confirmed user of distribute().
Verification means that distribute() has verified that the person making a request is indeed who they claim to be. In the case of larger publications, an entire domain can be verified. In general, you can assume people with the verified badge to have been checked to validate their identity. Most requests displayed as Very High Reach should be verified. If this is not the case, personally verify whether the e-mail tied to the request is indeed related to the publication the request claims to be for. It is not uncommon for people to pretend to work for a publication to get access to free copies of a game.
Verification allows you to log in with a personal code, rather than requiring an email verification for every request made. Developers will be able to confirm your identity at a glance and are capable of setting distribute() to handle verified requests automatically. In both cases, this has the potential to speed up your request. distribute() is fully functional without verification, and no limits are imposed on accounts that are not verified.
Requests that have Very High Reach are contacted within 1 – 7 business days to verify their identity. Partnerships with sites such as Twitch and YouTube will automatically give you a verified status on distribute(). distribute() continuously evaluates which accounts are eligible for verification. While the requirements for verification vary, patterns like frequent usage, High Reach or a manual request can lead to verification. To get verified, your email address will manually be cross-referenced with your publication. If things check out, you’ll receive an e-mail confirming your verification. A verification request that is not fulfilled will not receive confirmation that the request has been denied.
In case someone is deemed to no longer be secure, their account will lose their verified status. The verification status can be reinstated at a later time.
Reach is an algorithm that creates an approximation of a persons of publications effective reach.
Reach categorizes a publication into one of six levels of reach: None, Very Low, Low, Medium, High or Very High. By processing publicly available data sources (such as, but not limited to website metrics, social media and subscriber counts) the system assigns a value to a request. distribute() will never ask for any information about your reach. Developers can choose to sort requests on Reach. Publications with High Reach will be considered for verification.
The only way to increase you reach is to do exactly that. As your publication or channel grows, your Reach will reflect that.
distribute() is created to ensure convenience to both developers and press of all sizes, and Reach is simply a factor developers can use in their press strategy. distribute() does not high low-reach requests in any circumstance, and the ease of sending a build with a single click will encourage developers to send it to as many publications as possible – hopefully including yours! In the end, whether or not to fulfill a request is up to the sole discretion of the developer.