RunKeeper and the Health Graph API
- Nice 3 part video series on "Managing Body Weight" http://t.co/chPT5ni http://t.co/PyxJe9D http://t.co/F6phVZA via @RunKeeper TV #

PayPal X Platform
- @Magento resources http://bit.ly/nhL2ju #
- New @PayPalX site http://bit.ly/pjQOSH launched Monday Aug 29 #
- A @Magento community update http://t.co/hx80BIm #
- I will be attending @AndroidOpen http://t.co/u0OfofQ and @X_commerce Innovate http://t.co/Rj7oShX in October in San Francisco #
APIs and development
- I love how Codecademy http://t.co/P5PIn6d jumps straight into learning, then worries about signups later (more: http://t.co/S1M3ccZ ) #
- Handy side-by-side PHP, Perl, Python, and Ruby reference http://t.co/Reabhz6 via @newsycombinator #
- SSH remote server productivity tips http://t.co/z8cCtX0 #
Personal things
- Of all the things Steve Jobs is known for saying http://t.co/XDnepRZ I find his Stanford commencement speech far and away the most wonderful #
- How to space out your tweets http://t.co/PupkTYV using @bufferapp (I also like @tweetdeck for this) #
Running
- Easy 5k, neg splits 10:22, 10:11, 9:36, and 8:29. http://t.co/7sZROAP #RunKeeper http://t.co/gTR9DjA #
- Hot mid-afternoon 4.00mi run. http://t.co/uiPEsPJ #RunKeeper http://t.co/S3x7HHu #
- 4mi including 2mi marathon pace (target 9min/mi; actual 8:52 and 8:54). http://t.co/pPXzGhR #RunKeeper http://t.co/hvNPKUT #
- #Irene dashed our flight to Boston today, so I ran 14mi instead. http://t.co/O6sKYEB #RunKeeper http://t.co/hwlwTGk #
- I've been tracking my weight for the last two years. Happy I've stayed in a good range for last year+. http://t.co/dAC2Aap #

When last I wrote about Google payment options, Google had teased developers about their upcoming in-app payment technology with trailer-style videos like this:
Google promised that the Google In-App Payments API would offer:
An easy, effective way to make money while keeping your customers engaged in your web app, and it’s priced at just 5-percent.
Problem was, it wasn’t available yet.
Last month, Google made one small step to address that shortcoming by releasing in-app payments to developers with US bank accounts. As they noted in the blog post announcement:
Today, we’re making Google In-App Payments available for all web application developers to integrate with their web apps wherever they’re hosted, including the Chrome Web Store. Integration is simple with just a few lines of code. And pricing is set at just 5-percent.
Amit Fulay, Google Product Manager, went on to say:
In-App Payments is initially available for developers with a United States bank account and for buyers in more than 140 countries. We look forward to expanding to additional developer locations as quickly as possible.
So if you have a US based bank account, you can sign up to give Google In-App Payments a try. They require quite a bit of private and public business information as you can see below.


It’s no secret that I believe PayPal’s payment solutions to be superior to Google’s for most developers. As I wrote in my recent Alternative Payment Systems series concluding article:
Google Checkout does not provide anywhere near the full capabilities of the complete PayPal X Platform. It compares most directly to PayPal’s Website Payments, Fraud Management Filters, and Embedded Payments technologies. Even if you include Google In-App Payments and Google Wallet…Google solutions still fail to provide the full functionality available commercially today in the PayPal X Platform. Given the choice between the two, I would recommend the PayPal X Platform in most cases unless a merchant was already locked in a fairly tight business relationship with Google.
Click here to read the complete post on the PayPal X Developer Network including some resources to consider if you do fall into the “tight relationship” camp.

I don’t normally re-post announcements or bulletins, but I’ll make a special exception for a recent email sent by Carolyn Mellor and the PayPal team to members of the PayPal Developer Network.
It announces the redesign of the x.com site and contains important information that all PayPal, eBay, and Magento developers should take note of.
The message begins:
As a valued member of our developer community, we wanted you to know that on August 29th, we’ll be launching a newly designed site on x.com. We’ve listened to your feedback over the past year and made improvements to the current site in terms of functionality, search-ability, and design. The site will now be easier to navigate, have more tools, and improved documentation — all so that you can find what you need quickly and easily.
The announcement notes the following things in particular:
- x.com will be in read-only mode during the transition, Saturday and Sunday, August 27th and 28th.
- While in read-only mode, you’ll be able to search and read content on x.com, but not add anything new.
- You’ll use your existing PayPal credentials to log back into the site when it relaunches Monday August 29th.
Click here to read the complete post on the PayPal X Developer Network including information on sending your questions and feedback on the site redesign to PayPal.

