I mentioned the Blackberry article not because I think it's shady advertising, but just to point that out from my perspective anyone who thinks the Blackberry Priv is a great "one of the best Android handsets" simply does either not have enough exposure to the Android ecosystem or is just someone whose opinion I don't hold highly.
I'm not saying this confrontationally. Now that you have pointed it, I actually think you have a point.
I started becoming disengaged with them when they started repeating the Apple line of "Jaibreaking is bad, mm'key?" even though they continued to post tutorials about it, because that's what drove the visits (I wanted to jailbreak my device because I can't stand the standard iOS app menu interface. Besides, my device, my rules). The "f*ck it" moment came when they did a "report" of the latest apple iPhone charger, praising it's construction, it's electrical insulation, and whatnot. I'm an EE, and could easily tell that it was all BS and they had absolutely no idea what they were talking about.
I find that this happens regularly in the apple ecosystem, people follow the Apple talk too eagerly for my taste, and don't usually have a technical clue about what are they talking about. All the retina display marketing thing is a good example. Anyway, this applies to the second tier bloggers and commenters (huge majority), first tier, even if they follow the apple line to the letter, usually know what are they talking about.
As for their opinion of the Priv, it's an opinion, and there have been varying opinions about it in the tech press. The way your comment was phrased, it sounded like your disagreement with their Priv review was a factor in your evaluation of their Whatsapp article.
As mentioned by jc4p, that tiny bit of information has provided the author with just enough rope with which to hang himself.
Technical people know first-hand that the wrong information can easily lead you away from the source of a problem. Some (many?) slightly-technical people don't understand that screen-on time and cpu-awake time [0] are the major contributors to battery drain. If you provide a raw number for $ACTIONS_TAKEN [1] without establishing whether that number is in the normal range for that app and without tying that number to actual battery drain by correlating it to actual CPU or backlight usage, you're very likely to waste people's time on a wild goose chase.
When making reports for non- or slightly-technical people, you usually have to be careful to filter out irrelevant information.
[0] IIRC, both of which are stats that have been provided in Android for at least the past several major versions, and probably back to -at least- Gingerbread.
[1] In this case, number of times contacts have been accessed by a particular app.