Live data from Hacker News

Fakespot Is Acquired by Mozilla

fakespot.com

151–160 of 384 posts

Re: Fakespot Is Acquired by Mozilla

#151

You'd think that Mozilla has an excess of funding and has covered absolutely all needs in the browser space leading them to branch out like this... but the browser really needs a lot more hands and funding, I honestly can't make sense of this. And Fakespot: they present themselves as a company that focuses on detecting AI-generated content from human-generated content. It sounds like they've set out to play Whac-A-Mo…

I'm happy for them to branch out, but it is discouraging that once every 3-4 months I run into a bug or feature I need, google it, and am taken to a bug report in their tracker from 5-10 years ago that hasn't been touched.

Re: Fakespot Is Acquired by Mozilla

#152

You'd think that Mozilla has an excess of funding and has covered absolutely all needs in the browser space leading them to branch out like this... but the browser really needs a lot more hands and funding, I honestly can't make sense of this. And Fakespot: they present themselves as a company that focuses on detecting AI-generated content from human-generated content. It sounds like they've set out to play Whac-A-Mo…

From my perspective Mozilla is doing a better job with their browser than Google and Apple are, that's why I use it (despite the market share, I prefer their implementation of most things compared to alternatives). Everything else is gravy. I'm not sure that the money Mozilla spends on other things would be better spent on the browser... would it realistically close any existing gaps between their competition? Arguab…

Depends on what metrics you are using. Compatibility, APIs, Performance, Firefox is objectively worse than Chrome on all aspects.

I like Mozilla as a company and I still use Firefox over Chrome knowing that it is objectively a worse browser and experience because I dislike Google and their business practices and i support businesses that I believe in. I am very much against the monopoly Google has over the web space and their positioning to dictate future web standards that will probably benefit their ad revenue over user experience.

Re: Fakespot Is Acquired by Mozilla

#153
post #117
post #85

Presume they'll bring the add-on into their standard monitoring / security checking! "This add-on is not actively monitored for security by Mozilla. Make sure you trust it before installing." https://addons.mozilla.org/en-US/firefox/addon/fakespot-fake...

Many Firefox extensions including the "recommended" ones which are claimed to be actively monitored are breaking Mozilla's extension policies by secretly sending telemetry, injecting advertisements, load and execute external resources, etc. None of the ones I reported have had their recommended status revoked, several ones have since even been allowed to publish new versions where the same violations are still presen…

> None of the ones I reported have had their recommended status revoked, several ones have since even been allowed to publish new versions where the same violations are still present

Could you publish these publicly anywhere, so that we can do for ourselves the job that Mozilla apparently is failing to do (while claiming to)?

Re: Fakespot Is Acquired by Mozilla

#154

Earlier quoted context omitted.

I mean, this is a broad topic and I am more of a backend engineer than frontend these days. However, I did do a lot of frontend back in the old IE6/IE7/IE8 days when you essentially had to code a whole separate front end for Microsoft's standards-flaunting mess. So this is definitely an issue I care about. but behind the curtains it took additional effort from the developers of websites you visit to make it so This i…

>your chrome-specific shit okay, but does mozilla have a good reason for not supporting that stuff other than "we have limited resources to implement these things"? a lot of that chrome-specific shit is really really nice . like CSS nesting - that would be amazing. firefox has a bug for tracking the implementation, and supported the standardization of it. but there's no sign of any progress towards an implementation.…

> okay, but does mozilla have a good reason for not supporting that stuff other than "we have limited resources to implement these things"?

That depends on what you are referring to. No there is not a one size fits all answer. For example, Chrome has implemented Filesystem API that Mozilla is still debating on because they see it as a security issue. You can agree or disagree but there reason is still something other than "we don't have the resources to do it"

Re: Fakespot Is Acquired by Mozilla

#155
This is interesting. FakeSpot is already getting aggressive with injected ads and recommendations on product listing pages (Amazon as an example) and this tells me they're going money-heavy, while Mozilla on the other hand might have much left at all actually. How exactly the financial aspect shapes out remains to be seen.

Re: Fakespot Is Acquired by Mozilla

#156

Earlier quoted context omitted.

>This feels like a good long term vision for Mozilla. >The browser wars are basically over and why is that? Oh because Mozilla hasn't put any energy into getting better or pulling back market share from the moment it started to bleed out to Chrome. Let's not just sit back and go "Oh well, they lost nothing they could do" shrug . They built their tech in such an obtuse and opinionated way it's impossible to integrate…

Firefox has certainly improved a lot since 2008. Google has and had major distribution advantages for Chrome; same with Apple/MS and their browsers. I've gone back and forth between FF and Chrome a few times and since the big FF perf improvements several years ago, I don't understand why Chrome is still seen as a wildly better product except for residual Google goodwill among the tech crowd. FF has had much much much…

There must be something different about my web use, because I keep hearing anecdotally that Firefox has reasonable performance relative to chrome. My experience is now and has always been that they aren't even close. I'm working on a React app at the moment and just confirmed: some basic operations that are buttery-smooth and instantaneous in Chrome have noticeable delay in FF. No extensions installed in either.

Re: Fakespot Is Acquired by Mozilla

#157

Earlier quoted context omitted.

Remember "Firefox OS"?

It was a fantastic gamble IMO. Low chance of success, but enormous payoff if it had succeeded. Imagine a commercially viable alternative to iPhone and Android with multiple manufacturers and a completely open platform. Ultimately, I think they came to market too late and Android moved into the niche (low end market) they were targeting.

I seem to recall them saying they did reuse part of that work in Firefox on Android in terms of low-end performance, so it wasn't 100% wasted.

Re: Fakespot Is Acquired by Mozilla

#158

You'd think that Mozilla has an excess of funding and has covered absolutely all needs in the browser space leading them to branch out like this... but the browser really needs a lot more hands and funding, I honestly can't make sense of this. And Fakespot: they present themselves as a company that focuses on detecting AI-generated content from human-generated content. It sounds like they've set out to play Whac-A-Mo…

[deleted]

Re: Fakespot Is Acquired by Mozilla

#159
post #91

Earlier quoted context omitted.

The browser wars are over because Firefox lost them by spending all the time patting themselves on the back about how much better they were than the competition, wasting their money on stupid stuff like this instead of improving their browser. Getting themselves into a deeper hole is unlikely to help, imo.

Remember "Firefox OS"?

Firefox OS was not that bad. It was sold on terrible phones. Anyway it led to tons of APIs that we use now, like passing phone camera and microphone input to the browser.

Re: Fakespot Is Acquired by Mozilla

#160
Maybe Moz is on to something here; while they're at it, how about telling apart original content from copycat sites?

But what's really interesting is, can we not put ML to good use for generating a new browser for us, given a corpus of expected renderings? Or have we managed to make web standards so fscking complicated and out of hand so as to make that infeasible?

Post reply on HN