Author: Greg Swann (page 42 of 209)

by Greg Swann

Suburban Phoenix Real Estate Broker

Author website

Across all products is important. Across all devices is vital.

Drudge and the privacy geeks are going typically apeshit, but Google is playing my tune:

“If you’re signed in, we may combine information you’ve provided from one service with information from other services,” Alma Whitten, Google’s director of privacy, product and engineering wrote in a blog post.

How might that work?

For instance, a user who has watched YouTube videos of the Washington Wizards might suddenly see basketball ticket ads appear in his or her Gmail accounts.

That person may also be reminded of a business trip to Washington on Google Calendar and asked whether he or she wants to notify friends who live in the area, information Google would cull from online contacts or its social network Google+.

Hell, yeah! Those are the kinds of jobs I want from Sarah, your software secretary, but I can show you a very cool Constance the Connector connection here, as well.

How about I start a music service that seeks to sell you music that you will probably like and don’t already own. “Don’t already own” is an easy database from iTunes or whatever. But “will probably like” requires analysis — algorithm as art — and that’s what makes my business model work. To you-as-end-user, it feels like I know you, like we’re high-school buddies whose friendship is built around grooving to the same tunes.

How could I do that? Let me see your YouTube history, not just what you picked but how many times your replayed particular songs. Let me see your Amazon.com shopping history — especially the things you come back to again and again but don’t buy. I don’t need to know you. You already know you better than anyone else ever could.

That’s what we’re actually talking about, you collecting facts about yourself for future reference. Like a bad comic, Google can make anything sound dirty, but there is nothing wrong with you getting more of what you want — better, faster and cheaper.

Do you understand? Your fears, assuming they are real, are misplaced. The U.S. Government now has the lawful authority to assassinate you at will in Read more

by Greg Swann

Suburban Phoenix Real Estate Broker

Author website

It’s been a few weeks since I started talking about Constance, and since then I’ve come up with a completely different way of thinking about operating systems. There are three players who could profit from my thinking — Apple, Google and Amazon — and I would be more than happy to share my thoughts to the first one of those three who salutes.

Meanwhile, I give you Constance, which is in some ways the logical counterpart to Heidi, the self-maintaining CRM system I started talking about last August. Constance the Connector is a server-based service that maintains your handle — a topic we have discussed before.

So: Here are ways you can know of me:

• By name
• By street address
• By phone number
• By email address
• By Twitter handle
• By social media profile
• etc.

For now, if you want to address me by one of those means, you have to know the specific proper noun to be used — my actual name or my current email address. You are responsible for maintaining that information, and everyone who wants to make contact with me must do the same redundant and error-prone maintenance.

A Heidi-like CRM can do some of the maintenance by means of assiduous, arduous data-base mining. But if I don’t make my new street address public somewhere, your of-course-I-haven’t-forgotten-about-you greeting card is going to bounce.

There’s more: The way things work now, I have no control over who addresses me or how. I’m not just bitching about spam. I want cold-calling salespeople to go straight to voicemail — and when I have determined that I don’t want to hear from a particular caller again, I want never to hear from that person ever again.

So think of me this way, instead: @gswann. That’s my handle: @gswann. Sending em an email? Send it to @gswann. Want to try to get me on the phone? Dial @gswann. Snailmail? Send it to @gswann, you dinosaur. Want to pull my LinkedIn profile? It’s @gswann.

That much is just the handle idea — but with a twist. What we’re doing with the handle @gswann is sending a request to the Constance server for the current mission-critical contact information associated Read more

by Greg Swann

Suburban Phoenix Real Estate Broker

Author website

I first thought of the idea of an anticipator as hardware, I kid you not. The early 1980s? Software was dear in those days, but early computer-on-a-chip chips were cheap and abundant. There still would have been a software component to an anticipator, of course, but not much.

Here’s what I thought about then: Anything that could be monitored by signal processing — as, for example, the communication between a micro-computer and its peripheral devices — could have an anticipator in-line, monitoring all the signal traffic back and fourth. By maintaining a probabilistic database of past events, the anticipator could, over time, evolve strategies for anticipating resources likely to be called for in the near future, and, using otherwise dead time on the computer’s data bus, cache that data in advance, eliminating time lost on fetch requests made in real time.

Wow! How kludgey our world used to be! In the bad old days, there were pre-fetch routines built into operating systems, but they were a brute-force solution to a vast array of very small, fussy problems. An anticipator would strive to be optimally efficient and mission critical by dealing only with the specific data most likely to be requested.

An example? If a font required for a document is not stored on your printer, the printer must fetch the outline data from your hard disk. It’s a small job, on its own, but you could maximize your productivity from the printer if those fetch calls in real-time were ameliorated by intelligent pre-fetching. The anticipator could both maintain the most-often used outlines in the printer’s memory as well as anticipating exceptions to the everyday rules — for example, by keeping the boss’s favorite Christmas font on the printer from Thanksgiving through Christmas. That implies real secretarial smarts, but it’s simply probabilistic database mining being perfected over time.

So what about now?

Antoinette the anticipator harkens back to Heidi and Sarah, and to Constance, which I haven’t gotten to yet.

Imagine an anticipator function in Sarah that, when Sarah figures out that you are going to be late for a meeting, sends out all the appropriate notices, all Read more

by Greg Swann

Suburban Phoenix Real Estate Broker

Author website

The big buzz in the mobile computing biz is augmented reality, your phone or tablet takes in a scene and then echoes back to you what it can infer from an image and its GPS coordinates, compass direction, etc. This may be cool, or it may be cool like a QR-code, an idea whose time will never come.

Augmented reality will be that much cooler when it’s like Arnold-the-Terminator’s eyes, but that illustrates the key defects of the idea, as it is currently implemented:

Augmented reality is not done continuously but only on demand, and only in static and affected ways.

And, in consequence, it’s not doing anything terribly useful, except possibly in vertical market applications.

But reflect that an iPad can run continuously for 10 hours without recharging. Next year’s models may double that number. Soon you will get reminders to plug in, or your devices will find ways to provide for themselves while you’re asleep.

So instead of a truly amazing augmented reality presentation on the Black Hills of Dakota, how about a piece of software that watches you and your life all the time, and augments your activities however it can.

This harkens back to an idea I’ve brought up before, a hypothetical self-maintaining CRM called Heidi:

An email comes in over the transom. The spambot says it’s not spam and the sender is not already in your CRM database, so let’s extract as much information as we can from the email. With a name and an email address we can probably get the sender’s full contact information, and possibly a whole lot more.

Make that first contact a phone call instead. Caller ID is lame, but Google is not. From the phone number, can you get back to a name? A location? From those, can we effect the same kind of searches discussed above?

There’s more: Once your CRM knows a name, it should be watching for any changes in publicly-available databases that should be reflected in your private CRM database. That is to say, your CRM should be maintaining itself.

Sarah’s going to monitor every phone call, of course. She or Heidi should be doing all Read more