Embedding Google Waves in LJ

[facelessentity]

Title
Embedding Google Waves in LJ

Short, concise description of the idea
Enable Google Wave to make a post in LJ, which also embeds an entire Wave in said LJ post.

Full description of the ideaBlogspot and Wordpress already have bots or plug-ins embed Google Waves into Blogpost or Wordpress posts, and it'd be great if LJ has something like that too

Comments

[azurelunatic]

http://code.google.com/apis/wave/guide.html has more detailed stuff.
Generally the problem with embedding general external stuff is that the stuff requires scripting in order to operate, and said scripting can be used to carry out malicious operations on LJ. Not being an actual dev myself and not having looked through the documentation fully yet, I don't know how much of a risk nor how hard it would be to do this right.

I know there are, additionally, plugins for the Wave itself, so it might be not just a matter of trusting Google Wave to not be malicious, and isolating stuff so that only the Wave stuff could get through and other random stuff that a user might put in either on purpose or as the result of being duped would not work, but also a matter of trusting Google Wave to not let plugins do malicious things to it and any website it might be embedded in.

Certain members of lj_userdoc already have accounts and have been collaborating happily, and wouldn't be

[azurelunatic]

http://code.google.com/apis/wave/embed/ appears to be more topical still.

[azurelunatic]

Aha, finally, the actual developer details: http://code.google.com/apis/wave/embed/guide.html

It does involve javascript. The wave loads only after the page has finished loading. It loads in an iframe.

The documentation suggests that it can be styled; in this case it could be styled to match your journal. http://code.google.com/apis/wave/embed/reference.html

I may have turned into a crotchety old man

[pinterface]

I don't want a rich, multimedia, interactive experience on my friends page. I want plain, boring, read-only text.

Re: I may have turned into a crotchety old man

[licon]

IAWTC. If I wanted all the fancy new Google stuff, I'd be on blogspot or MySpace right now. I like LJ as the journaling medium it is - text, with occasional pictures.

Re: I may have turned into a crotchety old man

[guitarnerdster]

Well, it would be optional... I would assume.

Re: I may have turned into a crotchety old man

[turlough]

Hear, hear!

[koulagirl666]

I'm not sure this is really necessary for LJ in this way, especially as it's going to be limited to a tinytiny group of people for a while

[azurelunatic]

There's a thing that lets one share a wave with the public, by adding a specified designated email address as a party to the wave

[koulagirl666]

I am glad that the wave won't slow the rest of pages down, but still.

I think the TOS issue that makes Waves distinct from other embeddable content is that things such as YouTube videos are static content, whereas the Wave is editable - there will always be content added, and it will be coming from other people, but being part of the top-level post. My suggestion of using the Wave code to make a new kind of post would limit the TOS issues as the content will be LJ-side.

[azurelunatic]

Given that the TOS frowns on linking to TOS-breaking content, I don't see that this is a new issue, still, as a link can already be to any kind of page, even one that is updated dynamically.

And even though YouTube videos are the usual example of embedded content, LiveJournal has changed from the whitelist model to running stuff in a sandbox domain. I don't know what of the things there are already that can be updated, but there probably are some. Since it's no longer whitelist-based, you could probably already theoretically embed content hosted on your own server, which means that you could control the file fully, so even though it's a static filename, the file at that name might not be the same.

Though I'm just nattering here -- someone from Abuse will probably wander over and say what's what, eventually.

[jai_dit]

I think it's a nice idea, but it may be too early in Google Wave's deployment to implement on LJ just yet.