A big thing to work on that you might want to consider, is to change some of your bad habits; bad habits you are aware of (because I've seen you mention them before).
Being more open with your code and actually using git and GitHub like they were intended and possibly accepting bug reports & pull requests.
GitHub isn't just a glorified code-hosting site, and neither is git just a backup solution. You should realize that just because you accept contributions from others, Hydrus doesn't become yours any less. You even do that currently (just not in the form of code) and seem to have no issues with people providing tags, ideas, parsers, test & bug reports to you. I'm not sure where you're hung up with this whole thing, really.
Also consider this comment from the AUR:
> Indeed. To further explain the context for the benefit of others, the developer seems to have no experience or knowledge of OS best practices, general security concerns, or how to properly integrate software into any modern operating system. You can't package it as-is. He is receptive to suggestions and is respectful, but in general I think he is set in his ways. Another thing to point out is how he doesn't really use git- github is just a glorified webhost to him. No granular commits, no PR, no attention paid to issues. Just uploads a week's work in one commit. There are fewer commits than there are releases!
> Because of this scattered haphazard strange development, changes are necessary when trying to integrate hydrus into a package manager. These changes either have to come from upstream, or the package maintainer. Since the dev doesn't use github-issues or accept PRs, if you want upstream changes you have to take your plight to either the imageboard or the discord. Both are filled with younger teens who also don't understand how computers works, and in general your voice will be drowned out by their insistence that the dev shouldn't waste time on things like that. Which is amusing, I don't think they appreciate how rare it is for a side project to consistently update week-by-week. There's plenty of development time to go around.
> To be fair, some of the issues are inherit to targeting Windows as the primary platform.
Also, I realize that you've been doing this for a long time, but preceding any potential contributions from others, you should try to figure out if you want to follow PEP8 (or maybe something slightly less strict, like PEP8 - line length limit). The current way your code is formatted (e.g. very many superfluous newlines that make the code arguably less readable) and things within it are named, is very strange. I am aware that you might say that this is the way you've traught yourself Python and to code over the years, but I don't believe that you've reached the limit of what you want to or can learn. Trying to follow some of the best practices and allowing others to contribute to the beautiful software you've created, would be a huge step in that direction IMHO.
Just my two cents, I hope you realize that I mean absolutely no offense. I'm sure you've been asked this before/someone else requested it, but I really want you to reconsider once again; otherwise, when you eventually might stop working on Hydrus, the fans of your software will probably be stuck with an unmaintainable and confusing codebase.
Thanks for Hydrus.