Earlier quoted context omitted.
To me - as a long term FF user and Mozilla critic - it looks like: Spend money on everything except browser development (>$5 billions!). Market share down the drain. Use the market share as an argument for a lost cause and spend money on everything except Browser development. Ladybird - a browser spearheaded by one person - will expose Mozilla of what it is.
>Ladybird What’s the deal with serenityOS? Can it be run on bare metal yet, last I checked they only have a way to run it in a vm.
Fakespot Is Acquired by Mozilla
281–290 of 384 posts
Re: Fakespot Is Acquired by Mozilla
#282Earlier quoted context omitted.
To me - as a long term FF user and Mozilla critic - it looks like: Spend money on everything except browser development (>$5 billions!). Market share down the drain. Use the market share as an argument for a lost cause and spend money on everything except Browser development. Ladybird - a browser spearheaded by one person - will expose Mozilla of what it is.
>Ladybird What’s the deal with serenityOS? Can it be run on bare metal yet, last I checked they only have a way to run it in a vm.
Re: Fakespot Is Acquired by Mozilla
#283Re: Fakespot Is Acquired by Mozilla
#284Earlier quoted context omitted.
I never understood what geolocation was supposed to be within the context of of a desktop browser. If a website asks for this information, and I approve, what information is transmitted that couldn't be determined serverside via geoip?
GeoIP tells you at best what city someone is in, and even then, for smaller towns, will usually report the nearest large city, which could be quite a ways a way. Not to mention it's often even just flat-out wrong. VPNs and other things distort where you are. Sometimes a website might need (or at least think it needs) correct, fine-grained location information. I do suspect that most websites that ask for location inf…
Re: Fakespot Is Acquired by Mozilla
#285You'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…
> but the browser really needs a lot more hands and funding I had been using Firefox since 2002, when it was called Phoenix. I switched to a Chromium-based browser because the performance difference was noticable enough, and I am in the browser often enough, to finally throw in the towel and switch. They have a huge amount of money coming in from Google. Why is this going to acquisitions like this and not towards str…
Re: Fakespot Is Acquired by Mozilla
#286Earlier quoted context omitted.
So was apple once.
I wonder how things would be different if Microsoft never gave them that life-line when they needed it.
https://en.wikipedia.org/wiki/San_Francisco_Canyon_Company https://www.theregister.com/1998/10/29/microsoft_paid_apple_...
"the [QuickTime] patent dispute was resolved with cross-licence and significant payment to Apple." The payment was $150 million."
"Intel gave this code to Microsoft as part of a joint development program called Display Control Interface."
"Canyon admitted that it had copied to Intel code developed for and assigned to Apple. In September 1994, Apple's software was distributed by Microsoft in its developer kits, and in Microsoft's Video for Windows version 1.1d."
Re: Fakespot Is Acquired by Mozilla
#287Earlier quoted context omitted.
I never understood what geolocation was supposed to be within the context of of a desktop browser. If a website asks for this information, and I approve, what information is transmitted that couldn't be determined serverside via geoip?
Most MacBooks have a GPS antenna, so they will return pretty accurate location. And having a consistent API is important too, not having to care if your code is running on mobile or desktop is pretty nice.
Re: Fakespot Is Acquired by Mozilla
#288Earlier quoted context omitted.
Not GP, but Firefox runs on every OS I use, Safari does not. Chrome maybe does, but I doubt it.
What OS doesn't run chrome? BSD?
Re: Fakespot Is Acquired by Mozilla
#289A cookie consent on fakespot page states mainly Fakespot and Google cookies in a surprising manner. They give two options, but none to refuse any cookies:
- ok
- do not sell or share my personal information
How are they different? From reading details, I assume no difference.
There's no way to turn off any non-necessary cookies group (shared with Meta/Facebook (!) and Google).
It will be sad to stop using FF because of this integration.
Re: Fakespot Is Acquired by Mozilla
#290Earlier quoted context omitted.
Case in point: network ping spikes after using Geolocation that will persist until FF is closed: https://bugzilla.mozilla.org/show_bug.cgi?id=1711854
I never understood what geolocation was supposed to be within the context of of a desktop browser. If a website asks for this information, and I approve, what information is transmitted that couldn't be determined serverside via geoip?