> The article assumes that the location data must have been collected because he gave an app permission to access his location. I bet they couldn’t figure out which app it was because it wasn’t an app.
I worked on this story (and the others, we're still publishing [1] [2]).
The dataset we bought from Tamoco didn't contain an app name for most of the data. So instead of guessing, we're open about the fact that we don't quite know. Which is sort of the issue here – there's not a lot of transparency around what is collected and by whom.
The Norwegian Data Protection Agency (DPA) has opened an investigation into Tamoco [2] after our first story, and they want to cooperate with the UK DPA.
Also check out Lygte Info[1], the site of a Dane who checks chargers and batteries usually bought from the Chinese sites like Banggood and AliExpress. Spoiler: Not all of them are bad.
I wouldn't doubt that Walmart, between their acquisition of jet.com and intense focus on competing with Amazon in the e-commerce arena is taking drone delivery services very seriously right now. They are already trying nearly everything else.
I just tested it on a Samsung Galaxy S3, in several forms (as src in link, script, img, video and object elements, as well as the href in an a element). Nothing happened here.
Smooth Streaming is certainly a great piece of technology, and thanks to the guys at Code Shop, it now works on several devices and using nginx, Apache and lighttpd: http://smoothstreaming.code-shop.com/trac
> For example, everyone says you can 'use SQLAlchemy' in Django. On paper this is true. But then you lose the admin, the user auth system, the messages system, model forms, and all of the other batteries that make Django useful.
Using SQLAlchemy doesn't change any of that. For pre-built components, like auth and admin, just go with the flow. You're free to use SQLAlchemy side-by-side with Django's ORM.
I discussed this with a colleague of mine earlier today. I completely understand why they moved away from Drupal, but I'm not sure that "why Django matters to us" is the right way of putting it (although Django definitely works wonders for sites like The Onion).
"Why [a mature web framework] is the best fit for The Onion" is a more appropriate way of saying it. I've wrestled with enough blog platforms like Wordpress, where the client wanted it to work like a generic CMS, to know that the "You can put lipstick on a pig […]" phrase is very much applicable to web development.
Use the right tool for the job, damnit.
And The Onion did.
