> Signatures? Glad to hear there will be an option to turn off, but it wasn't in your slidedeck so it wasn't an "Ofcourse" [sic] when @PavlovsCat made his comm

> Signatures? Glad to hear there will be an option to turn off, but it wasn't in your slidedeck so it wasn't an "Ofcourse" [sic] when @PavlovsCat made his comment. > Real names @PavlovsCat highlights several areas where user 'security' trumps psychological civility reminders. Personally, I won't use systems that require real names for this reason alone. If someone wants to use their real name, good for them. But systems that require it aren't for me. > "flameware control" Sounds like some other systems I know that get in the way of actual conversation (e.g., I'm trying to respond to individual posts individually, and manage to do so too quickly). If the controls aren't too aggressive, I can see the benefit, but if they're too aggressive I feel like I'm being punished for being able to touch type, and subsequently avoid those forums. (I haven't hit any such limits in HN, so if they're here, they're a good gauge for not too aggressive.) > "tagging" I happen to be a big fan of tagging. Although some systems do limit to existing tags, which I'm not a big fan of. > hosted versus source As an end user, I use both. When I'm setting up a system, open always gets preference over closed. There are several packages that have hosted service as their primary offering, but if you read through their FAQs they still have their source opened on bitbucket, github, or an accessible self-hosted system. Such dual-offerings provide the ease of hosted, with the myriad of benefits that come from open sourcing the code.