New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Twitter blocks links from jsfiddle.net #1417
Comments
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 tweets that included links to the rogue fiddles. Twitter just went the easy route and blocked all jsfiddle.net links instead of blocking spammer accounts on their platform. Tried to contact Twitter many many times, with no reply whatsoever. They most likely have no-explanation-needed-policy, which is why they never replied. There's nothing that can be done here unless somebody has contact to a higher op at Twitter who has the decision power to help out here. |
By wallet code you mean a crypto mining script yes? |
I think I saw some variant of this. It's one of those "send some ETH and receive 2x more back!" With fake "live" transaction listing and fake testimonials. Edit: if memory serves me correct, the transactions being listed are actually not fake, though the live aspect is. Same transaction always reappear as if they're new if you refresh, and those transactions is the 2x amount that got send back. It's all just the scammers trying to make the site look legit. |
@tomglynch No, I mean a wallet code, pretty much as @applefreak explained. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is starting to become a complain thread, please keep it on topic. |
I preface what i'm about to say with Twitter sux...but why should twitter help your organization find a problem originating in your systems? Seems like YOU guys tried to take the easy way out, not them. Find a better way to validate the issue, plug the hole, and reach out to twitter. If they don't unblock your sharing urls, change them to a new url and reverse proxy the other url or something -- don't blame a social network for making a PERFECTLY ethical decision. |
They did those things. Quoting @oskarkrawczyk's above post:
What more do you think should be done? |
This comment has been minimized.
This comment has been minimized.
@zalun managed to get in touch with someone from Twitter and get us unblocked 🎉 |
Twitter is rejecting posts with JSFiddle URL inside.
If a URL shortener is used the unsafe page warning is displayed[1]
What is causing that?[2]
[1]
[2] We've tried to contact Twitter, but no answer.
The text was updated successfully, but these errors were encountered: