icio

{
  "name": "Open URL Collector",
  "version": "1.0",
  "description": "Creates a list of the URLs of open tabs.",
  "browser_action": {
    "default_icon": "famfamfam_silk_cut_tab.png",
	"popup": "popup.html"
  },
  "permissions": ["tabs"]
}

Marak

Breaker
Clutch
Flash
Hawk
Scarlett
Ace
Doc
Duke
Torpedo
Roadblock

coderoshi

A Very Short Guide to Writing Guides

This is just a few thoughts on the topic of writing technical guides. This was intended for Basho's engineering team, but this may apply to open source projects in general.

Audience

It's commonly preached that the first step in writing is to identify your audience; to whom are you writing? This is the most well known, most repeated, and most overlooked step of writing in general and technical writing in particular. Take this document, for example. My audience is technical people who need to communicate technical information, and not teenagers, so I shy away from images of pop icons and memes. I use jargon and words like "identify" rather than "peep this".

Pronouns

0xjjpa

#Introduction

Developing Chrome Extensions is REALLY fun if you are a Front End engineer. If you, however, struggle with visualizing the architecture of an application, then developing a Chrome Extension is going to bite your butt multiple times due the amount of excessive components the extension works with. Here are some pointers in how to start, what problems I encounter and how to avoid them.

Note: I'm not covering chrome package apps, which although similar, work in a different way. I also won't cover the page options api neither the new brand event pages. What I explain covers most basic chrome applications and should be enough to get you started.

Table of Contents

1. Understand the Chrome Architecture
2. Understand the Tabs-Extension Relationship
3. Picking the right interface for the job

benmarwick

Quick and dirtly look at Shakespeare's plays
====

Introduction
----
I was recently inpsired by the recent posts of Andrew Collier ([1](http://www.exegetic.biz/blog/2013/09/text-mining-the-complete-works-of-william-shakespeare/) and [2](http://www.exegetic.biz/blog/2013/09/clustering-the-words-of-william-shakespeare/)) and an earlier post by [Matt Jockers](http://www.matthewjockers.net/2009/02/13/machine-classifying-novels-and-plays-by-genre/) to take a recreational look at the plays of Shakespeare. 

Motivated by Jockers, the specific topic I was interested in is the genres of the plays. For example, are the genres discrete or is there lots of overlap? Are the genres equal in variation or is one genre very focused and other very diverse? What are the key attributes that define the genres? And can I reproduce Jockers' use of high frequency words to identify genres? Related to Jockers' work on high frequency words is an earlier study by [Brainerd (1979)](http://www.jstor.org/stable/30207229) who used pronouns 

kanazux

<?php

$compressed = array(
	".0"	=>	"Hacha Split Archive File",
	".000"	=>	"DoubleSpace Compressed File",
	".7z"	=>	"7-Zip Compressed File",
	".7z.001"	=>	"7-Zip Split Archive Part 1 File",
	".7z.002"	=>	"7-Zip Split Archive Part 2 File",
	".a00"	=>	"ALZip Second Split Archive File",
	".a01"	=>	"ALZip Third Split Archive File",

dutc

labnol

Best Google Chrome Extensions

List compiled by Amit Agarwal

1. Vimium — Power users can browse the web using keyboard shortcuts. No mouse required.
2. Buffer — Share links to multiple social websites with a go.
3. PushBullet — Send web links, text notes and even push files from computer to your phone.
4. Clip Better — Don't send raw links over email, send previews that suggest what a link is all about.
5. Streamus — A YouTube music play for Chrome that also includes a radio.
6. Mighty Text — Send and receive SMS text messages from your desktop

vjeux

JedWatson/classnames (2650855 dls, 1465 stars)
yannickcr/eslint-plugin-react (2077066 dls, 710 stars)
rackt/react-router (1833204 dls, 9050 stars)
facebook/react-dom (782024 dls, 33044 stars)
gaearon/react-hot-loader (708042 dls, 3250 stars)
rackt/redux (568969 dls, 10743 stars)
rackt/react-redux (495498 dls, 1509 stars)
jsdf/coffee-react-transform (463488 dls, 380 stars)
JedWatson/react-input-autosize (455277 dls, 107 stars)
reflux/reflux (393281 dls, 4316 stars)

wrenoud

{
  "version": "2.0.9",
  "replacements": [
    {
      "active": true,
      "case": "Maintain",
      "repA": "woman",
      "repB": "person",
      "type": "Simple"
    },