# Forum bug: "Reply" on nested citations leads to corruption of nested `> ` marks.

_Off-topic · started by dreieck on Thu, May 28, 2026 9:55 PM_

---

## Original post

**dreieck** · Thu, May 28, 2026 9:55 PM

Ahoj,

I think I discovered an issue with (the web based version at least) the forum:

When I hit "Reply" on a post which already has citations, the second-level `>` get replaced by `&gt`, and third level `>` get replaced by `>` -- and `>` definitely will be mis-rendered.

See for example in [this thread](/forum/general/anyone-running-an-rf-only-reticulum-mesh-with-20-rnodes) the message from @dreieck from 2026-05-28, which was generated by hitting the "Reply" button on the message above and filling my content there.

Precisely:

Message I want to cite:

```markdown
**welo** wrote:
> **Rob** wrote:
> > I was excited about the routing ability, but the more i dig into it, the more difficult it is
> May you expand on exactly what the difficulty is?

so I have a lab setup of nodeA and nodeB and "T" transport node. both A&B are connected to RNS and can communicate with each other. when I introduce T and the links are not symmetrical eg. A->T->B and the return path is B->A messages stall. If the return path is the same as the forward path it works. I read the logic where Mark mentions the announce as a indicator of the best path and load balancing, but It seems something is not working for me. so if A and B are totally isolated and T is in the middle everything works.
```

When I hit the reply on that message, I get:

```markdown
**Rob** wrote:
> **welo** wrote:
> > **Rob** wrote:
> > > I was excited about the routing ability, but the more i dig into it, the more difficult it is
> > 
> > May you expand on exactly what the difficulty is?
> > 
> > 
> > 
> > 
> so I have a lab setup of nodeA and nodeB and "T" transport node.  both A&B are connected to RNS and can communicate with each other.  when I introduce T and the links are not symmetrical eg. A->T->B and the return path is B->A messages stall. If the return path is the same as the forward path it works.  I read the logic where Mark mentions the announce as a indicator of the best path and load balancing, but It seems something is not working for me. so if A and B are totally isolated and T is in the middle everything works. 
> 
```

Regards!

---