Alexis C. Madrigal, writing for The Atlantic: If the recent numbers are any indication, there is a bloodbath in digital media this year. Publishers big and small are coming up short on advertising revenue, even if they are long on traffic. [...] In a print newspaper or a broadcast television station, the content and the distribution of that content are integrated. The big tech platforms split this marriage, doing the distribution for most digital content through Google searches and the Facebook News Feed. And they've taken most of the money: They've "captured the value" of the content at the distribution level. Media companies have no real alternative, nor do they have competitive advertising products to the targeting and scale that Facebook and Google can offer. Facebook and Google need content, but it's all fungible. The recap of a huge investigative blockbuster is just as valuable to Google News as an investigative blockbuster itself. The former might have taken months and costs tens of thousands of dollars, the latter a few hours and the cost of a young journalist's time. That's led many people to the conclusion that supporting rigorous journalism requires some sort of direct financial relationship between publications and readers. Right now, the preferred method is the paywall. The New York Times has one. The Washington Post has one. The Financial Times has one. The Wall Street Journal has one. The New Yorker has one. Wired just announced they'd be building one. (Editor's note: CNN is building a paywall, too.) Many of these efforts have been successful. Publications have figured out how to create the right kinds of porosity for their sites, allowing enough people in to drive scale, but extracting more revenue per reader than advertising could provide.
Sign up for the Slashdot Daily Newsletter! DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. ×
Kieren McCarthy, writing for The Register: Network admins, code wranglers and other techies have hit an unusual problem this week: their test and development environments have vanished. Rather than connecting to private stuff on an internal .dev domain to pick up where they left off, a number of engineers and sysadmins are facing an error message in their web browser complaining it is "unable to provide a secure connection." How come? It's thanks to a recent commit to Chromium that has been included in the latest version of Google Chrome. As developers update their browsers, they may find themselves booted out their own systems. Under the commit, Chrome forces connections to all domains ending in .dev (as well as .foo) to use HTTPS via a HTTP Strict Transport Security (HSTS) header. This is part of Google's larger and welcome push for HTTPS to be used everywhere for greater security.
An anonymous reader shares a report: Microsoft announced in October previews of new Edge browser apps for iOS and Android. On November 30, Microsoft officials are announcing that these apps are no longer in preview and are generally available for users in select markets. By making Edge apps available on non-Windows operating systems, Microsoft is hoping to do more than give Windows 10 users who use Edge a more convenient way to sync their bookmarks, tabs, etc., across devices. Microsoft also is doing this to improve its "Continue on PC" feature that it's been touting for Windows 10. With "Continue on PC," users will be able to share a web site, app, photo, and other information from their phones to their Windows 10 PCs in a faster and more seamless way. Microsoft is looking to Continue on PC to help keep Windows PCs relevant in a world where more and more computing is done on mobile devices.