Live data from Hacker News

Firefox Bugzilla: Remove Pocket Integration

bugzilla.mozilla.org

181–190 of 196 posts

Re: Firefox Bugzilla: Remove Pocket Integration

#181
post #112

Earlier quoted context omitted.

I'd much prefer them to improve the memory and performance reporting features over adding some features that goes against their core values. right now I have a firefox that uses tons of ram and slows down to a halt very frequently but there are no decent tools to diagnose what addin/plugin/webpage/bug might be causing trouble. it's very, very frustrating. edit: I am talking about multiple gigs of memory for firefox a…

There are a lot of people working on performance - it's just less press-worthy than new features, so less noticed I guess. But bugs do exist, of course. Do you see anything odd in about:memory that can help diagnose your specific issue?

I agree that it's a tough problem and they have smart engineers working on it. The about:memory anonymizer makes the output useless to the engineers looking at the bug. A better way would be to anonymize it but still keep it identifiable if you have the key. Say make each page a uuid or something so that the engineer can say, "search for this uuid in your in anonymous report and that's leaking memory"

It seems that the tools to diagnose what has been the most criticized series of bugs in Firefox are still lacking. Ideally it should list the plugins used and the memory of each along with a way to identify the heavy pages etc.

Re: Firefox Bugzilla: Remove Pocket Integration

#182
post #122

Earlier quoted context omitted.

I'd much prefer them to improve the memory and performance reporting features over adding some features that goes against their core values. right now I have a firefox that uses tons of ram and slows down to a halt very frequently but there are no decent tools to diagnose what addin/plugin/webpage/bug might be causing trouble. it's very, very frustrating. edit: I am talking about multiple gigs of memory for firefox a…

I see this argument all the time in the form of "why are they working on the UI instead of the backend?" Well, because UI engineers and backend engineers are different people and don't share one-another's competencies, is why. The people who are adding these things probably don't know how to improve Firefox's performance. They're probably networked-multimedia engineers scratching their own itch. (And it's not like Fi…

The ui for about:memory is bad and not very useful in tracking down where the memory is going or leaking. That's something the ui engineers can do to help Firefox with this.

Re: Firefox Bugzilla: Remove Pocket Integration

#183
post #38

Earlier quoted context omitted.

Almost certainly.

Mozilla employee here: That is incorrect. There is limited public information available about this deal, but the best quote so far is in this article: http://www.pcworld.com/article/2930532/reading-service-pocke...

Quote from the article: "There's no monetary benefit to Mozilla from the integration: Pocket didn't pay for placement in the browser."

Re: Firefox Bugzilla: Remove Pocket Integration

#184
post #122

Earlier quoted context omitted.

I see this argument all the time in the form of "why are they working on the UI instead of the backend?" Well, because UI engineers and backend engineers are different people and don't share one-another's competencies, is why. The people who are adding these things probably don't know how to improve Firefox's performance. They're probably networked-multimedia engineers scratching their own itch. (And it's not like Fi…

The ui for about:memory is bad and not very useful in tracking down where the memory is going or leaking. That's something the ui engineers can do to help Firefox with this.

It's useful to Gecko engineers, ie. the people who actually have to fix it.

Re: Firefox Bugzilla: Remove Pocket Integration

#185
post #96

Earlier quoted context omitted.

What's your beef with Hello, exactly? The whole point of Hello is to offer an alternative to Skype/FaceTime that uses open Web technologies and does not require you to create accounts or upload contacts. How does that not appeal to the privacy-conscious?

If that's the intention, they failed horribly. Not because the lack of adoption, but because a propietary server is involved. Only the client is open.

https://github.com/mozilla-services/loop-server

Re: Firefox Bugzilla: Remove Pocket Integration

#186
post #121
post #97

Earlier quoted context omitted.

WebRTC is now a web standard and ships in multiple browsers. If you consider such technology to be outside the scope of a browser, then you're going to need to convince a whole lot of people.

The complaint is not about WebRTC, but about Hello. The comments in this thread are going in loops. "Hello shouldn't be bundled with a browser." "But it is just a small wrapper around WebRTC." "Yeah, but it's out of scope for the browser." "WebRTC is a web-standard"

Mozilla's mission is to promote openness, innovation & opportunity on the Web. There's nothing specific about browsers in the mission, though it is used to help further the mission.

If you take that into context when you look at Hello, you can see why the organization might want to leverage the Firefox user base to introduce something with negligible overhead (Hello) that would help to advance that mission.

Re: Firefox Bugzilla: Remove Pocket Integration

#187

Earlier quoted context omitted.

I'm not as concerned with the Hello integration. With both features, I'd like to know more on the technical details. For Hello, I think Mozilla (but actually unsure who's servers?) is only involved in initial discovery and, if needed, WebRTC NAT traversal. In terms of code bloat, I think Hello is just a bit of extra javascript on top of functionality already built into the web platform. But I admit I haven't look tha…

Hello uses Telefonica servers. My guess is that Mozilla's partnership with Telefonica is the reason why Hello was added to Firefox.

Not really. Hello was added in order to offer an alternative to Skype/FaceTime that uses open Web technologies and does not require you to create accounts or upload contacts. The partnership with Telefonica made it more convenient since they host the server side.

Re: Firefox Bugzilla: Remove Pocket Integration

#188

Earlier quoted context omitted.

Pocket is not paying Mozilla, as said already. Also, anyone implementing a compatible backend can switch to it by changing a pref.

Can we get a public statement from Mozilla describing its deal with Pocket? I see a comment below from a Mozilla employee stating that "there is limited public information available about this deal", and claiming that the best quote is in an article that contains a paraphrase from an email from another Mozilla employee saying that Pocket didn't pay for placement. When a non-profit gives prominent placement to a for-p…

> Can we get a public statement from Mozilla describing its deal with Pocket?

I've been pleading internally for an official public response. Nothing.

The only other source I've seen is an email reply from Mark Mayo at http://www.planet-libre.org/?post_id=18514

Re: Firefox Bugzilla: Remove Pocket Integration

#189

Earlier quoted context omitted.

Mozilla wanted users to be able to use Pocket without needing to create an additional account.

It also encourages users to create a Firefox account to use Pocket. I suspect a lot of people are wary of "signing in" to browsers.....

> I suspect a lot of people are wary of "signing in" to browsers.....

Nobody's being held at gunpoint.

Re: Firefox Bugzilla: Remove Pocket Integration

#190

It is so unlike Mozilla to introduce something like that, I ran a virus scan and checked what programs had been installed recently -- I assumed it had been put there in the same way that IE users used to get the Ask Toolbar installed. Exactly how I felt. What the hell were they thinking? I'm generally very supportive of Mozilla, I even supported their initiative to put advertisements on Firefox's start page. But bund…

They bundele it because they get payed for it. Same story with the new suggested site advertising. The alarming thing is that this way Mozilla is loosing it's independency.

As repeatedly said elsewhere in this thread, Pocket is not paying Mozilla for this integration.
Post reply on HN