I agree - I was thinking the same thing. Using 3rd party gadgets is sort of like deep linking images from another website. Except, a gadget disappearing is much worse than an image disappearing.
I'm not sure what the right answer is. -J On Fri, Oct 22, 2010 at 10:46 AM, David Ahearn <[email protected]> wrote: > It's back alive. Interesting risk in the architecture... While it is > relative easy to build a similar capability, it's not a great > solution, sort of like "yeah, your brakes are shot. The good news is > setting up a brake pad factory in your backyard is pretty easy!" > > On Oct 20, 4:15 am, Vega <[email protected]> wrote: >> It is not that hard to make a similar extension. If i get it correctly >> - it takes URL as input and then displays the contents in an IFRAME. >> >> On Oct 20, 7:44 am, Joseph Gentle <[email protected]> wrote: >> >> > You could probably grab google's cached copy of that gadget and >> > re-host it yourself. >> >> > -J >> >> > On Wed, Oct 20, 2010 at 4:38 PM, Alex North <[email protected]> wrote: >> > > Hi David, >> > > wave-ide.appspot.com is not a Google-owned application. We've contacted >> > > the >> > > author but generally don't have any ability to fix it for you. >> > > Alex >> >> > > On 20 October 2010 14:08, David Ahearn <[email protected]> wrote: >> >> > >> Group, >> > >> I know this the wrong forum but I can't find any other Wave group or >> > >> resource that looks monitored by anyone with any consistency, and I >> > >> figure at the very least you guys are still using Wave. Apologies >> > >> ahead of time and I'll buy the answerer a beer in San Fran for at Wave >> > >> conference (if my request is accepted!) >> >> > >> We (at BluestoneLogic) use Wave for all internal comms (exclusive of >> > >> email) and suddenly our waves that use iFrames are failing with the >> > >> following error: Unable to retrieve spec for >> > >>http://wave-ide.appspot.com/iframe.xml. >> > >> HTTP error 404. >> >> > >> All our users are seeing this and it killing us because we use iFrames >> > >> to embed box.net previews into our waves to avoid pushing attachments >> > >> around and centralize doc management. If you care why we don't use >> > >> Google Docs I can outline why we went the box.net direction for a >> > >> business. >> >> > >> Are you guys seeing this too? There is no news I can find anywhere >> > >> and this has us at full-stop, and wave risk appearing very high. >> >> > >> We are using Wave as part of our Google Apps Suite. >> >> > >> Many thanks, (moderators please don't blitz this!) >> > >> -Davey >> >> > >> -- >> > >> You received this message because you are subscribed to the Google >> > >> Groups >> > >> "Wave Protocol" group. >> > >> To post to this group, send email to [email protected]. >> > >> To unsubscribe from this group, send email to >> > >> [email protected]. >> > >> For more options, visit this group at >> > >>http://groups.google.com/group/wave-protocol?hl=en. >> >> > > -- >> > > You received this message because you are subscribed to the Google Groups >> > > "Wave Protocol" group. >> > > To post to this group, send email to [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected]. >> > > For more options, visit this group at >> > >http://groups.google.com/group/wave-protocol?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
