Is undiscord abandoned/unmaintained? #446
-
This has not been updated since May which was a limited burst of activity from the original author that unfortunately lead some of the best forks to be archived (which oddly was done months after his last update), meaning that now that he has once again gone missing we are left with no choice but to scrap together a working version ourselves from each pull request. I'm sorry if you think I am lazy or demanding other people work for me for free. I'm just upset because this is the second time he's gone AWOL and this software is in pieces all over github when it doesn't need to be. I am not good at handling software on my own and I'm sure I'm not the only one. As far as I can tell he hasn't said we can't make forks anymore so I don't understand why there isn't a single big and popular one being used. But I'm scared of using less popular forks because of potential malware, as my discord account has a lot of personal conversations. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 15 replies
-
TLDR, no. About the infrequent updates
I would like to address a few things, I can only work on this from time to time, and it may seem that it doesn't receive updates as often as some would like, but this project has been an ongoing thing for at least 3 to 4 years. I can't just keep up with all the activity in this repository, because it is very time-consuming, the majority being just noise or just people having general questions (which is fine) but I can't answer each and every one personally. That's the main reason the issues tab has been disabled for some time, (even tho I rather have issues enabled) the discussion format is less developer-centric, and some folks have been able to help answer some questions. (Like @abbydiode, and some other names I will forget to mention, TY) About PRs
While there are some valuable contributions from the community from time to time, most are simply not high quality enough. So it's not just a matter of simply clicking "merge" to all of them. I have to read them to understand why, and how it works, make sure it's not malicious, and make sure it fixes one thing and doesn't break another. One buggy contribution and I will wake up the next day with a hundred messages complaining that it broke. Now I have to stop whatever I'm doing to fix it in a hurry. I've accepted some contributions in the past that were below my quality standards just because it was something that the community wanted. But after a few of those, the code became really messy and hard to modify further. About forks
Yeah, the code base is fully open-source, so I can't stop anyone from forking it, as long as they respect the license. Just because you can, doesn't mean I want to encourage people to fork it. But rather because I think for a tool like this you need the source to be fully transparent. All my projects are open source, but for this one, I take a bit of a different approach because I think the safety of the users is more important than only caring about the sharing aspect of open-source. I would really like to have more people taking care of this project, but I can't delegate the responsibility I have with people using this. That said being said, I have a full-time job, and I have many other projects (not just public GitHub), recently I suffered an accident and it's been hard to do my main job. But I will still keep working on this as long as it is viable. But that means you just have to be a bit patient sometimes. I'm working on an update tidying things up and hopefully, it will be easier for people to submit less hacky PRs. That new version will contain a few new features (don't expect anything major, at least for that immediate next version), but the main purpose of this version is rewriting and organizing the code. (Unfortunately, that means some PRs are going to be closed because I will not be able to merge them, but like last time I was able to incorporate some of the suggestions myself, the PRs were closed because I couldn't take the PR as is, the reason being the quality as I said before) I'm also working on semi-automatized testing to make my job of verifying if a PR works correctly easier. Sincerely, Victor. |
Beta Was this translation helpful? Give feedback.
-
NOTE: The original question was "Is there a most popular fork for this anymore?". |
Beta Was this translation helpful? Give feedback.
TLDR, no.
About the infrequent updates
I would like to address a few things, I can only work on this from time to time, and it may seem that it doesn't receive updates as often as some would like, but this project has been an ongoing thing for at least 3 to 4 years. I can't just keep up…