csinchok

This seems like you're viewing cycling as a hobby, where many people (including myself) use it as a sole means of transportation.

There are many cases where the safest way to ride is for a cyclist to take an entire lane. Note that in many states (including mine), this is absolutely legal and recommended. But of course, there are many motorists who don't know this, and get very angry (https://ashevilleonbikes.com/asheville-cyclist-punched-face-...).

The best thing is to post your comment directly on the FCC's website. Downtime/batch posting of comments can mean that your comment could show up late, or maybe not at all.

Last I knew, iOS Newsstand apps were allowed to do a special push to the app in the background—but only as often as the physical issue was released. So, it might be that they get to do a background push once a week, and aside from that, all downloads have to be started while the app is open.

Ha, I actually did not. That was my coworker's pet project (but the writers drafted all the achievement names/text). Glad you like it, it was one of my favorite features.

Here's a little insider's secret: http://www.clickhole.com/achievement-hole/

I worked on this! It was a pretty fun project, and I'm really excited to see what the writers do with it.

The Onion hasn't really been in the print business since 2010, when they made it a franchise operation: http://www.cjr.org/the_news_frontier/you_too_can_own_a_piece...

Our point there was this: the type of phishing that caught us was pretty casual, and aimed at users who weren't very technically sophisticated, and those users shouldn't have had access to our twitter accounts.

The proposed solution is certainly pretty drastic, but when it comes to securing twitter accounts, there aren't a lot of options. The safest one I can see is to connect the accounts to an email address that isn't part of our google apps organization, as that is the common attack vector here.

Our twitter accounts are a high value resource, and are pretty hard to protect. We have almost 5 million followers, and two factor authentication isn't even an option. Once hackers change the email address on the account, we lose all access until we can get in touch with someone at Twitter (which takes a while, even for us).

I get that this was rushed, etc. But it's not like you did a soft launch to test this thing out, or that you're on some kind of deadline here. You built the site lazily and rudely (in my opinion), and then immediately began promotion of it.

Also, you state that you only spent a few hours, and that "most of that time was spent playing with caching and deployment". If you were spending time making sure that the site was cached and performant, it seems less like the hotlinking was an oversight, and more like it was something you just didn't care about.

If you would have taken another few hours, made sure that your ducks were in a row, and THEN began promoting it, you'd be in much better shape right now, and I wouldn't be commenting here.

As for the circles, if you don't know anyone on the dev team, why are you repeatedly claiming to have a tacit OK from us?

As to the fonts, I want to be clear: your current use of the fonts is infringement. We have paid to license those fonts for use on our site. You have not done this, and so you're now infringing--not against us, but against the owners of those fonts. We're not going to come after you, I'd bet that someone will (eventually).

To summarize my position again: I'm not at all a fan of how you went about doing this, but it's honestly not a huge deal—just a bit rude.

Hi. I actually work as a developer at The Onion. Given the conversation we just had, I'd say that it seems like you're not in "our circles".

Honestly, I think this idea is pretty cool, but just ripping off our CSS and HTML seems a little scummy. Not only that, but the fact that you were initially hotlinking our static media makes it seems like this is a bit of a lazy effort (let it be noted: you're still hotlinking a lot of media—now it's just from other sites). I'm actually a little sad that you stopped hotlinking our css, because we were already working on another stylesheet to mess with you.

Beyond that, you're using our fonts. These are not free web fonts. They are fonts that we paid a good deal of money to be able to use legally on our site, and they are definitely not authorized for use on yours.

Bottom line: cool idea, not OK execution.