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…
> 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 seconds to format this yourself. Unfortunately copyright law is not going to be happy with that one. [0] It's insanely complicated, but basically, as things are at the moment, the original poster has a right to retract the publication at any time. You may find yourself in…
Twitter is using its embedded JavaScript to hide tweets that have been deleted
101–110 of 254 posts
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#102Just screenshot them instead of embedding them. If you cared about JS injection why would you embed anything?!
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#103It'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 sayin…
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#104It'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 sayin…
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#105Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#106I can see the publishers unhappy and actively obstructing such a solution though.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#107Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#108Just screenshot them instead of embedding them. If you cared about JS injection why would you embed anything?!
How are you supposed to prove the tweet actually happened if you just post a screenshot? It's trivial to forge a screenshot of a tweet to say whatever you want.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#109Just screenshot them instead of embedding them. If you cared about JS injection why would you embed anything?!
How are you supposed to prove the tweet actually happened if you just post a screenshot? It's trivial to forge a screenshot of a tweet to say whatever you want.
Re: Twitter is using its embedded JavaScript to hide tweets that have been deleted
#110Why 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.
- copy paste the content of the tweet - meta data is lost (date and time, author, obv it is possible to copy paste the text and add links to original tweet and link to an author; - screenshot - now you dont have to add custom styles, meta data exists, but it is not usable - you can make is to click on tweet will open a tweet, but click on tweet author will open authors profile. Also screenreaders and bots - they dont…
If not, that is a huge opportunity.