Thousands Of Academics Pledge To Boycott Springer's New Machine Learning Title In Support Of Long-Established Open Access Journal
Furnished content.
Among Techdirt's many stories chronicling the (slow) rise of open access publishing, a number have been about dramatic action taken by researchers to protest against traditional publishers and their exploitative business model. For example, in 2012, a boycott of the leading publisher Elsevier was organized to protest against its high journal prices and its support for the now long-forgotten Research Works Act. In 2015, the editors and editorial board of the Elsevier title Lingua resigned in order to start up their own open access journal. Now we have another boycott, this time as a reaction against the launch of the for-profit Nature Machine Intelligence, from the German publishing giant Springer. Thousands of academics in the field have added their names to a statement about the new title expressing their concerns:the following list of researchers hereby state that they will not submit to, review, or edit for this new journal.We see no role for closed access or author-fee publication in the future of machine learning research and believe the adoption of this new journal as an outlet of record for the machine learning community would be a retrograde step. In contrast, we would welcome new zero-cost open access journals and conferences in artificial intelligence and machine learning. The contact person for the statement is Thomas G. Dietterich, Distinguished Professor (Emeritus) and Director of Intelligent Systems at Oregon State University. He has a long history of supporting open access. In 2001, he was one of 40 signatories to another statement. It announced their resignation from the editorial board of the Machine Learning Journal (MLJ), which was not open access, and their support for the Journal of Machine Learning Research (JMLR), launched in 2000, which was open access. As they wrote:our resignation from the editorial board of MLJ reflects our belief that journals should principally serve the needs of the intellectual community, in particular by providing the immediate and universal access to journal articles that modern technology supports, and doing so at a cost that excludes no one. We are excited about JMLR, which provides this access and does so unconditionally. We feel that JMLR provides an ideal vehicle to support the near-term and long-term evolution of the field of machine learning and to serve as the flagship journal for the field. That confidence seems to have been justified. JMLR is now up to its 18th volume, and is flourishing. It is "zero cost" open access -- it makes no charge either to read or to be published if a paper is accepted by the editors. The last thing this minimalist operation needs is a rival title from a well-funded publisher able to pour money into its new launch in order to attract authors and take over the market. Hence the current boycott of Nature Machine Intelligence, and the call for "new zero-cost open access journals and conferences in artificial intelligence and machine learning" instead.As to why Springer decided to announce a competitor to a well-established, and well-respected journal, an article in The Next Web points out that the German publishing company is about to offer shares worth up to €1.6 billion (around $1.95 billion) in its imminent IPO. A new journal covering the super-hot areas of AI, machine learning and robotics is just the sort of thing to help give the share price a boost. And when there's serious money to be made, who cares about the collateral damage to a much-loved open access title running on a shoestring?Follow me @glynmoody on Twitter or identi.ca, and +glynmoody on Google+
Permalink | Comments | Email This Story
Read more here
posted at: 12:00am on 03-May-2018
path: /Policy | permalink | edit (requires password)
Amazon Joins Google In Making Censorship Easy, Threatens Signal For Circumventing Censorship Regimes
Furnished content.
A couple weeks ago we wrote about the unfortunate decision by Google to stop enabling domain fronting on its AppEngine. As we explained at the time, this was an (accidental) way of hiding certain traffic by using the way certain large companies had set up their online services, such that censors in, say, Iran or China, couldn't distinguish which traffic was for an anti-censorship app, and which was for others. The two largest services that enabled this were Google and Amazon, and a variety of different anti-censorship tools made use of the ability to effectively "hide" within those sites such that an authoritarian government couldn't block their apps without blocking all of Google or Amazon or whatever. Some CDNs have admitted that they don't allow it out of a fear for how it could impact other users on the system, but on the whole it appeared to be a useful, if unintended, way for Google and Amazon to do good in the world.However, when Google shut it down, the company just said that it was never supported, and the company had no plans to bring it back. Among the companies who relied on domain fronting is the popular encrypted communications app Signal. In a new blog post, Signal has explained why it believes Google suddenly decided to take action:Direct access to Signal has also been blocked in Iran for the past 3+ years, but it was not possible to use the same domain fronting technique there. In an apparently unique interpretation of US sanction law, Google does not allow any requests from Iran to be processed by Google App Engine. Requests would get past Iranian censors, but then Google themselves would block them.In early 2018, a number of policy organizations increased pressure on Google to change their position on how they were interpreting US sanction law so that domain fronting would be possible from Iran. Sadly, these lobbying efforts seem to have had the opposite effect. When Google's leadership became more aware of domain fronting, it generated internal conversations about whether they wanted to put themselves in the situation of providing cover for sites that entire countries wished to block.A month later, we received 30-day advance notice from Google that they would be making internal changes to stop domain fronting from working entirely. That is... quite unfortunate. But, the story gets even worse. Because Signal then switched to Amazon, which resulted in the following chain of events:With Google no longer an option, we decided to look for popular domains in censored regions that were on CloudFront instead. Nothing is anywhere near as popular as Google, but there were a few sites that used CloudFront in the Alexa top 50 or 100. We're an open source project, so the commit switching from GAE to CloudFront was public. Someone saw the commit and submitted it to HN. That post became popular, and apparently people inside Amazon saw it too. HN being Headline News. Amazon's response was even more stark than Google's. First, it sent Signal an email claiming that Signal was already violating its terms of service:Yesterday AWS became aware of your Github and Hacker News/ycombinator posts describing how Signal plans to make its traffic look like traffic from another site, (popularly known as domain fronting) by using a domain owned by Amazon -- Souq.com. You do not have permission from Amazon to use Souq.com for any purpose. Any use of Souq.com or any other domain to masquerade as another entity without express permission of the domain owner is in clear violation of the AWS Service Terms (Amazon CloudFront, Sec. 2.1: You must own or have all necessary rights to use any domain name or SSL certificate that you use in conjunction with Amazon CloudFront). It is also a violation of our Acceptable Use Policy by falsifying the origin of traffic and the unauthorized use of a domain. Signal points out, in response, that it's not actually violating Amazon's terms. It's not using security certificates from any other site, and it's not falsifying the origin of traffic when users get to Cloudfront (it's just tricking the censors in places like Iran). But, either way none of that matters much, because Amazon then announced that it was following Google's lead and killing domain fronting, claiming (again) that it doesn't want other Amazon cloud customers to find out that someone is effectively hiding behind their domain.Signal admits that this more or less means the end of being able to use domain fronting to avoid censorship in heavily censored countries. It says it will look for alternative ideas, but in the meantime, this could do serious harm to people in those countries. There is, perhaps, a reasonable argument that we shouldn't have needed to rely on Google and Amazon as ways to hide traffic for important apps like Signal, but the fact that it was used for years this way really highlights how little damage domain fronting really seemed to do compared to the wider benefit.With Google Cloud and AWS out of the picture, it seems that domain fronting as a censorship circumvention technique is now largely non-viable in the countries where Signal had enabled this feature. The idea behind domain fronting was that to block a single site, you'd have to block the rest of the internet as well. In the end, the rest of the internet didn't like that plan.We are considering ideas for a more robust system, but these ecosystem changes have happened very suddenly. Our team is only a few people, and developing new techniques will take time. Moreover, if recent changes by large cloud providers indicate a commitment to providing network-level visibility into the final destination of encrypted traffic flows, then the range of potential solutions becomes severely limited. In short, this isn't a particularly good look. Google and Amazon made these moves so that people don't call them out for "protecting" apps like Signal by hiding their traffic behind the domains of totally uninvolved third-parties. Which certainly leaves both companies to being called out for favoring the interests of their customers over the interests of the public -- especially those in countries with authoritarian regimes. And, again, the "cost" to Google and Amazon was not high. No one was free riding, they were just doing a bit of misdirection to get around a censor's block. And now that's gone.
Permalink | Comments | Email This Story
Read more here
posted at: 12:00am on 03-May-2018
path: /Policy | permalink | edit (requires password)
|
|