The binaries for UC (Eloston) are always being updated. It's only the browser that's not being updated. Why it wasn't frequently updated was discussed in their forums previously.In the past I used Ungoogled Chromium, because it had two advantages for me:
I downloaded it and added uBO to the mix to discovered a third advantage
- 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.
- 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)
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.
@HarborFront I have not been following the releases, how up to date is Eloston's ungoogled nowadays?
So when I understand you correctly, Eloston patches security bugs in his ungoogled browser code himself, instead of incorporating the updated browser. To be honest, I could not believe such an experienced/seasoned MT-member like you would use an unpatched browser with so many security holes in it. This background info explains why you kept using it.The binaries for UC (Eloston) are always being updated. It's only the browser that's not being updated. Why it wasn't frequently updated was discussed in their forums previously.
Eloston himself don't do it. There are contributors to do that. Like I mentioned the binary for Windows is always updated. It's only the UG browser that's not. The previous maintainer left so nobody compiles the binary to browser.So when I understand you correctly, Eloston patches security bugs in his ungoogled browser code himself, instead of incorporating the updated browser. To be honest, I could not believe such an experienced/seasoned MT-member like you would use an unpatched browser with so many security holes in it. This background info explains why you kept using it.
For a man with limited time, I can understand that he (Eloston) skips new releases when he does not use these features himself and only regards those additional features as bloat. On the other hand between V89 and V95 some same-origin restrictions were implemented which are considered security enhancements. Not updating the browser also means not benefitting from those security improvements.
Last question: does he transparently publishes the security patches he makes into his 'frozen' ungoogled copy of the browser?
The browser do NOT have auto update by default. You need to do manual update.How do i get the prompt for updates?
2 things need to take noteI've added the server blocking list to my hosts file and so far so good.
I found out that I could not sign into my Microsoft account with the blocklist2 things need to take note
1) MS Edge updating
2) Extensions updating
Must block these two because they are calling back to MS. Need to manual update like Ungoogled Chromium (Eloston) then it'll make a better privacy focus MS Edge browser
I believe you can block MS Edge from updating from your given link and can download a new version manually from below for installation but must export all the settings first.
but not so sure of manual download and install the extensions