Chromium

Yet another broken download. Unzips to a nonexecutable file.

ARM version is being flagged as damaged on MacBook Pro M1 Max Ventura (13.2.1)

ARM version is being flagged as damaged or incomplete on 2020 Mac mini M1 16/512 running latest Monterrey 12.6.2.

The BAD zip archiving of Chromium.app continues. I've submitted a detailed bug report to the project as I am sick of this nonsense.

ARM (Apple Silicon) version--> https://download-chromium.appspot.com/?platform=Mac_Arm&type=snapshots

Q: Are YOU running into trouble unzipping Chromium Apple Silicon archives? A: If you are, try different unarchiving apps that *aren't* Apple's Archive Utility. I don't know what's going on, but the very recent chrome-mac.zip archives, certainly for Apple Silicon, are showing up as strictly broken, according to macOS 12.5.1. (I am about to update to 12.6). At the moment, what I found actually worked as an unarchiver was "Unarchive" from Parallels Toolkit for macOS. Last time this happened (a few days ago, different version of Chromium) it was The Unarchiver app that worked. And yet it failed today. This is frustrating! I never have this problem with other zip files. So I have to point at the Chromium developer project as the source of this oddball problem. So :-P

The current version is 107.0.5272.0

The downloaded file is "Version 99.0.4775.0 (Developer Build) (x86_64)" - despite the fact it zip file has an ID of "98.0.4775.0"

The last Marmuduke build with all video playback codecs and ungoogled that still runs on pre macOS 11 (Big Sur) is Chromium v95.0.4638.69-r920003- is located here. https://github.com/macchrome/macstable/releases/ As of this date, his builds after 95.xx simply crash on startup, on Catalina and Mojave and presumably any macOS earlier. Marmuduke didn't seem particularly concerned or motivated to address this when responding to some inquiries. The issue IMO is not in the browser code per se but in the way the build is compiled, so those of you with the verve can always compile your own and compare the differences in the build flags used. Code and build flags are all at the same site I just mentioned.

Note that the DL link here points to a Development or beta build, AFAICT, not the "ungoogled" version. As such, you won't have all codecs neither. As for Marmaduke's current build (96.0.4664.45), he dropped support for pre 11 MacOS — I don't know if this is it's a temporary choice or a final decision... A few months ago I started using Brave instead, it's probably not as "ungoogled" as Chromium but it looks a very good alternative, and sometimes more stable.

I've been using Marmaduke's builds for years now and they usually work perfectly (some issue might arise with some not yet updated extensions, that's all). Only downside for the "ungoogled" version: it may be delayed quite a lot (currently 2 months and there's no sign there'll be a new one sometime...) Marmaduke seems to have switched his preference to the "sync" version, lately, probably easier to build. Still the fastest browser around!

There's a great thing about Chromium, it's the easy use of profiles. You can have a main profile and another one dedicated to Facebook, etc. each one having the settings and extensions it needs. It's still the fastest browser around, even if it has become slower since version 76, as some tests show. I've seen a lot of people complaining about bugs in v80, so for the time being I'm staying at v79.

Not usable for me, but I loved it ten years ago.

Chromium first wants access to my Keychain, then it connects to google without even having any browser window open. So much about Chromium being un-googlefied. No other browser acts like that, constantly trying to snoop and crawl and connect to services which you never wanted or used, trying to find and report anything that can be sold on the market for ads. For me anything google or chrome is just unacceptable. This is only on my harddisk for testing browser compatibility in webdevelopment. Sadly the Chromium people are obviously not able to get the spyware out of the code. Probably because there wouldnt be any code left.

This is great that FreeSMUG is offering those builds. THANK YOU!
One problem though is that the updater no longer works and is automatically removed and then no longer operational.
The website says "This build hasn't "Check for Updates…" command as building Sparkle update framework at 64 bit fail." Not sure, this should be solvable as sparkle is used in other 64bit applications. Hope they can find a solution for an update mechanism.

Trying to open v. 70.0.3538.102 and getting the "Chromium can’t be opened because it is from an unidentified developer" security alert. :'(

don't touch Chromium with a bargepole. Installed itself on my Mac without me having any knowledge and other apps started playing up

Your may not visit developer’s website which is not secure according to Chromium, huh.

Version 68.0.3440.84 says OS X 10.9 or later. I am on OS X 10.9, and it does not open! I even downloaded it twice, wasting 180 MB of mobile internet for — nothing!

Chromium v68 won't run on OS 10.9, even if FreeSMUG's site still says "OS X 10.9 or late". Other Chromium based browsers (such as Vivaldi) still run on 10.9, just because they're still using Chromium v67. ;-)