[email_protected] instead of CLI prompt; Cloudflare interference?

crts · 05-01-2019, 12:49 PM

Lately, when someone posts some code inside code-tags the prompt gets changed to [email_protected].

Code:

user@machine$ some commands

It should say "user_at_machine" but with "@" instead of "_at_".
Am I the only one who is seeing this?

jeremy · 05-01-2019, 01:35 PM

We're evaluating a couple privacy/security features. We don't want them to be intrusive, but is there a case you'd consider exposing a real email address publicly in the context of LQ to be desirable?

--jeremy

hydrurga · 05-01-2019, 01:53 PM

Quote:

Originally Posted by jeremy

We're evaluating a couple privacy/security features. We don't want them to be intrusive, but is there a case you'd consider exposing a real email address publicly in the context of LQ to be desirable?

--jeremy

I'd say no. Better to blanket ban (including use in usernames) in order to prevent posters including their email for personal contact which occasionally happens, as well as including email addresses without the owner's permission. If an email address is public then you can always provide a link to a web page where that address is listed. My tuppence worth anyway.

astrogeek · 05-01-2019, 02:07 PM

I'd agree there is no usecase for email addresses in public LQ posts and support masking them.

However, I would be interested in knowing whether the masking is done on the LQ platform, such as by data insert/select filtering, or whether it is being done by an upstream process modifying content as suggested by the OP's question.

crts · 05-02-2019, 04:59 AM

I am not advocating to expose email addresses. I am attaching a screenshot of what I was seeing before and shortly after I made the post. As you can see, the Bash prompt inside the code box was erroneously (?) blanked. If this was intended, well, I think it is quite distracting, not sure how others feel about it. If the intention is to also blank out user and machine names then I would prefer to change it to something generic inside the code box, e.g., "user_at_machine".

jeremy · 05-02-2019, 08:25 AM

To be clear, only email addresses should be impacted. Let me take a closer look at the implementation, but for example:

"user@example" should never be impacted
"user@example.com" should

We've completely disabled while I look into it further. Thanks for the feedback.

--jeremy