See http://www.openparenthesis.org/2008/03/06/tripit-to-dopplr-auomtation

which outlined how to link TripIt and Dopplr this way back in March of last year.

Or, better, a discoverability hook analogous to:

<link rel=”alternate” type=”application/rss+xml” title=”RSS 2.0″ href=”http://blog.jonudell.net/feed/” />

I haven’t tried Google Wave yet. But I wonder if the way I’m using FriendFeed here — http://friendfeed.com/elmcity — points toward the architectural shift you envision.

I’m working with people, namely curators for my project, and resources, namely calendar (ICS) feeds. Because I’m also using delicious to curate the ICS feeds, and because I’ve subscribed to the curatorial accounts on delicious from the elmcity room, there’s a webhook-like alert mechanism. When a curator finds and adds a new ICS feed, the room hears about it via an RSS feed.

The relevant constraint here is: “produces, and/or consumes, feeds”.

The “gadgets” are services that obey that constraint.

The “robots” are services that aggregate/slice/recombine “gadgets”.

In a wave you bring together a problem and some people. They can write about solutions and they can add gadgets and robots that help.

A gadget is any useful snippet of the web.
A robot is any useful software function.

Specific sets of gadgets plus robots solve the problem and are then useful elsewhere, as parts and whole.

Standards for wiring will emerge from hacks in the ecosystem of these component parts. The strategic move is shift to a standard frame for making modules.

The web architecture we know is underconstrained. The solution is not interchange standards, but such an architectural shift.

Now, even though Popfly has disappeared (or will do), anyone that built a Popfly mashup and “installed” it will continue to be able to use that mashup. This fits with your scenario of Yahoo Pipes disappearing.

Of course, there were other problems that caused Popfly to fail but at its core it was an interesting idea which was wholly decentralised and that is an important facet. Shame really.

-Jamie

what if your dopplr or tripit or yahoo pipes or whatever you are using goes away unexpectedly? this could break a lot of stuff you have built.

it might take forever to restore things to a working state, particularly if you relied heavily on one service.

here’s what i think might solve this problem:
you log in to yahoo pipes and design a filter that takes feed A and creates feed B.

rather than the filter being stored at yahoo, the pipes create a small object that you can add to your website (or wherever) that performs that functionality. all that is needed now is for feed A to continue to exist.

now, yahoo pipes suddenly disappears, to be replaced by google hoses. you still have that one piece of functionality you created with the pipes, which still works since you didn’t store it at yahoo.

this would give you time to switch to google hoses for new filters, while old filters continued to work (and might even be able to be imported into google hoses for future editing)

so the filters get stored with your data — after all, you spent time creating them, so they are sort of a type of meta-data, right?

Whatever happened to Live Clipboard?
(http://blogs.conchango.com/jamiethomson/archive/2009/05/27/whatever-happened-to-live-clipboard.aspx)

-Jamie

*(not ‘the’)