Consider adding maintainers

[adwhit]

Seems like development on this library has stalled. Not a big deal, it's open-source, it happens sometimes. However I think this is the most comprehensive Rust twitter library on crates.io, and based on the stars and PRs I'm sure the community would be interested in maintaining it - I certainly would. Would you consider adding some other maintainers to help work towards a 1.0 release?

[QuietMisdreavus]

I'm sure it's no secret at this point that i effectively abandoned egg-mode once i started taking on rustdoc (and later docs.rs) work more and more. The code has rotted somewhat, but i'm still happy with what i've written. I must admit i was slightly hoping someone else would pick up with a new crate, or that the competition between Twitter crates had continued in a similar state to where it was when i first started egg-mode, but it's clear that it's become a community favorite, with new users regularly trying it out. It's the most responsible thing to do to turn over ownership. To put it bluntly, i don't have the energy to work on this crate in addition to my dayjob and my responsibilities to the rust project as Rustdoc Team lead. I've invited @adwhit as a repo owner, since they have a good amount of experience with the code as the author of #40. Other potential collaborators are welcome at their discretion.

In terms of immediate goals, i guess i have this basic priority list:

• Fix the bitrot by making sure that we can properly link against OpenSSL, and fixing the struct definitions.
• Remove the streams module, or at least access to the user stream. User Streams got deprecated and removed, so this module is only useful for the firehose. To be honest, i'm not totally sure about the state of streams generally, so if this is useful for anything else, it can be added in the next release.
• Rework the Direct Messages API to use the newer API. I'm pretty sure the API that egg-mode is currently using is also deprecated if not totally removed by now, too.
• Update egg-mode-text to match the implementation of twitter-text 3.0. Much has happened with twitter-text since i last updated that library, and it's worth bringing it back up to speed.
• Design and implement a mechanism to register and listen for webhooks. IMO, this is best as a separate crate, unless there's a way to make the listening mechanism as transparent as the stream implementation currently on master. I remember looking into webhooks a long time ago, but i don't remember what was necessary to implement them.
• Fill in anything else missing that i've forgotten by now, or that was added since i looked last.

I'm confident that the community can continue to push the crate to the level of quality i always wanted for it. Thank you all for your appreciation over the years, and for your patience after i moved on. Here's to the future! 🎉

[adwhit]

Thanks for your hard work! I've got plenty of good use out of this crate in the past, looking forward to taking it further.