Richard van der Hoff 64765e5199 When we do an invite rejection, save the signed leave event to the db
During a rejection of an invite received over federation, we ask a remote
server to make us a `leave` event, then sign it, then send that with
`send_leave`.

We were saving the *unsigned* version of the event (which has a different event
id to the signed version) to our db (and sending it to the clients), whereas
other servers in the room will have seen the *signed* version. We're not aware
of any actual problems that caused, except that it makes the database confusing
to look at and generally leaves the room in a weird state.
2017-04-07 14:39:32 +01:00
..
2016-01-07 04:26:29 +00:00
2017-03-16 11:54:26 +00:00
2016-11-16 14:47:52 +00:00
2017-03-24 11:46:24 +00:00
2017-03-16 11:54:26 +00:00
2017-02-02 10:53:36 +00:00
2017-03-13 11:53:26 +00:00
2017-02-20 15:02:01 +00:00
2017-03-16 13:04:07 +00:00
2016-11-16 14:47:52 +00:00