# 我的帖子长度包含图片和链接

**URL:** <https://meta.discourse.org/t/min-post-length-includes-images-and-links/116518>\
**Category:** Feature\
**Created:** [2019年五月1日 06:15 UTC](https://meta.discourse.org/t/min-post-length-includes-images-and-links/116518 "2019-05-01T06:15:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)\
**Post date:** [2019年五月1日 06:15 UTC](https://meta.discourse.org/t/min-post-length-includes-images-and-links/116518/1 "2019-05-01T06:15:34Z")

</div>

It seems the `min post length` setting counts **all** the characters in a post, including the markdown for images and links. This leads to quite a few people posting image-only posts without any comment. Bumping the setting to a much higher value is not desirable - it would be great if min post length could avoid all ‘non printing characters’ as they’re not actually contributing to the conversation?

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [2019年五月1日 10:22 UTC](https://meta.discourse.org/t/min-post-length-includes-images-and-links/116518/2 "2019-05-01T10:22:06Z")

</div>

This has been covered many, _many_ times in previous topics. The intent is not to plug every possible unicode space “filler” exploit, just to cover the basic ones.

However it looks lke your goal is a bit different here, you want to prevent image only posts? Why not have a policy and enforce it?

---

<div class="post-metadata">

**Author:** ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)\
**Post date:** [2019年五月1日 11:40 UTC](https://meta.discourse.org/t/min-post-length-includes-images-and-links/116518/5 "2019-05-01T11:40:21Z")

</div>

We’ll do that, thanks!
