Go read the source find the security issues write a pull. As a foss user you either pay up and donate or submit a pull. Having issues with a developer doing their best isn’t productive in making foss better for everyone.
Browsers and Operating Systems are pretty senstive pieces of software. Any developer that show lack of knowledge in securing them, should not be trusted, foss or not.
Freedom means anyone can write almost any code that they want. If u don’t like how they write that software u can do it yourself or pay the guy to do it differently. That’s free will bro
The maintainer’s claim is that it was a small hobby project at the time. If their security record since gaining more users is acceptable, we probably shouldn’t rake them over the coals for leaving an unsafe debugging option turned on at an early stage.
Seems like the developer just didn’t realise the security risk. Looks like things are being rectified. So all good.
That is unacceptable when it comes to browsers.
You are putting all your trust in someone who does not know how security works.
Go read the source find the security issues write a pull. As a foss user you either pay up and donate or submit a pull. Having issues with a developer doing their best isn’t productive in making foss better for everyone.
What are you talking about?
Browsers and Operating Systems are pretty senstive pieces of software. Any developer that show lack of knowledge in securing them, should not be trusted, foss or not.
Freedom means anyone can write almost any code that they want. If u don’t like how they write that software u can do it yourself or pay the guy to do it differently. That’s free will bro
The maintainer’s claim is that it was a small hobby project at the time. If their security record since gaining more users is acceptable, we probably shouldn’t rake them over the coals for leaving an unsafe debugging option turned on at an early stage.