IFTTT finally releases its own API, sort of, with “Maker channel” triggers

IFTTT finally just released its own API (sort of) when it announced the introduction of its new “Maker” Channel which may very well be the closest we ever get to a true API. It offers HTTP-based activation of Actions to carry our when invoked or Triggers which can be combined with another service.
The Maker Channel extends the power of IFTTT to any DIY project, big or small,” said the company in a recent blog post. “You can now build and connect Recipes to any device or service that can make or receive a web request.”
Since launching nearly four years ago, If This Then That (IFTTT) has provided a web-based platform for “thing” integration towards realizing the promise of the Internet Of Things (IoT) helping to make our lives simpler rather than more complicated as it often does as new technologies continue to be introduced.
For a quick refresher from my previous post on IFTTT’s role within the Internet of Things, it enables its users to authenticate/authorize and inter-connect a variety of tools, devices/sensors, applications and web services through unique “recipes” that are based on an “if this happens, then do that” formula. These could accomplish anything from the serious (such as automatically receiving a text message if suspicious activity is picked up by your home surveillance system), to the fickle but convenient (for instance backing up photos uploaded to Facebook which have a particular tag to a dedicated Dropbox folder). Recipes like these have all been created by the community and are free to use (unless you wish to mark your recipe private, and either way the data you enter into your recipe of course stays private and only a template of it is shared)
Dusting off my 2008 cover letter to RIM on BlackBerry’s future, rejected job application

While backing up some files to an external hard drive from my older one, I recently came across an old Cover Letter which had accompanied my resume in a job application I sent to Research In Motion (RIM) back in Summer of 2008.
It’s interesting to look back at, because I recall back then being very frustrated with the state of the Mobile industry in North America (particularly in Canada). These feelings were only magnified by my time spent in Japan 2006-2008, a country which at that time was a clear leader in Mobile technologies and in the global consumer electronics in general. Since then, Korea and China (two other countries I was fortunate enough to have spent some time in during my Graduate school vacations in between terms) have now caught up in terms of innovation and even surpassed Japan’s leading Mobile technology companies in sales as well.
Back then companies (again particularly China & Korea but many European firms as well) were sending some of their top experts and technologists to Japan to do market research with and/or attempt to poach talented Japanese engineers from, the likes of world leading Japanese tech companies: Sony-Ericsson, Panasonic, Sharp, Toshiba, Hitachi, Mitsubishi, Fujitsu, Fuji-Xerox, Konica-Minolta, Nintendo, Softbank, NTT, KDDI, etc. The goal was of course to glean as much information and consumer insights as possible from the country which boasted the fastest home fiber internet speeds, mobile internet speeds, mobile data usage, and mobile revenue per unit (ARPU) in not just gaming which usually comes to mind when thinking of Japan, but all application sectors.
My experience in Japan indeed taught me a thing or two about “sticky” services, particularly the infamous “iMode business model” by Takeshi Natsuno of NTT DoCoMo which succeeded by providing a cohesive ecosystem of applications and a flat-rate (about $40 USD/month) unlimited data service, which drove subscriptions through the roof. On top of this, standards and specifications which were simple to follow for developers and which reduced page-size for web content with cHTML then later WAP/WML helped grow the service’s offerings in an organic way. Only now are we starting to see the same sorts of initiatives by Google [LINK] & Apple [LINK] in North America. Over here, very little regard has been made for how to optimize mobile services for users, which is why our Mobile industry is only now catching up to and finally surpassing where Japan was 9-10 years ago. Indeed, we constantly hear reports about the growth of Online/Mobile Video (i.e. streaming ad-supported content like YouTube, Vimeo, etc), On-Demand/IPTV (i.e. rentals or purchases on iTunes, GooglePlay, etc), and OTT (i.e. subscription services like Netflix, Hulu & Amazon Prime Instant Video). However, MobileTV via OneSeg had already reached millions of users whereas SMS texting was just starting to take off in North America (in any meaningful way that resembles its adoption level today).
Speech Recognition – Apple’s Siri (iOS)

Speech Recognition really hit the mainstream when Apple acquired the company and technology behind Siri, a voice-activated virtual assistant.
BC$ = Behavior, Content, Money

The goal of the BC$ project is to raise awareness and make changes with respect to the three pillars of information freedom - Behavior (pursuit of interests and passions), Content (sharing/exchanging ideas in various formats), Money (fairness and accessibility) - bringing to light the fact that:
1. We regularly hand over our browser histories, search histories and daily online activities to companies that want our money, or, to benefit from our use of their services with lucrative ad deals or sales of personal information.
2. We create and/or consume interesting content on their services, but we aren't adequately rewarded for our creative efforts or loyalty.
3. We pay money to be connected online (and possibly also over mobile), yet we lose both time and money by allowing companies to market to us with unsolicited advertisements, irrelevant product offers and unfairly structured service pricing plans.