I read Comp Risks. While I have not responded to postings there, if I
did, due to the way it works I would have to extract a reference to the
piece I wanted to reply to, and respond to it.
But comp.risks demonstrates a significant part of the problem. When I
read replies there, I frequently have to scratch my head to figure out
what they are commenting on. And conversations there are almost always
very short. I grant that following deep conversations on email is
tricky. I would like better support. But following them on a digest is
essentially impossible.
And as I said, getting a digest once a week effectively excludes one
from most of the conversation.
Yours,
Joel
On 1/7/2021 1:21 PM, Salz, Rich wrote:
Sorry, a once a week summary, no matter how good, does not let someone
engage in the conversation. Also, responding to emails from such a
summary in a fashion that is understandable is quite difficult.
Your also comment brings to mind a question I asked earlier: did you ever subscribe to the RISKS or other digests? Ever reply to a posting there?
Have you followed any GitHub repo's, and seen the email that comes when someone comments on an issue or pull request? Did you know you can click on "watch"? https://docs.github.com/en/free-pro-team@latest/github/managing-subscriptions-and-notifications-on-github/configuring-notifications
So no, I do not consider that a useful middle ground.
Your turn to make a proposal.
