It's most fun when you are just trying to decline this invitation because you do not have time and are asked to create an account and password (with stupid password rules, naturally), and fill out an amount of personal information just to do that.
"Why don't you just stop doing X thing you don't like?"
"Because if we do, they won't let us do Y thing we do like. Or, well, we would like it, except the way they make us do it is so awful."
"So stop doing that, too, or go do it your own way instead."
"But if we don't do Y thing we don't like, then they also won't let us do Z thing. Incidentally, we don't like that one, either. But we need it to be able to do X."
But I'm not sure how this world works anyway. I read about research in books that refer to it, Hacker News and Reddit that links to it, etc. but never in a magazine. Yet the magazines seems to be what everyone is aiming for to be published in, they are apparently some big deal. I suppose there is some reason why "peer reviews" are not between "peers".
I'm not saying this is the best way to do it, just how it is now.
Also, if you want someone to just read your paper, sure, email is fine. One does not exclude the other. The central system is there to ensure that should any doubt arise over the quality of the work, the feedback can be read and interpreted.
Again, there might be many other more high-tech solutions out there to solve this problem.
1. Authors write paper.
2. Authors send paper to journal or conference address. (...using a web form)
3. The editor gives the paper a once-over and decides to send it out for review.
4. (Editor sends links to reviewers, who log in, read paper, and leave comments.)
5. Lather, rinse, repeat until accept/reject decision is made.
They used to send pdfs, but now use web systems for roughly the same reason HN isn't a mailing list.
Note: the last time anyone let me review a paper was a long time ago, when they sent paper forms to fill out. Parts in (...) are how I assume it works now.
Imagine you trying to get someone to review a 1,000 line patch. If you can just get them to log in to GitHub, they can use all of the pull request commenting tools, and it'll be easy. Otherwise, you have to mail them a big .patch file, and then somehow manually manage comments across all of that. The assistive tools are more convenient.
A journal may have dozens of submissions at various stages of the peer review process. Each requires two or three peer reviewers, who are busy academics who will often fail to meet the deadline. The editor has to track all of these, follow up with lagging reviewers, and then put together all the reviews for a paper to make the final decision.
Doing all that by email would be a mess. Reviews would get lost, the editor would lose track of which reviewers were sent which papers, and so on.
So the online systems make sense. But they all suck. I've reviewed for several journals which use the ScholarOne system, for example, and despite all being hosted centrally, they inexplicably require separate logins. The website is a clunky piece of crap. If they just had an automated system email me a PDF and ask me to email back a review, and had their script grab reviews from the inbox and format them for the editor to review, it'd be a lot easier. Or if they emailed me a personal link that let me view the paper and leave a review, no login required. But alas, they must overcomplicate it...
It's a bit burdensome on the patch submitter, to collect the feedback into one place, but not that much. At least the burden is on people who want to get the patch in.
Fuck no.
Here: https://ello.co/dredmorbius/post/vv0bq6oia_06z_yjnmjwzw
If publishers all used the same software package for content management, we might be somewhere. But every company with an IT department seems to build their own Content Management System at some point. I joke with coworkers that we would solve the developer shortage in north america if we figured out how to stop everyone from writing their own CMS.
Not saying you could do that with GitHub, but there's design space for it.
EDIT: Folks email is not secure. Even if someone doesn't have access to login to your mail account. Emails in transit are insecure.
Using outside systems to send confidential data is common practice and has been for years.
And if you want to take matters into your own hands, you use PGP. But outside of the computer security business I guess that's mostly unused.
But the pledge was just a formality - should there be any interest to check the mail, there was nothing technically stopping anyone with the required access except for someone else with equal access having a problem with it. Likewise, various management offices had no issue with submitting email fetch requests for the simplest of things, with date ranges exceeding two or three years sometimes for what turned out to be incredibly minor reasons.
There really is no expectation of privacy with academia in the US when it comes to University owned property or services.
(The only reason I found out about any of this from legal was because I asked for clarification on our "duty to report", and one of the lawyers was almost excited as he told me about how we own everything legally.)
At my company we trust our people and have a web of review. However, we try never to have anyone be the final trusted party - even the boss.
There's nothing _private_ about the paper, since the author intends to publish it, or about the reviews, since they're going to the author anyway. Only the identity of the reviewers is confidential, and for that email is perfectly sufficient. Well, a standard email client would be far too error-prone; you'd want something like a blind mailing list just so the editor doesn't click the wrong button and accidentally unmask the reviewer.
It's odd, but it still happens all the time.
> Prof. Aaronson, given your expertise, we’d be incredibly grateful for your feedback on a paper / report / grant proposal about quantum computing. To access the document in question, ...
It seems odd to want feedback and then ask someone to go and register somewhere, probably requiring to accept a bunch of legalese in the privacy policy and terms of service... Just attach the document you want feedback on, right?
At least if I'd email someone (out of the blue or an acquaintance) for feedback due to his expertise, I'd be grateful for the time taken and try to make it as easy as possible to do.
Edit: it has been made clear to me that it's not about individuals contacting the author, it's some big corporation that probably sends this out, probably in an automated manner. I still don't understand why anyone would bother with this when "peer reviews" can happen between "peers" (i.e. sending each other documents for review, rather than going through the middleman that everyone seems to hate such as Elsevier, if blog posts linked on HN are to be believed).