eeeeeta / glitch-in-the-matrix Goto Github PK

FYI @eeeeeta I have opened an issue for tracking in matrix-org/synapse#9096 which may need some resolution on the client side.

Feel free to close this and I can reopen if homeserver owners cannot resolve the issue on server side

• relax error handling on MatrixRequestable to accept anything coerceable into failure::Error
• maybe un-specialcase the hyper errors while we're at it
• go over and fix missing docs
• fix README
• write at least one nice example
• clarify how cloning a MatrixClient works, and perhaps special-case this for ASes

according to Half-Shot, you can't discard keys on event content; they might be used for important non-specced extensions. probably best to chuck 'em into a serde::Value or something alongside the strongly-typed representation.

master has hyper-openssl 0.7, but the current release on crates.io is quite outdated with 0.3.

master is compiling just fine, and this update improves openssl compatibility.

Please can you cargo publish a patch release?

gitm 0.14 uses an outdated version of hyper that transitively depends on a version of smallvec with a critical CVE

It would be good to add a note that folks should use official maintained crates if there's no plan to make another release here

It'd be useful to have some method to send state events, modifying the state of the room.

My usecase is for a bot that would store its state directly into the room, allowing the program itself to be completely stateless.