TinyPaste is a tool that does for blocks of text what TinyURL does for URLs: Give you a nice, short, URL to pass along, rather than the full-length one for the page. (A TinyURL example: http://tinyurl.com/3f94fe is much shorter than the full URL for the page you get to.)
So TinyPaste lets you copy a block of text, paste it into a form at tinypaste.com, and get a similarly short URL in return. See http://tinypaste.com/5172c — which is the entire text of this blog post. There is also a Firefox extension that makes TinyPaste available from the right-click menu, so any text you see in your browser can be highlighted and turned into a TinyPaste URL.
TinyPaste is handy for getting long blocks of text into services like Twitter or a Facebook status (by putting in the TinyPaste URL rather than the full text), but it comes with several drawbacks. All formatting (other than line breaks) disappears completely. So do links. And most disturbing, to me, is the utter lack of indication of where the original came from. In the web page version it is, of course, possible to manually insert the URL or other attribution into the text before creating the TinyURL. For the Firefox plugin, though, this can — and I think should — be automatic.
Issue 3 of the Code4Lib Journal was published today:
Feedbooks is a site that turns an RSS feed — your own or your favorite daily read — into a PDF file for offline reading. A sample of Feedbooks’ PDF options for RSS4Lib’s feed can be found here: . It includes PDF files formatted for A4 paper, the Cybook & Sony Reader, iLiad, and “Custom PDF,” which is in this case standard-sized U.S. paper.
The tool works quickly, generating a PDF on the fly. First, set up an account at Feedbooks. Then, create a “News” item and enter the RSS feed you wish to subscribe to. The system defaults to A4 paper size; there is not a default 8.5″ x 11″ size. (You can set the Custom PDF page size to this selecting the “custom settings” link and entering the page size in millimeters: 216 by 279 millimeters.) The resulting PDF file can then be downloaded; a link is provided for bookmarking.
Other customizations are font (from a handful of common fonts), font size, and line height. The font choice only applies to the item content, not to the item title. Feeds are displayed one per page, which leaves a lot of white space (a solution I prefer to that used by FeedJournal, which I reviewed in December 2007). The PDF download has a table of contents with page numbers, though the page numbers themselves are not displayed on subsequent pages. I also noticed that some posts in the Feedbooks PDF version lost their paragraphs and were presented as one long block of text. The site seems to reproduce all the items in the RSS feed; the RSS4Lib RSS feed has 15 items, all of which are in the Feedbooks feed.
[Via The Distant Librarian.]
The Associated Press has stepped back from its original position on copyright and the blogosphere and will be developing a (hopefully) more nuanced policy. According to an article in the June 16 issue of The New York Times, “The Associated Press … said that it will, for the first time, attempt to define clear standards as to how much of its articles and broadcasts bloggers and Web sites can excerpt without infringing on The A.P.’s copyright.”
The recent controversy arose when AP requested that the Drudge Retort (a left-leaning response to Matt Drudge’s conservative Drudge Report) remove seven portions of its syndicated news stories from its web site. (I should note that the excerpts varied in length from 39 to 79 words; the excerpt I have in the previous paragraph is a hopefully safe 37 words.)
The AP’s move to better define fair use when it comes to blogging about news is a welcome one. As I discussed last month, there is a vast gap between what publishers desire and what common practice defines in the realm of copyright. The doctrine of “Fair Use” is “unclear and not easily defined.” (This according to the U.S. Copyright office itself!) Fair use is usually decided in the courts, after the fact. Bloggers have taken their stand through their actions — for better or worse, a significant portion of bloggers view fair use liberally. Publishers have, as fits their economic interest, taken a more restrictive view. It is refreshing to see a major publisher declare its interest in finding a middle ground that it can endorse.
The University of Iowa launched a flood blog to inform students, faculty, staff, and the public about the flooding on the Iowa City campus. The University of Iowa Flooding Blog provides a strong example of web technologies to aid in communication during a disaster. Linked from the blog are Flickr photostreams of campus images, a headlines feed from the Iowa City Press-Citizen, and, of course, updates and news about campus, buildings currently flooded or currently at risk, where there is power, what is open, and what is closed.
This is a very handy tool for grabbing a single feed and placing it on a web page; it could be very useful for libraries that do not have an abundance of technical expertise but have a blog they want to include elsewhere on the site.
One part of Google’s interface confused me (odd, as Google is usually so clever at interfaces). When entering a “Feed Expression”, Google will not take an RSS feed’s URL. It expects you to type keywords describing your feed, and it will figure out the actual feed URL. So entering my feed’s URL (http://www.rss4lib.com/index.xml) did nothing; entering simply “RSS4Lib” produced the feed.
Visit the full text of this entry to see what the code looks like embedded in a web page: Google Has an RSS Embedding Tool.
Continue reading Google Has an RSS Embedding Tool
Figuring out how much bang you’re getting for your blogging effort is not as simple as it first seems. While it’s relatively straightforward to calculate readership of static Web pages on your server, making a similar estimate of syndicated content readership is much trickier. (For an exploration of that topic, see my 2007 blog post, “Counting RSS Subscribers,” and the feedstats application I built to estimate out how many people might be reading RSS4Lib.)
The trick, of course, is when you “free” your content via syndication formats, it becomes harder to tell at a glance how much those syndicated files are being read. This is a problem for libraries, as for any other business operation, because library managers need information about the effect of their publicity and public relations efforts to justify them.
With the goal of creating a tool to help bloggers, library bloggers in particular, quantify their feed readership, I created a version of my older RSS4Lib-specific tool for general use: YourStats.
YourStats parses a log file and generates an estimate of total “direct” readership (that is, readership of the feed itself). It summarizes readership reported by aggregators like Bloglines and counts unique IP addresses for PC-based readers (such as Firefox or NetNewsWire). Of course, individual blog posts often far afield, being reproduced in other systems that do not report readership numbers. Other tools, such as Magpie (the RSS feed cacher) or Yahoo! Pipes, almost certainly redistribute your content to many other readers but do so in completely opaque ways. This sort of readership is not included in YourStats.
A couple notes:
- If you use Movable Type or WordPress to power your blog, and your RSS and Atom feeds have the default names, the application will take your log file and process it, giving results for both RSS (index.xml or feed=rss2) and Atom (atom.xml and feed=atom) readership.
- You can specify a different feed by entering its directory path and filename (for example, if your blog’s RSS feed is at http://your.blog.com/stuff/feed.xml, you would enter /stuff/feed.xml.
- YourStats only handles Apache standard log files.
I hope YourStats will provide you with quantifiable numbers around your blog’s readership. Try it and let me know what you think.