-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future of the Project #342
Comments
@daylamtayari Yes Sir 🫡 ahaha welcome back. |
Well, there's obviously no obligation to follow any noted time line. Even if the project is cancelled, it's cancelled. I'm just wondering why communication and activity on github died rapidly around two...three weeks after the OP post.🤔 |
Is this still maintained? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After a long absence for which I sincerely apologise, I am back to working on the project and going to resolve issues, patch errors and afterwards rework it.
If you want to help contribute to the project or want help with using the program, please join the discord: https://discord.twitchrecover.com.
A full FAQ is present in the Discord under the
#readme-faq
.Project Roadmap
Afterwards, in November
Rewrite the entire of Twitch Recover in Go, fixing various fundamental issues and designing it in a way for additional features to be easily implemented.
The text was updated successfully, but these errors were encountered: