Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

66%
+2 −0
Q&A False positive for 30,000 character limit

My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it,...

posted 2y ago by Taeir‭  ·  edited 2y ago by Taeir‭

Answer
#3: Post edited by user avatar Taeir‭ · 2022-10-25T17:28:07Z (about 2 years ago)
  • My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it, and the second is the HTML representation.
  • In HTML, a lot of the lines would get some extra characters, for example a header like `# Test` becomes `<h1>Test</h1>` and a list of items changes too:
  • ```markdown
  • * a
  • * b
  • * c
  • ```
  • changes into
  • ```html
  • <ul>
  • <li>a</li>
  • <li>b</li>
  • <li>c</li>
  • </ul>
  • ```
  • This could explain the count you see being a few thousand characters shorter than what QPixel tells you.
  • That said, I don't think this was taken into account when setting the limit. Perhaps a larger limit would make more sense (or perhaps it should be checked on both). Programmatically, I don't believe there is a specific reason for putting the limit at 30.000, and a bigger limit should potentially be considered (and the limits should differ between the markdown and the html to avoid this issue). The maximum for the way things are currently stored is roughly 65.500 characters, so there is room to up the limit.
  • My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it, and the second is the HTML representation.
  • In HTML, a lot of the lines would get some extra characters, for example a header like `# Test` becomes `<h1>Test</h1>` and a list of items changes too:
  • ```markdown
  • * a
  • * b
  • * c
  • ```
  • changes into
  • ```html
  • <ul>
  • <li>a</li>
  • <li>b</li>
  • <li>c</li>
  • </ul>
  • ```
  • This could explain the count you see being a few thousand characters shorter than what QPixel reports when checking for the limit.
  • That said, I don't think this was taken into account when setting the limit. Perhaps a larger limit would make more sense (or perhaps it should be checked on both). Programmatically, I don't believe there is a specific reason for putting the limit at 30.000, and a bigger limit should potentially be considered (and the limits should differ between the markdown and the html to avoid this issue). The maximum for the way things are currently stored is roughly 65.500 characters, so there is room to up the limit.
#2: Post edited by user avatar Taeir‭ · 2022-10-25T17:26:49Z (about 2 years ago)
  • My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it, and the second is the HTML representation.
  • In HTML, a lot of the lines would get some extra characters, for example a header like `# Test` becomes `<h1>Test</h1>` and a list of items changes too:
  • ```markdown
  • * a
  • * b
  • * c
  • ```
  • changes into
  • ```html
  • <ul>
  • <li>a</li>
  • <li>b</li>
  • <li>c</li>
  • </ul>
  • ```
  • This could explain the count you see being a few thousand characters shorter than what QPixel tells you.
  • That said, I don't think this was taken into account when setting the limit. Perhaps a larger limit would make more sense (or perhaps it should be checked on both). Programmatically, I don't believe there is a specific reason for putting the limit at 30.000, and a bigger limit should potentially be considered. The maximum for the way things are currently stored is roughly 65.500 characters, so there is room to up the limit.
  • My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it, and the second is the HTML representation.
  • In HTML, a lot of the lines would get some extra characters, for example a header like `# Test` becomes `<h1>Test</h1>` and a list of items changes too:
  • ```markdown
  • * a
  • * b
  • * c
  • ```
  • changes into
  • ```html
  • <ul>
  • <li>a</li>
  • <li>b</li>
  • <li>c</li>
  • </ul>
  • ```
  • This could explain the count you see being a few thousand characters shorter than what QPixel tells you.
  • That said, I don't think this was taken into account when setting the limit. Perhaps a larger limit would make more sense (or perhaps it should be checked on both). Programmatically, I don't believe there is a specific reason for putting the limit at 30.000, and a bigger limit should potentially be considered (and the limits should differ between the markdown and the html to avoid this issue). The maximum for the way things are currently stored is roughly 65.500 characters, so there is room to up the limit.
#1: Initial revision by user avatar Taeir‭ · 2022-10-25T17:25:01Z (about 2 years ago)
My best guess would be that the check is performed on the HTML representation of the post. In the database, two representations are stored. The first is the markdown representation as you typed it, and the second is the HTML representation.

In HTML, a lot of the lines would get some extra characters, for example a header like `# Test` becomes `<h1>Test</h1>` and a list of items changes too:
```markdown
* a
* b
* c
```
changes into
```html
<ul>
<li>a</li>
<li>b</li>
<li>c</li>
</ul>
```

This could explain the count you see being a few thousand characters shorter than what QPixel tells you.

That said, I don't think this was taken into account when setting the limit. Perhaps a larger limit would make more sense (or perhaps it should be checked on both). Programmatically, I don't believe there is a specific reason for putting the limit at 30.000, and a bigger limit should potentially be considered. The maximum for the way things are currently stored is roughly 65.500 characters, so there is room to up the limit.