[The subject of this topic sounds painful!]
Problem
People want to write about something — such as an image, a map, or a
movie — and not require readers to have to break the flow by clicking a
link to view the object. Instead, the author would line the object to
appear in the middle of the post.
Solution
GroupServer replaces recognised URLs — such as links to YouTube — with
embedded objects, such as the Flash movie player from the aforementioned
Google department. This would be done as part of the post-rendering
code. The same code already replaces URLs with links; the idea is to
extend this code to create a pluggable architecture of URL handlers.
Comments? Suggestions?
Sorry, that should read “the author would like the object to appear in the
middle of the post.”
Michael JasonSmith wrote:
> [The subject of this topic sounds painful!]
>
> Problem
> People want to write about something — such as an image, a map, or a
> movie — and not require readers to have to break the flow by clicking a
> link to view the object. Instead, the author would line the object to
> appear in the middle of the post.
>
> Solution
> GroupServer replaces recognised URLs — such as links to YouTube — with
> embedded objects, such as the Flash movie player from the aforementioned
> Google department. This would be done as part of the post-rendering
> code. The same code already replaces URLs with links; the idea is to
> extend this code to create a pluggable architecture of URL handlers.
How would this work if you used a text-only email client ? Presumably it
would require the sending of HTML emails ?
On Tue, 2007-08-28 at 15:22 +1200, Andrew Groom wrote:
> How would this work if you used a text-only email client ? Presumably it
> would require the sending of HTML emails ?
No, it would only affect the web-view (and even the web view would still
be styled in such a way to display the *actual* link).
It wouldn't work to send HTML emails, most clients, AFAIK, disable
object embeds (as required to display youtube videos for example).
I think this is a swell idea.
Mediawiki has a number of extensions which allow a wiki host to offer embedded
content. Mostly videos from third-party sites. However they all require a tag
of some kind. Press edit here: http://pages.e-democracy.org/Video
If GS can be smart enough to simply read the URL from videos on key services
and using their APIs embed a player in the web view (while simply passing on
the URL in text via e-mail) then you'd have the easiest forum tool out there
for sharing videos.
I would say you might want a limit on the number of videos displayed per post,
say three, to keep web view download times in check.
Displaying a small version of linked Flickr photos might also be nice, but
would probably not be used as much as an integrated thumbnail display of
uploaded photos straight to the group.
Also, a positive name might be Empowering Users to Share Related Third-Party
Content.
Finally, while renderring web feeds within posts probably doesn't make that
much sense (there are mediawiki and wordpress plugins that do this, but I don't
know how much they are used within posts/pages), this does raise the issue of
how to best raise the profile of group related "new" content. The group
"mashup" if you will. I could see the value in designing your embedding
framework to include evolving content. An example might be YouTube videos or
Flickr photos tagged "mnpolitics" which could be called the default external
"tag" for our mn-politics group. Note this pilot "mashup":
http://e-democracy.org/voices
Again, I think starting with post is great, but if the code can be leveraged
for content in pages down the road, I think you have a win win.
Steven Clift
On Tue, 2007-08-28 at 04:50 -0500, Steven Clift wrote:
> If GS can be smart enough to simply read the URL from videos on key
> services and using their APIs embed a player in the web view (while
> simply passing on the URL in text via e-mail) then you'd have the
> easiest forum tool out there for sharing videos.
As I said to Mike when we were discussing this ... I don't think it's
clearly a user-win, but it definitely has a coolness factor to it that I
think will be appreciated.
One thing that hasn't been addressed is this ... under what
circumstances should it detect special URI's? For example, when marking
up links we look for 'http://somelink.com/'. It doesn't matter if the
link is in the middle of the sentence, we still provide markup (because
it doesn't disrupt the flow).
The only sensible way I can think of doing image and video markup is if
the images are on individual lines, eg:
http://youtube.com/video
http://flickr.com/image
If we provide detection in the middle of lines it will disrupt the flow
of the text, and just make it look stupid. For photo and video posts, I
think individual lines will be fine -- I just wonder if users will
quickly pick up the 'rules'?
That sounds reasonable. Instructions might be as simple as:
"To display a video from YouTube, X, or Y, simply place the full link to that
video's page, including the http://, by itself on its own line."
I agree on the coolness factor. This will definitely give us a wow moment when
we show off our forums.
I agree with Richard, that detecting links on lines by themselves will probably
be the best URLs to detect; thankfully the formatting issues with long URLs
encourages one link per line.
I was thinking about the large load times too, Steve. Loading a number of Flash
movie-players should not cause too many difficulties: the movies are downloaded
separately, so there should be little difference to the user if there is one or
three players rendered. However, I do believe the user should be given the
option of what he or she sees, be it maps, players, or even HTML-formatted
posts.