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.

Comments on o@ßX shows up as [email protected]ßX

Parent

o@ßX shows up as [email protected]ßX

+6
−0

On the first comment here, o@ßX was turned into [email protected]ßX.

Email protected

However, when I go to the comment thread, it shows up normally:

Normal text

Oddly enough, I couldn't reproduce this on the dev server. I commented on the thread named "test thread" on this post, and neither I (signed in) nor other people (not signed in) could see the [email protected] link. The comment looks normal both from the question and after going to the thread's page.

History
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

422 - Unprocessable (3 comments)
Testing here because it didn't work on the dev server (1 comment)
Post
+6
−0

This looks like an issue with Cloudflare, which (wrongly) assumes that what you entered is an email. They apparently have an anti-spam-measure, that requires JavaScript to uncover email addresses. Since the JS doesn't run when the preview is created, the message is shown.

An easy fix would be to turn the tool off, as we don't really need it here as far as I can see. I currently don't have access to the computer where I could do that, but I pinged someone who should have, so we should be able to get this fixed quite soon.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Still broken (1 comment)
Still broken
Canina‭ wrote over 2 years ago

This still seems to be an issue.