Unintended diff format while posting a reply

[abitmore]

Here is a reply to my post, the text reads:

How about if they (we - not sure if I'd be classed as a 'large' SP holder) voted an hour after posting? That could act as an extra incentive for early voters.

I think the issue with getting authors to refrain from voting for themselves early, is that some will do it via a proxy/ shill account. Thereby getting the benefit without being perceived to be greedy.

If I reply to this comment with this text:

>How about if they (we - not sure if I'd be classed as a 'large' SP holder) voted an hour after posting? That could act as an extra incentive for early voters.

I support this.

>I think the issue with getting authors to refrain from voting for themselves early, is that some will do it via a proxy/ shill account. Thereby getting the benefit without being perceived to be greedy.

It's all about reputation. Technically it's unable to prevent anyone from voting for herself/himself early.

The result shows as:

@@ -1,8 +1,9 @@
+%3E
How abou
@@ -154,16 +154,34 @@
oters.%0A%0A
+I support this.%0A%0A%3E
I think
@@ -373,8 +373,117 @@
greedy.
+%0A%0AIt's all about reputation. Technically it's unable to prevent anyone from voting for herself/himself early.

Link is here.

[jcalfee]

This could have been two edits that got out of sync due to a fork. We have since improved the TaPOS header so if this were to happen again the older version would have alerted you by rejecting the transaction. We can not fix the post now though. Can you fix it by hand or can you get original version and edit that back into the post?

[abitmore]

Still buggy. Just posted another reply and same result.

[abitmore]

To be clear, I replied to a reply of my post and had some quotes (using >) inside.

[roadscape]

Another report - https://steemit.com/steem/@steemitblog/steem-0-14-2-released-bug-fix-release#@thecryptofiend/re-steemitblog-steem-0-14-2-released-bug-fix-release-20160917t155441149z

[Gandalf-the-Grey]

Recently reported: #538

[jcalfee]

It is very tricky to get the original data used to create the patch, this succeeds in JavaScript and we don't know there is a problem until we try to view it back from the C++ node applying the patch. If we can't easily find a bug we may have to code around this to detect it.

[jcalfee]

Another finding from roadscape:

roadscape [10:34 AM]
https://steemd.com/tx/1cf51df79ebdda9cb5890aa53096f12b58762353 — as far as I can tell, this was the original post. it wasn’t an edit
if that’s the case, for some reason the UI decided to post a patch for a new comment

roadscape [11:27 AM]
https://steemd.com/tx/1cf51df79ebdda9cb5890aa53096f12b58762353
Included in block 6,159,017 at _2016-10-26 03:18:51_
https://steemd.com/life/@logic/re-kairos-re-logic-re-kairos-re-logic-re-cassandracomplex-re-logic-discrimination-objectification-and-exploitation-of-women-is-pervading-we-live-in-patriarchy-the-facts-for-patriarchy-deniers-20161026t031847728z
last_update 2016-10-26 13:22:54
created _2016-10-26 03:18:48_