Aaron Reimann

A Widget that uses jQuery (if you want) and Twitter to fade in and display a user’s tweets one at a time, then fades into the next. You can set the amount of tweets and how long they stay before they fade into the next tweet. The tweets are in an infinite loop. It only uses the jQuery library that comes with WP. It is simple, but if you know CSS you can make it look very very nice.
<h4>Twitter API 1.1 Keys and Tokens</h4>
You now have to go to <a href="https://dev.twitter.com/apps/" rel="nofollow ugc">Twitter’s Dev Section</a> and create an “app”. Please don’t be terrified by this. It takes 5 minutes. The hardest part is copying and pasting the keys once they are created 🙂
<ol>
<li>Go here and login with your Twitter account: https://dev.twitter.com/apps/</li>
<li>Click ‘Create New Application’</li>
<li>Give it a name like “WP-Jweets for YourDomainName”</li>
<li>Give it a description like “This is so I can show my tweets”</li>
<li>The “Website” field can be the domain name the tweets are going on</li>
<li>The “Callback URL” can be empty</li>
<li>Accept the agreement</li>
<li>Next, click on “Create My Access Token”</li>
<li>Create your token, you will need the following: Consumer key, Consumer secret, Access token and Access token</li>
</ol>
<h4>Server</h4>
Your server must have cURL enabled, it is required by the Twitter OAuth library (Thanks goes out to https://github.com/abraham/twitteroauth)

WP-jTweets

A widget that uses jQuery and Twitter to display a user's tweets (or can just list the updates).  Works with the Twitter API 1.1

hamzarauf

Show Latest posts news ticker at bottom…
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wordpress.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>10 Latest Blog posts </li>
<li>Rotating text </li>
<li>Current time</li>
</ol>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

WP-jTweets vs Posts News Ticker