-
-
Notifications
You must be signed in to change notification settings - Fork 331
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
Is this project dead? #1028
Comments
The developer said "I will definitely update nekox after submitting my paper by the end of September" so I think you can wait a few days for an update. |
Nope:) I'm sorry for the long delay, at least Oct 3 I will make up for all updates |
This is extremely good news! |
Just a note: NekoX is affected by https://www.cve.org/CVERecord?id=CVE-2023-5129. It should be very easy to fix it: you just need to update the submodule to https://github.com/webmproject/libwebp/commits/1.2.0. |
Sure. I have noticed this issue. |
Will you fix it soon? Should I patch that for F-Droid? |
Last commit to dev 14 hours ago!! 🙌🙌 I love this client ❤️. Looking forward so much for it to be updated. |
It looks like the project is dead. It's a pity(( |
? |
What date is today?? What update did they promise? Draw your own conclusions. |
looks as good as dead. No updates, despite security vulnerability. Would advise against further use of this fork for security reasons. Just stick with the official client. Doesn't make sense with the forks anyway. Sooner or later, Telegram will only make the API public for money, just like Twitter "X". |
Looks like we need to move to fork: https://github.com/nextalone/nagram |
I don't like nagram, it does not allow you to open issues and is not released on fdroid. |
You can definitely open issues for NekoX - but nobody will fix them as development is dead ))) As for fdroid it marks NekoX as dangerous because of non-fuxed vulnerability. |
It's not since we have updated the libwebp with a patch. |
Are you using the F-Droid version? If you are using the apk from upstream, F-Droid can't update it but still shows the warning. If you are using the F-Droid version then it should show you an update instead. |
Unfortunately I am using upstream as I prefer GCM version for a number of reasons. |
you were talking about nagram and I replied talking about nagram, what does nekox have to do with it? |
Mate, I am talking about possible alternatives those are as close as possible to this dead project. Ok you can stay at NekoX if cons are more important for you than pros ))) |
I'm sorry but why not https://github.com/Nekogram/Nekogram ? |
For me, because it's not in F-Droid. |
You are right. I just asked them Nekogram/Nekogram#30 feel free to upvote it |
It looks dead. Last release was 9 Months ago and last commit 8. Please, I want to use this client. |
The last commit is 3 days ago. https://github.com/NekoX-Dev/NekoX/commits/dev Please stop spamming here, it doesn't help. |
Oh, sorry. Didn't see that. My mistake. |
Two months ago there was also activity, so what? |
search for nekoX ghetto on tg . maintained fork . by today last version posted is 10.6.1 ,posted january 23 |
https://github.com/PreviousAlone/Nnngram this project seems great too, it adds nekoX features and from other forks too , im experimenting . just dont like the translate that dont work like here on nekoX. |
Just curious will this project move further or it is dead?
We have some info about future plans: #982 but they are stuck.
Also none of reported bugs are fixed.
I understand that every developer has own life but maybe users can obtain some information and decide will they wait (for smth) or move to another client?
The text was updated successfully, but these errors were encountered: