13 ms·
Why Is Google Blocking Inbox on Firefox?
- josteink 12y ago> I'm not 100% sure on how the browsers implementation differs with CSP but there is a main difference in that there seems to be no CSP protected between Google domains in Google Chrome If this is true, does this mean that Google is short-cutting internet-security for their own applications in their own browser? Or am I reading this all wrong?
- johnward 12y agoThat's the way I read it too and I'm surprised no one else has mentioned this. Unless I'm missing something Google is allowing XSS for their own domains in chrome.
- gcb0 12y agoyes. and much more. for example, even when using open source web kit or chromium they actively removed all options to disable referrer. go on. try to find it on your current chrome build. or even on chromium thanks to their legacy. then remember that referrer with its most exposing setting is required for Google to monetize both their organic and paid search.
- lkbm 12y agoThe only way to do it in Firefox is through the scary and arcane about:config (or an extension). Historically, methods to remove that have not been provided by browsers, whether Google-developed or not. I've always done it via Privoxy, never the browser.
- gcb0 12y ago> scary and arcane i use it every day. even on firefox mobile! and it serves my purposes just fine. not to mention you are not exactly right. as you can update those values via user scripts that can be easily distributed or even made as an extension that change those values for you and/or provide a new settings controller UI.
- lkbm 12y agoYeah, and I use the command line every day. Whenever people see it on my screen, they think I'm "hacking". There are Chrome extensions to do it as well. The point is, the lack of a UI control usable by the average user is not some Google conspiracy. It's always been the standard in pretty much all browsers.
- jaimeyap 12y agoI think the term "blocking" is a bit misleading. It implies they have it running properly in FireFox and are going out of their way to make it only run in Chrome. It seems more likely they had an aggressive plan to ship inbox across Web, Android and iOS. And they started with "Chrome only" to save development time. I'm sure support for other modern browsers will follow soon.
- couchand 12y agoExcept that with a few quick changes the application ran, so intentionally blocking seems like a valid description.
- Blahah 12y agoChanges that included disabling a browser security policy - not something it's reasonable for Inbox to request its users to do.
- couchand 12y agoBut serving all content from a single domain is a reasonable thing for Google to do.
- mahouse 12y agoThat is not true, the application does not run, or at least not securely, with its animations, etc.
- Kalium 12y agoRunning is not the same as running securely and with acceptable performance. You don't ship things you know will perform poorly.
- diggan 12y agoYes, it is indeed functional in Firefox, with some adjustments to their animations, it would be "running properly". And yes, they are going out of their way to make it run only in Chrome since all the rest of the browsers are blocked.
- transfire 12y agoGoogle's attempt to take over email does not sit with me well. We need better email. But email is too important to be proprietary. We need open standards here. And we need open source developers to kick it in high gear to create better email clients.
- pjc50 12y agoThere's no shortage of mail clients. There's even a decent choice of webmail clients. But Gmail offers free hosting with decent antispam, which are things that otherwise cost money. Unless people want to get syndicalist/cooperative with their email, they'll go with the large free email providers.
- Oculus 12y agoI don't think the issue is as much with the clients as it is with the spam filtering Google provides. The sheer volume of emails they handle allows them to have the best spam filtering in the world. Something, that will be very difficult to duplicate through OSS.
- jimktrains2 12y agoThe issue is with sending mail. Running my own mail server just feels like a loosing proposition as inevitably it'll be blocked because it's not a well known one.
- a3_nm 12y agoCertainly this is what will happen if everyone thinks the same way as you... (I have been my own SMTP server (hosted by OVH) for a few months now. I was blocked exactly once, by custom filtering from a small provider where the delivery status notification said to appeal to abuse@, I emailed them and they fixed it in minutes.)
- tedunangst 12y agoSimilar story. I couldn't email msn (or exchange, etc.) but there was a web form I could fill out. Annoying, but I got to have some fun describing the type of emails I sent to my "list" and its "unsubscribe process".
- tedchs 12y agotl;dr: here are a couple stabs at why, but I still don't know.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- tedchs 12y agoI don't understand the 4 downvotes. The blogger himself says "However, we still haven't figured out exactly why Google is blocking Inbox on Firefox. That the application is not working, seems to not be fully true."
- Tyrannosaurs 12y agoThe last paragraph: "However, we still haven't figured out exactly why Google is blocking Inbox on Firefox. That the application is not working, seems to not be fully true. With some more man hours, it seems trivial for Google to get the application to run in Firefox to. Maybe too much Chrome specific technologies or just a try to limit the usage of Firefox on the web?" Is odd as he's spent the rest of the article pointing out that there are bits of missing functionality (such as transitions), he's disabled CSP which worries him and that there are errors showing, and that's just what a relatively brief review found. Given what is listed it seems pretty straight forward to me that in it's current form it shouldn't be supported on Firefox.
- couchand 12y agoAnimations are not important enough to justify. Not wanting to serve all your content from a single domain is not enough to justify. These are excuses, not technical reasons.
- Tyrannosaurs 12y agoI disagree. They're short cuts you might take to get a product out and get early feedback, the same sort of shortcuts most of us have taken when pushed to release something sooner. This is a product in Beta, not the finish article. Even if everything work in theory just dropping multi-browser testing would save time. If their aim is a beta product for early user testing, I really don't think what they've done is unreasonable.
- diggan 12y agoGetting a product out in the web development world includes getting it out for other browsers than the browser you develop in house. Otherwise, you won't get the early feedback you wanted. Especially when your application is working, with some minor glitches. It's not like the application is completely broken in Firefox with the fixes mentioned. Bypassing CSP for your own domains feels like a hack that you shouldn't be able to do.
- pilif 12y agoOn the HN thread accompanying the release of Google Inbox, a (supposed) engineer working on Inbox was saying that the reason for the exclusion of Firefox was a performance issue with accessing sparse arrays with huge indexes. Link to the post: https://news.ycombinator.com/item?id=8495498 https://news.ycombinator.com/item?id=8495498 Link to the bugzilla entry: https://bugzilla.mozilla.org/show_bug.cgi?id=1087963 https://bugzilla.mozilla.org/show_bug.cgi?id=1087963
- diggan 12y agoThanks a lot for that information! Will include it in the post when I get a chance. The performance is kind of bad in Firefox but I'm not sure it justifies blocking the entire browser because of that. For a comparison, Google Photos is slow as hell in Firefox, but you could still use it if you want to.
- phpnode 12y agoIf they'd supported Firefox from the start everyone would be slating them for "crippling" Firefox, or they would have had a poor user experience that would turn a non trivial percentage of early adopters off the entire product. They cannot win here, it was a bug in FF, it is now fixed, presumably they'll stop blocking when the fix is more widely available.
- shadowmint 12y agoThey could have made the effort to make this work on firefox from the start, but someone decided the effort wasnt worth it. The 'would have been bad experience to new users' is a strawman arguement. Solution: dont release product until it works. Firefox is fast enough if you write code with it in mind. ...but hey, who cares about anything except chrome right? If someone visits play.google.com on an ipad and safari crashes screw them for not using android right? Its Business Politics at play, not technical restrictions.
- aroberge 12y ago
- qnk 12y agoGoogle is not the same it wanted to be back in 2009 [1]: Today, we base our developer products on open standards because interoperability is a critical element of user choice. [1] http://googleblog.blogspot.com/2009/12/meaning-of-open.html http://googleblog.blogspot.com/2009/12/meaning-of-open.html
- whizzkid 12y agoI think this slide explains everything about how Google has changed the way of handling their business. http://www.slideshare.net/ericschmidt/how-google-works-final-1 http://www.slideshare.net/ericschmidt/how-google-works-final... They are more focusing on managing their business which is limiting their contributions to open standards.
- custardcream 12y agoYes. It's now Microsoft circa 2001.
- deleted 12y ago[deleted]
- spindritf 12y agoBecause they don't want a slow webapp under their logo. And this one would be particularly handicapped by that. Everyone praises Apple for user experience, right? There you go. They're giving you want you want. And at least Chrome works on multiple platforms, even Linux. What seems like a more arbitrary limitation is that Inbox doesn't work with Google Apps. Thought it, too, probably has some technical reason deep in the belly of the beast.
- frandroid 12y agoWhoa, good to know. But considering that the product is beta, they probably want to test it on regular free customers first...
- mintone 12y agoGoogle have produced a product which offers a great experience on one browser. They are happy with the performance of the application on that browser. They have no doubt tested it on other browsers and found the performance to be sub par. That application is clearly still in 'beta' mode (The app is still invitation only). I am sure that they will 'un-block' the browsers that Inbox doesn't perform well on once they've resolved the performance issues - I'm sure it's also not a slight against Firefox or any other browser. The alternative of course is that instead of this discussion thread we'd have a thread about how poorly Inbox performs on firefox which would damage the products overall reputation.
- couchand 12y agoOr, you know, a third option. They could always do what every other web developer must and make their software progressively enhance so it works at the very least on a few major browsers.
- mintone 12y agoAnd I absolutely expect them to do that, but when you have a platform you know works well with your software then you'd rather get to market there and then once you have everything working across the board release for all. Again, as every web developer must, release a beta that works under x specific circumstances and then fix for all resulting in your v1.0 product. If you don't do that then time to market doubles or more.
- dzhiurgis 12y agoThey also produced a product that leaks user data (mostly to them). In their book, 'How Google works' they claim to settle with more what's best the user than their customer. That's such a bold claim when you are a monopoly.
- mintone 12y agoI get really frustrated with the monopoly attack on Google, and really, with any attack on a company that is a monopoly through being great at what they do. Google is the best search engine; we use Google because it's really fucking good at what it does. Yes DDG exists but it doesn't compete, Bing is well, Bing, and others don't hold a flame. You may not like that they are a monopoly but for 99% of people, Google is the Internet.
- hokkos 12y agoGoogle Inbox is using between 365MB and 460MB, when Ghostery and Add Block Edge is activated, it is more than 600MB. This is where multi process seems to be useful (otherwise it is using much more memory for no real gains), and extensions can be really taxing sometimes.
- gcb0 12y agowhy do you even bring that up? also, unless you know what's on that memory and also tell us about total ram I'm just writing this off as anecdotal cache usage.
- kailuowang 12y agoWhen you decide whether to release a product on a certain environment, it's not as simple as something like: a) if it works, or seems it would work, on that environment, then we should release it there. or b) that environment is a competitor, so we shouldn't release it there. If you think it should be that simple, you never worked with a real product manager responsible for products with millions of users. Having a product to support a new environment isn't a trivial effort for devs, QA and a bit design. At a particular stage of the product (think about the goals they want to achieve for Inbox at this stage, which I think is something along the line of polishing the product based on mass but controlled feedback), I would've probably made the same decision if I were the product manager.
- gcb0 12y agojust like Microsoft was praised for releasing their OS with a free, supported browser. with all the development and qa done for free...
- bgarbiak 12y agoOut of curiosity: does it work in Opera?
- cognivore 12y agoThere's not really a good reason for Google to make applications they create work outside their own run-time environment - Chrome. Any technical reason they might offer (sparse array performance) is just facetious. They have the technical know-how to solve such problems, but business wise it makes little sense. I use three web browsers for just that reason. Chrome for Google products (YouTube, Gmail, now Inbox, etc.), IE for Microsoft products (Outlook.com, etc.), and Firefox for the open web and general usage.
- custardcream 12y agoYes there is. It's the world wide web. An interoperable universal interaction standard. Or it was until Google started pulling an IE6 game. I use Firefox for everything because there is no central motivation to specialise. If a site doesn't work well, it doesn't get my business.
- untothebreach 12y agoI'm with you. The day Google announced Inbox, and the fact that it wouldn't work with Firefox, was the day I finally got motivated enough to set up my own email server. I ended up just using mail-in-a-box, which doesn't come with the _best_ client, but is good enough, and I can use it from any browser I want without any problems.
- cognivore 12y agoWell, yes, that'd be nice if we had a "interoperable universal interaction standard." But now the majority (and soon, almost everyone) will be using the internet on tiny personal computers (smartphones) that run native apps. Using a web browser will become less and less important or even relevant. In such a case the costs of optimizing for multiple run-times makes little sense. Really, abandoning the browser for native apps (in the old days we called them "programs") across the board makes more sense, and leave browsers to what they were originally intended for - document perusal and simple data collection. And web browsers absolutely suck at UI for applications. Imagine the man hours and effort that went into building Gmail. It boggles the mind. Who would even want to maintain that?! All for something that could have been created as a native app much easier. There's a lot of reasons that people have gravitated towards apps on phones, but one of them is assuredly that the experience is better than using a web browser.
- Siecje 12y agoIt is not just Inbox http://www.otsukare.info/2014/10/28/google-webcompatibility-bugs-list http://www.otsukare.info/2014/10/28/google-webcompatibility-...
- deleted 12y ago[deleted]
- Bahamut 12y agoFor those who did not see my comment in the gist, I'll paste it here: "Probably the performance threshold Google has for its consumer facing products - if it runs slow on Firefox, then it would have normally have been a release blocker." Google cares probably the most out of any tech company I have seen about performance, especially with any consumer facing apps. CSP would probably be trivial for Google to fix. Animations/transitions similarly so. The only real explanation that makes sense is performance.
- dblohm7 12y agoYet they didn't file a single bug against Firefox!
- juanmnl 12y agoBecause, you know, "Best viewed in Chrome" is a thing, and somebody is becoming the new IE. It's saddening.
- deleted 12y ago[deleted]
- SimeVidas 12y agoA $400B company cannot get their app to work securely & performantly in Firefox, so they’re blocking access via UA sniffing. Seems legit.
- Kalium 12y agoRelease early, release often, iterate fast. Google's doing these things. Just because you have the resources to do something doesn't make it a wise use of resources.
- SimeVidas 12y agoAchieving web compat with Firefox (and possibly other browsers) is not a wise use of resources? What?
- Kalium 12y agoFor an initial beta release on a product with no revenue gains? Yeah, probably not. For later releases? Sure.
- SimeVidas 12y agoLike accessibility, web compatibility is harder to achieve (and requires more resources) when addressed late in the development process. A web app must be accessible and compatible with the major browsers, so ensuring this from the start is the optimal approach.
- Kalium 12y agoAnd it's clear that they were looking at it from the start. If you read around a bit, you'll see that they ran into a particular performance problem with Firefox. They're working to solve it, but decided they could release something usable for Chrome users immediately.
- 12y ago
- ausjke 12y agoI removed chrome from both linux and windows and use Firefox all the way. If no Firefox, then I'm just walking away.
- manishsharan 12y agoI subscribe to Google Apps for Business ( Gmail, Calendar etc.) The Google Admin console for my company is barely functional in Firefox. Switching menus causes the page to crash and Firefox prompts me to stop the scripts. On the other hand , the same console works fine on Chrome. One could argue that this is because FireFox "is not as fast as Chrome and I should use Chrome if I use Google Web applications". Hmm -- I do recall hearing a similar argument sometime in the 90s.
- SimeVidas 12y ago1. Develop app specifically for Chrome 2. Wonder why it doesn’t work well in Firefox 3. Block Firefox via UA sniffing 4. Disband web compat team and use money on NASA hangers, balloons and robots 5. Profit
- skywhopper 12y agoAny time you see a comment like "With some more man hours, it seems trivial for Google to get the application to run in Firefox", you know the author either doesn't know what they're talking about or just hasn't thought about it very much. Anyone who's done any serious web-app development in the past decade knows that cross browser compatibility at the bleeding edge (ie, past what the JS frameworks have worked out) can consume as much time as the rest of the application put together. At the early fast-iteration stage of a limit-seeking webapp like Inbox, it makes sense to focus on the app itself and limit yourself to just one browser. For Google, obviously they will choose Chrome. Once the app reaches some stability, and major changes are coming far more slowly, then it makes sense to start working in cross-browser compatibility.
- msabalau 12y agoTo build upon that, it's worth noting the context: a public beta that's only a few weeks old.
- TeMPOraL 12y agoI think that most of those comments stem from Google-hating, which is currently a big fashion here. Were it Apple doing it, they'd be lauded for their attention to user experience. Was Inbox a product of a random startup, it'd be praised for good business approach and proper prioritizing of developer time. But it's Google, so it must be some evil plan.
- msandford 12y agoI'm sure that there's a lot of that going on, yes. But Google has the legacy of their "don't be evil" company motto to content with. Which is to say that people expect (foolishly) for them to at least try not to appear evil. The difference between Google prioritizing Chrome vs anyone else is that Google owns Chrome whereas Apple doesn't, and some random startup certainly doesn't. It smells of Microsoft's "we'll only make this work in IE and fuck everyone else" strategy and that doesn't bring other warm thoughts to mind. So it's not JUST that it's fashionable to think the worst of Google these days.
- hellbanner 12y agoI want to point out that a while back Apple seemed to "block" -- or at least not implement -- iOS apps uploading on Chrome or Firefox. The page would just stall loading forever, but it worked in Chrome.
- mark_l_watson 12y agoKey quote from article: ""It's slow, a lot slower than Google Chrome."" So, InBox (which I really like by the way) is a rapidly developing project and the team only wants to optimize for their own Chrome browser during rapid development -- this seems really reasonable to me. If InBox does not run well on Firefox and Safari a year from now, then the author of the article would have a valid complaint.
- GrinningFool 12y agoThis is a good exploration of how the blocking is being done. As far as why, it seems self-explanatory. They're not ready to support other browsers yet. Why does this need to be a thing?
- dksidana 12y agoTLDR: 1. Inbox currently using XSS right now, it is disabled by default in firefox. Refer: https://developer.mozilla.org/en-US/docs/Web/Security/CSP https://developer.mozilla.org/en-US/docs/Web/Security/CSP 2. Firebox has option to enable XSS, so inbox can work on it. But that allows XSS attacks.
- JoseVigil 12y agoThere is always a conspiracy theory on everything Google does. I think this has nothing to do with that. Besides, everyone that has a startup and fresh ideas is always "afraid" of Google next step not stepping on top of its startup. This generates paranoid among us, its natural given the size of Google.