Is anyone going to support their fork?

[ChocolateLoverRaj]

I see 3 forks in https://github.com/WillSewell/pusher-http-rust/network. @melkir @Star3Lord @ehsanR91 do any of you want to maintain a fork? It would focus efforts on a single fork instead of everyone maintaining their own fork.

Update: I realized that I'm also looking for a client library for actually receiving events...

[melkir]

Thank you for considering me as a potential maintainer. However, I don’t currently use this library in my day-to-day work, so I don’t see a strong benefit in maintaining it at this time. It might be best if the original author could transfer ownership to someone they trust who is actively using it.

[countradooku]

https://github.com/RustNSparks/pusher-http-rust

[countradooku]

@ChocolateLoverRaj @melkir I maintin this : https://github.com/RustNSparks/pusher-http-rust
also i have built a webscoket server compatible with pusher protocol in rust
https://github.com/RustNSparks/sockudo

[countradooku]

can i take the pusher crate name? @WillSewell

[ehsanR91]

Hi,

I work actively on the library, i will see if i can do my level best to push whatever i can and make as much community based updates possible. As of now i am already working on it.

[countradooku]

@ehsanR91 i work too on mine. It is quite complete

[countradooku]

It is as complete as pusher-http-node

[WillSewell]

Hey, I appreciate the interest in working on an alternative!

Just for the benefit of future readers: I'm afraid I am not willing to transfer ownership of the existing crate. I'm concerned about it from a security point of view (possible supply chain attack).

Best of luck with building an alternative.

[countradooku]

@ChocolateLoverRaj i support my fork https://github.com/RustNSparks/pusher-http-rust. It is not a fork. It written from scratch