I've got this:

in this reply, at both YouTube links.
Is there a per user way to disable this?
Thanks.
Moderators: Lootyhoof, FranklinDM


I asked this because I thought some more progression has been done to this, but now I understand I'm wrong.Matt A Tobin wrote:This kind of inattention to the forums and threads is what creates so much extra work on our or other user's end that could be expended in more productive ways.

Code: Select all
http://outbound.palemoon.org/example.org/

Code: Select all
https://greasyfork.org/en/scripts/22256-unsurlyThat's a relief.If sur.ly for whatever reason goes down or has an issue, links will be direct after disabling it. The original links are at all times stored in the forum database.
Okay, but will this actually happen? I think I already made my point that sur.ly is a problem by design.It takes exactly 1 operation in the forum to disable it if it is a problem for any reason whatsoever.
I am aware of this argument. The problem I have here, it is essentially ignoring my privacy and cracker arguments I posted before. You are buying “some” protection by introducing a VERY attractive attack surface. As I said, sur.ly must NEVER EVER be cracked, or else many users will be screwed. So any potential “security” gained by protecting users from direct malware links would instantly be undone if sur.ly gets cracked only once. I argue this is not worth the risk and goes directly against the idea of what sur.ly is supposed to achieve.Apart from reducing the risk of having direct malware links AND making the forum less attractive for SEO spammers (that require direct links to target domains to be useful), sur.ly offers you an indicator of the trust level of the external site from several sources and a quick way to go back to the forum. That is added value. Some protection, even if it isn't the one you'd personally choose, is better than no protection.
In the very unlikely event this happens, it'd be only for as long as none of the generally observant users of this forum notices. As I said (once again), it takes 1 operation to disable this if needed for whatever reason.Wuzzy wrote:As I said, sur.ly must NEVER EVER be cracked, or else many users will be screwed.
There is no such thing. You are always going to rely on a third party for this kind of thing one way or another.Wuzzy wrote:are you maybe aware of any alternatives which don't rely on a 3rd party redirect?

It goes the other way, too: If sur.ly breaks, most links in this forum will be “infected”. An attacker only needs to attack 1 site for a large impact. But with “raw” links, an attacker would need to “infect” ALL these links to achieve the same effect. So it isn't that easy, after all.Moonchild wrote:What you argue is that placing trust in any 3rd party is faulty by design. I think you need to re-evaluate how you view the current web. For argument's sake, consider this statement: I'd rather place my trust in 1 3rd party that I have some measure of control over, than all parties involved in raw links (both users and externally-linked sites). I'm aware of the "worst case" scenario - it's why I audit these kinds of services before I consider them.
Read again: I wrote “3rd party redirect”. Yes, you obviously have to depend on 3rd parties to get the data about website security ratings. But fetching this data could be done in the background (server-side), while the actual “intermediate” site is hosted on forum.palemoon.org, generated from the data acquired in the background. So it is perfectly possible to have some sort of link checking without exposing users to any “intermediate” pages hosted by 3rd parties, therefore avoiding the introduction of an additional attack surface.There is no such thing. You are always going to rely on a third party for this kind of thing one way or another.Wuzzy wrote:are you maybe aware of any alternatives which don't rely on a 3rd party redirect?
