Wednesday, May 16, 2012

OpenWeb 05/17/2012 (a.m.)

  • After reading this article i gave a try.  It's very simple to sign up different networks like Facebook, Disquis, Tweeter, G+, Tumblr, LinkedIN and FourSquare.  But there doesn't seem to be a way to add my bookmarking network, Diigo?  Still, Engagio looks like a very useful service.  No idea how they plan on making money :) excerpt: The killer app for the social Web is the one that will filter the signal from the noise. In the Facebook age, even casual Web users hold tons of conversations at once. Engagio, the conversation discovery company, pulls them all into one place. It also leads you into new ones. And with a new dashboard view released today, it lets you click one button to figure out what's actually going on in all these conversations. Engagio's dashboard breaks out articles, sites and other links from all your social networks into separate panels, and lets you reply, share and like straight from there. But the best part of this section is the "context" button.

    Tags: engagio, social-networks

  • Nice infographic!  Shows that great transition from Windows desktop client/server to Cloud Computing is well underway.  I've tried RingCentral, and it's very good.  But i much prefer Google Voice - especially since i have an HTC Android.  RingCentral only offers one advantage over gVoice; they have integrated fax.  Everything else about RingCentral seemed like a throwback to DOS applications.   gVoice is slowly evolving.  Seems like it's taking forever to complete the integration with gMail, gSearch, and gDocs.  But i can see the incredible potential of Cloud integrated communications, content and collaborative computing.  gVoice has a potential like no one else. excerpt: The results are in from our annual smartphone survey! We polled 300 RingCentral SMB customers about their mobile device adoption and cloud use. The key takeaway: 57% of business owners said the majority of their business-critical applications currently run in the cloud.

    Tags: gVoice, RingCentral, Cloud-Computing, Cloud-Productivity, Cloud-SMB, Great-Transition, InfoGraphic, Graphic

  • Fascinating conversation between Douglas Crockford and Jeremy Geelan. The issue is that XSS - the Cross Site Scripting capabilities of HTML. and "the painful gap" in the HTML5 specification of the itnerface between JavaScript and the browser.I had to use the Evernote Clearly Chrome extension to read this page. Microsoft is running a huge JavaScript advertisement/pointer that totally blocks the page with no way of closing or escaping. Incredible. Clearly was able to knock it out though. Nicely done!The HTML5-XSS problem is very important, especially if your someone like me that sees the HTML+ format (HTML5-CSS3-JSON-JavaScript-SVG/Canvas) as the undisputed Cloud Productivity Platform "compound document" model. The XSS discussion goes right to the heart of matter of creating an HTML compound document in much the same way that a MSOffice Productivity Compound Document worked. The XSS mimics the functionality of of embedded compound document components such as OLE, DDE, ODBC and Scripting. Crack open any client/server business document and it will be found to be loaded with these embeded components.It seems to me that any one of the Cloud Productivity Platform contenders could solve the HTML-XSS problem. I'm thinking Google Apps, Zoho,, RackSpace and Amazon - with gApps and Zoho clearly leading the charge. Also let me add that RSS and XMP (Jabber), while not normally mentioned with JSON, ought to be considered. Twitter uses RSS to transport and connect data. Jabber is of course a long time favorite of mine.excerpt:The fundamental mistake in HTML5 was one of prioritization. It should have tackled the browser's most important problem first. Once the platform was secured, then shiny new features could be carefully added.There is much that is attractive about HTML5. But ultimately the thing that made the browser into a credible application delivery system was JavaScript, the ultimate workaround tool. There is a painful gap in the specification of the interface between JavaScript and the browser, and that is a source of XSS and other maladies. The responsible course of action was to correct that defect first.That course is still available to us. My recommendation is that we suspend the current HTML5 activity. We start over with a new charter: To quickly and effectively repair the XSS vulnerability. Then we can mine the bloated HTML5 set for features that have high value and which do not introduce new security vulnerabilities.HTML5 has a lot of momentum and appears to be doomed to succeed. I think the wiser course is to get it right first. We have learned the hard way that once an error gets into a web standard, it is really hard to get it out.

    Tags: Douglas-Crawford, HTML5-XSS, XSS, compound-documents

Posted from Diigo. The rest of Open Web group favorite links are here.

Post a Comment