A few weeks ago I wrote about the announcement of the merger of the eBay, PayPal, and Magento developer platforms and communities under the X.commerce banner. I followed that up with a post on eBay resources to help PayPal X community members get up to speed with eBay development.
Now that Magento’s officially a part of the X.commerce family, I think it’s time to share some resources to help everybody learn about Magento’s ecommerce solutions.
Here are some of the top level sites and information you should check out as you dive into Magento:
- First, you may need information on what the Magento ecommerce platform enables. Go to the Magento “Features” page for answers including a video introducing you to the Enterprise Edition’s features. This page also links to information comparing the three editions (from the free, open source Community Edition up through the Enterprise Edition) and their pricing.
- The Magento wiki contains links for detailed information on store setup as well as articles targeted both at designers and at developers. I highly recommend spending some time reading through this material as you familiarize yourself with the system and how to use it.
- The Magento forum is the place to go to get answers to any questions you don’t see addressed in the high level product FAQ or elsewhere on the Magento site.
- Subscribe to the Magento blog for the latest official information. Click here for the feed.
- Get social with Magento via their @magento Twitter feed and Facebook page.
Click here to read the complete post on the PayPal X Developer Network and leave your own questions or Magento resource suggestions for other community members.
RunKeeper and the Health Graph API
- Hair-thin bio-sensors could open up some very interesting possibilities http://t.co/I8vBXdL via @DiscoverMag #
- The key to harnessing feedback loops as discussed in @wired http://t.co/jkfaqe8 is cheap sensors #SensorsFTW #
- Nice @lifehacker device and software roundup: "How I Got in Shape with the Help of Technology" http://t.co/9gNiRht #RunKeeper #
- A healthier, more connected world with @runkeeper and the @HealthGraphAPI http://t.co/rKnXL17 via @programmableweb #

PayPal X Platform
- Easily exploitable Square card reader vulnerabilities http://bit.ly/qrTrSK #
- "Bitcoin: Money without Governments" http://bit.ly/n9qlRk is my latest @PayPalX article (includes @Magento Payment Gateway Plugin info) #
- Google rocks Android by buying Motorola http://bit.ly/mRqh7T including partner reactions and what might be next for developers #
Wireless and mobility
- Whoa! Google is buying Motorola Mobility http://t.co/v37QAai (press release http://t.co/cBv55yI ) #
- Will hardware makers trust #Google after #Motorola buy? http://t.co/y02N2oe (somehow the partner quotes seem flat http://t.co/5psWstC ) #
- More on Google discontinuing @AppInv http://t.co/1pNIjX5 particularly interesting given their big bet on #Android with their #Motorola buy #
- TC's @parislemon picked up on the same Googerola partner nonsense http://t.co/6zC559H that I wrote about http://t.co/yZzsu16 for @PayPalX #
- How Google *really* stuck it to Apple and Microsoft with the Nortel patent bidding, then Motorola purchase http://t.co/kabD2UM via @sai #
APIs and development
- API adoption tip: You need at least one simple, open method http://t.co/g9j8NBh via @apigee (very well said!) #
- Elegant single file backup before you edit http://t.co/hAr97c7 via @commandlinefu #
Personal things
- How to reach influencers using @exportly and @gist http://t.co/IdctheA #
- Thank you, Warren Buffett, for saying what needs to be said (and done): "Stop Coddling the Super-Rich" http://t.co/13rc9D6 via @nytimes #
Running
- Preparing for a trip by reading up on running the Esplanade in "Boston: A Runner's Guide" http://t.co/QaHrL1f via @runnersworld #
- Charles River running map http://t.co/DQrtUcF #
- 5k EZ after yesterday's long run. http://t.co/Kqc69sa #RunKeeper http://t.co/fMkfYvJ #
- Easy 5k, neg splits 10:30, 10:04, 9:36, final 0.1mi at 8:22 pace. http://t.co/HL19v3i #RunKeeper http://t.co/jO0sGZu #
- 8mi in mid-90s heat, ugh. http://t.co/hAJBzLt #RunKeeper http://t.co/UPSOUgY #
- 5.00mi gravel roads, first run with Camelbak Octane. http://t.co/TRATo0Y #RunKeeper http://t.co/UVFmc9R #
I recently completed a six part series examining alternative payment systems and comparing them to the PayPal X Platform. As I wrapped that up, I asked readers to weigh-in on which topic they’d like to read about next. I received votes for several topics on the list including a request for coverage of the eBay APIs (watch for more from me on that coming soon). But the one request that caught me off guard was for an article on Bitcoin.
Bitcoin is a relatively new digital currency. But there’s much more to it when you dig a bit under the covers. Shall we?
What is Bitcoin?
Here’s the high level description of what Bitcoin is and provides from its Wikipedia page:
Bitcoin is a digital currency created in 2009, based mainly on a self-published paper by Satoshi Nakamoto. (It) enables rapid payments (and micropayments) at very low cost, and avoids the need for central authorities and issuers. Digitally signed transactions, with one node signing over some amount of the currency to another node, are broadcast to all nodes in a peer-to-peer network. A proof-of-work system is used as measurement against double-spending and initial currency distribution mechanism.
The Bitcoin site WeUseCoins.com provides a high level video overview of what Bitcoin is, how the coins are created, and what you can buy with them (click here if the YouTube video fails to load below).
For more detail, you can also watch a short Ignite presentation from the current Principal of the Bitcoin project, Gavin Andresen (@gavinandresen). Click here to watch Gavin’s presentation on YouTube if the embed below isn’t working for you.
You can get a feel for the frequency of Bitcoin transactions by watching them occur via the Bitcoin Monitor site.

