Last active
March 8, 2016 00:27
-
-
Save nothings/69806d918a62903e2d3b to your computer and use it in GitHub Desktop.
Twitter Link Etiquette
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Twitter Link Etiquette (IMO): | |
| 1. Give some indication of what's behind the link (e.g. what | |
| it's about), so people don't click through to the same | |
| article multiple times (especially important if the URL is | |
| being shortened and they can't even tell it's the same | |
| oddball site they've already visited twice today). Don't just | |
| post "Awesome" and a link; different people follow you for | |
| different reasons and some of them don't care about Ancient | |
| Greek, Rare Violins, or Deep Space Anomolies, and it doesn't | |
| take much for you to instead write "Awesome rare violin!" | |
| 2. Do not report old news as new news. Feel free to report old | |
| news because people might have missed it, but annotate that | |
| it's old. Typically this is stuff that's months or years old, | |
| but even a week-old event might not really be news if it's | |
| been covered elsewhere, so you still might want to call | |
| attention to it being a week old. Don't write in headline-ese | |
| with everything present tense if it happened months or years ago. | |
| 3. Avoid click-bait links; if posing a question, or a mystery, | |
| give the answer too. Your goal should be to help people decide | |
| what they want to read, not to try to drive maximal traffic | |
| to your link. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment