Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request: Please can you credit Marmaduke, the main developer of your Chromium release? #9

Closed
woolyss opened this issue Jul 3, 2020 · 8 comments

Comments

@woolyss
Copy link

woolyss commented Jul 3, 2020

Hello @crazy-max: I salute your effort to make a portable version of Chromium. 馃憤
https://github.com/portapps/ungoogled-chromium-portable

Please, can you credit the source of your Chromium releases which is done by Marmaduke (@macchrome)?

Indeed, Marmaduke is the only developer on the Web who compile the latest stable Chromium versions with support of all codecs (H.264, H.265...) and the Widevine plugin. Note: the support of H.265/HEVC (Online audio/video tester) in Chromium is not documented at all. Most of browser does not support it. So it is difficult to reproduce this release.

The Windows versions from the Eloston repository are all outdated.

After that, I can promote your work on our site if you want.
It means a link of your portable release at https://chromium.woolyss.com/ for the corresponding Marmaduke's "ungoogled" release. 馃槈

Thank you very much.

Contact me in private (https://info.woolyss.com/) if you prefer.

Regards.

@crazy-max
Copy link
Member

crazy-max commented Jul 3, 2020

Hi @woolyss,

Please, can you credit the source of your Chromium releases which is done by Marmaduke (@macchrome)?

Sure I will add a note in the README, thanks for your input!

@crazy-max
Copy link
Member

crazy-max commented Jul 4, 2020

@woolyss Done.

@woolyss
Copy link
Author

woolyss commented Jul 4, 2020

@crazy-max: Thank you very much. I added a link to your Chromium releases, on our website (near the "Ungoogled" versions). 馃槈
https://chromium.woolyss.com/

@dm17
Copy link

dm17 commented Dec 26, 2020

@woolyss Can you help dispel some misconceptions and make it easy for us to stay informed on the privacy/security aspects of ungoogled-chromium: what are the exact privacy/security differences between Eloston's and Marmaduke's ungoogled-chromium builds?
Thanks!

@woolyss
Copy link
Author

woolyss commented Dec 27, 2020

@dm17 Please, check your mailbox ;)

@dm17
Copy link

dm17 commented Dec 28, 2020

@dm17 Please, check your mailbox ;)

Thanks, but I have to say the email did not include anything directly about privacy patch differences between Marmaduke's and Eloston's ungoogled-chromium. Perhaps it is a suggestion to look at the latest patches and just compare them?

@woolyss
Copy link
Author

woolyss commented Dec 28, 2020

As I said before, Maramaduke uses all patches apart from "Safe Browser".
You can check that for each release:
https://github.com/macchrome/winchrome/releases/tag/v87.0.4280.88-r812852-Win64

This release was compiled Friday, December 4, 2020. So, Maramaduke used all latest ungoogled-chromium patches from the Eloston's project (except the safebrowsing patch, like mentioned)
https://github.com/Eloston/ungoogled-chromium/tree/master/patches
https://github.com/Eloston/ungoogled-chromium/commits/master/patches (history of changes)
As you can see the last patch was fixed on December 4, 2020


1

@dm17
Copy link

dm17 commented May 13, 2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants