[GH-ISSUE #724] State of Humanify, why we are here, where we're heading #102

New issue

Open

opened 2026-03-03 13:52:58 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 13:52:58 +03:00

Owner

Originally created by @jehna on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/jehna/humanify/issues/724

Hi everyone!

TL;DR: Humanify went quiet for ~1.5 years due to real-life priorities. That was a conscious trade-off (as this is a free-time project). I now have some time again and I’d like to use this issue to align on what we should do next.

The why

I feel I need to explain a bit of the why after such a long radio silence.

Humanify got traction and active usage in 2023–2024, and I tried to keep up. Then life happened:

Late 2024: I spent most of my available spare time on a national CTF, leading to hacker tickets to a national hacker event (it was intense, but it paid off and was a great experience).
2025: I got the chance to fully focus on doing OSCP certificate. That basically consumed my project bandwidth for the year. I passed the exam at the end of 2025 (first attempt 🎉 ), which was the goal.

As a result, Humanify's maintenance fell to a very low flame for a while. I understand that this has been frustrating for users, but I also want to be clear that this has always been a hobby project, maintained in whatever spare time I can realistically carve out.

I’m back with a bit more bandwidth again, and I’d like to have a discussion about where we are at the moment to find good ways to continue on Humanify.

Next steps

I genuinely appreciate everyone who has contributed, commented, reported bugs, or sent PRs.

I understand that the maintenance load would be easier to share among members of the community. However, I think that since the primary audience of this tool are security-minded people, I want to keep write access to this repository to myself for the time being. Getting someone inject bad stuff would not be cool, and trusting anonymous Internet people nowadays is hard.

I'm now taking some time to check where we're at, fixing obvious bugs and thinking where we should take Humanify next. Performance and stability are the most obvious bottlenecks for using this tool for bigger files, so those will probably be the primary focus. A lot has happened with LLMs too during the last year and a half, so we'll need some maintenance to check how the state of art models can best be utilized.

I'll appreciate any thoughts on the steps going forward. I have a big backlog of going through all the issues, but at least for now it looks I have some time to spend on this again (until life sends the next curveball, of course).

Originally created by @jehna on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/jehna/humanify/issues/724 Hi everyone! **TL;DR:** Humanify went quiet for ~1.5 years due to real-life priorities. That was a conscious trade-off (as this is a free-time project). I now have some time again and I’d like to use this issue to align on what we should do next. ## The why I feel I need to explain a bit of the _why_ after such a long radio silence. Humanify got traction and active usage in 2023–2024, and I tried to keep up. Then life happened: - **Late 2024:** I spent most of my available spare time on a national CTF, leading to hacker tickets to a national hacker event (it was intense, but it paid off and was a great experience). - **2025:** I got the chance to fully focus on doing OSCP certificate. That basically consumed my project bandwidth for the year. I passed the exam at the end of 2025 (first attempt 🎉 ), which was the goal. As a result, Humanify's maintenance fell to a very low flame for a while. I understand that this has been frustrating for users, but I also want to be clear that _this has always been a hobby project_, maintained in whatever spare time I can realistically carve out. I’m back with a bit more bandwidth again, and I’d like to have a discussion about where we are at the moment to find good ways to continue on Humanify. ## Next steps I genuinely appreciate everyone who has contributed, commented, reported bugs, or sent PRs. I understand that the maintenance load would be easier to share among members of the community. However, I think that since the primary audience of this tool are security-minded people, I want to keep write access to this repository to myself for the time being. Getting someone inject bad stuff would not be cool, and trusting anonymous Internet people nowadays is hard. I'm now taking some time to check where we're at, fixing obvious bugs and thinking where we should take Humanify next. Performance and stability are the most obvious bottlenecks for using this tool for bigger files, so those will probably be the primary focus. A lot has happened with LLMs too during the last year and a half, so we'll need some maintenance to check how the state of art models can best be utilized. I'll appreciate any thoughts on the steps going forward. I have a big backlog of going through all the issues, but at least for now it looks I have some time to spend on this again (until life sends the next curveball, of course).

kerem commented

2026-03-03 13:52:58 +03:00

Author

Owner

@0xdevalias commented on GitHub (Jan 26, 2026):

@jehna Awesome to see you back with some bandwidth for this; and congrats on the CTF / OSCP achievements!

I'm finding myself pretty low bandwidth lately unfortunately; but keen to keep an eye across happenings here as I am able and contribute if / where I can.

@0xdevalias commented on GitHub (Jan 26, 2026): @jehna Awesome to see you back with some bandwidth for this; and congrats on the CTF / OSCP achievements! I'm finding myself pretty low bandwidth lately unfortunately; but keen to keep an eye across happenings here as I am able and contribute if / where I can.