Skip to content
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

update the npmjs library release #2815

Open
marcelocecin opened this issue Oct 11, 2024 · 9 comments
Open

update the npmjs library release #2815

marcelocecin opened this issue Oct 11, 2024 · 9 comments
Labels
bug Something isn't working needs triage Needs avaliation

Comments

@marcelocecin
Copy link

please update the npmjs library release

@marcelocecin marcelocecin added bug Something isn't working needs triage Needs avaliation labels Oct 11, 2024
@ghayman
Copy link
Contributor

ghayman commented Oct 31, 2024

I wish I could... @jonalan7 @orkestral ?

@Alynva
Copy link

Alynva commented Nov 13, 2024

Up... I need a21267d

@9cb14c1ec0
Copy link
Contributor

@ghayman Can we close this issue now?

@ghayman
Copy link
Contributor

ghayman commented Nov 18, 2024

We still don't have access to the npmjs account so I'm not sure best way forward - do you think we should create a new account and publish it there

@jonalan7 @orkestral we really want to keep this project going. It appears to be used by many people. You can contact me directly if necessary.
nós realmente queremos continuar esse projeto. Parece ser usado por muitas pessoas. Você pode entrar em contato comigo diretamente, se necessário.

@jonalan7
Copy link
Contributor

jonalan7 commented Nov 18, 2024

@ghayman
Man, I really wanted to help, but I don’t see any future in this project anymore. It’s way too outdated.
I have nothing against Orkestral, but from what I can see, he’s no longer involved: no commits, no bug fixes, and it seems like he doesn’t care about the project’s progress.

On top of that, the project is full of issues and unresolved problems. Why would I invest my time and effort in something packed with bugs and outdated code when even the creator himself doesn’t seem interested in maintaining it?

I can see you’ve been putting in a lot of effort to keep it alive, but honestly, this project would need to be rebuilt from scratch. Simple fixes wouldn’t be enough.

That’s why I decided to focus on another project: refactoring Venom-Bot, which I had paused due to a lack of time but am now resuming. It’s much better and way more stable than this one! https://github.com/jonalan7/Hydra-bot

@9cb14c1ec0
Copy link
Contributor

For me personally, it would not be easy to migrate to a new library. If this repository is going to die, I will maintain a fork.

@jonalan7
Copy link
Contributor

The most challenging parts of Venom-Bot have already been integrated into Hydra-Bot! If you access it, you'll see that most of the main features, such as sending text messages, files, images, audio, and much more, are already implemented. I will continue working on improvements and adding new features soon!

@jonalan7
Copy link
Contributor

Another improvement is the implementation of Web Services, which makes it easier to integrate Hydra-Bot with other libraries, allowing it to be used as an efficient backend!

@ghayman
Copy link
Contributor

ghayman commented Nov 18, 2024

@jonalan7 I totally understand your position, however I think both @9cb14c1ec0 and I and probably others have a lot of time invested in this.
Would you able to give as full admin access to the repo and npmjs so that we can stop bugging you or is that something only @orkestral can do?

Also, I am more than happy to see if we can make your new venture work - can you email me so that we can discuss? Email is on my commits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage Needs avaliation
Projects
None yet
Development

No branches or pull requests

5 participants