Interested in the nitty gritty of how the system works? You can dig deeper by reading Nakamoto’s original “Bitcoin: A Peer-to-Peer Electronic Cash System” paper (click here for PDF). There is also a Bitcoin wiki with links to much more information, a FAQ, discussion forums, and developer information; click here to jump to the wiki. You can also link to more information on the Bitcoin project and community via Bitcoin.org.
One very important thing to note:
The Bitcoin system is based upon public-key cryptography. Without the crypto, you’d have no Bitcoin. Bitcoin being crypto-currency leads to some interesting properties, not the least of which is that it cannot be inflated by a central bank or governmental authority. This means that Bitcoins have commodity-like properties similar to gold and other precious metals.
Bitcoin’s being based upon public key cryptography also means that there are concerns about it being used for nefarious purposes. Governments and organizations interested in cryptography, money laundering, and cyber attacks are taking close looks at Bitcoin. We’ll discuss these issues more later.
Acquiring and storing Bitcoins
In order to use Bitcoins, you must first have a Bitcoin wallet.
You can either download a piece of wallet software to install on your computer (click here for links to download the official Windows, Mac, or Linux client or here to grab the source from GitHub) or use an online wallet. There are options for the latter listed on the “Getting Started with Bitcoin” page from WeUseCoins.
The official Windows wallet starts up like this (note that the provided Bitcoin Address has been removed from this screenshot):

Here’s an example online wallet, Instawallet, which creates a new wallet for you by default when you visit their homepage:

To continue using the same Instawallet in the future, you would need to bookmark the unique wallet URL assigned to you. The Instawallet site notes that you should only view this option as a “spare change” wallet, rather than store a large amount of Bitcoinage here.
Whether you choose to use a downloaded wallet or an online one, there are some potential gotchas to consider. If you lose your downloaded wallet, say through a system crash or theft, you also lose any coins stored in it. Likewise if you use an online wallet such as Instawallet and lose the URL or authentication information for that wallet, or the service provider disappears, or anything else keeps you from reaching your online wallet, you may also loose coins. So be sure you have a backup and security strategy in place to avoid any problems later.
Whichever approach you choose, once your wallet is ready you will have a new Bitcoin Address. You use this address to send and receive coins.
So how can you get some Bitcoins to try the system out? There are several options listed on the aforementioned “Getting Started with Bitcoin” page. But perhaps the easiest option is to use a free service from Gavin Andresen, Free Bitcoins. Gavin’s service will transfer a small amount of coinage (0.001 Bitcoin, or BTC, as I write this) for free to whatever receiving Bitcoin Address you specify. The only catch is that you do need a Google account (free to acquire if you don’t already have one).
For example, I entered my Google account information and Bitcoin Address for Instawallet into the Free Bitcoins “faucet” and it sent 0.001BTC my way.

After a little bit of time for the network communication and computations to happen in the background, the Bitcoinage appeared in my Instawallet.

There are a number of other ways you can add coins to your wallet. You can earn them, purchase them in a market (check out Bitcoin Charts for a view into the various markets and currency-to-Bitcoin purchases), and even buy them over the counter (OTC). Bitcoins can also be created via a process known as “mining“, but for most consumers and merchants interested in Bitcoins for commerce but not in becoming a mining business, the amount of computational horsepower required may be prohibitive (see this ZDNet article for more on mining).
Using and accepting Bitcoins
However you acquired your Bitcoins, once you have some you will probably want to start using them. There are a wide and growing variety of legitimate services and merchandise being sold today for Bitcoins. Visit the “Trade” page on the Bitcoin wiki to see a list of many of the available items.
What if you want to accept Bitcoins as a method of payment? The same wiki contains a Merchant Howto to help you get started. It provides information on both manually accepting Bitcoin and automating Bitcoin based purchases. And you can automate purchases via existing shopping cart solutions (for example a Magento Payment Gateway Plugin) or programmatically yourself using a JSON-RPC interface.

For more information on the Bitcoin ecosystem, I would recommend reading through the linked resources on Dave Mackey’s “A Bitcoin Primer“.
Threats and opportunities
As Bitcoin has gained somewhat wider acceptance and much wider visibility, criticism has been heaped upon it. There have been exchange data issues, threats against the system because of its use in black market purchases for illegal items such as drugs, and claimed heists of large sums of Bitcoinage. There has also been some incredible speculation which saw the value of 1 BTC, as expressed in US dollars, climb nearly 1000% in a single month earlier this year!
Things have gotten so heated in this space that even the CIA is studying up on Bitcoin. So what are the significant threats and opportunities for Bitcoin?
One major threat to Bitcoin’s longterm success is ease of use. Needing to have a working knowledge of “crypto-currency” and “peer-to-peer” may not turn off techies, but it certainly confuses a lot of other people. If people can’t understand Bitcoin, they won’t use it. If not many people use Bitcoin, it will continue to see non-sticky value jumps versus other currencies. And large swings in value lead to a further lack of confidence in any currency or commodity.
The opportunity inherent in this problem lies in making the Bitcoin system very easy to use. Implementers need to concentrate on bulletproof clients and merchant software if they hope to maximize Bitcoin uptake. And for goodness sake, hide the cryptography details and never use the acronym “p2p” in getting started guides and consumer-oriented documentation!
Another threat to Bitcoin’s viability is that it has in fact been used in certain high profile illicit markets. The opportunity here is for legitimate Bitcoin users and supporters to educate their governmental representatives on the many legitimate uses of Bitcoin. Just as with dollars or any other currency or commodity, Bitcoin is inherently neither good nor evil. But unlike the other more established value stores and means of commerce, Bitcoin is terribly new, and therefore poorly understood, which in some cases leads to fear. Education is the only way out of that.
Click here to read the complete article on the PayPal X Developer Network including discussion of the biggest potential impediment to Bitcoin’s long-term viability.
It’s impossible to capture the vastness and dizzying beauty of Yosemite Valley in pictures or video.
But this comes close:
(I suggest watching this full screen for maximum effect.)
The news is abuzz today with Google’s announcement that they are buying Motorola Mobility, that part of Moto spun out to focus on Android smartphones, tablets, and related digital gadgetry.
Google went out of their way in the announcement to note:
This acquisition will not change our commitment to run Android as an open platform. Motorola will remain a licensee of Android and Android will remain open. We will run Motorola as a separate business. Many hardware partners have contributed to Android’s success and we look forward to continuing to work with all of them to deliver outstanding user experiences.
If you were Samsung, HTC, or another of Googerola’s Android hardware partners, would that make you feel any better about trusting Google’s Android intentions? Sure there were the usual quotes trotted out from said partners, but don’t they sound a bit like each partner simply echoing back the official “line”? To wit:
“We welcome today’s news, which demonstrates Google’s deep commitment to defending Android, its partners, and the ecosystem.” – J.K. Shin, President, Samsung, Mobile Communications Division
“I welcome Google‘s commitment to defending Android and its partners.” – Bert Nordberg, President & CEO, Sony Ericsson
“We welcome the news of today‘s acquisition, which demonstrates that Google is deeply committed to defending Android, its partners, and the entire ecosystem.” – Peter Chou, CEO, HTC Corp.
Click here to read all the quotes provided by Google.
Most importantly for X.com community members, what will this purchase mean for Android app development? It’s a bit early to say, although I would speculate that we’ll see skinless Moto devices as follow-ons to the Nexus series of phones coming at some point. I have a guess what next year’s big Google I/O giveaway may be…

Click here to read the complete post on the PayPal X Developer Network including links to additional coverage and information on Google’s Motorola acquisition.
I’ve written some about Square and their mobile card reader before. Click here to read my most recent article on them, part of my alternative payment systems series.
The problem is, Square’s dongle has been hacked. And hacking it is pretty embarrassingly simple to do, it seems.

