@baris sure thing!

See it here

Review from Claude.AI

Look at these two lines in your post.tpl:

Line 14:  {{buildAvatar(posts.user, "48px", true, "", "user/picture")}}
          — rendered BEFORE the author scope opens (still inside the outer
            <li> from data/topic.tpl)

Line 19:  <div>

Line 27:  {{buildAvatar(posts.user, "20px", true, "", "user/picture")}}
          — rendered INSIDE that author/Person scope (it's the mobile-only
            duplicate avatar, class "d-sm-none")

Both calls render the exact same thing — posts.user's picture. NodeBB's avatar markup has historically stamped itemprop="image" directly onto the <img /> it generates (you can see this explicitly in older NodeBB themes, e.g. <img src="{posts.user.picture}" />), and buildAvatar() almost certainly carries that forward. That means:

Line 14's avatar sits outside the Person scope → its itemprop="image" attaches to the enclosing Comment scope → becomes comment.image
Line 27's avatar sits inside the Person scope → its itemprop="image" attaches there → becomes author.image

Same picture, same URL, two scopes → exactly the "should not have the same value" complaint.
```</div></li>