Archive for November 2016

Blogs.. yay

Here, I control my words. Nobody can shut this site down, run annoying ads on it, or sell it to a phone company. Nobody can tell me what I can or can’t say, and I have complete control over the way it’s displayed. Nobody except me can change the URL structure, breaking 14 years of links to content on the web.

But the ecosystem for independent publications is fundamentally broken. Getting discovered, building a readership, and profiting from your work as an independent writer are all much, much harder than they used to be.

Source: Redesigning Waxy, 2016 edition

Publishers Are Rethinking Those ‘Around the Web’ Ads – The New York Times

These ads are “built on a premise for publishers to maximize revenue — it’s not built on a premise of finding the next great things for your readers to do,” he added.

“When you’re looking at things from that prism and you’re not maniacally obsessed with monetizing every single pixel, Outbrain is very obviously not fitting into your equation anymore,” he said. “If your readers’ trust and loyalty is No. 1 as the thing you care about most, you can’t have that on your page.”

Source: Publishers Are Rethinking Those ‘Around the Web’ Ads – The New York Times

in the fundraising meetings for Giphy, did anyone ask “Hey, you know you’re just a gif site, right?”

600M valuation, no revenue plan. Ok ?https://twitter.com/f/status/793224416448708609

Browsers are Deprecating Powerful Features on Insecure Origins

Google is removing geolocation support on insecure origins in Chrome

We want to start by requiring secure origins for these existing features:

As with gradually marking HTTP as non-secure, we expect to gradually migrate these features to secure-only, based on thresholds of usage, starting with lowest usage and moving towards higher. We also expect to gradually indicate in the UX that the features are deprecated for non-secure origins.

Source: Deprecating Powerful Features on Insecure Origins – The Chromium Projects

 

WebKit just removed geolocation support on insecure origins:

Source: https://trac.webkit.org/changeset/200686

There is a broad industrial agreement that Internet connections should always be encrypted. The new Service Worker API requires HTTPS from the first. As per Mozilla developers’ proposal, several functionalities that need user permission, including the Geolocation, Notification, Fullscreen, Pointer Lock and Media Stream APIs, may also require HTTPS later.

Source: Insecure HTTP will be deprecated (Affecting) | Firefox Site Compatibility

A collision of Chinese manufacturing, globalization, and consumer ignorance could ruin the internet

Xiongmai’s negligence is without question, analysts say, but it is just part a larger problem in the global hardware industry. In fact, the same system that brought exploding hoverboards into consumers’ homes last Christmas is responsible for unleashing hundreds of thousands of vulnerable cameras into American households—and probably millions of other equally vulnerable internet-connected devices.

..

Manufacturers like Xiongmai could fix the security issues, said Boland, but instead “spend as little money as possible on security, in order to make as much margin as possible.”

There are likely many more cameras with Xiongmai components operating in households right now, although neither Xiongmai nor its partners has publicly stated which brands and devices are vulnerable.

Source: A collision of Chinese manufacturing, globalization, and consumer ignorance could ruin the internet