We should maybe release a new version.

[museun]

https://github.com/museun/twitch_message/compare/e014029e81ee41b3c7a91ae00dd7d8eb97001f41..3ed7a259565bcf172a03f7f3d15a266442076845

that are the changes since then, and its been about 3 years.

the notable things are using twitch-types and the aliri braid stuff. I remember having some private hesitations for bringing in a few more deps and the braid stuff.

but if its worked great for the twitch-rs projects, I can concede to including them.

personally I just use the git master for my random twitch projects e.g. https://github.com/museun/yomi/blob/d76a6053c0d63a3168d5a0990579bb1e7530b2b7/Cargo.toml#L27 (also, this literally my twitch irc client for that bot. three functions. one for connecting, one for the main loop: https://github.com/museun/yomi/blob/d76a6053c0d63a3168d5a0990579bb1e7530b2b7/src/irc.rs#L352-L438 with one that does my encode api as async: https://github.com/museun/yomi/blob/d76a6053c0d63a3168d5a0990579bb1e7530b2b7/src/irc.rs#L572-L597)

so, if I haven't noticed anything that can't be done with them, then they are probably perfectly fine to use.

I may have some time in the upcoming days so I can go ahead and give this a refresh/add whatever twitch changed in the last 3-4 years (Kappa).

@Emilgardis do you have any ideas or opinions? also, would you like me to transfer this over to the organization?

if I do get, say, an afternoon I can even write a pair of simple client libraries (std sync and tokio async). which'll use this. which'll sidestep that irc problem (see #43)