Live data from Hacker News

Twitter is rejecting posts containing JSFiddle URLs

github.com

161–170 of 208 posts

Re: Twitter is rejecting posts containing JSFiddle URLs

#161

Earlier quoted context omitted.

> 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.

And it's Twitter's job to train them?

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

#162
post #125

Earlier quoted context omitted.

I think the math would then lead to only big sites being "good enough" to pass the twitter test as to who gets a whole domain filtered or not, and if you're running a site that someone does a bad thing on ... so much for anyone linking to you anymore on Twitter. That seems inherently bad.

That’s not entirely my point. The whole point of JSFiddle (which I love) is at odds with the bulk of the demographic of Twitter. If your content sharing site inadvertently has malware you can remove it, JSFiddle will always be risky. The bulk of the people I follow on Twitter would have no clue what it was or how to even begin to understand it.

>The whole point of JSFiddle (which I love) is at odds with the bulk of the demographic of Twitter.

I'm not sure that's a line that Twitter would draw, or is even accurate.

I also suspect that most content on twitter the bulk of twitter users / demographics wouldn't care about...

Re: Twitter is rejecting posts containing JSFiddle URLs

#163

At what point is the tech community going to abandon twitter? From my perspective it is just bots, "influencers", and propaganda. I see very little social utility for using the network, especially when compared to the damage it is causing through the spread of misinformation and outright lies.

I think you're preaching to the wrong platform here. HN is one of few corporate tech forums out there and twitter is a very corporate medium.

Whole twitter culture honestly is quite saddening and it's leaking to alternative mediums as well (like mastodon.social has started to suffer from same problems).

We worked so hard to create easy and accessible way to micro blog and communicate through text via formatting, proper structures with rss feeds etc and twitter just threw all that through the window in favor of short unformated, unsorted and algorithmitized, toxic "chats".

Ugh, I'm excited to finally see it go the way of the dodo.

Re: Twitter is rejecting posts containing JSFiddle URLs

#164
post #82

Earlier quoted context omitted.

I don't understand how posting a "wallet code" is dangerous. Is it mining coins while you are browsing the code? Then it just a minor annoyance. Also, browsers should block cryptominers when they are in the background tab.

I don’t think it’s mining code, I think it’s wallet addresses posted by scammers. Here’s an example of the scam I think this is intended to curb: https://s3.amazonaws.com/aws-website-staticfiles-25g9k/elon_...

I visited that page. I didn't check but I don't think any of my satoshis were stolen. Don't see what's dangerous there.

Re: Twitter is rejecting posts containing JSFiddle URLs

#165

It’s due to crypto scammers using it. From the founder’s post: At some point in the past crypto scammers used JSFiddle to host pages with a wallet code and posted links to that on Twitter. Due to the nature of JSFiddle, anyone can post anything, so wallet codes are ok – we did implemented a content filter to shadow-ban these. I asked Twitter if they they could help out and ban twitter accounts that were posting scam…

On a complete tangent, I think "rogue" might be the most misspelled word for those that otherwise have good spelling. It's still jarring every time I see it, decade after decade. And "loose" instead of "lose", but that one is just confusing.

I see "break" ALL THE TIME where "brake" should be used.

    rouge -> rogue
    loose -> lose
    lose  -> loose
    break -> brake
And many more that I can't recall at the moment... In my youth I spent an absolutely obscene amount of energy correcting these people, bit now I just automatically lower the veracity of what they're saying each time I see some literacy problem.

That isn't fair to those people because not everyone speaks English as a first language, and phones autocorrect a lot of things that should not be corrected.

Re: Twitter is rejecting posts containing JSFiddle URLs

#166
post #132
post #97

Earlier quoted context omitted.

I would wager most of the people dealing in crypto currencies are actually precisely the kind of people that would fall for pretty much anything. I don't think it's a stretch to say that the fact that they deal in crypto currencies is actually a pretty good indication that they would.

I think you're conflating categories. Here's what I think: https://i.imgur.com/d4ocNXa.png That is to say, gullible people are found everywhere but I don't think people inclined to fall for fraud are the same as get-rich-quick tech-heads.

Responding by a Venn diagram, love it.

More to the point - there is a significant number of people who started learning about computer security precisely because they got some cryptocurrencies. And frankly, if someone wants to really understand the details, it's hard to miss all the frequent warnings and examples of scams, hacks, leaks.

Re: Twitter is rejecting posts containing JSFiddle URLs

#167
post #162

Earlier quoted context omitted.

That’s not entirely my point. The whole point of JSFiddle (which I love) is at odds with the bulk of the demographic of Twitter. If your content sharing site inadvertently has malware you can remove it, JSFiddle will always be risky. The bulk of the people I follow on Twitter would have no clue what it was or how to even begin to understand it.

>The whole point of JSFiddle (which I love) is at odds with the bulk of the demographic of Twitter. I'm not sure that's a line that Twitter would draw, or is even accurate. I also suspect that most content on twitter the bulk of twitter users / demographics wouldn't care about...

This is all true, I guess I just come down to supporting twitter’s calculus on this one.

Re: Twitter is rejecting posts containing JSFiddle URLs

#168

A reminder that you don't need to technically link in order to refer to a link, nor even mention the site directly: "See JSviolin xxxxx" If anyone gets confused, simply reply "replace violin with synonym starting with f"... This reminds me of when YouTube banned URLs in comments (I don't think they do anymore), so people started posting pieces of them (like video IDs, the part after watch?v=...) with hints instead: "…

That workaround reminds me of phpBB Forums that blocked URLs, so users would spell them like "hxxp://www..."

Re: Twitter is rejecting posts containing JSFiddle URLs

#169
post #82

Earlier quoted context omitted.

I don’t think it’s mining code, I think it’s wallet addresses posted by scammers. Here’s an example of the scam I think this is intended to curb: https://s3.amazonaws.com/aws-website-staticfiles-25g9k/elon_...

I visited that page. I didn't check but I don't think any of my satoshis were stolen. Don't see what's dangerous there.

The page itself is not the scam. It's a page showing tweets where somebody is scamming people on Twitter, pretending to be Elon Musk giving out ETH.

Re: Twitter is rejecting posts containing JSFiddle URLs

#170

Earlier quoted context omitted.

I just don't agree with this sentiment. I don't work for twitter or any social media company, but it strikes me as their prerogative to ban content deemed unsafe if they don't have the means or wherewithal to properly police the content. From an engineering standpoint, how exactly do you propose to scan fiddles for objectionable content. With an image link, you could throw a neural net at it and at least tag it as ns…

>> From an engineering standpoint, how exactly do you propose to scan fiddles for objectionable content. But if this was about getting people to click more ads, Twitter would be throwing enormous amounts of resources at it. I mean, let's not pretend that this is an engineering problem.

Engineering and cost to me are intricately intertwined, so yes it is an engineering problem. If they could solve it without affecting the bottom line (or even better improving the bottom line), I'm sure they would.
Post reply on HN