269 karma · joined January 12, 2010
"Bridges to Web 2.0 technologies with JSON filtering and validation, support for REST verbs, and converting/bridging of REST and Web services."
http://publib.boulder.ibm.com/infocenter/wsdatap/v3r8m1/inde...
"An XML firewall is a specialized device used to protect applications exposed through XML based interfaces like WSDL and REST and scan XML traffic coming in and out of an organization. [snipped] XML Firewall is often used to validate XML traffic, control access to XML based resources, filter XML content and rate limit requests to back-end applications exposed through XML based interfaces."
Seems like they rewrote IE's engine using newer, lower-level, hardware-accelerated APIs to achieve better performance compared to earlier versions of IE. This is at the expense of dropping compatibility support for older versions of Windows. I think they are also saying, by avoiding the use of cross-platform compatibility layers, they were able to build a faster browser compared to their competitors'.
http://blogs.msdn.com/b/ie/archive/2011/04/12/native-html5-f...
http://www.networkadvertising.org/managing/opt_out.asp
When you opt out of a network, the participating network will assign you an opt out cookie. When you visit a website that indirectly loads these tracking pages, it will check to see if you have their opt out cookie. If you do, they will avoid assigning you their tracking cookie.
These tools basically help you manage and persist the opt-out cookies so that when you clear your browser's cookies, the browser doesn't remove these opt out cookies.
All the participating networks provide an URL that tell you whether or not you have their opt out cookie. If you do, they will redirect that request to: http://www.networkadvertising.org/verify/cookie_optout.gif
Otherwise, they will redirect you to image that says you have their tracking cookie. You can subsequently use javascript to inspect the dimension of the image to determine whether or not you have opt out of that network.
http://forum.developers.facebook.net/viewtopic.php?pid=19404...
However, FB did remove that specific example from their TOS.
Example: http://stackoverflow.com/questions/90924/what-is-the-best-ph...
Screen Scraping: http://code.google.com/p/phantomjs/wiki/QuickStart#Rendering
http://www.quora.com/Quora-User-Feedback/What-features-would...
Of all the suggestions, Khalid's suggestion seems most relevant to yours:
"I just signed up, and was a bit horrified to see 40 odd possible e-mail notifications I could receive. But I was disappointed not to see a link to an RSS feed of those notifications." (http://www.quora.com/Quora-User-Feedback/What-features-would...)
Note that his main suggestion is to have Quora provide RSS feeds in place of email notification as opposed to adding a button that lets users disable all email notifications.
Like I said earlier, their sensible default settings make this feature somewhat unnecessary.
Things that aren't publicly viewable are question comments and revision logs.
One recurring problem in creating real-time web applications is how to sync the display between browser windows/tabs amongst different users (and of the same user).
You can render the page, stream compact JSON data to the browser, and use the data to update the page with javascript. However, doing so likely require you to duplicate your server-side templates on the client-side. You can, of course, avoid duplicating your template code by only implementing them on the client-side. However, doing so will hurt your site's SEO because your webserver would now generate JSON data instead of rendered HTML that search engines understand.
Duplicating template code increases complexity while removing duplicate code using client-side-only templates hurts SEO. This is the problem that Quora solved. Instead of streaming compact JSON data, Quora streams rendered HTML that updates any part of the page (not just a section of the page).
From an answer Charlie wrote: "If I were making a new website from scratch without LiveNode, the first thing I would do would be to rebuild LiveNode. Pretty much everything about web development is easier and faster and more correct using it." [2]
One of Abert's (Quora Engineer) tweets: "Going back to Django after having used Livenode is just painful." [3]
More info:
[1] http://www.quora.com/Quora-Infrastructure/What-is-webnode2
[2] http://www.quora.com/What-limitations-has-Quora-encountered-...
http://vimeo.com/16647049 (jump to 2:23)
In any case, it's still a neat idea.
Here's a video clip showing a wood gasifier (they eventually got it to work but that part isn't shown in this clip): http://www.youtube.com/watch?v=bkH6mFlfH3o
Also, will this work with existing browser plugins? If users are unable to use their plugins, would they actually switch to use a customized browser with no plugin support?
Is this project intended to let developers create installable web apps (like Google Chrome's installable web apps with the manifest's "container" field set to "panel" [2])? If so, probably it'll better to just market it like so. I think people are far more interested in building monetizable web applications than customized browser layouts.
[1] XUL elements: https://developer.mozilla.org/en/XUL_Reference
[2] Chrome Web App's "panel" option: http://chromestory.com/2010/07/panel-tab-and-window-styles-c...