alienbob's take on chromium for slackware
by nycace36 from LinuxQuestions.org on (#5DNA9)
Slackware's alienbob wrote in follow-up comments to his recent blogpost Google muzzles all Chromium browsers on 15 March 2021
Quote:
A bit different from alienbob's reqrd "userdata sync capability" in Chromium is this from a locally renown sysadmin..
Quote:
If we Slackw users don't need access to Google cloud services and userdata sync capability, then no problem at all to keep using Chromium on Slackware! :doh:
FWIW, am mostly an FF-ESR user on both Slackware 14.2 now (decidedly non-current) and probably on Slackware 14.3 / 15.x as well. :p
NB: the Pale Moon browser just today came out with a new full-version release as per https://www.palemoon.org/releasenotes.shtml.
Quote:
Unfortunately, Pale Moon v29 SlackBuild pkgs not yet available at the time of this writing via khronosschoty's http://repo.khronosschoty.org/Slackware/Pale-Moon/, but based on alienbob's view on the bad attitudes of the Pale Moon devs at https://alien.slackbook.org/blog/pal...my-repository/ that might also be no problem at all. ;)
--


Quote:
I am looking for ways to keep using Chromium on Slackware. Sure, using Google's own API key in an environment variable is a way around the muzzle, but Google stated that this may break at any moment in time without warning. But a browser without userdata sync capability is not a solution for me. If Chromium really loses that ability then I will drop it for sure as my preferred browser and switch back to Firefox. That would also mean I stop providing packages for it. Someone else can pickup the SlackBuild and maintain it on SBo then. |
Quote:
In a functional sense, Google's peevish behaviour matters only if you care about Google cloud services, which are the _only_ thing to be denied to everything except the proprietary Google Chrome browser prospectively. If you don't, then this doesn't affect you. For comparison, the ungoogled-chromium persistent fork, which I rather like, has all of that Google cloud services code stripped out of it in the first place. https://ungoogled-software.github.io/ Personally, I don't have any wish to outsource any of my computing to the second-most-nosy corporation in the world, so '...and we're going to prevent Chromium from accessing Google cloud services!' makes me think 'Um, OK. So my browser won't keep trying to phone home to Auntie Goog, then, and will stop nagging me about logging into a Google Account that I don't want to have or use, to get access to Google server-side features I have no interest in? Whatevs.' To me, that's a little like 'We're going to restrict your access to overcooked brussels sprouts!' |
FWIW, am mostly an FF-ESR user on both Slackware 14.2 now (decidedly non-current) and probably on Slackware 14.3 / 15.x as well. :p
NB: the Pale Moon browser just today came out with a new full-version release as per https://www.palemoon.org/releasenotes.shtml.
Quote:
v29.0.0 (2021-02-02) A new year, a new milestone! While our initial intent was to have Google WebComponent support with this milestone, any reasonable deadline has passed for it. Instead, this new release continues to build on further improvements and enhancements in the platform and additions to the browser, as well as a large number of bugfixes. |
--