> attempting to fob Matrix development off on them is really not on. My point is that if you have requirements for a bridge (eg configurable scrollback retenti

> attempting to fob Matrix development off on them is really not on. My point is that if you have requirements for a bridge (eg configurable scrollback retention), you should submit a feature req to let us know about it at the time rather than ragequitting and telling people that matrix is broken. Anyway, point taken that we need to make scrollback retention configurable (whether for bridging or in general); have bumped it up the todo list.