TL;DR: I accidentally deleted the old repository with 107 stars, and have moved the project to GitLab because GitHub requires a paid account to recover deleted repositories. I take full responsibility for this, it was an extremely stupid mistake on my part. I deeply apologize for the inconvenience. I understand if this damages the trust in the project.
I appreciate all the support you all have given towards the project, it truly means a lot to me! For those of you who bookmarked the repo, please update it to the new GitLab page which will now be actively maintained.
If you don't know what Open Source Everything is, see my original post. It's my own curated list of open source software.
Update: GitHub was able to restore the repository! Special thanks to Seve from GitHub Support for bending the rules a bit. GitLab will still be the primary place where the repository is hosted.
Hey, your upfront, honest, no-excuses post goes a long way, in my opinion.
Shit happens. We've all screwed things up - letting everyone know immediately what's going on means we won't guess when our shortcut doesn't work, etc.
Also thanks for the effort you put into this. It's really helpful.
Thank you! I tried my best to get things back on track ASAP, but GitHub's support ticket system was in an outage at the time. I'm just happy to get it resolved.
I may mirror it to Codeberg in the future. The honest answer is that I was in a panic and needed somewhere to quickly get the project back up in case GitHub never resolved itself. GitLab was a good choice since it's open source and has a lot of other big open source projects on there.
I'd like to urge you not to use GitLab for your source code due to the ridiculous numbers of severe CVEs. I don't think they have any idea how to write secure code and I don't think they care to learn.
Here is the most recent one I know of. The article mentions it's the fourth in a year. Here is the most egregious one IMO, how are they so bad at coding they would accept unverified inputs to send emails to?
Firefox is less private than some forks (Librewolf, etc.) and less secure than Chromium-based browsers due to a lack of Per-Site Process Isolation. Mullvad Browser and the Tor Browser are the only two Firefox-based browsers I can recommend due to their high privacy standards.
I'm still on the fence about adding KeePass, since I don't see anything it provides over KeePassXC. Notepad++ I will definitely look into, as well as ShareX and Greenshot. Thanks so much for the suggestions!
Greenshot is so handy. I've successfully converted several of my coworkers to using it. Some of our corpo contract IT folks are secretly pissed about it because unlike us they aren't allowed to use open source software (LOL) so they have to put up with windows snipping tool
Gecko based browsers are less secure to Chromium based browsers due to a lack of Per-Site Process Isolation. Mullvad Browser and the Tor Browser are exceptions due to their high privacy standards. Brave was recently added, since the list previously had no Chromium-based browsers.
ProtonVPN will not be added due to their slow action taken towards fixing multicast packet leaks. Once they fix this, I will consider adding them back.
I will eventually add a section for firewalls and public recursive name servers, but there are complications finding those at the moment. Thank you for the suggestions!
Look on the bright side: I bet a fair number of folks like me didn't know about this and now it's on my front burner to-do list to check it out! Thanks for the good work.
The fork you are thinking of is Tenacity. They explain in their history why it was made. Yes, Audacity was bought by Muse Group. There were talks of adding trackers, but nothing ever actually got added. They changed the privacy policy at one point, but reverted it after backlash. The reason I am keeping Audacity there is because I believe it is better to have quick security/feature updates from upstream (Audacity) so long as the upstream project does not have any current code issues that warrant a fork (Tenacity). If Audacity ever does add any telemetry, etc. I will absolutely change it to Tenacity.
Weren’t the trackers opt-in? This doesn’t seem like a bad thing if you don’t mind giving up those user metrics for them to build something better. It is the opt-out stuff with no transparency over the kind of data collected to be worried about.
I do not accept donations, although I appreciate it! I would rather not support Microsoft/GitHub if they are going to make you pay to use features that costs them nothing.
Agreed. You fucked up and now hopefully you learned from it. The reason any of us have (typical local) backups is because we lost data, whether a little or a lot. This is no different.
I meant general computer backups, I just had trouble phrasing it correctly. As in, you and I probably didn't backup our computers properly until we lost something. That's how most of us get into backups. Similar here.
it is still a great list so thanks for getting it back up 👍
but i have a few questions:
is there a reason (or privacy concern) why Linux Mint isn't one of the recommended distros?
and am I wrong or isn't bitward a good privacy friendly password-manager?
The recommended distro section will get overhauled, as it doesn't quite meet my standards. I personally don't like Linux Mint because Cinnamon is less than what I would like it to be, but it is getting a makeover.
Bitwarden was heavily considered as a password manager, and it is a great option, but they make you pay to use certain features (hardware security keys, etc.) that KeePassXC and others offer for free. Hence, KeePassXC is a better option and Bitwarden didn't make the cut.
I'm going to mostly copy paste a similar reply I made in this thread: A fork of Audacity was made called Tenacity. They explain in their history why it was made. Yes, Audacity was bought by Muse Group. There were talks of adding trackers, but nothing ever actually got added. They changed the privacy policy at one point, but reverted it after backlash. The reason I am keeping Audacity there is because I believe it is better to have quick security/feature updates from upstream (Audacity) so long as the upstream project does not have any current code issues that warrant a fork (Tenacity). If Audacity ever does add any telemetry, etc. I will absolutely change it to Tenacity.
I will be creating an FAQ section that answers this question in more depth.