Celebrating Our WABetaInfo Community
Contributions play a vital role at WABetaInfo, helping us improve the quality of service we provide to our followers. We are like a close-knit family, and we are really delighted to be a part of this community. Over the years, numerous users have joined our ranks, elevating WABetaInfo to become one of the most trusted sources on the web. Each day, we receive valuable reports from our followers, which not only supplement our own contributions but also serve as a key factor in delivering timely and accurate news. It is also through these insightful reports that WABetaInfo has achieved the remarkable results we celebrate today.
As an expression of our appreciation, we would like to acknowledge some people who contribute to enhancing our services at least 15 times. They always report new findings in updates, identify new features, bugs, and provide insights on various matters. This list will automatically be updated by our website once more users share their reports with us, reducing our dependency on manual monitoring. We have more updates and acknowledgments planned for the future, so stay tuned! Your contributions make a real difference, and we're excited to continue growing and improving together. Following this list, you will find our credit policy, which details the criteria required to be mentioned in our articles.
| Position | Contributor name | Number of valid reports |
|---|---|---|
| ★ | WBI | 2675 |
| 1 | Sc | 197 |
| 2 | Akan | 158 |
| 3 | Kingcyrious | 158 |
| 4 | FastenM | 147 |
| 5 | Rubiokarim | 78 |
| 6 | UnluckyTester | 78 |
| 7 | Hypogriff | 71 |
| 8 | Saadh Jawwadh | 71 |
| 9 | Swakshan | 60 |
| 10 | Muhammad Hammad | 56 |
| 11 | flakoflow | 55 |
| 12 | Youssef Salem | 53 |
| 13 | Sniper | 52 |
| 14 | SiLent | 51 |
| 15 | shw_9876 | 47 |
| 16 | Traiti | 43 |
| 17 | Hamada | 34 |
| 18 | IgnacioAF | 33 |
| 19 | Thiago | 32 |
| 20 | Federico Trevisani | 32 |
| 21 | ShuhaibNC | 32 |
| 22 | Eloy | 29 |
| 23 | AnonymousWP | 29 |
| 24 | Elias | 27 |
| 25 | Mateus | 26 |
| 26 | IsaacAndHisIsaac | 26 |
| 27 | Adwaith Varma | 23 |
| 28 | Radu Oncescu | 23 |
| 29 | DarkCrystal | 15 |
| ◦◦◦ | Other 78 contributors | Less than 15 reports each |
Credit policy
- We always mention those who have helped us with a report or specific test in our articles when they directly inform us through our main social channels. However, while we acknowledge and credit people who report new features, we obviously cannot be aware of everything that happens on the web or have control over all events, particularly when our articles are already scheduled for publication within the next 13 hours or when we are unavailable (we still strive to do our best to recognize contributions even when reports are shared during times we are not actively monitoring our notifications). Therefore, credits are always added in good faith when we are directly informed, based on the information available to us at the time. Note that Threads and Bluesky are not yet considered our main social channels, as these profiles are automatically and fully managed by our server. As a result, we do not see reports shared with us on Threads and Bluesky, and they are not considered for credit in our articles. We encourage users to reach out through our primary social channels to ensure their contributions are noticed.
- A report shared after an article about the same feature has been published will obviously not be considered for credit. This is because the article already provides recognition to the original sources who reported the feature beforehand. Allowing credits for late reports could undermine the contributions of those who were the first to bring the feature to our attention. To maintain fairness and ensure that original findings are acknowledged, we only consider reports made prior to the publication of the relevant article. It would be similar to pretending to have won the lottery after choosing the numbers after the draw: it diminishes the fairness of the process and disregards the genuine efforts of others.
- We may occasionally forget to mention someone in an article, even if they have recently contacted us. This can happen due to the numerous details to remember or because we may not have noticed the report for some reason. Since we are not robots but humans, we can make mistakes and may overlook some credits. If you notice that your mention is missing, please feel free to send us a private message reminding us that your report was previously accepted. We are committed to ensuring that all valid contributions are always recognized and we will update the article accordingly to include the credits, and the correction is also reflected in the previous credits list.
- We reserve the right not to mention users who reported a feature already released for a particular platform (for example, iOS) if its availability was already announced for another platform (for example, Android) less than 13 hours earlier. This is because articles are often scheduled in advance, and if a feature is announced for a specific platform, it is likely already planned to be announced for the other platform soon after. Users who report the feature shortly after the first article is published might be attempting to gain unfair recognition for a feature that's already in the publishing queue. These users become aware of the feature thanks to the first article and may try to obtain recognition in the second article, which would be unfair to those who actually discovered the feature for the second platform before the first article about the first platform was even published. As a result, this wouldn't be fair to those who genuinely discovered and reported the availability of a new feature before the initial article, as it could lead to others getting credit easily without contributing original findings. Note that this policy is applied only if the second article is published within 13 hours of the first article. In fact, if an article about a new feature released to some beta testers is published more than 13 hours after the corresponding article about the same feature available for the other platform, and it does not include a mention, the user may contact WABetaInfo privately on X to request a correction if their report meets other criteria listed on this page.
- In some cases, at the discretion of WABetaInfo, reports about specific news may require a unique screenshot to be considered valid. This is necessary because someone might claim credit for a report that should rightfully go to others, which would be unfair. The need for a unique screenshot helps us ensure that credit is accurately assigned. These situations vary on a case-by-case basis, and WABetaInfo assesses the validity of each report individually. At the same time, WABetaInfo may still consider a report valid in certain situations, even without a unique screenshot, based on the context and details provided.
- When an article is already scheduled for publication, some people may report to WABetaInfo the availability of a feature that is about to be covered in the upcoming article. In such cases, if the feature has not been discussed in the past 13 hours for a different platform and the publication of the article has not been pre-announced on X, we will still grant credits to acknowledge the report and give value to the contribution, even if we were already aware of the news. This ensures that all relevant reports are always recognized, even if they coincide with our content already in the pipeline in case we haven't pre-announced its publication.
- Articles might not include credits if news is directly announced by WhatsApp in their official blog posts or channels, in changelogs on the App Store, TestFlight, or Google Play Store, at Meta conferences, or by verified sources such as Mark Zuckerberg, Will Cathcart, Meta's social profiles, or other similar credible sources affiliated with Meta. These official sources always take priority. However, we may still consider certain exceptions in specific cases.
- If there are more than a certain number of reports (a number determined at our own discretion), we may shorten the list of credits in the article by not including the complete list. An extensive list could be too lengthy and complicated to manage and incorporate, potentially making the article appear cluttered. In such cases, we reserve the right to choose which people to credit based on predetermined criteria, also considering certain priority based on previous reports or the current rank in the credits list. This limit and conditions may change over time based on various factors. Out of a total of 2675 articles, we believe this has likely happened between 5 and 10 times, making it a very rare event, and we expect it to remain uncommon.
- Reports shared with WABetaInfo that are based only on the discovery of specific strings related to new features will not be considered for credit unless a screenshot of the feature in action is included with the report. This is because anyone might easily read certain strings with minimal effort. It is important to recognize those who genuinely share evidence with WABetaInfo, including a screenshot that demonstrates their ability to use the feature. This approach helps ensure that credits are awarded fairly and accurately.
- We may choose not to mention certain users, even if they believe their report is valid, if the user has previously engaged in inappropriate behavior toward WABetaInfo or have taken actions that directly violate WhatsApp's terms of service.
WABetaInfo reserves the right to update this credit policy as necessary to adapt to changes in reporting practices, user feedback, or any other factors that may potentially impact the recognition process. WABetaInfo also reserves the right to make exceptions to certain rules where appropriate by giving credit even if a report does not fully meet the usual criteria, personally evaluating specific cases to ensure fair recognition when unique circumstances arise. By sharing reports with WABetaInfo, users automatically accept this credit policy. If they were previously unaware of the existence of this credit policy, it is important for them to understand that it is in place and applies to all reports made. This ensures a fair and consistent recognition process for everyone contributing to our community, guaranteeing equal conditions for both long-time contributors and newcomers alike. Since sharing reports is entirely optional, users are free to decide whether or not to submit information to WABetaInfo if they do not agree with this credit policy, as the purpose of sharing is for public recognition of their contributions.
These 10 rules might seem strict and rigid, potentially making it appear difficult or overly complicated to receive credit for a report. However, this is not the case, as shown by the total number of credited reports, which currently stands at 1894 (including contributions from users who have shared less than 15 reports each). This demonstrates that we genuinely value and recognize contributions from users who share valuable insights, reports, and discoveries with us, as long as they meet our fair standards and WhatsApp's terms of service. In addition, we ask users to follow these guidelines to ensure fairness, and we're still very open to making exceptions when the situation allows, or to temporarily or indefinitely extending specific rules further when needed. Adding a name to one of our articles costs us nothing, but it further highlights the strength and size of our community and shows how much users rely on WABetaInfo to discover and report new features for WhatsApp. As a result, we are happy to give credits to those who contribute valuable insights and information.