The reason you should not link directly is because the embedded tweet loads tracker elements into the browser of anyone who opens it. Very similar to what happens with Facebook Like Buttons. This means that they then have insight into who specifically is viewing the post even if it’s the embedded version (because the video loads from their servers).
Screenshots are another way to avoid this for text and image posts on Twitter and other social media. You can also download videos from tweets using this:
Then you can repost to any of these locations with a link in the description back to the source tweet (this does not leak info to Twitter and gives people the choice to visit the source):
Thank for throwing down the nitter link!
~
For everyone else’s benefit:
The reason you should not link directly is because the embedded tweet loads tracker elements into the browser of anyone who opens it. Very similar to what happens with Facebook Like Buttons. This means that they then have insight into who specifically is viewing the post even if it’s the embedded version (because the video loads from their servers).
Screenshots are another way to avoid this for text and image posts on Twitter and other social media. You can also download videos from tweets using this:
Then you can repost to any of these locations with a link in the description back to the source tweet (this does not leak info to Twitter and gives people the choice to visit the source):
Video Hosting
Or even upload to a distributed service like IPFS or Siasky that is way more difficult to censor (plus you maintain your local copy).
Yep, we help them censor things by showing them exactly what we're watching and sharing.