Chat message

Slack / Private Message Drop, p.967 [SLACK_001181] · slack_pm:msg:10082

Date: 2021-06-30 10:20
Type: chat message · slack
recipient: Kristian G. Andersen, Edward C. Holmes, Andrew Rambaut
speaker: Robert F. Garry

Recipients on this medium are inferred from channel membership, not per-message addressing.

Perhaps, word version and request that they use track changes probably works the best. Old school. You can do the same with Google docs obviously but when ten or more ppl get to making changes as we've seen now about 5X itgets unwieldy.

In context

A single line often inverts meaning once you see what it answers, so neighbouring messages are always shown.

2021-06-30 09:59 Andrew Rambaut open

How are we doing new coauthors like Mike? Could give him comment only permissions on the GoogleDoc or send him a word version and then manually work in the comments? Ora PDF for initial look? Could embed a secret code in each version we send out to track leaks
2021-06-30 10:20 Robert F. Garry

Perhaps, word version and request that they use track changes probably works the best. Old school. You can do the same with Google docs obviously but when ten or more ppl get to making changes as we've seen now about 5X itgets unwieldy.
2021-06-30 10:36 Andrew Rambaut open

Personally I find it much worse when I get 10 word documents with track changes on and have to merge them.
2021-06-30 10:37 Andrew Rambaut open

I have created a PDF version with a code in the DOI of the last reference. [shared file(s): Image from iOS.jpg]
2021-06-30 10:39 Andrew Rambaut open

But I may be a bit paranoid
2021-06-30 10:42 Andrew Rambaut open

I am thinking for the figure a simple two panel with the tree rooted between A and B and the map with the cases onit. We can link them up using colours.

Full conversation →