> The official Zen browser repo got flagged by GitHub, in turn its currently unavailable for you.
> There is no code loss, We just waiting on a review by GitHub.
> Also affected is Mods download, Binaries download, Docs website and Update-Server.
This is concerning because it suggests they somehow violated the terms of service. However, I wouldn't be surprised if it's a ploy by the project author to forcefully close all the opened issues again.
I'm assuming the project is burdened with technical debt yet again, since most of the bug "fixes" are just monkey-patches. They're mostly superficial, where the root cause is usually never addressed, which creates more issues when new features are implemented, this additionally causes many regressions, with previously fixed issues resurfacing.
The repo owner is in damage control mode. He just renamed the title and commented on a 7 month old PR, now admitting it was a toy project back then. He claims it was "NOT because of un-experience" and that, 7 months after the fix, they "now provide the most private and secure experience". It doesn't seem convincing to me, but very comical.
> The official Zen browser repo got flagged by GitHub, in turn its currently unavailable for you.
> There is no code loss, We just waiting on a review by GitHub.
> Also affected is Mods download, Binaries download, Docs website and Update-Server.
This is concerning because it suggests they somehow violated the terms of service. However, I wouldn't be surprised if it's a ploy by the project author to forcefully close all the opened issues again.
I'm assuming the project is burdened with technical debt yet again, since most of the bug "fixes" are just monkey-patches. They're mostly superficial, where the root cause is usually never addressed, which creates more issues when new features are implemented, this additionally causes many regressions, with previously fixed issues resurfacing.