Twitter.com is a popular content hosting silo most well known for 140 character text notes.
CC license your tweets
Note, tweetcc's creators decided to take it down in July 2013."
We're looking into having tweetcc restored.
This allows anyone else wanting to:
Etc. your tweets to do so, per that CC license (e.g. CC-BY, attributing you) independent of Twitter's TOS, and thus independent of any Twitter requirements, e.g. their display "guidelines".
Reverse Syndicating At-Replies
Per the POSSE model, you may want to reverse-syndicate @-replies on Twitter to the tweet-copies of your post as "comments" back into your post permalink page on your own site. By using TweetCC, you can check to see if those @-replying to you have CC-licensed their tweets and then incorporate them using the CC license, displaying them however they fit in with your site design, instead of having to shoehorn Twitter's display "guidelines" into your site / post-permalink page design.
Porting to the IndieWeb
Download all your tweets
The Twitter archive is made of per month JSON files. It can be used as a way to PESOS a whole Twitter history, even though POSSE is the recommended way to do it.
The most interesting things in the JSON twitter archive are:
After you download your archive, you can update in using a Ruby Gem called GrailbirdUpdater.
POSSE to Twitter
POSSE to Twitter in general
Given Twitter's limitations:
When POSSEing to Twitter:
Once POSSE is successful:
POSSE Notes to Twitter
For notes, you can POSSE out up to 140* characters of your note to Twitter.
POSSE entire note to twitter
has the permashortcitation of a permashortid in a classical parenthetical citation:
which is easily expanded (see related: original-post-discovery) by unparenthesizing and joining the two pieces with a forward slash "/":
which resolves (redirects) to the original post:
You should NOT include a post permashortlink at the end of tweet copies of notes that include the entire note.
There's an unspoken convention on Twitter that a link in a tweet (especially at the end of a tweet) should provide more information.
Having an active permashortlink at the end of your tweet when all you provide on your own site is the *exact* same content is bad UX for your friends that follow you on Twitter.
The whole point of POSSE is that you still care about your friends on Twitter (or other silos) reading you, so you should care about their UX also.
Only provide permashortlinks as part of your POSSE tweets when they link to an the original post with more content than in the POSSE tweet copy. Otherwise use permashortcitations so that your original posts are still automatically discoverable using the original-post-discovery algorithm.
POSSE abbr note to twitter
If your note (with permashortid) exceeds 140 characters, you should abbreviate your note to 119 (118) characters (e.g. using the CASSIS
You may want to put an ellipsis character at the end of your POSSEd note to Twitter before your perma(short)link. Be sure to leave room for the ellipsis too: instead of just 1 character for a space before your permashortlink, save 4 characters for "... ", or 3 characters for "… " (ellipsis entity character). Ideally elide at a punctuation boundary (like sentence terminator or a comma - the above-mentioned CASSIS function does this too). Examples (which link to original posts after eliding with "... ")
Exception, if your abbreviated tweet already has a ":" (colon) character at the end, no need for an ellipsis, simply append a space " " and your permashortlink. Examples which truncate after a ":"
IndieWebCamp community members who are doing this:
POSSE Notes to Twitter Pseudocode
Assume that to start with you have some HTML markup representing the content of the note ($text), the canonical URI to link back to from the syndicated tweet ($url) and an optional in-reply-to url associated with the note ($inReplyTo).
POSSE Articles to Twitter
Similar to POSSEing a note, you can POSSE an article to Twitter, but instead of the first 140 characters of the post, you should POSSE the first 140 characters of the entry name (title) of the article, followed by optionally a ":" character (unless the entry title already ends with punctuation), then a space " ", then the perma(short)link to your original post. Examples:
IndieWebCamp community members who are doing this:
POSSE Replies to Tweets
Similar to POSSEing a note to Twitter, when POSSEing a reply to a tweet, you also set the
You can use this regular expression to extract tweet IDs from tweet URLs:
Examples, i.e. IndieWebCamp community members who are doing this:
POSSE Replies to Twitter
When posting a comment which is a reply to another indieweb post, the POSSE tweet of your comment should attempt to set the
This is similar to how you POSSE Replies to Tweets but with one extra step to discover the POSSE tweet of the original post:
POSSE Reposts of Tweets
When posting a repost of a tweet, the proper POSSE behavior should be to do a native retweet (on Twitter) of the tweet that you're reposting on your own site.
POSSE Reposts to Twitter
When you do a repost of an indieweb post:
POSSE Favorites of Tweets
When posting a favorite of a tweet, the proper POSSE behavior should be to natively favorite (on Twitter) the tweet that you're favoriting on your own site.
POSSE Favorites to Twitter
When you post a favorite of an indieweb post:
See full article: Twitter-API
The Twitter iOS client has an option to use a different API root, "intended for a Twitter proxy server"
It may be theoretically possible to re-implement enough of the Twitter API on your own site to set your own site as a "Twitter proxy server" and thus use the Twitter client as a client to post directly to your own site (and perhaps read from it as well).
Most recent first:
Email Identity Removal
This 2013-05-17 screenshot seems to demonstrate an odd interaction and vulnerability on Twitter:http://twitter.com/t) with a yellow warning box just below the global black toolbar that says:
New email address required. Twitter has removed the email address from your account, by request of the email owner.
Hyperlinks as present in original. No such warning on m.twitter.com equivalent page when logged in (i.e. on a mobile device).
It's not clear how this happened, how the email address was revoked, how to avoid having it revoked in the future etc.
Appears to be an identity threat/vulnerability.
Early User Interface
Twitter's early user interface (circa 2006-2007?) was quite simple and minimal: