Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Other Chromium Legacy: Google Chrome for OS X 10.7 – 10.9

If it's completely gone forever, total disaster. Just found recently as a replacement browser in 10.13 when Firefox esr dies in September.
 
Oh my god!

I was always worried he'd stop updating it, but I never expected all the repositories to disappear like that! I can't believe I never thought to save a copy of everything! It's just that stuff on Github is usually so stable, it's so unusual for something to be suddenly deleted.
 
Last edited:
  • Sad
Reactions: f54da
I have skia, but it's from years ago:
github.com

GitHub - Wowfunhappy/skia: Skia library patched for chromium-legacy

Skia library patched for chromium-legacy. Contribute to Wowfunhappy/skia development by creating an account on GitHub.
github.com github.com

And, this gist contains many of the build scripts (although it's also from a couple of years ago):
gist.github.com

.gclient

GitHub Gist: instantly share code, notes, and snippets.
gist.github.com gist.github.com

And you can download the code for the main Chromium Legacy from the Internet Archive:

But... virtually everything else is gone! This is such a terrible loss!

I have reached out to Bluebox via an email address I have, we used it to correspond once. I don't know if he will reply.
 
Last edited:
  • Like
Reactions: f54da
Surprising that this came out of the blue (no pun intended), no warning of any kind.

Fingers crossed was just some sort of glitch, and will be back in business soon. As of this writing, still giving 404s.
 
Wowfunhappy said:
Bluebox doesn't know why his Github account disappeared, but it was not intentional and he has contacted Github support!

🎉
Click to expand...
Thanks for letting us know. Like many others, I panicked when I realized that blueboxd's whole account was gone, as I was searching for Chromium Legacy to set up on my Mac. Hopefully they'll be able to sort this out soon.
 
Could it be some sort of autoflagging copyright claim? Seems to be iffy with Chromium forks.

I hope it returns, doesn't have to be on Github of course, could also be on a Gitlab instance for stability sake.
 
A copyright claim would have wiped out all forks though. It's really very strange.

I'm really confident it will come back though. Maybe not on Github.
 
  • Like
Reactions: Heindijs
In my first comment I said that my suspicions were towards the rights. Mr Google. Some code or assembly that Google considers to be a modification of yours is not available.
 
Yeah but that doesn't really make sense to me. Aside from everything else (such as the fact that Chromium is quite clearly available under an open source license), Github posts all DMCA takedown notices here: https://github.com/github/dmca I don't see anything for Chromium Legacy under May 2024.

And by the way, nothing has been deleted from Github's servers, everything is still visible to Bluebox when he's logged into Github. It's just that nobody else can see it.

It's all really strange.
 
Not much point speculating but it's probably some automated anti-abuse system gone awry and doing the equivalent of shadowbanning.
 
  • Like
Reactions: Wowfunhappy
^ Yes! And you can also imagine why that type of system might flag Chromium Legacy: Chromium has an exceptionally high number of commits, releases have a high file size, and so on.
 
@Wfh:

Not sure where things stand at the moment* between blueboxd and Github support, but would it perhaps be helpful for those of us with Github accounts to write to support to explain how adversely this sudden disappearance of Chromium Legacy affects so many of us. Or could that just make things worse?

*Has he at least gotten some kind of reply to the effect that they are looking into it? Or any reply at all?
 
Last edited:
RK78 said:
*Has he at least gotten some kind of reply to the effect that they are looking into it? Or any reply at all?
Click to expand...
I haven't asked since my initial email, I really do my best not to bother Bluebox. I get the sense that reading/writing in english is taxing for him (since it's a foreign language).

I'd encourage patience. I will follow up if nothing happens in a couple of weeks.

(I don't know what to make of Supermium, yeah something is up!)
 
Last edited:
Today, June 3 , Googles war begun

Google plans to show a banner to Chrome users who run Manifest V2 extensions in their browser. This starts on June 3 for development editions -- Beta, Dev, and Canary -- of the browser.

Manifest V2 extensions that have the Feature badge will lose that badge on that day.

The extensions management page in Chrome lists the soon-unsupported extensions. It provides a link to read up on the change and "find alternative" buttons next to each extension.

Then, in the months that follow, Manifest V2 extensions will be disabled automatically by Chrome. Google says that users may enable the extensions again for a short period of time. This option will be removed eventually, leaving users with no option to re-enable their extensions.

Most Chromium-based browsers will follow Google. Some may extend support for Manifest V2 extensions, but in the end, it is likely that support will be dropped

And Google intensifies fight against YouTube adblockers. The message was posted to the official YouTube support website.

Hans Solo against the Empire of evil (or good $$)
 
I made a post on Hacker News. I don't know if it will go anywhere, but it could potentially get the issue more attention, maybe even from people who work at Github: https://news.ycombinator.com/item?id=40567326

I find it really hard to believe that Google cares about these niche projects. But I can't explain what's going on.
 
Last edited:
  • Like
Reactions: philgxxd
From the dev;s thread on msfn: "the account was flagged for 'spamming'. as I found out when trying to export the repository directly from GitHub to GitLab. The repositories were not deleted, but they are hidden from public view along with my account itself."
 
f54da said:
From the dev;s thread on msfn: "the account was flagged for 'spamming'. as I found out when trying to export the repository directly from GitHub to GitLab. The repositories were not deleted, but they are hidden from public view along with my account itself."
Click to expand...
Specifically, the Supermium developer commented in this thread: https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1267168 (Thank you for the Google keyword!)

So it really was some spam filter then? But odd that it hit two different "Chromium for legacy operating systems" projects.
 
It could be something about the rate of commits, and/or some keywords in the commit message? I doubt very many people are actively mirror the chromium repo, so it would make sense that it would hit two repos both pulling the same base commits.
 
  • Like
Reactions: Wowfunhappy
I mean it's as good an explanation as any, but:

f54da said:
I doubt very many people are actively mirror the chromium repo
Click to expand...
Github says there are 6.6K Chromium forks. Seems like a lot of them at least are active. https://github.com/chromium/chromium/forks?include=active&page=1&period=&sort_by=last_updated. (The Chromium Legacy repo was considered one of these forks by Github, it used to say "forked from Chromium" at the top.)

I realize no one else has answers either, I just... I don't know!
 
Last edited:
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back