Nifty. I’ve been looking at ways of allowing an organization’s supporters to syndicate their content; Bitty has a neat take on it.
Let’s see how this works for, say, a political party’s newsfeed:
Or for allowing others to display it on their sites:
Why, yes — I’d LOVE to speak at your event
Public speaking and speechwriting: the essential guides
Looking for advice on public speaking, speechwriting and leadership communications? Here are some of my most comprehensive posts, on topics that people ask me about most often.
I see that the iframe tag they provide you with has a url pointing to their site. Seems that “embeded browser” might just be a fancy name for an iframe?
Yikes! Best of luck to them. Hope they have a good server cluster.
In fact, this is the essence of their “embedded browser”:
iframe width=”400″ height=”500″ src=”http://b1.bitty.com/browser/”
At first I though maybe bitty serves up an html page that loads into the ifmame with javascript that controls either another iframe or a frame? Looks like they have the right-click menu disabled so it is hard to tell. Thinking more… I am not even sure this requires and DHTML? You would only need javascript that sets the href for the frame/iframe, no DHTML. Hmmm, wait the “Menu” and “Open URL” pages in are just served up from bitty and loaded into the iframe.
http://b1.bitty.com/browser/openurl/
http://b1.bitty.com/browser/menu/
Wait, these are ASP server pages! Try:
http://b1.bitty.com/browser/openurl/?a=0
These pages are passed the id you included on the iframe url “a=0824903D…”. Hmm, and “openurl” has a cleverly hidden form that posts your url request back to bitty with the id.
I smell smoke… and mirrors.
The fact is that anyone skilled in javascript and html can implement the functionality of the bitty browser with an iframe, some basic javascript, and a couple of html pages hosted on their own server. One of the authors, Scott, claims good intentions, but I can’t see any reason for the use of server side processing.
Why track the user requests at all? Why submit each request to the bitty server in an obscured form hidden in the openurl page? Why not just serve the frame wrapper, menu, toolbar and openurl pages as static html pages? Anyone could then install the code on their server, without the need for the bitty server at all.