Just FYI. The proofread breaks quotes. This has that way a while now.
Doesn’t really break the quote, only the preview visualization.
I’d say this, plus the the animated diff we have on the roadmap, means we should move to doing a diff without the cooking part of it.
What do y’all think @awesomerobot @keegan ?
Just to add to this…
We recently updated Discourse, and from what I recall, the plugin wouldn’t try to proofread quoted text (as it shouldn’t because technically it’s not really quoted anymore if it does).
Below is a screenshot…
@keegan just rolled out a new implementation, the diff is now applied to markdown and streamed ![]()
It works great for this case and even handles fixing typos in quotes ![]()
Ik ben hier omdat ik niet denk dat proeflezen geciteerd materiaal zou moeten corrigeren (het is niet geciteerd als het “gecorrigeerd” is)
Is er een manier om een overstap aan te vragen om geciteerd materiaal niet aan te raken?
Trouwens: Geweldig werk met de recente upgrade en het standaard maken van zoveel plugins, waaronder AI. Ik host zelf en ik moest een paar plugins verwijderen om te upgraden, die standaard waren. (bedankt voor de naadloze ervaring met het behouden van onze emoji’s). Ik ben blij dat iedereen die niet weet hoe plugins toe te voegen nu de volledige ervaring krijgt. Ik heb de AI-ervaring gisteren ingesteld en het is goed.
I think we can do something here. It is somewhat tricky cause we need to hoist out content and then re-insert it into the post.
I certainly consider this a bug, will put a pr-welcome on this for now, I may get to it, but it is a bit tricky. The server side needs to partially parse the markdown, remove the quotes, give to proofreader and then add them back in, this may end up resulting in the proofreader getting an incoherent thing to proof read.
Tricky problem.
Is proofreading quotes actually a real issue
After all, the error should have been fixed by the quoted user in the first place. Anyway, as long as the AI doesn’t change the context itself — and it does/did make such changes sometimes.
I almost hate to say this out loud, but worrying about changes per se sounds almost like code-based behavior where the most horrible thing that can happen is if x=y changes to x=1 even when the latter one is true too ![]()
But sure. If a quote can stay untouched, just like a code block should be left alone, that would be nice or even great. But is it such a big thing that anybody should use a lot of paid hours to fix it?
Another sure. That is just my opinion and I know there are situations where a quote should be a 1:1 copy.



