Heh. “A couple of years ago.”
Heh. “A couple of years ago.”
to further suit its* business.
Thanks for explaining.
That’s a shame.
But Firefox is open source, though. It’s not going to disappear just like that.
How does KDE do it with Konqueror?
Why don’t you care for GrapheneOS?
As the matter of fact, I’m curious about the differences now.
Understood, thanks. So on a clean install, I’m assuming user.js
is either empty or missing, correct?
Nice FUD.
By your own logic, Chrome should have fewer developers than Konqueror, since its engine is essentially a fork of a fork of a fork.
No, you’re mistaken. A fork is a whole new product. This is not a whole new product. It’s a patch.
Have you independently confirmed this?
What is preventing user.js
from doing exactly what you’re describing right now on your system?
These are old options. I checked these off long ago.
Yes. Yes, they did.
The issue is that I already knew about cookies. I don’t want my browser to phone home (or anywhere else) without my consent.
Search terms is not some minor thing to collect, though.
Interesting! I’d like to experience this at some point.
Yes.