Skip to main content

Things in Need of a Feed

Syndicated feeds are much bigger than blogs and news stories; they're aplatform.  A bunch of use cases, several of which actually exist in some form, others just things I'd like to see:
Addendum 11/11:

Comments

  1. Not just comments, but things I post to newsgroups, discussion boards etc.etc.

    ReplyDelete
  2. John, you wrote:
    "News stories matching a custom filter I've set up". At http://pubsub.com/ we provide the ability to create free custom filters ("subscriptions") for matching content in blogs, newsgroups, SEC Edgar Filings, Press Releases, and FAA Airport alerts. In the future, we'll be supporting many more types and sources of data.

    Your general point reminds me very much of an article in the June 2004 Harvard Business Review "Feeding Time" by Paul Kedrosky. He wrote: "Every time eBay lists a new book, FedEx touches a package, or Proctor & Gamble changes a price, the act generates data. But most of that information isn't easily accessible, despite its immediate value to someone, somewhere. That's about to change. Soon, any data-generating act, no matter how trivial it may seem, will be released over the Internet in real time to anyone who wants to know about it. This isn't wide-eyed speculation. It's already happening, and it will change how companies and customers do business. ... These broadcasts take the form of syndication feeds..."[1]

    While I think Kedrosky may be exaggerating when he says "*any* data-generating act" will be syndicated, his general point is an excellent one. We're soon going to see much, much more data available in real time via the magic of syndication. Now, all we have to do is figure out is how to use and filter all this new data! Hopefully, PubSub.com will be able to help a bit.

     bob wyman

    [1] Reprint F0406A
    http://harvardbusinessonline.hbsp.harvard.edu/b02/en/common/item_detail.jhtml?id=F0406A

    ReplyDelete

Post a Comment

Popular posts from this blog

Personal Web Discovery (aka Webfinger)

There's a particular discovery problem for open and distributed protocols such as OpenID, OAuth, Portable Contacts, Activity Streams, and OpenSocial.  It seems like a trivial problem, but it's one of the stumbling blocks that slows mass adoption.  We need to fix it.  So first, I'm going to name it:

The Personal Web Discovery Problem:  Given a person, how do I find out what services that person uses?
This does sound trivial, doesn't it?  And it is easy as long as you're service-centric; if you're building on top of social network X, there is no discovery problem, or at least only a trivial one that can be solved with proprietary APIs.  But what if you want to build on top of X,Y, and Z?  Well, you write code to make the user log in to each one so you can call those proprietary APIs... which means the user has to tell you their identity (and probably password) on each one... and the user has already clicked the Back button because this is complicated and annoying.

The problem with creation date metadata in PDF documents

Last night Rachel Maddow talked about an apparently fake NSA document "leaked" to her organization.  There's a lot of info there, I suggest you listen to the whole thing:

http://www.msnbc.com/rachel-maddow/watch/maddow-to-news-orgs-heads-up-for-hoaxes-985491523709

There's a lot to unpack there but it looks like somebody tried to fool MSNBC into running with a fake accusation based on faked NSA documents, apparently based on cloning the document the Intercept published back on 6/5/2017, which to all appearances was itself a real NSA document in PDF form.

I think the main thrust of this story is chilling and really important to get straight -- some person or persons unknown is sending forged PDFs to news organization(s), apparently trying to get them to run stories based on forged documents.  And I completely agree with Maddow that she was right to send up a "signal flare" to all the news organizations to look out for forgeries.  Really, really, really import…
Twister is interesting.  It's a decentralized "microblogging" system based on putting together existing protocols:  Bitcoin, distributed hash tables, and Bittorrent.  The most interesting part for me is using Bitcoin for user registration and spam control.  Federated systems handle this with federated trust, which is at least conceptually simple.  The Twister/Bitcoin mechanism looks intriguing though I don't know enough about Bitcoin to really comment.  Need to read further.