![]() So, everytime you upgrade something, don’t expect your previous settings and configurations to last. So whatever security options you set, once an upgrade comes through, they can be UNSET. If they change Name to Name0 and Lastname to Name1, then those 2 new fields can be set to a default value till you change it. Name,Lastname,DateofBirth,PlaceOfBirth,CurrentLocation,CitizenSerialNumber,CellPhone-telemetry-GIS-Data,PoliticalProfile,DegreeOfDangerForTheState,ForCorporateWorld,ForTheGlobalDictatorship In a very Mozilla like fashion, where your “options” are no longer compatible and the new defaults are reversing your options.ĭo you know how a common database works? Fields, columns of data, for example: With brave-nightly you may get two updates a day, so whatever you set up the one morning maybe unset by after lunch time. It run inside firejail fine, up until recently, then it couldn’t. I was under the impression brave was created to avoid such tactics. So, where do we go from here? Anybody knows? I have been toying around with Brave (brave nightly to be exact – alpha/beta stuff) which when researched deep inside the “advanced” settings, it tunneled private information back to “their trustworthy” associate, themselves. ![]() So, keep your 2020.02 version of waterfox as the last, broken, but not signed by a major corporation browser alternative to evil itself (chrome,firefox,explorer) or the weirdo palemoon. – Waterfox never run in musl, and I failed at all attempts to build it without glibc. But if we were to run to such measures to just use a browser we might as well sandbox the authentic Mozilla corporate/agency product, isolated tab by tab, and entering no personal information anywhere ever. Decreased security of disabling sandbox internally may mean the necessity of sandboxing (firejail …?) around waterfox. None of Alex’s business anymore, let the corporate team figure it out.īut it is the only fix for now, unless you know how to run a container with the previous stable glibc library and run waterfox in it. Too busy with lawyers and bankers to push a patch. Related => /show_bug.cgi?id=1600574īut why fix a MAJOR BUG while you are about to sign in and get some cash. It’s rather temporary fix, disabling sandbox may decrease security. In a terminal ~]$ export ~]$ export ~]$ waterfoxĪnd after this was published Feb5 as a problem and nobody at Waterfox responded (usually the specific insider named below has been extremely helpful with any problems), for 2 weeks ( now), we get this response: It would automatically be fixed if you reverted to 2.30.xx but then most of your other software compiled with that new library “might” break. Waterfox lost sound ability while playing videos when glibc 2.31 started hitting some distros. Goodbye and good luck for all that you had done up to now. ![]() Thank you Alex for your sincere efforts and sleepless nights of coding, all these years, it has been a great ride, and it is too bad it had to crash in such a bad time for browser variety and period. Or why else would they buy to promote their own browser, to make all others break while they are getting robbed? Waterfox officially was sold by mr Alex Kontos to System1, a UK payperclick ad company, which it would be absurd to believe that it wouldn’t utilize the browser’s ability to feed their other interests with private data. We had seeked refuge at Waterfox, retaining some old firefox functionality and ensuring us it is blocking all of Mozilla tactics of robbing you of private data and feeding it to “who knows who”. We had dedicated much energy in the past, 2 years ago, to advocate for Palemoon and you should at least read the piece about the NoScript parody, and how we gave up on it for specific suspicious reasons (still holds unchanged, Palemoon has branded NoScript as “dangerous” because it breaks pages).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |