Skip to main content

AOL Pictures Beta and woohoo

In conjunction with the new Pictures Beta, there's a cool tool called woohoo which displays a an AIMPages picture gallery in a widget, embeddable anywhere.  Fun stuff...  for example:


  1. John I thought you could only use in your aim profile.  Is there way to add to your journals now?


  2. The tool lets you embed your AIMPages album pictures anywhere.  First you need to create them on your AIMPages profile, then they're available to woohoo... or on woohoo...  not quite sure if it's a verb or a noun.  Anyway, the woohoo web site shows how to copy and paste the HTML into Journals or elsewhere.

  3. Why keep it to AOL pics only?  This is an awesome widget, and I'd love to use it, AOL branding and all, but all my pics are on Flickr.  It would be great for someone to make a cross-platform photo widget that allows anyone... Flickr People, AOL people, Photobucket people, to pull in their pictures.  That would be the one I would use.

  4. We are working on a couple of things : 1) to allow upload directly from the woohoo page.  2) to allow pictures from other photo sites to be put into woohoo... stay tuned!


Post a Comment

Popular posts from this blog

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:

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…

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 hill outside Google HQ, about a 270 degree panorama.