Well, we have TrackBack, Pingback, and RSS, so I just continued that line of thinking.
For example, you have a site like LazyWeb, which is intended to passively aggregate content via a somewhat sideways use of TrackBack. At the moment, the page contains a list of links and excerpts. However, I think it might actually be better served by having entire entries posted to the site, along with links back to the original entries. That way LazyWeb readers can be even lazier. There would be no need to actually click one more link to go and read the entry in its entirety. That is what I would like to call PostForward (I thought remotepost might be a better name, but that may have some problems. Maybe Stickee would work?).
The other side of this idea is what goes on when somebody leaves a comment. Say I go ahead and sent an entry to LazyWeb via PostForward (or remotepost, or Stickee, or whatever we call it). That entry appears in its complete form on the LazyWeb site. Why force people to browse over to my site just to leave a comment? They can do that if they want to read more of my content, but if they only wish to leave a comment that seems a little silly. This is where CommentBack (or maybe ComeBack? LOL) comes in. When somebody leaves a comment on the entry at LazyWeb, a CommentBack connection is made from the LazyWeb site to mine, containing all of the comment data (timestamp, author, email, site, and comment text). This comment can then be displayed in my site's list of comments for that entry, along with a link to the site from which it orginated.
Now that I think about it, this type of system would be perfect for News Aggregators. The content is aggregated for the user already. They could just leave a comment in the aggregator itself, which would then be forwarded on to the site hosting the entry, which could then be forwaded on to the originating site if that entry was posted there via PostForward, and so on.
; "Feed Stats Widget")
; "Google Referrer")
; "MediaConsumer Template Output")
; "MediaConsumer List Items")
; "MediaConsumer Edit Item")
; "mt-qotd.png")
; "Vox-qotd.png")
The main obstacle to this is the way Movable Type is set up. The amount of text sent out in a single ping is 252 characters plus an ellipse. Some custom solution would have to be worked out in the meantime if the post-it solution were to work. I do like it, though, don't get me wrong - personally, I think it's great. (Personally, I think the LazyWeb should just be a collaborative blog which can be posted to via xml-rpc.... but I'm getting ahead of myself again. ;))
People implementing Trackback could just ignore that limit, if they're implementing it as a remote comment feature. The ping handler should realize that the client might have given it more input than it wants to allow, and truncate it to whatever it likes.