Closed woolyss closed 4 years ago
crazy-max
commented
4 years ago 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!
woolyss
commented
4 years ago @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
commented
3 years ago @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
commented
3 years ago @dm17 Please, check your mailbox ;)
dm17
commented
3 years ago @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
commented
3 years ago 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
dm17
commented
3 years ago Hey Jerry, I found this awesome thread to do with deduplicating, streamlining, and optimizing degoogled chromium development efforts: https://github.com/Eloston/ungoogled-chromium/discussions/1395#discussioncomment-726202 Hopefully you can participate as well :)
On Mon, Dec 28, 2020 at 3:13 PM Jerry @.***> wrote:
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
Like for each binary, you must trust its developer. If you don't trust him/her, do it yourself! ^^
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/portapps/ungoogled-chromium-portable/issues/9#issuecomment-751708223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUABX5NQQ2WI3TVCCACENLSXB77TANCNFSM4OPUIMAQ .
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.