HNHacker News
TopNewBestAskShowJobs

fpgeek

6,372 karma · joined September 27, 2009

submissionscomments
fpgeek··on FCC urged to investigate Verizon’s statements on utility rules
Applying Kushnick logic to another industry: if Apple raises prices on Macs and uses that cash to bankroll iPhone development, well that's something that requires a federal investigation.

Yes, if Apple claimed in an SEC filing that they hadn't raised prices on Macs to fund iPhone development and it turns out they had, I'm sure they'd let it slide the way they always do. It's not like the SEC filed criminal charges or anything when they found out Apple had mixed up a few stock option dates. Oh, wait: http://www.sec.gov/news/press/2007/2007-70.htm

fpgeek··on Google Loses Most US Search Share Since 2009 While Yahoo Gains
I'm a big fan of Self-Destructing Cookies (on the desktop and on mobile).
fpgeek··on Apple’s Dev Agreement Means No EFF Mobile App for iOS
If the EFF didn't develop the application and release the source, what exactly is this: https://github.com/EFForg/actioncenter-mobile

And quoting from the README: "Although it works on both iOS and Android, the app is only targeting Android as of today. If you need to deploy to iOS as well, please check out the Ionic docs or contact the project maintainer for help."

What more do you want?

fpgeek··on Monster Sues Beats Electronics, Founders for Fraud
I'm having a hard time seeing how they're going to prove the Beats / HTC deal was a sham transaction.

The partnership went as far as HTC including Beats Audio and/or bundling Beats headphones with some of their phones, which sounds pretty substantive to me. Beyond that, HTC wasn't planning to sell their Beats stake back so quickly - they had to because they ran into unexpected financial trouble.

fpgeek··on The Fire phone debacle
Apple didn't screw up. The disadvantages you cite are inevitable consequences of the strategy they consciously chose (selling premium devices differentiated by user experience).

If Apple hadn't waited until carriers (especially Verizon) to come to them, iPhones would be as full of branding and bloatware as any other carrier-sold phone, not to mention interference with updates, interference with retail launches and who knows what else. Limiting the range of phones they offer means they miss niches, but also helps control costs (allowing them to use premium components more affordably), simplifies the buying process for customers, supports a broader and deeper accessory ecosystem and so on. Not jumping on many new technologies (e.g. LTE), creates an opening for competitors, but also lets Apple avoid the associated growing pains so they can provide a more consistent user experience.

If Apple had followed the path you advocate, they'd have picked up many of the disadvantages of the Android ecosystem, without the corresponding advantages (most notably rapid improvements via intra-ecosystem competition). That seems obviously worse than the path they actually chose.

fpgeek··on The Fire phone debacle
FireTV was a much, much easier product to develop. It was pretty clear an Android STB was worth doing. In this case, Amazon wisely took the simplest path to get there: Google TV + better content deals and updated hardware and software.
fpgeek··on Apple has lost the functional high ground
In the past, when you were having a problem with an Apple app you had a relatively large window during which you could just update that app without touching anything else to see if the upgrade fixed your problem. In trickier cases you might even try installing a specific version that wasn't the latest and so on.

Today, far more often, updating the app you're having a problem with requires an OS upgrade, bringing in tons of unrelated changes and triggering updates to other apps and ...

If you don't see how the first scenario involves wider options for self-help, plus greater agency and control than the second, I don't know what to say.

fpgeek··on Apple has lost the functional high ground
To take a simple example, faster OS updates combined with more aggressive OS version requirements for Apple apps (e.g. iPhoto) mean that getting the latest app bugfixes demands much more upheaval in your computing environment than it used to.
fpgeek··on Apple has lost the functional high ground
The decline of "It just works" is one side of the problem. The other, more painful side (driven by the iOS-ification of the OS, I suppose) is: "When it doesn't work, you're helpless".
fpgeek··on Why Rosyna Can't Take a Movie Screenshot
Easy or hard isn't the issue. The problem is there's an evil catch-22 at the intersection of copyright law and DRM: She's allowed to take the screenshots and clips, but it's illegal for her to get the DRM removal tools that would let her do that. And even if she magically acquired the tools, it is illegal for her to use them, even for an otherwise legal purpose.

