I can hard code a static page but then I would lose the Facebook integration; I want a lot I know.
Live streaming is really live, like in live TV.
Content is streamed out of a live encoder (in my case Wirecast) and uplinked (NOT uploaded) to a streaming server(Like Adobe FME, Wowza, Red5) tipically hosted at a CDN. The streaming server "reflects" the uplinked stream to clients, which in the case of RTMP are Flash players.
This is where Flowplayer and its RTMP plugin come in; as per the JS snippet in my first post in this thread, it needs to be told the rtmp:// URL and stream descriptor.
My proposed solution is adding a dummy extension (e.g. *.rtmp) to the list of extensions the Flowplayer plugin intercepts, and storing the Live parameters in the database. This will produce a proxy (fake) entry in the gallery/local storage that other plugins can refer to (I care about the ZenFBsuite at the moment).
I know I'm bending zenPhoto into shape to suit my needs, so I understand if you won't take on such development; it was proper form to ask, since you are the author of the plugin. Currently my installation uses a private branch (with zp-core hacks) out of the [5736] build. If I keep hacking away on that build I doubt my additions will ever make it back to the mainline.
I'm decent at hacking something quickly but have no deep understanding of ZenPhoto's architecture (and I'm working on pre 1.4 code, so I'm behind the mainline anyway). On top of that I'm in the business of TV/video production, so zenPhoto was just a technology choice for my site.
Not sure how to go forward, as I would like to stay reasonably in sync with the mainline.