Got a tip for us?
Let us know
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
- Thread starter Wowfunhappy
- Start date
-
- Tags
- web browsers
- Sort by reaction score
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.
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:
I have skia, but it's from years ago:
github.com
And, this gist contains many of the build scripts (although it's also from a couple of years ago):
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.
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
And, this gist contains many of the build scripts (although it's also from a couple of years ago):
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:
Bluebox doesn't know why his Github account disappeared, but it was not intentional and he has contacted Github support!
🎉
🎉
You can at least recover repo state as of last release (from 2 weeks back)
github.com
Same procedure can be applied to recover deps as well (GH doesn't really garbage collect refs).
guard change_fdguard_np() · Wowfunhappy/chromium-legacy@039c59a
Latest Chromium (≒Chrome Canary) for Mac OS X 10.7/10.8/10.9/10.10 - guard change_fdguard_np() · Wowfunhappy/chromium-legacy@039c59a
github.com
Same procedure can be applied to recover deps as well (GH doesn't really garbage collect refs).
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.
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.
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.
^ 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?
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:
Interesting: supermium (chrome fork for win 7/xp) also taken down now, https://github.com/win32ss/supermium and the account also deleted in the same fashion.
Something strange afoot...
Something strange afoot...
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:
From the supposed supermium site: https://www.win32subsystem.live/supermium/
>the Supermium GitHub repository is currently unavailable. Efforts are being made to restore the repository.
Probably you could follow that for updates as well, since I'm guessing it's a similar root cause.
>the Supermium GitHub repository is currently unavailable. Efforts are being made to restore the repository.
Probably you could follow that for updates as well, since I'm guessing it's a similar root cause.
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 $$)
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.
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:
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."
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.
I mean it's as good an explanation as any, but:
I realize no one else has answers either, I just... I don't know!
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: