I think you should be conscientious about the tiny "phoning back to the mothership with more info" privacy problem, and how best to manage that, even if it's just real disclosure (not "privacy policy" smallprint). I can't think of anyone else in the US who is right now, but I think that information privacy should always be a consideration in automated community-sourcing problems.
</pre>
</blockquote>
<pre wrap=""><!---->
Sigh... I respectfully disagree. I feel that in some ways, this argument eight years ago prevented us from gathering a whole bunch of information that could have been quite useful to us. It depends on whether you see Racket as a bulwark against a rising tide of invasive internet presence, or as the potential beneficiary of social media tools.
</pre>
</blockquote>
<br>
I'm saying: do it, but be conscientious in how you do it.&nbsp; Look at it
this way: you're setting a good example for the students, who will go
on to build the next generation of systems, and who will influence
their contemporaries and the generation beyond that.&nbsp; Otherwise, we'll
all just continue to take our lessons from billionaire sociopaths. :)<br>
<br>
<div class="moz-signature">-- <br>
<a class="moz-txt-link-freetext" href="http://www.neilvandyke.org/">http://www.neilvandyke.org/</a><br>
<br>
</div>
</body>
</html>