Try:
Interesting. I was considering building my own browser based on chromium. I’ll look into this. I use Java based technologies (Java already had a wrapper for Chromuim called CEF). I’d have to look for a Java wrapper for this one. Thanks.
This is the dilemma we are in. The two main browser engines are derived from Google and Mozilla, both of which are untrustworthy and add crap in that needs to be taken out. Open source is nice that you can fork it, but unless main development moves away from the original bad actor, it's a never-ending battle reliant on the efforts of a handful of people.
I agree, but the point of Ungoogled Chronium is that all that crap is never in there to begin with. Chrome is based on Chronium, with the added Google cancer, and Ungoogled Chronium is also based on Chronium, but no Google cancer is in there. And its completly open-source so I trust everything is taken out.
The core is fine, its the added layers that cause troubles.
I agree, but the point of Ungoogled Chronium is that all that crap is never in there to begin with.
Some of it is. That's why it has to be "Ungoogled". Look at their at all the stuff they take out, even starting just with Chromium:
"Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. However, Chromium still has some dependency on Google web services and binaries. In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations.
ungoogled-chromium addresses these issues in the following ways:
Remove all remaining background requests to any web services while building and running the browser
Remove all code specific to Google web services
Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.
Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).
These features are implemented as configuration flags, patches, and custom scripts. For more details, consult the Design Documentation."
is that all that crap is never in there to begin with
THE FUCKING CHROMIUM CORE IS DESIGNED TO FINGERPRINT USERS FOR ADVERTISERS.
THE FUCKING CORE.
IT IS BUILT, FROM THE GROUND UP, TO FINGERPRINT USERS FOR ADVERTISERS. THE FUCKING CORE. THE ENGINE. FROM THE GROUND UP. TO FINGERPRINT USERS. GET. IT. THROUGH. YOUR. FUCKING. HEAD.
No, you fucking retard, do you not understand what I just wrote?
>Do yOu nOt uNdErStAnD WhAt i jUsT WrOtE?!?!?!
Kill yourself faggot
Fuck you, bitch. I know who my enemy is, I would never kill myself unlike a weakdick faggot offended bitch who can't understand a single sentence such as yourself.
What is wrong with you? Why are you cussing? He was helping us by discovering a way to get around the privacy weaknesses in Chromuim. Chromuim is still the strongest engine even if Google has become one of the worst offenders in privacy in recent years. I will likely build my own browser with it though seriously, for very simple sites like this one, I could also just build my own specialized browser from scratch.
Godspeed.
Because Chromium is built from the ground up to fingerprint users. Suggesting Ungoogled Chromium is suggesting an engine that is built from the ground up to fingerprint users. It demonstrates a lack of understanding and is contrary to specifically what I wrote, indicating the lack of understanding on the matter while simultaneously giving advice on the same matter on which there is a lack of understanding. That's why I'm cussing, because the blind should not volunteer to lead the blind.
(post is archived)