Do things that dont scale. Most problems can be solved. The most difficult one is making ppl love your service. eg. gaining users.
By the time a noticeable subset of your users are doing things your investors/advertisers/hosting providers/app stores/mother would consider "deplorable", it's _way_ too late to be thinking "Yeah, maybe we should have built in some protection for ordinary users against griefers/trolls/russian and chinese misinformation campaigns."
I'm not saying they need to do it right now, or that it's a more important thing than gaining users/traction right now, but it should without doubt be a thing that's very near the top of their list of "things we have considered and have vague plans to implement, that need to watch carefully for, and to have not painted ourselves into corners where our ideas about what we'll need to do to stamp it out no longer work any more..."
Otoh, seems to me that Tusk is "micro social" - a term I just invented - to socialize a page/concept amongst a smallish group of people. Unless that link leaks, how will the online trolls even find a page to tusk? And even if does, adding an auth layer on top of page tied to your identity should be relatively easy.
FD - I am working on a "public" micro-social offering as well (info in profile) so how Tusk addresses this is of interest to me.
There's a difference among:
A) We are having someone in the company moderate this manually and gain insight into how we could do so scalably.
B) We are outsourcing moderation and therefore not gaining insight into how to reduce the burden of that cost centre.
C) We aren't worrying about that until later.
D) We are building a fully-automated solution from the beginning.