Next: Deleting Links, Up: Things You Can Do With the Program   [Contents][Index]

2.1 Sending Links to Pinboard ¶

The original use case for pin was sending links to Pinboard from the command line, or in situations where the only interface available was process-based.

In Pinboard terms, a link is a “post”, or a “bookmark”, and it has certain attributes. The two mandatory attributes are:

1. url The URL being saved, as defined in RFC3986. Allowed schemes are http, https, javascripts, mailto, ftp & file.
2. description The display name for the link. Per the API docs, “This field is unfortunately named ’description’ for backwards compatibility with the delicious API” The description must be fewer than 256 characters in length (see Technical Details).

A post has several other optional attributes. pin supports the following:

1. tags Zero or more tags, each less than 256 characters in length and may not contain commas or whitespace. Tags beginning with a ’.’ are “private”.
2. toread Mark the post as “unread”.

The relevant sub-command is ’send’, with arguments being the link or links you’d like to send to Pinboard. The links may be given in one of two ways. The first is simply giving the URL as an argument, in which case the title will be taken from the -T or --title option (which must be provided, in this case; it is illegal to send a link with no title):

pin send --title=foo http://foo.com

The other is to give arguments in the form “URL | TITLE” in which case the title given for each argument will be preferred to the --title

pin send "http://foo.com | foo"

The latter form happens to be the export format of the One Tab FireFox plugin.

You can tag the links given as arguments as “to be read later” by adding the --read-later. You can tags the links given with the --tag option (which can of course be given more than once).

• Instapaper
• Targets
• Reading URLs From File