The gist is this: Square’s dongle plugs into the audio port on supported devices such as iPhone, Android phones, etc. Cards are swiped through the reader dongle by merchants. The reader then turns the credit card swipe data into audio files that are transmitted through the Square system and turned into transaction requests for card issuers.
But the Square app accepting the dongle’s audio files cannot tell the difference between dongle input and properly recorded audio files from another source. As reported by Mashable, researchers at Aperture Labs proved someone can hack the Square system with just a little bit of code and a cheap stereo cable:
In order to bypass the need to swipe a card, (the researchers) wrote a simple program — in fewer than 100 lines of code — that enables (them) to feed magnetic strip data from stolen cards into a microphone and convert that data into an audio file. Once that file is played into the Square device via a $10 stereo cable, the data is sent directly to the Square app for processing.
If Square had just digitized and encrypted the data on-dongle before passing it to the on-phone app, this hack wouldn’t work. Security 101 stuff, really.
Click here to read the complete post on the PayPal X Developer Network including information on a second Square exploit.
RunKeeper and the Health Graph API
- Nice @Launch coverage of FitnessKeeper's growth, @HealthGraphAPI, and prospects http://bit.ly/qpwmDy (more: http://bit.ly/rtKwS4 @RunKeeper) #

PayPal X Platform
- For @PayPalX, @Magento, and other developers sizing up the new X.commerce world: eBay developer resources http://bit.ly/qOlYrj #
- My latest: @X_commerce #Android Apps the Easy Way, Part 1: Understanding App Inventor http://bit.ly/pbIic3 http://bit.ly/pzyiN1 #
- Part 2 http://bit.ly/rlbtEt of my @X_commerce #Android series http://bit.ly/rkxjTU focuses on accessing web APIs in @AppInv apps (@PayPalX) #
- How to build native #iOS #Android #Blackberry & other apps with @PhoneGap and @PayPalX http://bit.ly/r35dlO using HTML, JavaScript, & CSS #
Wireless and mobility
- "An iOS Developer Takes on Android" http://bit.ly/pojAfc by @nfarina should be read, and re-read, by #iOS and #Android developers alike #
- Strong words from Google against Apple, Microsoft, and Oracle: "When patents attack Android" http://bit.ly/mTMIS1 #AndroidFTW #
- Microsoft's response to Google's #Android patent related claims does make the GOOG look pretty stupid, though: http://tcrn.ch/mPGx7D #
- "How to find the perfect Blogs and Websites to tell the World about your App" http://bit.ly/qikZNm via @appbackr (hint: Google @AdWords) #
- No more Symbian in North America. As @rww puts it: "The death spiral of Nokia's smartphone brands continues." http://rww.to/n7WO1A #
- Designing for #Android tablets http://bit.ly/qCKLyK from @smashingmag (follow-up to previous Android design article http://bit.ly/qL1FuV ) #
APIs and development
- Tips on designing command line interfaces http://bit.ly/n4wYVC #
- Seven handy new API consoles from @apigee http://bit.ly/njzavH including consoles for @bitly and @nytimes #
- Google+ Platform blog launched by the GOOG http://bit.ly/q0dXhi #
Personal things
- "The jobless future" http://bit.ly/oWfUnR by @jeffjarvis needs to be read and brainstormed by our best and brightest; pay attention D.C. #
- Tips on running a software business http://bit.ly/o1p8Qq applies equally well to writing and many other endeavors #
Running
- Dream run: Down the South Kaibab Trail into the Grand Canyon http://bit.ly/o2CkMG preferably all the way rim-to-rim #IWillMakeItSo #
- Hot 10mi run. But marathon long, slow distance run #1 completed! http://t.co/OEGoAaW #
- Here's the exact same 10.00mi run recorded on my @Garmin 405cx for comparison http://bit.ly/pfzNKV #RunKeeper #
- 5k recovery after yesterday's 10mi. 92 deg F at start, 98 at finish. http://bit.ly/r1yEx7 #RunKeeper http://bit.ly/qI77Vb #
- 4mi running in the 70s is much nicer than 90s or 100+ deg F! http://bit.ly/oG47aK #RunKeeper http://bit.ly/pwuwgY #
- Ran 5 miles in 51 mins and felt great. Temps in 70s after much needed 4in of rain this morning. Pure joy! http://bit.ly/q7L8LY #
- Great fun running 4mi in the cool rain! Splits 10:17, 9:57, 9:27, and 8:56. http://bit.ly/qGH5dO #RunKeeper http://bit.ly/n8zOkC #
- 12mi cool and cloudy. Saw another runner fall, roll to his left, and pop up running! http://t.co/U5byy1B #RunKeeper http://t.co/VjeCnyq #