• 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 #

This series examined the following alternative systems:

• Amazon Flexible Payments Service (FPS)
• Facebook Credits
• Google Checkout (plus a bit of discussion on Google Wallet and Google In-App Payments)
• Dwolla
• Square and Intuit GoPayment mobile card readers (one article discussing both since they are quite similar in many ways)

The final article in the series summarized and cross-compared each of the systems with each other and the PayPal X Platform.  It included a table of key features, availability information, pricing, and other details important for developers and merchants considering their payments options.  Please note that the table appears clipped in the HTML version in many browsers; to see the full thing, you can view it in the PDF version of the article (click here to access the PDF).

I’ve also created a bit.ly bundle summarizing and linking to all six articles in the series (available here).

If you read the entire series, you will understand the major payment system options available to you and be able to make recommendations on which system(s) would be appropriate for specified sets of payments requirements.

Click here to read the complete post on the PayPal X Developer Network including the key takeaways from the series.

PayPal X Platform

• My latest @PayPalX post: Which payment systems interest you? http://bit.ly/l3G1Qv (all feedback greatly appreciated) #
• Google Wallet commentaries http://bit.ly/iiJhmr via @paymentsnews #

Wireless and mobility

• Was just speaking with a friend about #mobile strategy for his business yesterday; timely gotchas to avoid http://oreil.ly/k4Acxt via @radar #

Running

• Ran 6.21 miles in 1 hour and 9 mins and 38 secs and felt great. Mile paces 8:25, 8:40, 8:37, 8:19, 8:32, and … http://dailymile.com/e/VEx2 #
• This @outsidemagazine article on persistence hunting http://bit.ly/iXrgcG is interesting from running, hunting, *and* anthropological angles #
• Ran 6.85 miles in 1 hour and 14 mins and 42 secs and felt alright. Tempo plus cooldown after. http://dailymile.com/e/VM6X #

So far, I’ve written articles discussing Amazon’s Flexible Payments Service (FPS), Facebook Credits, and Google payment technologies including Google Checkout and Google Wallet (read my related blog post from last week on the latter by clicking here).

My articles look at the strengths and weaknesses of each of those systems, and especially how they compare to PayPal-based development and deployment.  For instance, FPS provides a similar sandbox-based development and testing environment to PayPal’s Sandbox and provides somewhat similar functionality to PayPal’s Adaptive Payments, but it is limited to merchants and consumers with Amazon accounts.  Similarly, the Facebook Credits API is similar in functionality to PayPal’s Express Checkout, but  is only usable by Facebook Platform-based applications whereas Express  Checkout can be used with applications built for any proper  Internet-ready application container and environment.

The series explores those points and much more, even down to the level of payment flow through some of the alternatives (example:  Facebook Credits as pictured below).

Click to read the complete post on the PayPal X Developer Network including information on other systems to be considered and a request for your input on them. You can also access the included survey directly below: