They are not alone. I know many people who would find this offensive. It isn't like they shadowbanned them or deleted the repo outright. The maintainers were given 24hrs and instructions to fix it.
-- @ybur-yug
No, what actually happened is that somebody reported the original upstream of this fork (WebMBro/WebMConverter) but since @WebMBro himself left a while ago (which prompted me to make this fork in the first place), GitHub couldn't get a response from him, so they shut down that repo
along with all forks, with seemingly no communication towards other fork developers.
I had to contact GitHub myself in order to even get a notification of what was going on, and it took them about 3 days to restore any kind of access to my fork of the project.
This article uses "password managers" ambiguously. In my opinion, a browser is a terrible password manager because of what is stated in the "pros" section of the article. My advice aligns with others who have replied here - get a real password manager such as 1password and allow autocomplete="off" to do what it is supposed to do.
Sorry, but which of the two points in the ‘pro’ section (storing truly sensitive visible information and hacking of client-site databases) makes a browser less capable of acting as a password manager than a ‘real’ password manager?
Or maybe you could rephrase why you think browsers are terrible password managers? I’m quite fond of Opera’s Wand.
I'm going to go out on a limb and suggest just because 1password is really really good. So good that I don't even want to try a browser's password manager (especially since I want access to my passwords on multiple browsers and my phone/tablet as well). I'm sure browser password managers have made leaps and bounds, but so as 1password and it's amazing.
I'm 33. Though I have older code that I cannot find anymore, the oldest I have online is from 2001 - Rain - the powerful, Unix packet builder. It is still in *nix distros today.
nixxquality commented on c1ac0ba 4 hours ago
No, what actually happened is that somebody reported the original upstream of this fork (WebMBro/WebMConverter) but since @WebMBro himself left a while ago (which prompted me to make this fork in the first place), GitHub couldn't get a response from him, so they shut down that repo along with all forks, with seemingly no communication towards other fork developers.I had to contact GitHub myself in order to even get a notification of what was going on, and it took them about 3 days to restore any kind of access to my fork of the project.