Add warnings to edited links (prevent viruses, potential scams or hackers) [Serious]

[Ilay A]

I want you to click on this link https://www.google.com

a google link right?
nope, that's an imgur picture, could have been a scam, keylogger or even a scary virus!

my point is, you can't really tell if there's a mimic link that had been edited with a virus, affiliate link or a keylogger pasted onto a legit website link.

So my suggestion is, whenever a URL is edited, there should be a warning displayed right near the hyperlinked text that says in brackets "(this link had been edited)". that warns you that it was indeed edited to something else. and also a pop-up that displays a "that's the original link, are you sure that you want to continue?" warning right before entering the edited link

 

[Ilay A]

I’m thinking of a BbCode parser that checks if there’s a link between the url tags and if there is and it doesn’t match with the actual url, it would make a pop up with a redirect confirmation.

Could also make it pop up for anything that doesn’t match the actual link, but I’d opt to have that off by default.

Sounds good!

But you might have to add it with hyperlinked images, let's say a thread design portfolio bait that actually links to a grabify. can be really dangerous so matching 2 links together alone might not be enough

 

[Ilay A]

Ehhh, well maybe we should edit out some stuff, like yeah edited links are a problem, but I need more opinions on how to solve it, the solution should be very simple and less annoying

 

[Kieraaaan]

No one cares, if you get redirected to a bad link ... guess what? all browsers let you click the little x icon !

If you have 0.1Mbit/s internet then you might have time to press that, otherwise it will be a bit too late won’t it.

 

[Sloth]

MCM hasn't has gone without this for years and guess what.... it's fine.

Huh you’ve been here since Friday

 

[Mick]

I've been staff on the forum for several years, and have never before seen an instance of when this has been abused in the past, and it simply isn't an issue that we're experiencing so I can't justify the custom development time that would go into this.

Denied, thanks for the suggestion.