Reply to thread

Message

<blockquote data-quote="ForgottenSeer 92963" data-source="post: 964062">In the past I used Ungoogled Chromium, because it had two advantages for me:<ul>
<li data-xf-list-type="ul">Being ungoogled obviously has some privacy advantages and because the maintainer is a hardcore &#039;less is more&#039; promotor I think (soft non rational emotional argument) that this ungoogled variant was a bit more ungoogled than other ungoogled browsers</li>
<li data-xf-list-type="ul">Being an unsigned program and I have set UAC to block elevation of unsigned programs, ungoogled chromium ran in an additional standard user rights container.</li>
</ul>I downloaded it and added uBO to the mix to discovered a third advantage<ul>
<li data-xf-list-type="ul">Microsoft Defender Protected Folder blocks ungoogled from changing my user folders, so now I have an additional data layer protection on top of the build in site permission block (allow file access)</li>
</ul>In the past I stopped using Eloston&#039;s ungoogled because the maintainer (Eloston) was (to) many release cycles behind Chrome, which sort of nullified the standard user rights security advantage (became a security risk) and made me move over to Woolyss ungoogled.[USER=55987]@HarborFront[/USER] I have not been following the releases, how up to date is Eloston&#039;s ungoogled nowadays?</blockquote>

[QUOTE="ForgottenSeer 92963, post: 964062"] In the past I used Ungoogled Chromium, because it had two advantages for me: [LIST] [*]Being ungoogled obviously has some privacy advantages and because the maintainer is a hardcore 'less is more' promotor I think (soft non rational emotional argument) that this ungoogled variant was a bit more ungoogled than other ungoogled browsers [*]Being an unsigned program and I have set UAC to block elevation of unsigned programs, ungoogled chromium ran in an additional standard user rights container. [/LIST] I downloaded it and added uBO to the mix to discovered a third advantage [LIST] [*]Microsoft Defender Protected Folder blocks ungoogled from changing my user folders, so now I have an additional data layer protection on top of the build in site permission block (allow file access) [/LIST] In the past I stopped using Eloston's ungoogled because the maintainer (Eloston) was (to) many release cycles behind Chrome, which sort of nullified the standard user rights security advantage (became a security risk) and made me move over to Woolyss ungoogled. [USER=55987]@HarborFront[/USER] I have not been following the releases, how up to date is Eloston's ungoogled nowadays? [/QUOTE]

Verification