Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter is using its embedded JavaScript to hide tweets that have been deleted

kevinmarks.com

Post reply on HN
Print view View original

161–170 of 254 posts

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#161

Post by renewiltord »

demarq wrote: post #147

> However, Twitter has broken this API contract. What contract?

The API contract laid out in their documentation. There’s a screenshot in the post right around there.

The API contract is:

> What happens when an author deletes their Tweet? The Twitter widgets JavaScript will not display a fully-rendered Tweet if the Tweet no longer exists on Twitter. The fallback

containing Tweet information will be visible on the page.

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#163

Post by 0des »

tom_ wrote: post #140
simonw wrote: post #135

Earlier quoted context omitted.

"If you want to act as a repository for the public record, you better use your own system." I deliberately chose Twitter's JavaScript because I inspected the design of how it worked and saw that they had deliberately built it in a way that would respect my preferences for how deletion should be handled. They've changed that on me - without even announcing the change. This is a rug-pull. Now I have to replace their co…

Ask for your money back.

I normally hate comments like this but damn I laughed till I died when I read this. Take care tom

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#164

Post by 0des »

jdrc wrote: post #26
WatchDog wrote: post #10

Functionality aside embedding random scripts from twitter seems like a big risk for security and privacy. At a minimum, it should probably be embedded in a sandboxed iframe. Just taking a screenshot, and linking to the tweet, seems like a more robust solution, that won't randomly stop working, and doesn't have the same privacy issues.

There should be an HTML tag or something that downloads and embeds HTML from a remote site without scripting

Guess I'll start on that exploit now, beat the crowd.

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#165

Post by 0des »

saagarjha wrote: post #144
jdrc wrote: post #133

Earlier quoted context omitted.

why would they?

Because you're requesting a resource from them, and they consider that resource to be deleted?

Are you asking or telling, I'm prepared to answer if asking.

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#166

Post by 0des »

TomGullen wrote: post #69
retSava wrote: post #50

Earlier quoted context omitted.

We as human beings should always strive for the better, to improve, to do the best we can within reasonable bounds. It's imo not about pettiness, finding errors of others to shame them, or holding others to a bar set too high, but rather, if we don't, we start tumbling towards lesser good things as a society and community and humans. Not to say that it's not ok do make errors (it is, and it's human), but if we spot o…

Perhaps not so relevant for a misplaced apostrophe, but language is malleable and if we were always using it 100% correctly it would never evolve.

If this is the case, why not speak AAVE or patoix or Esperanto?

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#167

Post by 0des »

dumpsterdiver wrote: post #48
abofh wrote: post #40

Earlier quoted context omitted.

In which case, it's still wrong in the title. Just because people are too lazy to scroll up and read the erroneous title doesn't mean nit picking pedantry makes them correct.

I just scrolled back up to the title and realized that my argument is totally wrong. They weren't trying to say "it is". I was wrong.

Get in the corner!

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#168

Post by causi »

sacrosancty wrote: post #31
tofuahdude wrote: post #16

You don't need to use Twitter's JS to show Tweets. If you choose to use their system, you're subject to their rules. If you don't like their rules, don't use their stuff. Calling it "altering the public record" is a little hyperbolic imo. If you want to act as a repository for the public record, you better use your own system. Twitter is under no obligation to retain this kind of stuff on your behalf. I'm not trying…

I think this is a little unexpected though since "you" are still hosting the text of the tweet on your site and publishing it to your visitors but also with a Twitter script that hides it.

Doesn't that mean it should be pretty easy to automate converting all your "deleted" embedded Tweets to a local rendering, albeit without the integration back to Twitter?

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#169

Post by macspoofing »

tofuahdude wrote: post #16

You don't need to use Twitter's JS to show Tweets. If you choose to use their system, you're subject to their rules. If you don't like their rules, don't use their stuff. Calling it "altering the public record" is a little hyperbolic imo. If you want to act as a repository for the public record, you better use your own system. Twitter is under no obligation to retain this kind of stuff on your behalf. I'm not trying…

There's always a few that posts like this. Yes Twitter has a legal right to do stuff like this but can YOU separate what Twitter is legally allowed to do from what is the right thing to do? What's wrong with criticizing a particular policy from a corporate behemoth?

Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted

#170

Post by cxr »

victorstanciu wrote: post #55
WatchDog wrote: post #10

Functionality aside embedding random scripts from twitter seems like a big risk for security and privacy. At a minimum, it should probably be embedded in a sandboxed iframe. Just taking a screenshot, and linking to the tweet, seems like a more robust solution, that won't randomly stop working, and doesn't have the same privacy issues.

"Functionality aside embedding random scripts from twitter seems like a big risk for security and privacy." When I started blogging again, I wanted to render my Twitter feed on the homepage, as a sort of bitesize alternative to the regular content, but I too have a deep aversion to allowing external scripts on my websites. So I added some code to my Hugo theme that pulls the tweets from my profile via the Twitter API…

This is still "vulnerable", in a way (though not the same kind of vulnerability as embedding third-party scripts): if Twitter disappears—or just stops returning your tweets for some other reason (e.g. they shut down their API or your account)—then you lose access to your content. It can be mitigated by making sure your SSG output is also in version control—not just the input. (While you're at it, it's a good idea to make sure your SSG is version controlled, too. That doesn't have to be a whole copy of the SSG source and/or binary in your repo; it can be e.g. its version string.)

That of course still leaves open the matter of whether/how you're making sure to trigger a new build for every new tweet.

Post reply on HN