News for hackers. Stuff that matters.
Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @05:13AM (#20122883)
What I find strange how this is presented as an either-or option between banning and not banning. You can also have an intermediate warning page. YouTube does this to any third-party website for example. Something like "Warning: JSFiddle has been abused by spammers to run crypto mining scripts. We recommend that you that you do not continue to this JSFiddle page unless you trust the source of the link" should work just fine, no?
Re:Twitter is rejecting posts containing JSFiddle URLs by skrebbel on Friday June 07, 2019 @06:02AM (#20123095)
Twitter doesn't exactly target the kind of demographic that understands what "to run crypto mining scripts" even means, let alone how to assess whether they "trust the source". I mean, it was retweeted by someone I follow and it has a funny picture of Trump with a dancing turd emoji on his head, what's there not to trust?

It's extremely hard to coach non-technical users into making the right call when presented with a security warning box.

That said, if Twitter can assess whether a posted video contains "sensitive material" (i.e. exposed body parts), they can also assess whether a jsfiddle link (or any link, really) likely contains crypto miners.

Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @06:25AM (#20123167)
> It's extremely hard to coach non-technical users into making the right call when presented with a security warning box.

And not presenting them with any call at all is guaranteed to keep them non-technical. We have to take the training wheels off at some point.

Re:Twitter is rejecting posts containing JSFiddle URLs by themacguffinman on Friday June 07, 2019 @12:42PM (#20126409)
And it's Twitter's job to train them?
Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @01:29PM (#20126832)
It's not about whether it's Twitter's job to "train" them, a warning page before continuing a link is hardly that.

It's about whether they should trust their users and believe that the latter can take responsibility for their own choices, and figure these things out themselves.

Re:Twitter is rejecting posts containing JSFiddle URLs by themacguffinman on Friday June 07, 2019 @02:27PM (#20127337)
> It's about whether they should trust their users and believe that the latter can take responsibility for their own choices, and figure these things out themselves.

You're just begging the question. Why should they do that?

Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @04:52PM (#20128509)
Not really, this is turning into the equivalent of a six year old replying with "why?" to every answer, except you're adults pretending to be oblivious.
Re:Twitter is rejecting posts containing JSFiddle URLs by themacguffinman on Friday June 07, 2019 @05:44PM (#20128908)
You're free not to reply, but I'm not sure why you're calling me childish to ask for an actual reason you think it makes sense for Twitter to do all these things you're asking them to do.

Enlighten me. I could assume the worst of your intentions as you've done, but I'm honestly interested in why you think it makes sense for Twitter to "trust their users" to "take responsibility for their own choices".

Re:Twitter is rejecting posts containing JSFiddle URLs by userbinator on Friday June 07, 2019 @07:51AM (#20123579)
The companies don't want that, because they are afraid of losing control over their "users" as the latter become more technologically literate and realise there are better alternatives.

You can already see some of this in things like DRM and adblocking, and of course the various walled gardens.

Mainstream software is all about keeping users blissfully ignorant and consuming.

Re:Twitter is rejecting posts containing JSFiddle URLs by jmull on Friday June 07, 2019 @09:49AM (#20124423)
There's a UX problem with this:

You're making the user answer a question they (generally) don't know the answer to and don't want to answer anyway.

Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @09:54AM (#20124478)
I do agree that there is a UX problem and that it matters a lot how this is presented, bu I'm not sure if I agree that it's a real problem here. The question is basically "do you know if you can trust this source?", which means it should "round down" to no.
Re:Twitter is rejecting posts containing JSFiddle URLs by stordoff on Friday June 07, 2019 @05:11PM (#20128653)
Steam does this:

> Notice:

> You are leaving Steam.

> Never enter your Steam password on an untrusted website. Any login form on an official Steam site will display "Valve Corp." in green with a padlock icon in your browser’s address bar, as shown below:

https://steamcommunity.com/linkfilter/?url=https://anyURL

For anything that looks malicious ("https://anyURL<h1>"):

> Link Blocked!

> This link has been flagged as potentially malicious.

> https://anyURL%3Ch1%3E has been flagged as being potentially malicious. For your safety, Steam will not open this URL in your web browser. The site could contain malicious content or be known for stealing user credentials.

> Never enter your Steam password on an untrusted website. Any login form on an official Steam site will display "Valve Corp." in green with a padlock icon in your browser’s address bar, as shown below:

https://steamcommunity.com/linkfilter/?url=https://anyURL%3C...

Re:Twitter is rejecting posts containing JSFiddle URLs by jrockway on Friday June 07, 2019 @05:36PM (#20128846)
This isn't even true anymore, though. Chrome doesn't display TLS as green, and I believe EV certs are on the way out. (Because anyone can register a company called "Valve Corp." and be issued an EV certificate.)
Re:Twitter is rejecting posts containing JSFiddle URLs by scifi6546 on Monday June 10, 2019 @08:22PM (#20152128)
This is inside of steam's browser
Re:Twitter is rejecting posts containing JSFiddle URLs by thinkingemote on Friday June 07, 2019 @10:35AM (#20124924)
They could use the same warning for fake news websites or for anything they deem worth warning or are ordered to. Could be interesting at least.
Re:Twitter is rejecting posts containing JSFiddle URLs by luu on Friday June 07, 2019 @05:16AM (#20122897)
[Edit: whoops, misread the issue. Sorry!]
Re:Twitter is rejecting posts containing JSFiddle URLs by vanderZwan on Friday June 07, 2019 @05:48AM (#20123033)
Thanks for clarifying that you misread, but please keep the text or at least enough contextual information so we know what the replies to you are talking about. Which link did you edit out? Because I missed it.
Re:Twitter is rejecting posts containing JSFiddle URLs by bestnameever on Friday June 07, 2019 @05:31AM (#20122955)
Per the text, the screenshot you are seeing is what happens when someone links to a jsfiddle using a url shortner but posts linking directly to jsfiddle are rejected.

>Twitter is rejecting posts with JSFiddle URL inside.

>If a URL shortener is used the unsafe page warning is displayed[1]

Re:Twitter is rejecting posts containing JSFiddle URLs by danmur on Friday June 07, 2019 @05:31AM (#20122957)
I think that screenshot was from a link posted with a URL shortener. Weird that it makes a difference.