News for hackers. Stuff that matters.
Re:Testing Cliqz in Firefox by shevy on Saturday October 07, 2017 @09:57AM (#15423778)
It's not "kinda shitty" - it is an act of betrayal by mozilla.

The company once known to care about user privacy, now u-turned and works against you.

The sooner mozilla dies, the better. It has become evil - not as evil as google yet, but on its way towards more and more evilness.

Re:Testing Cliqz in Firefox by girvo on Saturday October 07, 2017 @10:31PM (#15426717)
So what should we use instead? Let’s assume you’re 100% correct and Mozilla needs to die. What’s our replacement? Which of the other browser vendors listen to the community whatsoever? Mozilla is a large ship, and hard to steer, but it’s not impossible to change. I think killing it, however it is achieved, isn’t the right move. Baby, bath water, etc.
Re:Testing Cliqz in Firefox by justinclift on Monday October 09, 2017 @04:42PM (#15437294)
Personally, kind of wishing projects like QupZilla had more devs/maintainers/releases:

• https://www.qupzilla.com

• https://github.com/QupZilla/

The concept seems good, but the software gets so few releases it's unlikely be safe for use as a daily browser. :(

Re:Testing Cliqz in Firefox by girvo on Monday October 09, 2017 @07:49PM (#15438317)
But then we're headed even more into a WebKit monoculture... which is dangerous in it's own way, I think. I don't know, there's no easy answer here, because a brand-new modern web engine is basically an impossible task for a standard FOSS community.