[HN Gopher] Tell HN: Chromium forks for legacy platforms are dis...
___________________________________________________________________
Tell HN: Chromium forks for legacy platforms are disappearing from
GitHub
This is really strange! Chromium Legacy is an up-to-date fork of
Chromium which supports back to Mac OS X 10.7 Lion (from 2011). On
Friday, the developer's Github account and all of his repositories
suddenly disappeared. The links now return 404 errors.
https://github.com/blueboxd/ https://github.com/blueboxd/chromium-
legacy Today, the same thing happened to Supermium, an equivalent
project for Windows which supports back to XP. To my knowledge, the
developers of Chromium Legacy and Supermium are wholly
unaffiliated. https://github.com/win32ss/
https://github.com/win32ss/supermium Does anyone happen to know
what the heck is going on? It's a little scary and makes me not
want to trust GitHub. I don't see anything relevant in GitHub's
repository of DMCA notices[1], and I'm having trouble coming up
with legal grounds on which such a takedown could happen. --- 1:
https://github.com/github/dmca
Author : Wowfunhappy
Score : 27 points
Date : 2024-06-03 20:43 UTC (2 hours ago)
| its-summertime wrote:
| https://forums.macrumors.com/threads/chromium-legacy-google-...
| beretguy wrote:
| Looks like this is a step towards Google DRMing the internet.
|
| This is bad.
| lxgr wrote:
| How would Google push DRM by filing false [1] copyright
| claims against various Chromium forks, which presumably
| wouldn't even contain any hypothetical DRM keys?
|
| Regular old Chrome does in fact include a Widevine DRM binary
| blob, but Chromium doesn't contain the source for it.
|
| If Google really wanted to push something like browser
| attestation (like they potentially did with their Web
| Environment Integrity proposal), almost by definition that
| part couldn't be open sourced either and would not be part of
| Chromium.
|
| [1] Chromium is licensed under various open source licenses
| that Google can't retroactively revoke. Even for code that
| they own the full copyright on, they can at most release
| future versions under a closed license; for GPL-ed
| dependencies, that wouldn't work at all (not sure if Chromium
| has any).
| toomuchtodo wrote:
| https://github.com/gdamdam/iagitup
| Wowfunhappy wrote:
| It's a little late for that, sadly.
| toomuchtodo wrote:
| Second best time to plant a tree is today.
| HackOfAllTrades wrote:
| Could this be tied to Google's push to force everyone to use
| Manifest 3, and nerf Add Blockers?
| lxgr wrote:
| How would it? Google can't retroactively un-license the
| Chromium source, which is under various open source licenses
| that I'm almost certain all include at a minimum the right to
| host a fork somewhere.
|
| Additionally, if you are concerned about MF3, your best bet
| isn't some outdated Chromium fork - it's Firefox.
| beretguy wrote:
| Somebody needs to upload their local all over the internet to
| gitlab, codeberg, anywhere else.
| lxgr wrote:
| Their local what?
| acheong08 wrote:
| Even though all of this should be perfectly legal and follows
| TOS, GitHub really isn't the place to host anything possibly
| damaging to or annoying big tech.
|
| You can add push URLs to your origin branch such that `git push`
| automatically mirrors your code on multiple remotes: `git remote
| set-url --add --push origin git://another/repo.git`. If you
| maintain an open source repository, I would encourage you to have
| mirrors across gitlab, codeberg, and/or a self hosted gitea
| instance.
| Wowfunhappy wrote:
| I'm certainly not against mirrors. But--
|
| > GitHub really isn't the place to host anything possibly
| damaging to or annoying big tech.
|
| Why would Google give a crap if a handful of people futzing
| around with ancient versions of Windows and macOS want to run
| up-to-date Chromium browsers?
|
| If you wanted to be super conspiratorial, you could point to
| Supermium's announcement that they plan to retain Manifest V2
| support. But that merely puts them in the same category as
| Brave and Firefox.
|
| At the same time, I don't know how else to explain what is
| going on!
___________________________________________________________________
(page generated 2024-06-03 23:02 UTC)