Post body with full uppercase and images

AI-generated summary

Post body with full uppercase and images discussion revolves around a loophole in the uppercase check. marianord discovered that posts with all caps text and images don’t trigger any issue with this check. sam explains that the image in the post causes a bypass and suggests that a partial fix is not ideal.

To resolve this, sam proposes a test on Raw -> Cooked -> converted back to text without images, but acknowledges it would add cost to the pipeline. codinghorror considers this case too rare to warrant significant engineering work, pointing out that other bypass methods exist.

tophee suggests an alternative solution, triggering the setting at 90% uppercase instead. marianord likes this idea and proposes using a regex to exclude common use cases like emojis, links, and images from the parsing.

I’ve seeing and issue where posts with all caps text and images, doesn’t trigger any issue with the uppercase check.

Here is the setting unchecked (as expected)

image

And here’s the post:

The link if you want to see it live is: Puntas de tripoides y copas - Club Corsa CCV

2 Likes

Tricky, this is related to the image in the post, it causes a bypass.

We can not really have a partially working site setting though :slight_smile:

@codinghorror how much do you want this fixed ?

The problem is that we need to do this particular test on Raw -> Cooked -> converted back to text without images. This adds definite cost into the pipeline.

1 Like

I don’t feel this rare case is worth doing a lot of extra engineering work for. There are lots of ways to bypass. Putting   in your post would work too, for example.

3 Likes

Just an idea: maybe another way of dealing with with this would be to make the setting trigger at 90 percent uppercase or so?

I really like this idea.

I was thinking maybe in a regex, to avoid taking into account [ * ]( * ) something like that. So the most common use cases, without trying to really bypass the limitation like emojis, links, images, are excluded from the parsing.