It's like giving you a driver's license, but making it illegal for you to buy, rent, borrow or be gifted a car. And if you did happen to have a car anyway, it's also illegal to start, stop or steer it.

fpgeek··on Last Call: HTTP2
Actually, I think I now understand where we disagree. It isn't exactly where I expected.

You want a New Improved Transport Protocol that is a sharp break with HTTP's past. I agree that would be a good thing. We both agree that HTTP2 isn't that.

Where we disagree is this: You want NITP to be called HTTP2. I think doing that would be the surest way to smother NITP in its crib. In my opinion, an HTTP2 that made a radical change like not supporting cookies wouldn't be a step forward, it would just be perceived as "breaking everything" and would never get adopted.

You can't just slap HTTP's brand on a radically different protocol and expect people to not notice or care about what's inside. If you want to do something really new, that's a much longer and harder path than what we see here. That's why things like HTTP2 (making improvements where practical while carrying forward the concepts and baggage of the past) are worth doing. Because while we're waiting for a bigger leap forward, we've accumulated a set of problems we can solve and that are worth solving.

fpgeek··on Last Call: HTTP2
I agree the developing world wasn't an explicit consideration, but mobile most certainly was. And since better mobile performance and behavior is what developing world Internet clients most need from a new protocol, many of their concerns are being explicitly addressed.

As for whether "shaving a couple of bytes off of a header" makes a practical difference, you should consider the "Why do we need header compression?" answer here: http://http2.github.io/faq/ which references concrete evidence provided by an HTTP2 advocate. Personally, I find that more convincing than your apparently unsupported assertion.

Separately, it's nice to say websites should drop the eye candy and the Javascript frameworks (the hundreds of requests is addressed by HTTP2 multiplexing, I believe), but that's missing the point. As has been repeatedly demonstrated since the earliest days of WAP, mobile users don't want a stripped-down subset of the Internet, they want as much as they can get. From that perspective, raising the bar on what's possible (as HTTP2 tries to do) moves the ball far more than trying to convince websites to fit themselves into today's constraints (especially since the mobile user in the developing world has one of the strictest versions of those constraints).

fpgeek··on Last Call: HTTP2
The score most certainly not even. HTTP is still way, way behind. There's a qualitative difference between a spelling error in the document describing the protocol and a spelling error in the protocol itself. In my opinion, the substantive point wasn't about the mechanics of referrers, but that the lack of care and attention to detail demonstrated by "Referer" is strong evidence that HTTP is not as elegant as you claim.
fpgeek··on Last Call: HTTP2
> Bandwidth is cheap.

Says someone who I'm certain doesn't rely on a prepaid SIM for their primary Internet connection. Not that I do either, but I'm far more aware that tens (if not hundreds) of millions of these people exist today. In fact, it's likely that such people will be a clear majority of Internet users early in the life of HTTP2. Leaving them out of the conversation, as you implicitly do here, would be a colossal mistake for a protocol that intended to stand the test of time.

fpgeek··on Many Android bugs with 500+ stars closed as obsolete on December 25
> There are places where a device running Android 4.2 are the best one on the market.

Where? With the possible exception of China [1], after the Moto G and Android One, I'd expect that you could get a KitKat (or better) entry-level device pretty much anywhere.

[1] where there are entry-level KitKat devices, I'm just not sure of their quality since some major entry-level manufactureres (e.g. Xiaomi) are still on 4.2, not to mention that I wouldn't expect Google to go out of their way to support Chinese devices since they don't come with and generally can't use most Google services.

fpgeek··on Many Android bugs with 500+ stars closed as obsolete on December 25
Um, as the comment thread in the bug demonstrates, it isn't that simple.

Android does support downloading .ics files, you just need to install a third-party app to handle the calendar integration. Is that ideal? Of course not. But it is bog-standard prioritization to close issues that have easy workarounds in favor of issues that don't (and that's before you get to the possible patent complications someone mentions late in the thread).

More generally, I'd argue that this is a missing feature in the proprietary Google Calendar app, and not an OS issue at all.

fpgeek··on Many Android bugs with 500+ stars closed as obsolete on December 25
Say what now? I just opened my Kindle app and the store hasn't gone anywhere.

Are you maybe thinking of Google blocking Amazon from including the Amazon Appstore in the Amazon shopping app? That's a different issue and, more importantly, that doesn't really affect what's possible on Android, just how convenient it is. After all, anyone who wants to can download the store Google blocked from Amazon directly.

