✨This repository is moving!✨

[HACKERALERT]

First of all, I would like to thank all of you for using Picocrypt and for helping me out where needed. It's truly amazing to see a small side project of mine turn into a well-regarded encryption tool that many people use and love! Now that there are so many users and potential contributors, I think it's time for a change. I originally had the mindset of maintaining Picocrypt myself for better quality control and security, but I think by now, the software is already stable and it's time to try something new, especially as my life gets busy and my time available to work on Picocrypt decreases.

I've created a Picocrypt organization on GitHub, accessible through github.com/Picocrypt. This will be the official organization for future work on Picocrypt, allowing for a clean URL to share with others (without my funny username) and for community contributions to the codebase. Now, anyone who wants to contribute to Picocrypt can, and can do so without my supervision once we establish a team of trusted code reviewers.

As for this repository, don't worry: it's not going anywhere. While I am excited about any new developments that will occur in the new organization, I still want to provide a stable and secure "backup". So for people who need a high level of trust and stability, keep using my personal repository which you can trust has undergone a lot of careful designing and testing by me. For people who are a bit more brave and open to more experimental (and potentially less stable software), I encourage you to check out the new Picocrypt organization and any goodies that may exist there.

There is still a lot of groundwork to lay, but I'm confident this will be a beneficial change for everyone. Onward!

[HACKERALERT]

In terms of housekeeping, please don't create any new issues in this repository. Development will now take place in the new Picocrypt organization so any issues should be posted there where there will be more eyes on code and keyboards ready to code.