Live data from Hacker News

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

kevinmarks.com

91–100 of 254 posts

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

#91
* its embedded javascript

(it is correct on the site itself)

> That widgets.js script looks for blockquotes with the class="twitter-tweet" on, and replaces them with a Twitter branded iframe to confirm that it is a real tweet

And that's how most libraries work? I don't see an issue. Yes, if you delete the tweet it seems they changed the behaviour (and that might be an actual bug) but still...

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

#92

I've never understood why people even wanted to use this. For the styling? So you can just copy some random stuff from Twitter and it looks like Twitter but is also interactive? Just with the Facebook like-Button, you're exposing your visitors to the tracking of Twitter. For what? Just so you can quickly copy one snippet and be done with it, instead of manually copying author name, content and link and spending 10 se…

It is for a good reason. The original content of the tweet is preserved and not editorialized. Also Twitter has explicit rules around the display of tweets

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

#93

I've never understood why people even wanted to use this. For the styling? So you can just copy some random stuff from Twitter and it looks like Twitter but is also interactive? Just with the Facebook like-Button, you're exposing your visitors to the tracking of Twitter. For what? Just so you can quickly copy one snippet and be done with it, instead of manually copying author name, content and link and spending 10 se…

One advantage I've seen people recently point out about using content transclusions in general (where the Twitter widget is an example of such), is that these provide some level of evidence that the transcluded content is really something that exists at the source. Screenshots and other "fetch and burn into the reciever" approaches can be fabricated very easily to create fake news; but it's a bit more of a technical challenge to fabricate a widget such that it appears to be pulling material from a source — especially if there's also a canonical deep-link back to said source embedded in it.

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

#94
> Tampering with the public record

Oh come off it already. What a remarkably brain dead opinion.

Twitter _is not a public utility_. It owes you _nothing_. Their property, their decision. That simple.

I do have an issue with the idea of their JS manipulating your own website but fuck off with this "Twitter is a public service" argument.

- They don't have to give you an account

- You are not entitled to make demands of them

- You can always use another service

Goddamned children. Enough already.

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

#95

Well, any third-party script that you embed on your website can edit your site and do many other nefarious things (key logging, credential stealing, ...). I never got how people can just copy/paste some random JS into their own websites (often without even using integrity tags). Social embeds in particular have turned the web into a surveillance machine for large corporations, as every FB/Twitter/Instagram/... embed…

We used to have this concept in software engineering, called "coupling". Dependency or independence of each module greatly determines the quality and reliability of the overall system. Generally, too much coupling is bad. But you can also use inappropriate coupling, where even a little is bad. This is an example of inappropriate "external control coupling" (where js code is being chenged remotely - am I wrong?) arising where light data coupling (where data only is pulled in) is required.

The "web" has been going to hell in this way for a decade at least, because it ceased to have boundaries. Without boundaries there cannot be responsibility. Widespread introduction of JavaScript created a quite different kind of technology from the WWW in which concepts of client-browser and document-server made any sense.

Minus any reliability/security it can't be considered safe for delivery of important materials now. If even the site owner can't trust what you see on a site that's bad (though as people point out, we've had this even since banner ads) But it's why I think the future of critical "information services" (as opposed to e-commerce / social media) is on something like Gemini.

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

#96
It's a shame there's no better way to preserve a tweet than taking a screenshot -- there's no way to prove that an individual said something, save for perhaps trusting the record on archive.org

It doesn't have to be this way. Either the individual or the platform could cryptographically sign content to prove that it really happened. I guess Twitter would prefer a plausible deniability. If anyone screenshots you saying something you regret, you can just say it was forged.

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

#97
post #71

I've never understood why people even wanted to use this. For the styling? So you can just copy some random stuff from Twitter and it looks like Twitter but is also interactive? Just with the Facebook like-Button, you're exposing your visitors to the tracking of Twitter. For what? Just so you can quickly copy one snippet and be done with it, instead of manually copying author name, content and link and spending 10 se…

I mean it's fairly easy to understand why people used this. It's very convenient (just click share or use a WordPress widget to embed tweet), it always look pretty, and there are multiple actions available from the tweet: go to profile, reply, share ... So more features for less time to set-up. This is a service like all other Service, you usually tradeoff something like privacy for convenience. Why use Dropbox when…

> you usually tradeoff something like privacy for convenience

You trade GDPR-complience for convenience and all the Functions gained are not that hard to replicate..

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

#98
post #33

Why not just copy paste or screenshot the Tweet? It's bizarre to reference a script from twitter.com directly in your site's source code and then complain that the script is doing exactly what it is supposed to.

Because if it's just a screenshot or your own copy/paste, I have no reason to believe it's real. The only hint of authenticity is that it's served from twitter.com. The fact that there's no way to prove a tweet even happened after it was deleted or account banned seems like a problem to me.

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

#99
post #33

Why not just copy paste or screenshot the Tweet? It's bizarre to reference a script from twitter.com directly in your site's source code and then complain that the script is doing exactly what it is supposed to.

The problem here is that you are erasing history. Imagine someone going into the town square and yelling something profane. That can never be unheard, people will never forget. There will be record of it. Twitter is the only authority that can validate that a tweet actually happened. All other archival services can be considered questionable and easily manipulated (albeit unlikely).

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

#100

Omg... the thing about cited deleted tweets becomin a white glob, gives me some vibes of 1984's "rewriting history".

Twitter is already a bone fide Memory Hole. When an account is banned, there is no proof that any of it ever happened.
Post reply on HN