Grapevine is a simple message aggregator. It works by feeding in messages from various sources such as Twitter and grouping them into topics. Then it will periodically send out a notification with the most popular topic. Once topics are sent out in a notification, they won't be sent out again for a specified time window.

Currently Grapevine supports:

Loading messages from Twitter.
Integration with GitHub for filtering trackbacks.
Sending notifications to Twitter accounts.

The fantastically good sequel to the original: paulirish.com/​2010/​10-things-i-learned-from-the-jquery-source/​

Comments and details: paulirish.com/​2011/​11-more-things-i-learned-from-the-jquery-source

This is a list (a very subjective list) of scripts that perform tasks you may wish were actual iTunes Menu commands. Just copy and paste 'em to your AppleScript Editor and save to your iTunes Scripts folder...then add a Shortcut.

Optionally, you can click the mini-AppleScript Editor icon link beneath each snippet to open the script in AppleScript Editor on your computer. These links use URL Protocol Messaging to safely and securely send the contents of the script to your AppleScript Editor application.

12 Second Fade/Stop and Next Track
Artist to Album Artist
Choose Playlist
Current Track to (Select Playlist)
De-Shuffle All Playlists
Delete Selected Playlists
Eject iPods
Erase Bookmark
Jump to Playlist
Just Played These
Open iTunes Scripts folder
Play Random Playlist
Play Random Track of Random Playlist
Play Selected Track Once
Remove (Album Version)
Remove SOME TEXT From Names
Reset Start and Stop Times
Search Results to New Playlist
Selected Tracks to Current Playlist
Set Skipped Count/Skipped Date
Show Get Info Window of a Track's File
Skip Ahead n Seconds
Skip and Pretend We Played This
Super Shuffle
Toggle Checkmarks of Selected
Toggle Mute
View Current Playlist
Virgin Again

Selection Routines
Single Selected Track
Get a reference to a single selected track.
Each Selected Track
Get a list of references to each selected track.
Select Playing or Single Selected Track
Get a reference to the current track if player is paused or playing; otherwise, check for a single selected track.
Selected Tracks or Entire Playlist
Repeat with a reference to each of the selected tracks; or, if no tracks are selected, repeat with a reference for each track in the currently selected playlist.
Handlers
Is iTunes Running
Returns true or false.
Choose/Restore Encoder
Change encoders on-the-fly and restore Preferences-set encoder afterwards.
Nuke Track 1
Delete a track from iTunes entirely.
Nuke Track 2
Delete a track from iTunes entirely and delete its file immediately (and unrecoverably).
Nuke Track 3
Delete a track from iTunes entirely and move its file to the Trash.
text_to_list(), list_to_text(), replace_chars()
Frequently helpful text and list handlers.
Basic Idle Routine
Checks for new current track. Save as Stay-Open Application.
List Manually Managed iPods
Sets two corresponding lists to manually managed iPod names and source references
Export Artwork as File to Folder
Supply an iTunes track reference, path to folder as text, name of new file as text, and scale in pixels. NOTE: probably will not work with iTunes 9/Snow Leopard. See the slightly updated version below.
Export Artwork as File to Folder II
Supply an iTunes track reference, path to folder as text, name of new file as text, and scale in pixels.This version seems to work better in Snow Leopard with iTunes 9
Rating to Text Stars
Pass the value of a track’s rating property. Regretably, the chevrons in the Unicode do not translate into UPM so you’ll have to copy-and-paste this off the page.

GNU cflow analyzes a collection of C source files and prints a graph, charting control flow within the program.

GNU cflow is able to produce both direct and inverted flowgraphs for C sources. Optionally a cross-reference listing can be generated. Two output formats are implemented: POSIX and GNU (extended).

Input files can optionally be preprocessed before analyzing.

The package also provides Emacs major mode for examining the produced flowcharts in Emacs.

A sample of a direct flowchart is available online.

If you operate a website that features lots of code examples, you know how important it is to spend some quality time styling the <pre> element. When left unstyled, wild <pre> tags will mangle your preformatted content and destroy your site’s layout. Different browsers treat the <pre> tag quite differently, varying greatly in their default handling of font-sizing, scrollbar-rendering, and word-wrapping. Indeed, getting your preformatted code to look consistent, usable, and stylish across browsers is no easy task, but it certainly can be done. In this article, I’ll show you everything you need to create perfect <pre> tags.

There are two different ways to display a source code instead of executing a source code in a post or page. Depending on preferences which HTML tag is defined in the style sheet and provided with formatting, code fragments are either declared by <code> or <pre>. In some cases, combining the blogger even both tags.
Conversion of special characters

If you want to use the pre Tag, then you have to take care that the code snippets, while parsing, are not executable. HTML-Entity is the solution.

Two options are available: One, manually, such as search and replace before pasting into the editor (HTML-Entities-table). but if you are smart you let WordPress doing the job.

Numerous methods for the simple conversion of the code set between pre-and/or code tags are on the web. But there is one for the direct use in WordPress, which takes over to convert the characters perfectly since WordPress 2.8.

AppleScripts to resize windows simply

I anatomize a successful open-source project, fetchmail, that was run as a deliberate test of the surprising theories about software engineering suggested by the history of Linux. I discuss these theories in terms of two fundamentally different development styles, the ``cathedral'' model of most of the commercial world versus the ``bazaar'' model of the Linux world. I show that these models derive from opposing assumptions about the nature of the software-debugging task. I then make a sustained argument from the Linux experience for the proposition that ``Given enough eyeballs, all bugs are shallow'', suggest productive analogies with other self-correcting systems of selfish agents, and conclude with some exploration of the implications of this insight for the future of software.