chromium-legacy
ua-client-hints
chromium-legacy | ua-client-hints | |
---|---|---|
37 | 13 | |
238 | 575 | |
- | 1.7% | |
0.0 | 4.4 | |
about 23 hours ago | about 1 month ago | |
Bikeshed | ||
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
chromium-legacy
-
Supermium – Chromium fork for Win 2003 and newer
See also: the equivalent for legacy OS X (Lion and newer): https://github.com/blueboxd/chromium-legacy
- I'm having issues trying to update from lion osx to high Sierra
- Macbook air 2015 OS X browser problems
-
Advice sought: Mid-2009 Macbook (not Pro) and Mojave / Monterey / Ventura
A niche suggestion if you have all of the time: if you don’t rely on icloud services, you can actually try very old os x like mountain lion + this for browser
-
What's the best browser for Mac OS X Snow Leopard?
If you can do it, I'd go to Lion. It added so many features such as the launchpad, the option to reopen windows when you restarted your computer, etc. It's new enough that Chromium Legacy will work, and it's what I use for my unsupported Mac OS X installs. Unlike Arctic Fox which is essentially pale moon 27 under the hood, Chromium Legacy is fully up to date as of when I'm posting this.
- Need help updating 2012 MBP with Mountain Lion
-
What is the oldest Mac OS that is compatible with a version of Waterfox that still receives security updates as of now?
Chromium Legacy goes back to OS X Lion 10.7 and is being actively worked on. It has its limitations compared to the original Chromium (see Readme): https://github.com/blueboxd/chromium-legacy
- Chrome is dropping support for MacOS 10.13 and 10.14 this summer, that is too soon! A lot of Macs were high end machines when they were released, they are still capable today as mid-range machines. Eventually people will have to switch to Firefox OR Chromium-Legacy in order to use a recent browser
-
Chrome is dropping support for MacOS 10.13 and 10.14 this summer! That is too soon! I guess people will have to switch to Firefox or chromium-legacy in order to use a recent browser
I don't use GitHub much so I don't know, so how can you tell how many people are working on a project, like for Chromium Legacy: https://github.com/blueboxd/chromium-legacy
-
Latest browser versions for 10.11.6 El Capitan
I haven't tried it myself, but a couple of minutes ago I found out about Chromium-legacy. The description says it's equivalent to current upstream versions of Chromium except for some limitations caused by older OS versions. Viewing DRM-protected content (e.g. Netflix) requires separately installing the Widevine library.
ua-client-hints
-
Website Fidelity
The Client Hints specification covers a lot of this already - https://wicg.github.io/ua-client-hints/#content-adaptation-u... ... DPR, width, and viewport-width are already available in some browsers. Hopefully other hints will be available soon.
- UA Gotta Be Kidding
- Példátlan leállás jöhet a neten, és nem is lesz egyszerű megoldani
-
Version 100 in Chrome and Firefox
I encourage you to review the decision making and engage in the discussion here: https://github.com/WICG/ua-client-hints
- W3C User Agent Client Hints
-
Google Chrome Update will cause Big Issue For 2 Billion Users
chrome is starting to implement UA-CH, which splits up user agent info into individual headers sent by the client: https://wicg.github.io/ua-client-hints/
-
JP Morgan Chase Bank, or Why Not to Whitelist Operating System User Agents
As a Firefox/FreeBSD user occasionally annoyed by this nonsense, but not being knowledgeable about modern web standards evolution, I wonder if https://wicg.github.io/ua-client-hints/ will fix this by killing User-Agent headers.
- W3C User-Agent Client Hints ( SEC-CH-UA-* HTTP Headers)
-
Mozilla tests if 'Firefox/100.0' user agent breaks websites
ua-ch might reduce the amount of data browsers send, though it's gonna take a while to move away from regular user agents: https://wicg.github.io/ua-client-hints/
-
Mozilla alters stance on User-Agent Client Hints from “non-harmful” to “harmful”
There is a JS companion to this proposal that splits up the information in a similar way
https://wicg.github.io/ua-client-hints/#interface
What are some alternatives?
chromium-web-store - Allows adding extensions from chrome web store on ungoogled-chromium. Also adds semi-automatic extension updating.
web - Pi-hole Dashboard for stats and more
osx-patcher - A reupload of Julian Fairfax/RMC Team's OSX patcher, for patching old macs/macbooks from Mountain Lion to El Capitan (10.8-10.11), since he deleted his account and website.
stylelint-no-unsupported-browser-features - Disallow features that aren't supported by your target browser audience.
ravynos - A BSD-based OS project that aims to provide source and binary compatibility with macOS® and a similar user experience.
evercookie - Produces persistent, respawning "super" cookies in a browser, abusing over a dozen techniques. Its goal is to identify users after they've removed standard cookies and other privacy data such as Flash cookies (LSOs), HTML5 storage, SilverLight storage, and others.
Telegram - Telegram for Android source
ethical-ad-client - Ethical Ads JavaScript client
winchrome - Chromium for 64-bit Windows - All Codecs: MS Visual Studio 2017
stylelint-no-unsupported-browser-fe
eslint-plugin-compat - Check the browser compatibility of your code
hosts-blocklists - Automatically updated, moderated and optimized lists for blocking ads, trackers, malware and other garbage