- #WIDEVINE UNGOOGLED CHROMIUM FOR FREE#
- #WIDEVINE UNGOOGLED CHROMIUM ANDROID#
- #WIDEVINE UNGOOGLED CHROMIUM SOFTWARE#
It’s like talking to corporate drones – every question we asked is replied to with the same bogus standard texts. When Google dropped the bomb on us – on the distro packagers in particular – a fierce discussion started in two Google Groups (posts in one group are mostly duplicated into the other group): Chromium Packagers and Chromium Embedders. This helped to prevent us poor distro packagers from being billed for Cloud API usage in case our browser packages gained popularity.Īnd then, early 2021, some Google white-collar people decided they had enough of these freeloaders. So on top of providing us access to these Google APIs (in the case of Open Source Distro Chromium packagers) the Chromium team also substantially increased the non-billed monthly API consumption by the users of our distros’ Chromium browsers.
#WIDEVINE UNGOOGLED CHROMIUM FOR FREE#
If you offer a product that calls upon Google’s Web Services there is a monetary cost involved once the number of your users’ connections exceeds the monthly upper limit for free usage. In order to boost the development of Chromium-based (embedded) browser products, Google made deals with 3rd parties as far back as 2013 (from what I could find) and spiced the API keys of these 3rd parties with access to crucial Google Webservices providing features that would draw users to these products.
#WIDEVINE UNGOOGLED CHROMIUM ANDROID#
This Chrome Sync capability in Chromium based browsers allows you to login to Google’s Sync cloud servers and save your passwords, browsing history and bookmarks/favorites to your personal encrypted cloud vault inside Google’s infrastructure.Įxtremely convenient for people who access the Internet using multiple devices (like me: Chrome on a few Windows desktops, Chromium on several Slackware desktops and laptop and Chrome Mobile on my Android smartphone) and who want a unified user experience in Chrome/chromium across all these platforms. The most prominent feature which will be blocked after March 15th is the “Chrome Sync”. The safe browsing feature identifies unsafe websites across the Internet and notifies browser users about the potential harm such websites can cause. The most important service that remains open is “safe browsing”. Meaning, every Chromium based product not officially distributed by Google will be limited to the use of only a few public Google Chrome web services. On March 15th 2021, Google is going to block non-Google chromium-based browsers from accessing certain “private Google Chrome web services” by unilaterally revoking agreements made with 3rd parties in the past. > understand this is not exactly related to the DRM matter but it does > A different but related matter is the build process itself.… Aka the future of Chromium based (embedded) browsers I can open another bug over this if needed.
#WIDEVINE UNGOOGLED CHROMIUM SOFTWARE#
To avoid duplicate work, it would be useful if you ran this analysis on > indicate that which is very clearly free software and that which needs > fully vetted any particular results but it does help to at least > Of course, automated licenses analysis is never perfect and I have not Actually, less than a third of the total files > recently submitted upstream's Chromium. The tarball produced by `guix build -source ungoogled-chromium`. > * third_party/blink has some images under CC-BY-NC-SA-2.0 I don't mean that to be an exhaustive list of everything, > Even in the short time I was reviewing it I found a number of freedom
> building seems to involve downloading Chromium, then runnning > Taking this and considering Guix's build process: The method of > * Google Toolbar is in there, with a non-free EULA Did you record the absolute paths to these files? I cannot find these images: grepping for CC-BY-NC-SA or 'CreativeĬommons' did not aid.
> other packages have their freedom problems fixed in this way but this, > ungoogled-chromium over it, and then building. If not it still amounts to distributing non-free software to > compile should itself be 100% free software and FSDG compliant from the > clean-up program after downloading the source, even if that has been > should not be hidden/removed after the fact by asking the user to run a > just like build flags, should not be sufficient. the user when they want to, for example, do guix build -S chromium.Īs Leo says, `guix build -source` should never return nonfree softwareĪs a matter of policy.
0 kommentar(er)
