<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>zedstar dot org &#187; btlogger</title>
	<atom:link href="http://zedstar.org/blog/tag/btlogger/feed/" rel="self" type="application/rss+xml" />
	<link>http://zedstar.org/blog</link>
	<description></description>
	<lastBuildDate>Mon, 19 Mar 2012 07:28:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>btlogger updated to support OAuth</title>
		<link>http://zedstar.org/blog/2010/09/17/btlogger-updated-to-support-oauth/</link>
		<comments>http://zedstar.org/blog/2010/09/17/btlogger-updated-to-support-oauth/#comments</comments>
		<pubDate>Fri, 17 Sep 2010 10:57:37 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[twitter]]></category>
		<category><![CDATA[btlogger]]></category>
		<category><![CDATA[oauth]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/?p=211</guid>
		<description><![CDATA[Twitter pulling the plug on basic authentication meant I had to make changes to btlogger to support OAuth. Fortunately, librest made the code changes trivial. However, I ran into some problems. The clock was out of sync on the PC where btlogger runs. This caused the authenticate process to fail at the token request stage [...]]]></description>
			<content:encoded><![CDATA[<p>Twitter pulling the plug on basic authentication meant I had to make changes to <a href="http://gitorious.org/btlogger/">btlogger</a> to support <a href="http://dev.twitter.com/pages/oauth_faq">OAuth</a>. Fortunately, <a href="http://moblin.org/projects/librest">librest</a> made the code changes trivial. However, I ran into some problems. The clock was out of sync on the PC where btlogger runs. This caused the authenticate process to fail at the token request stage and was not easy to debug. The other issue which has been heavily <a href="http://arstechnica.com/security/guides/2010/09/twitter-a-case-study-on-how-to-do-oauth-wrong.ars">documented</a> is how to support authentication keys in FOSS. Currently <a href="http://gitorious.org/btlogger/btlogger/blobs/master/configure.ac">configure.ac</a> requires an edit to supply the key information. In theory I could supply the keys to somebody who wants to <a href="http://gitorious.org/btlogger/btlogger/blobs/master/INSTALL">build</a> the software from source until I figure out another way to handle this. I think they call this &#8220;best effort security&#8221;.</p>
<p>btlogger is now running from its own twitter account at: <a href="http://twitter.com/bluetoothlogger">http://twitter.com/bluetoothlogger</a></p>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2010/09/17/btlogger-updated-to-support-oauth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>btlogger update</title>
		<link>http://zedstar.org/blog/2009/09/06/btlogger-update/</link>
		<comments>http://zedstar.org/blog/2009/09/06/btlogger-update/#comments</comments>
		<pubDate>Sun, 06 Sep 2009 17:41:23 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[twitter]]></category>
		<category><![CDATA[Bluetooth]]></category>
		<category><![CDATA[btlogger]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/?p=157</guid>
		<description><![CDATA[I finally got around to fixing btlogger. It broke after an Ubuntu upgrade which contained BlueZ changes. Anyway, I have moved the code over to Gitorious and made a new tarball and Debian package. Binary: http://zedstar.org/deb/btlogger_0.3.3-1_i386.deb Tarball: http://zedstar.org/tarballs/btlogger-0.3.3.tar.gz Repo: git clone git://gitorious.org/btlogger/btlogger.git Take a look at the README for further information.]]></description>
			<content:encoded><![CDATA[<p>I finally got around to fixing btlogger. It broke after an Ubuntu upgrade which contained BlueZ changes. Anyway, I have moved the code over to <a href="http://gitorious.org/btlogger/">Gitorious</a> and made a new tarball and Debian package.</p>
<p>Binary: <a href="http://zedstar.org/deb/btlogger_0.3.3-1_i386.deb">http://zedstar.org/deb/btlogger_0.3.3-1_i386.deb</a></p>
<p>Tarball: <a href="http://zedstar.org/tarballs/btlogger-0.3.3.tar.gz">http://zedstar.org/tarballs/btlogger-0.3.3.tar.gz</a></p>
<p>Repo: <span id="repo-10997-git-url"> <code> git clone <a href="git://gitorious.org/btlogger/btlogger.git">git://gitorious.org/btlogger/btlogger.git</a></code></span></p>
<p><span>Take a look at the <a href="http://gitorious.org/btlogger/btlogger/blobs/master/README">README</a> for further information.<br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2009/09/06/btlogger-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>btlogger debian package</title>
		<link>http://zedstar.org/blog/2009/03/25/btlogger-debian-package/</link>
		<comments>http://zedstar.org/blog/2009/03/25/btlogger-debian-package/#comments</comments>
		<pubDate>Wed, 25 Mar 2009 10:14:37 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[thumbtribes]]></category>
		<category><![CDATA[btlogger]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/?p=122</guid>
		<description><![CDATA[I packaged up the tarball into a debian package: http://zedstar.org/deb/btlogger_0.3.2-1_i386.deb After installing run btlogger &#8211;help]]></description>
			<content:encoded><![CDATA[<p>I packaged up the tarball into a debian package:</p>
<p><a href="http://zedstar.org/deb/btlogger_0.3.2-1_i386.deb">http://zedstar.org/deb/btlogger_0.3.2-1_i386.deb</a></p>
<p>After installing run btlogger &#8211;help</p>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2009/03/25/btlogger-debian-package/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Bluetooth logging to Twitter with btlogger</title>
		<link>http://zedstar.org/blog/2009/03/06/bluetooth-logging-to-twitter-with-btlogger/</link>
		<comments>http://zedstar.org/blog/2009/03/06/bluetooth-logging-to-twitter-with-btlogger/#comments</comments>
		<pubDate>Fri, 06 Mar 2009 22:17:55 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[thumbtribes]]></category>
		<category><![CDATA[Bluetooth]]></category>
		<category><![CDATA[btlogger]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/?p=118</guid>
		<description><![CDATA[I decided to hack my Bluetooth logger so that it could post any new devices it saw to my Twitter account. This should be interesting once I get it setup on my desk at work! After moving to Intrepid Ibex I realised the changes in BlueZ versions borked my software. It took me a while [...]]]></description>
			<content:encoded><![CDATA[<p>I decided to hack my Bluetooth logger so that it could post any new devices it saw to my Twitter account. This should be interesting once I get it setup on my desk at work! After moving to Intrepid Ibex I realised the changes in BlueZ versions borked my software. It took me a while to figure out what needed to be fixed. Anyway, these changes and Twitter hack are available as a tarball here:</p>
<p><a href="http://zedstar.org/tarballs/btlogger-0.3.2.tar.gz">zedstar.org/tarballs/btlogger-0.3.2.tar.gz</a></p>
<p>The tarball should install an sqlite db file in /var/lib/misc but you can move it else where if you don&#8217;t want to run as root. If you supply a username and password on the command line it will try and post the scan results to Twitter like:</p>
<p><a href="http://twitter.com/jptmoore">http://twitter.com/jptmoore</a></p>
<p>To see the command line options run btlogger &#8211;help</p>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2009/03/06/bluetooth-logging-to-twitter-with-btlogger/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>btlogger for the beagleboard</title>
		<link>http://zedstar.org/blog/2008/09/17/btlogger-for-the-beagleboard/</link>
		<comments>http://zedstar.org/blog/2008/09/17/btlogger-for-the-beagleboard/#comments</comments>
		<pubDate>Wed, 17 Sep 2008 20:42:16 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[thumbtribes]]></category>
		<category><![CDATA[beagleboard]]></category>
		<category><![CDATA[Bluetooth]]></category>
		<category><![CDATA[btlogger]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/2008/09/17/btlogger-for-the-beagleboard/</guid>
		<description><![CDATA[I have built btlogger for the beagleboard. The ipk is available: http://zedstar.org/beagle/btlogger_0.2.2-r0_armv7a.ipk It requires the sqlite db some where on the device. Download: http://projects.openmoko.org/frs/download.php/313/btlog.db run btlogger -v to see what it does and reference the db file with -d /location/of/file TODO: I am going to modify the program to log more stats. I should also [...]]]></description>
			<content:encoded><![CDATA[<p>I have built <a href="http://projects.openmoko.org/plugins/wiki/index.php?btlogger&amp;id=136&amp;type=g">btlogger</a> for the beagleboard. The ipk is available:</p>
<p><a href="http://zedstar.org/beagle/btlogger_0.2.2-r0_armv7a.ipk"> http://zedstar.org/beagle/btlogger_0.2.2-r0_armv7a.ipk</a></p>
<p>It requires the sqlite db some where on the device. Download:</p>
<p><a href="http://projects.openmoko.org/frs/download.php/313/btlog.db">http://projects.openmoko.org/frs/download.php/313/btlog.db </a></p>
<p>run btlogger -v to see what it does and reference the db file with -d /location/of/file</p>
<p>TODO:</p>
<ul>
<li>I am going to modify the program to log more stats.</li>
<li>I should also add the database to the ipk so it installs automatically</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2008/09/17/btlogger-for-the-beagleboard/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>btlogger 0.2</title>
		<link>http://zedstar.org/blog/2008/06/08/btlogger-02/</link>
		<comments>http://zedstar.org/blog/2008/06/08/btlogger-02/#comments</comments>
		<pubDate>Sun, 08 Jun 2008 15:06:40 +0000</pubDate>
		<dc:creator>john</dc:creator>
				<category><![CDATA[thumbtribes]]></category>
		<category><![CDATA[Bluetooth]]></category>
		<category><![CDATA[btlogger]]></category>

		<guid isPermaLink="false">http://zedstar.org/blog/2008/06/08/btlogger-02/</guid>
		<description><![CDATA[I have updated btlogger to allow various command line options. The software should work on any Linux system with Bluetooth. There is a packaged version for Openmoko: https://projects.openmoko.org/plugins/wiki/index.php?btlogger&#38;id=136&#38;type=g and a binary for the Nokia Tablet: http://zedstar.org/chinook/btlogger An empty database can be dowloaded from here: http://projects.openmoko.org/plugins/scmcvs/cvsweb.php/thumbtribes_project/misc/btlog.db?cvsroot=thumbtribes]]></description>
			<content:encoded><![CDATA[<p>I have updated btlogger to allow various command line options. The software should work on any Linux system with Bluetooth. There is a packaged version for Openmoko:</p>
<p><a href="https://projects.openmoko.org/plugins/wiki/index.php?btlogger&amp;id=136&amp;type=g">https://projects.openmoko.org/plugins/wiki/index.php?btlogger&amp;id=136&amp;type=g</a></p>
<p>and a binary for the Nokia Tablet:</p>
<p><a href="http://zedstar.org/chinook/btlogger">http://zedstar.org/chinook/btlogger</a></p>
<p>An empty database can be dowloaded from here:</p>
<p><a href="http://projects.openmoko.org/plugins/scmcvs/cvsweb.php/thumbtribes_project/misc/btlog.db?cvsroot=thumbtribes">http://projects.openmoko.org/plugins/scmcvs/cvsweb.php/thumbtribes_project/misc/btlog.db?cvsroot=thumbtribes</a></p>
]]></content:encoded>
			<wfw:commentRss>http://zedstar.org/blog/2008/06/08/btlogger-02/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

