pipboy96
pipboy96
@zeorin We are aware of this issue. We can't make a hotfix release due to COVID-19 lockdown. See https://github.com/EFForg/https-everywhere/issues/19029#issuecomment-602771741 for details.
@zoracon Maybe we can move towards using local browser storage instead of the sync one, or allow the user to choose? As far as I know, local storage is almost...
There's way too much off-topic conversation here. @Eloston can you hide all these comments (mostly about hardware "needed" to build Chromium) using GitHub's new feature ([like this one](https://github.com/vslavik/winsparkle/issues/187#issuecomment-448955605)) and if...
@SuperRobinHood I also think baseline stuff such as blocking and HTTPS Everywhere could be simply integrated into the browser.
@Eloston Need your opinion since the situation had changed.
@Eloston Maybe implement basic blocking as part of our patches? So even if uB0 is discontinued we can still use the lists.
@emanruse Not quite true, there are cases when simply doing `s/^http:/https:/` causes redirect to wrong/broken page.
@emanruse > So in regards to that there is no need for HTTPS Everywhere at all
@mikhoul A side effect of background page deprecation is that `` will no longer work.
Related: Eloston/ungoogled-chromium#706.