Sending multiline quotes is tedious

What I did

I sent a message that had a multi-line quote of text. e.g.:

Hi, I found this description, do you think it's adequate?
>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
>
>Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

What happened

The quote displayed but with a > for the blank line in the middle of the quote instead of inserting a blank line in the middle of the quote.

What I expected to happen

I expected the message to look like this:

This is what it looks like if for that blank line I insert a space, e.g.: > instead of >. We can manually use this work around but it'd be great if Keybase handled multi-paragraph quotes better out of the box.

Other better solutions

There's an issue here specifically with the > and a blank line, but there might be a better overall solution that Slack has adopted. Slack supports the >>> at the beginning of the quote that causes all the lines for the rest of the message to become quoted. e.g.: https://twitter.com/slackhq/status/472098178838179840.

No files, tests, or entry points are named in the issue. Start by locating the client’s multiline quote handling; done means blank quoted lines render as blank lines without requiring a space, with regression coverage.