discussions

Why share your discussions in comp.programming.functional where you could create a mailing list just for your new fancy language?

You know how to have productive technical discussions and how to make things as simple as possible, but no simpler.

And yes, distributed discussions that preserve free speech and allow eliminating crap is definitely moon-shot hard.

For many subreddits, there are truly fantastic discussions that are very relevant to the subreddit topic.

The drivers, at bottom, are personal, which explains why the discussions aren't intellectually interesting—they're driven by a different kind of interest.

I continue to be amazed that it's not more widely mentioned when these sorts of discussions pop up.

I try to highlight interesting commits, mailing list discussions, and blog posts (tips and submissions always welcome!).

We encourage open discussions and make decisions as a team, as we see collaboration as the key to success.

This is how I'd do it: - you already track a set of URLs that have discussions (I assume).

The signal to noise ratio of most discussions has gotten out of control.

Undoubtedly, in the background, some stiff demand letter has already been sent asking for some payout in the context of confidential settlement discussions.

Livejournal is still the best for writing posts and having discussions on.

Twitter needs multi-level threaded discussions and "sub-tweets" that are more than 140 characters.

>>"merely because they represent an average citizen." I think as in most discussions, balance between viewpoints is what must be sought.

Discussions on general groups became less frequent as most of the interesting ones were on dedicated mailing lists.