٥اتعتاقر٧و
Twitter is using its embedded JavaScript to hide tweets that have been deleted
181–190 of 254 posts
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#182Earlier quoted context omitted.
> Twitter is under no obligation to retain this kind of stuff on your behalf. You have badly missed the most crucial message of the post. When you copy the embed link, you are copying the string literal of the tweet too. You put this text on your site. You are the one retaining it. The twitter module is hiding the text from the rendered page, rather than loading the local copy.
Yes and it's tricky because in one side you're siding with the person that copied it, and in another, with the original author of the tweet.
I don't know why you are (half) working off the presumption anyone cares about the post-hoc desire of the author.
This isn't tricky at all imo.
Just as if I pasted the text directly, I expect my copying of the content to have the same lifetime as the page I put it on. This is irrespective of anybody's wishes after the fact.
Nobody has the expectation that the text would disappear from my page if copied directly - so why should behavior change in any other case?
The original author of the tweet also has the intent. An unfortunate side effect of having a voice, is that sometimes people will listen and make notes.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#183Earlier quoted context omitted.
Yes and it's tricky because in one side you're siding with the person that copied it, and in another, with the original author of the tweet.
>with the original author of the tweet. Not necessarily. The example VOX article[1] had Trump's tweets embedded in the article, which are now hidden. Trump didn't delete those tweets. He was banned. [1] https://www.vox.com/policy-and-politics/2018/4/13/17233422/d...
There are many more cases of deletions than banned ones, let's not think of the exception as the rule
And the blog author still has the text as well
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#184Earlier quoted context omitted.
I disagree. Twitter doesn't own that content. Someone posting the Twitter JS on their website to allow Twitter to format the tweet to Twitter's brand standards and allow a link to drive traffic back to Twitter is a favour that they're doing Twitter. They should respect that favour by not changing the contract unilaterally.
Unfortunately, it doesn't really matter if you disagree. They own the platform, and they can operate it how they please. There's no "changing of the contract" here. Their TOS certainly don't guarantee anything at all in exchange for website owners embedding tweets in this way. Any theoretical moral argument is kind of irrelevant.
You, and many in these comments, seem to be conflating twitter’s legal rights with their informal social obligations. No one is saying this is illegal behavior by Twitter. Some are saying it’s very annoying of them to go back on their established policies and break thousands of websites.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#185Earlier quoted context omitted.
An email provider (which you most likely pay for - and don't publish on a website) is very different to a social media site (that you don't pay for and want it out in the public) It's a free service that they provide - why can they not change how their system works when they want? People can object whenever they want - but it doesn't change the fact that they don't have any 'rights' to show someone elses content via…
If I embed your JavaScript on my page I am giving you a HUGE amount of my trust. You should treat that as sacred.
But why would you trust a corporation that owes you nothing?
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#186You 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'm not trying to say that this is right or wrong Why are you not, though? I feel like we have been so co-opted by the system that we forgot we are allowed to criticize it. A giant company with billions of dollars should not be given get out of moral jail free cards. They should absolutely be held to higher standards because of all the power they wield.
I feel like two groups are talking over each other.
One is saying Twitter shouldn’t have done this and should be called out for breaking a promise.
The other group mostly agrees, but is pointing out that problem was giving Twitter so much control over one’s own content in the first place.
I agree with this: Banking on what’s nothing more than a handshake is a bad call.
Having to go to the court of public opinion is largely a failure, not the recourse of choice.
The commercial internet of today works this way, and it’s increasingly becoming fragile for it.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#187I am not particularly upset by this. You choose to embed JavaScript that interoperates with your website to make tweets look like Twitter … Twitter has decided that deleted tweets look like nothing now … that’s what you wanted. Apparently the “contract” that Twitter would preserve the text of a deleted tweet was a tweet from some random employee.
And the documentation for the embed api on their website https://developer.twitter.com/en/docs/twitter-for-websites/e...
Thanks, that is something I can get disappointed at.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#188So twitter is distributing malware now?
Malware is defined by Wikipedia as:
> Malware (a portmanteau for malicious software) is any software intentionally designed to cause disruption to a computer, server, client, or computer network, leak private information, gain unauthorized access to information or systems, deprive users access to information or which unknowingly interferes with the user's computer security and privacy.
This script distributed by twitter is software intentionally designed to cause a disruption to a server and to deprive users access to information.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#189You 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…
It is entertaining to watch the waves of opinion crash against each other when things happen that people don't like. The cognitive dissonance must must a deafening roar. On one hand, people get miffed when twitter changes their JS to block out quotes of deleted tweets, citing an alteration of the public record. On the other hand, people argue that twitter is not a "public square" and can do what they want with the co…
It's almost like there's a diverse range of opinions and there isn't a monolithic Hackernews.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#190I see so many people here arguing that by embedding javascript directly from Twitter, you are accepting whatever they choose to make that javascript do. While that is true to an extent, Twitter has provided documentation for this javascript that says that if the Tweet gets deleted, the javascript will simply stop styling your quote of the tweet that you have on your website.
By changing the behavior of the javascript, without even updating the documentation, Twitter has broken every rule of being a good distributor of third-party code. In a similar vein, any third party code could at any time do any number of malicious things. Just because I didn't pay Twitter for the privilege of running their code and just because I embedded their code in my website does not make it okay for them to start distributing malware to modify my website to their liking.
There are lots of other malicious things Twitter could have the javascript do. Twitter could start showing ads before and after all quoted tweets. This would also conflict with the documentation and would be malicious.