fpgeek··on Linus Torvalds on semaphores (1999)
If you're talking about building blocks, goto is also a necessary evil...
fpgeek··on Larry Lessig’s Long Walk
It's worth noting that the group accusing Lessig's SuperPAC of violating FEC disclosure rules is a well-known opponent of exactly those rules: http://lessig.tumblr.com/post/103204564762/on-the-center-for...

I guess you're more trusting, but, personally, when someone is opposed to a rule, I'd take their claims about what the rule actually requires with many grains of salt.

fpgeek··on Google Removes Amazon’s App Listing from Google Play Search
I can think of three reasons I use Amazon's store beyond the free apps:

1. It's a great way to share paid apps within a household without sharing Google accounts.

2. We have one device (a kids' tablet) that didn't come with and still doesn't have Google Play. Even Amazon's store is light years ahead of the one that came pre-installed.

3. Exclusives. For me that's Instant Video, but I believe other people also care about the temporary third-party exclusives (usually games). This reason often provokes annoyance and grumbling because it feels arbitrary and unnecessary, but it is still a reason nevertheless.

fpgeek··on Google Removes Amazon’s App Listing from Google Play Search
Amazon's store absolutely is allowed. Users just have to go to Amazon's website to download and install it for themselves. Considering that using Amazon's store means trusting not only Amazon and the store app, but every app installed via their store (almost certainly including some Google has never seen), this is an entirely reasonable requirement.
fpgeek··on Google Removes Amazon’s App Listing from Google Play Search
Well, considering how long they were separate and the little or no user benefit that came from merger of their app store and Amazon's other shopping app (especially post-Amazon SSO), it seems pretty clear that the primary purpose of the merged app was to sneak an otherwise prohibited app store past Google's terms, so...
fpgeek··on Google Removes Amazon’s App Listing from Google Play Search
I think their plan was to see how far they could get twisting the Play Store guidelines using the extra leverage they got from the long-awaited Instant Video app release. From their perspective, the worst case was returning to the previous status quo, so what did they have to lose?
fpgeek··on Google News to shut down in Spain
> They are NOT GEO-BLOCKING IT.

FOR NOW.

As we all know, Google's reaction isn't the result the people pushing for the law intended. Do you think they will just give up? They've already gone through several rounds in several countries on this issue, so I don't. Considering that past experience, I'd say there's a substantial chance the law will be amended to be stricter and more far-reaching and/or it will be interpreted that way by the courts.

fpgeek··on Apple Deleted Rivals’ Songs from Users’ iPods
The selling point is that there's enough uncertainty and complexity in the process that many (most?) people won't successfully avoid charges for re-buying music.

The icing is that the mere existence of the complex, uncertain process insulates record companies from accusations that they're forcing people to re-buy music (as with the transition to CDs). Re-buying just happens to be the much more convenient option.

fpgeek··on New Search Strategy for Firefox
I can get at the post and I also couldn't see anything about the default outside of US/Russia/China.

What makes this particularly interesting is the rest of the globe includes some of Firefox's strongest markets. My gut suggests this is obscure because Google will remain the default there, but that's just a guess.

EDIT: My gut seems to be wrong. The Yahoo post on this ( http://yahoo.tumblr.com/1313 ) mentions "the long-term framework we developed with Mozilla for future product integrations and expansion into international markets". I think that means Yahoo will end up being the default outside Russia and China, though the rollout may take some time.

fpgeek··on New Search Strategy for Firefox
Um, there's more to the world outside the US than Russia and China...
fpgeek··on The Rise of Extreme Daycare
Well, the people caught in this trap can find it difficult to take time out of their schedule on the Tuesday after the first Monday in November, not to mention the many other hoops they may have to jump through in order to be counted politically.
fpgeek··on Facebook, Microsoft, Apple Make Year-End Lobbying Push to Curb NSA Spying
Of course money. You make the argument that your audience is most likely to hear. And between lobbying and campaign contributions, jobs for their constituents, lost tax revenue and so on... money is the argument Congress is most likely to hear.
fpgeek··on Firefox Developer Edition
Is there an Android version? I can't find a download link when browsing from my Nexus 7.
← PreviousPage 7 of 34Next →