Is this project deprecated?

[elight]

There hasn't been any movement on it in over 5 months. There are 18 PRs open and 84 issues.

this looks like an amazing project. I know there's a need because I want it! But if it's gone cold...

@rishikanthc Are you coming back to the project any time soon? Not asking to nag. Seeking understanding.

From your profile, it looks like you've mostly dropped out of public commits. You ok? 🙏

[MadDogTen]

The last update I've seen was the one he posted around a while back: #426 (comment)

I hope everything is going well, and that it's just taking time settling into a new job rather then anything more serious.

[rishikanthc]

Hi @elight and @MadDogTen
Apologies for the radio silence.. I did find a new job, but had to move across the country for it. So between multiple moves, settling down into the new job and just recuperating from all the stress and anxiety I went through during the process made me want to take some time off.. So I was taking it easy, spending time with my family and didn't really have a lot of free time nor the mindset to expend on my personal projects..
That said, things are good now and boredom has been creeping up and I have been itching to get back into my personal projects.. I still need to setup my self-hosting server which I have been procrastinating for a while now xD

TLDR the project isn't abandoned. I'll be starting development again this week :)
Look like a lot of advancements and developments have happened in this domain in the past few months and I could actually use your input and thoughts on something.

So clearly a lot of issues and PRs have piled up. However, there have been some great projects like onnx-asr and audio.cpp have come up which actually provides a nice clean backend. I'm thinking switching to one of these is the right move over me maintaining a fragmented backend and having to put in some effort and hack to add support for new models (And new models are popping up so quickly I don't think I can keep up with them).
Additionally I feel, the main value for this project is the ecosystem it enables around ASR. So I'm thinking I'll focus on the rewrite and new ecosystem and UI that will enable this rather on spending effort on addressing the issues and PRs as that would also take up a significant time and I don't see the point in merging all of them only to go and rewrite everything..
I know this is going to cause some inconvenience to current users:
a) the issues and PRs would improve quality of life immediately
b) rewrite would probably mean breaking changes (we have been through quite a few of those) which is also a nuisance for users

However, before the radio silence, I had actually built a new frontend that would provide feature parity with some paid apps like Otter / Plaud.

So in my mind, I'm thinking I would want to go with the rewrite over focusing on fixing the issues and PRs especially coz my time on this project is limited and I can't split efforts between both aspects and that would also cause me to rush things.

So I'm curious what your take on this would be.. Would appreciate any thoughts or criticisms on this.
You all have been very patient and understanding and your continue interest in the project as well as concern for my well being makes me feel all warm and fuzzy xD

This project is a long long long away from getting abandoned any time soon. So don't worry about that :)
It's good to be back :)