The First Personal Platform—for Everything

Maybe the biggest thing that ever happened to Linux — at least scale-wise — is virtualization. As I recall, virtualization first materialized in a big commercial way with IBM, which started by putting many Linux instances on System z mainframes. (Once on the old Linux Show we had a guest geek from IBM who said it was not only his idea, but that he came up with it over lunch.) They didn't call those mainframes "clouds," but that's what they hosted. Now we have clouds of clouds of Linux all over the place. Nothing could be more widespread and ordinary. (Of Netcraft's ten most reliable hosting company sites for June of this year, eight are Linux and two are FreeBSD.)

Now think about the Internet of Things, often abbreviated IoT. It is generally assumed today that the Internet of Things will require embedded smarts. But in fact any thing can have a cloud, whether the thing has embedded smarts or not. This insight comes to us from Phil Windley, the hacker-in-chief of Kynetx, a small Utah start-up with very big plans. (Disclosure: I sometimes consult them, as I do a number of other companies.) Phil is also the inventor and alpha maintainer of CloudOS, a small and simple cloud operating system for anybody and anything, including you and every thing you own. CloudOS is open source and GPL'd. So is KRL (kinetic rule language), the first language for programming on CloudOS (among other things), also first authored by Phil.

By abstracting intelligence away from physical things, we can unburden those things of the need to be intelligent in themselves. In fact, we can enlarge to absolute the variety of things that can have intelligence. Phil embodies this range in the word "pico", for persistent compute object. One of his is a pothole in front of his house. That pothole has brains in the cloud Phil gave to it, and that cloud is in Phil's personal cloud. To help demonstrate how this can work in everyday life, here is a list of things I've made smart by giving each its own cloud:

  • Canon 5D camera body
  • Canon 30D camera body
  • Dish Network VIP 922 set top box, with Slingbox
  • Eurorack UB802 audio mixer
  • LaCrosse Technology BC-9009 battery charger
  • Sangean PR-D5 radio
  • Delkin Sensor Scope
  • Ful backpack
  • InFocus Model LP-130 projector
  • Teac model HD-100 HD Radio receiver
  • Sirius Sportster satellite radio receiver
  • Garmin Legend HCx GPS
  • A 30" x 30" tablecloth that looks like a QR code

Figure 1. Doc's 30" x 30" tablecloth looks like this QR code.

The doors to those things' clouds are the QR codes I've hung or stuck on them — and, in the case of the last one, the item itself is a QR code. There can be other doors as well (e.g. URLs), but QR codes are handy because: a) as with Ethernet, the patent owners (Denso, in Japan) decided they would rather create more value than they capture, so let anybody do anything they want with QR codes; and b) they're easy to scan with a smartphone.

Until now QR codes have had the misfortune of being exploited mostly by marketers, which is why they appear as "robot barf" on promotional jive all over the place. But now it's time for the hackers to take over, which is what the ones working for Kynetx have done. They created a service called SquareTag, which hosts things' clouds. SquareTag's business model, for now, is selling hang-tags and stickers with QR codes on them. I'm using some of tags and stickers for the things in the list above. (Note that SquareTag isn't a silo. I can take my things' clouds, plus my own personal cloud, and put them wherever I want. That means I can self-host them, put them in DropBox, or stick them in some other cloud service.)

Through a feature called "safe and mine" you can present a message to any Samaritan who scans the QR code of a thing you've lost. For example, "This bag belongs to (your name). Text me at (your number)". From any computing device, you can write or change that message.

But here's the biggest thing: Every thing's cloud is a platform for relationship — between you (as the owner) and whoever else you welcome aboard: notably the companies that make and sell the things you've bought.

For example, I have messages waiting for the makers of many of the items above. Here are a few:

  • Canon — I'm in the market for a 5D Mark III when the price for a new one falls below $2500.
  • LaCrosse — I'll be glad to testify my love for the charger in any promo you want to run. It's the best charger I've ever used. The display also tends to flicker and fade. Is there an easy fix for that?
  • Sangean — Gave the radio a 5-star review on Amazon, but I won't buy another one like it unless it does HD too.
  • Garmin — Love the sensitivity and the UI. What I want are more than 10,000 waypoints in memory, and the ability to produce KML files.
  • Dish Network — DishAnywhere is a great system. That's mostly how I watch the VIP 922. What I'd like is to have access to all the menu items remotely through the browser UI and on the tablet app. Please notify me when that feature is ready. Thanks.

I can also advertise to the world, should I wish, some or all of what I say about those products in my cloud. Or I can restrict what I say just to the companies I invite into a relationship, such as the ones above.

Likewise any company (e.g. Canon, LaCrosse, Sangean and Garmin) can give every product they sell a unique cloud of its own, with its own QR code, and transfer ownership of that cloud to the customer along with the product itself. If the customer welcomes a relationship with the company, and the company agrees to the customers' terms of engagement (such as, "respect the privacy of this communication channel in the following ways"), the whole "own cycle" of a product becomes a much richer experience for both the customer and the company. The QR code then becomes what's called a "TalkTag." Meaning that its purpose is to serve as a way for the customer to signal his or her interest in talking to the company. For example, I can program the cloud of my Dish Network set top box to make a scan of its QR code send a message to the company saying I'd like a call from an agent to help me work through a problem. I've talked to call center people about this possibility and they love it.

What they love especially is that it's now possible to have a standard way for customers to relate to companies. The problem today is that every company's CRM (customer relationship management) system is a silo, each with its own silo'd "relationships" with customers, all of which are governed at call centers by IVR (Interactive Voice Response) systems, followed by scripted interactions when a customer gets through to a human being. If ways can be found to normalize the protocols of genuine relationship between companies and customers, the work of the call center can be made far more easy and efficient. In fact the only way that can happen is if the customer's side does the normalizing.

Once that happens, both sides can learn far more from each other, in far better ways. If the product is the platform for genuine two-way relationship, both company and customer are in far better positions to learn from each other. Companies can update manuals and provide notices of firmware updates. Customers can tell companies directly what's working or not working, how the product might be improved, and what new products the company might consider making.

We can also start to evolve past the current marketing system, by which makers and sellers labor constantly to entrap and coerce customers into restrictive dependencies. Communications inside silo'd coercive systems tends to be far more restrictive, and far less useful, than communications between free and independent parties who are ready and able to truly help each other.

At this point, as T.Rob says in his essay on page X, we're still at the beginning of whatever it is we'll make of personal clouds. CloudOS itself is about where Linux was in the months after Linus wrote " I'm doing a (free) operating system...". But the population of available hackers for personal cloud projects is several orders of magnitude larger than the one Linus wrote to. (You'll find many on the Personal Clouds wiki and list, hosted by the Personal Data Ecosystem Consortium.) Yet the challenge is remarkably similar: take something that has been purely corporate (in this case "the cloud") make it personal, and then ramp it out to everything it might conceivably work on, improving it along the way, and not stopping.

The result, if all goes according to plan, is a true Internet of Things, and the re-framing of business around fully useful relationships between customers and companies. Or, for that matter, between anybody and anything.


Doc Searls is the Editor in Chief of Linux Journal


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

may loc nuoc

may loc nuoc's picture

I really like what you guys are up too. Such clever work and coverage! Keep up the superb works guys I've you guys to blogroll. buying instagram followers provides quality social services. it is possible to buy followers on instagram.
may loc nuoc
Tủ sấy quần áo

thanks for the information

jinumm's picture

dinosaur onesie

miyazyn's picture

Buy Hot Animal Kigurumi Onesies Pajamas At Wholesale Price.
dinosaur onesie
stitch onesie


timemart's picture

I really like what you guys are up too. Such clever work and coverage! Keep up the superb works guys I've you guys to blogroll. buying instagram followers provides quality social services. it is possible to buy followers on instagram.

máy tập cơ bụng ab rocket twister
máy tập cơ bụng black power
máy tập cơ bụng ad rocket
may tap bung fitness

máy tập cơ bụng six pack care
máy tập cơ bụng
máy tập cơ bụng
máy tập cơ bụng
máy tập cơ bụng


cnbestmall's picture

++++ ++++

Paypal online order accept, FREE SHIPPING

Nike AIr max, Shox, Rift, dunk, blazer, air force 1 shoes: 48 USD

Nike free running shoes: 42 USD

D&G, LV, Gucci, parda DC, polo, puma, supra shoes: 42 USD.

Timberland boot: 50 USD

T-shirts (polo, ed hardy, lacoste,gucci, lv, etc) $28

Jeans (AF, armani, bape, BBC, CA, coogi, D&G, Diesel, Evisu, Levis, gucci, true religion, versace) 45 USD

Down Coat jacket parka vests (moncler, canada goose, barbour, parajumpers, woolrich) 168 USD-268 USD

++++ ++++

Not agree with you in some

NedToler's picture

Not agree with you in some details

Linux could rule microsift. I

Richard McKenzie's picture

Linux could rule microsift. I love linux OS. I can do anything and everything. But Microsoft has nothing but visual graphics. Its is true that In most cases, we will want some form of DC current.

anticipate the commodity will

mensagens para celular's picture

anticipate the commodity will be abundant easier to accept if you change the phrase: "any affair can accept a cloud" to read: "any affair can accept a almanac in a database".

Understanding something new

Doc Searls's picture

Yo, all.

Personal clouds are as new and strange as personal computers were in 1975. Cut them — and the people working on them — a bit of slack. Have you visited Have you read what Phil Windley — the Linus of CloudOS — has been writing about personal clouds, the IoT and the rest of what I'm talking about in this piece?

Damn the message and the messenger if you like, but please visit the sources.

Doc Searls is the Editor in Chief of Linux Journal


Doc Bonez's picture


I admit I still don't quite 'get' what Windley has here, but I feel like it is powerful.

Indeed the commenters whining about this need to visit the sources and kick the tires a bit before lamenting this. It could be quite different than at first glance.


Anonymouseketeer's picture

Uhm, that was not useful. What Doc seems to be talking about is not interesting to the vast majority of people. Why would I want to spend time on setting up a channel with providers of goods or services when such channels already exist? Why would a provider use MY (and everyone else's) channel, as that seems awfully inefficient?

It's early

Doc Searls's picture

Why would anybody want a car when a horse would do? Or a personal computer when one could have a mainframe terminal? Or word processor when a text editor will do? Why do anything that a vast majority isn't doing yet?

Can you name any technology that wasn't preceded by vast majorities (or the whole world) not using it?

This is new stuff. Follow the links and see what work is going on. As construction goes, it's foundation and framing work, not finishing.

Doc Searls is the Editor in Chief of Linux Journal


Joe@FleaBites101's picture

Touche, Mr. Searls.

With that said, there are numerous instances where old, outdated technology stuck around and beat the snot out of the new kid on the block - so to speak.

Mr. Obvious (and with apologies)

hyping the word 'cloud'

Kaustav Bose's picture

I don't understand why you are using the term 'cloud' here in this context. All you are saying is that there is a one step process of doing something (read about, send email, post a comment etc.) about the things you like. Smartphone apps have the capability to scan a QR code and direct you to a website which has a record about the item.

Now, what you are suggesting is that something more special can be done besides reading about the record. You now want to use the information about that thing in the record to do something special. So, in essence you want to be redirected to a website (a CGI script perhaps or even more modern like a REST call?) that enables you to do those special things. An automated single transaction with the website is what you are referring to and that that is what you just need to say, instead of using the word 'cloud'. Of course you get more attention to what you are saying by hyping it all up by using the word 'cloud' which is such a shame!

"Cloud" in use vs. hype

Doc Searls's picture

A couple points here.

First, the QR code is just a shortcut to a record in a space on an operating system on which programming can be done. The OS's space is defined, at least for now, as a personal cloud. It's not about being redirected to a website, and that's not what I'm referring to. Read my response to Randy Kramer's comment below, which sources recent hacking and annotation of work by Phil Windley. In it he visits the "cloud" issue as well.

Second, nobody using "cloud" in the context I describe in this post is trying to hype it. They are merely borrowing and bending a term already in common use. I think we can improve what we're doing there, but we need to crawl before we walk. Help is welcomed.

Doc Searls is the Editor in Chief of Linux Journal

Understanding the article

Randy Kramer's picture


I think the article will be much easier to understand if you change the phrase: "any thing can have a cloud" to read: "any thing can have a record in a database".

cloud vs/+ database vs/+ pico

Doc Searls's picture

That's a good point.

What we have here is the appropriation of a B2B term (cloud) for C2-anything use. We saw this with personal computing in the 80s and networking in the 90s as well.

Still, "cloud" itself is an awful vague term, by design.

Here is what Phil Windley writes about personal clouds and picos:

The term "personal cloud" has been used recently to describe everything from networks hard drives to cloud-based storage like Dropbox to much broader concepts. Consequently, I find the term "personal cloud" to be ambiguous.

Persistent compute objects, on the other hand, have very specific characteristics and are usable for much more than just a person's online storage. A pico has the following features:

  1. Identity—they represent a specific entity
  2. Storage—they persistently encapsulate both structured and unstructured data
  3. Open event network—they respond to events
  4. Processing—they run applications autonomously
  5. Event Channels—they have connections to other picos
  6. APIs—they provide access to and access other online services

A pico is a small, general-purpose, online computer. In practice they are usually virtualized for scalability's sake, but that's not a fundamental feature. Another way to think about picos is as objects (in the object-oriented programming sense) that have persistent storage and are always online.

In our implementation, picos run inside a container (similar in concept to a Java Web container) called the Kinetic Rules Engine, or KRE. KRE provides the underlying environment for picos to exist, execute, and communicate.

Picos supported by KRE are all programmed with rules, but rule-based programming is not fundamental. Rules are, however, the most convenient way to handle events. The rule language supported by picos in KRE is the Kinetic Rule Language, or KRL.

Picos are persistent in the sense that they exist from when they are created until they are explicitly deleted. Restarting the KRE container, for example, doesn't change the state of the picos for which is it is responsible. They come back online just as they were when the container was stopped.

This is like Linus scaffolding Linux, and describing it along the way, in 1991.

Doc Searls is the Editor in Chief of Linux Journal

I have worked with computers,

E's picture

I have worked with computers, more or less steadily, since 1981 and I have to say, with respect, that I have absolutely no idea what the hell this guy is talking about.

I've worked with computers,

E's picture

I've worked with computers, more or less steadily, since 1981 and I have to say, with respect, that I have absolutely no idea what the hell this guy is talking about.

Linux could rule microsift. I

seoseoer86's picture

Linux could rule microsift. I love linux OS. I can do anything and everything.
Lam dep, cong ty bao ve

Planet Security

planetsecurity's picture

Linux could rule microsift. I love linux OS. I can do anything and everything.
Cong ty bao ve will help you every thing when you need.

gald to hear that I was not

Moosa's picture

gald to hear that I was not the only one failing to make anything out of this article.

Follow the links

Doc Searls's picture

The article points to work that needs to be visited to be understood. I recommend doing that.

Doc Searls is the Editor in Chief of Linux Journal