Here , here and here, you will read about the new Google AJAX Feed API. It looks like a great thing for people to use for creating new web applications - all without having to buy server farms in order to proxy data. Yes, great I say! Kind of like Yahoo! Pipes...
Yes, great indeed, just don't attempt to make money off of the new creation you make. Note the following from the terms of service:
5.6 You agree that if you use the Feed API to develop a service for other users, it must be made accessible to your end users without charge.
There you have it... I wonder how far this extends? Certainly it makes sense that you could not create a service that wraps up the same functionality and brand it your own - then sell it. However, that seems to be covered here:
5.7 Unless you have been specifically permitted to do so in a separate agreement with Google, you agree that you will not reproduce, duplicate, copy, sell, trade or resell the Services for any purpose.
I would hope 5.6 is simply poorly written, but I am guessing it is intended to be as far reaching and ambiguous as it appears. Does that cover usage where you might have a subscription site where users are charged and some feed reading is added on later? Point being, what if the "feed" usage is a minimal part of the site, as far as payment goes?
At any rate - it would be much more useful if these services would simply charge like the Amazon services do, i.e. S3 etc.Apr 18, 2007 at 06:38 PM in Software & Internet Development
Have you experienced terribly slow speed when attempting to debug/view ASP .NET sites locally on Windows Vista with Mozilla Firefox? The terrible performance will occur when using the built in "Cassini" web server to dish up your development pages.
Even after installing the Visual Studio SP1 along with the Vista update, Firefox will load pages 1, item, at, a, time, so, slow, that, it, is, as, if, you, are, loading, the, page, with, a, 1200, baud, modem, rather than from your local hard drive. It ends up being pretty easy to fix this problem: disable IPv6 within Firefox.
Fire up Firefox and type about:config in the address bar. Now type ipv6 into the filter text box. Either right-click and select toggle (or double-click) on the network.dns.disableIPv6 to set the value to true.
Once the network.dns.disableIPv6 value is set to true, Firefox will be back to its normal self and as speedy as before.
Mar 30, 2007 at 11:35 PM in Software & Internet Development
Several months ago I stumbled upon a site I now visit daily. Ajaxian (http://www.ajaxian.com) is like the morning shot of caffeine I can no longer do without. I have written before that I am an information junkie and Ajaxian does an excellent job of providing a constant stream of information of all things Ajax.May 8, 2006 at 12:57 PM in Software & Internet Development
Microsoft Web Plan takes aim at Google - via News.com
Now this may be what I wanted... Very exciting. It appears Scoble either did not know or was playing a masterful game of poker (okay - I am not sure how masterful, but it sounded better). Here is another link (via Dare Obasanjo) worth checking out. I must say that while I am not entirely surprised because of the open Google release, this does appear to be a departure from previous actions. I do recall that in 2002/2003 there were plans to open up the system, but all of a sudden it closed up to only the IMLogic's of the world. Either way, 2+ years later, this could be good news for the developer.
And, no, Chris Payne, I didn't make any deals with Joe to open up MSN Messenger's APIs. Although if we had continued drinking the wine Buzz brought you never know! ;-)
I know this is meant to be funny, but I honestly wish Scoble would have had more to drink and signed an agreement. No I am not joking. As I have already stated in the above linked items, it serves not only customers, but Microsoft too. There has been (at least in the past and if the above is any indication, continues to be) this walled garden approach and attitude within the MSN Messenger group. Yes, I know MSN is a "separate" part of Microsoft, but I would say it is important to recall how Windows became ubiquitous and it was not by being closed... not by being what Apple became. I know a little more than I am writing, but I think now is the time for the Messenger group to wake up before the competition forces it down their throats. This is not just about Messenger either, but Messenger is an example of an oft repeated mistake... Once again, another reminder of the lesson learned via search engines. Say it with me, developers, developers, developers developers! They are the gardeners, planters, seeders and nurturers of the Microsoft ecosystem... they are not to be feared.
I think it is also prudent to remember a big reason Windows has been and or was so successful: Windows provided a platform for other companies to innovate, not just Microsoft.
I will say again, by enabling other companies to roll out products and innovations around a platform, this takes the onus off the platform maker, creates a market and sells more platform product; in this case Google product. I only wish other companies such as Microsoft (MSN Messenger and related), Yahoo!, AOL AIM (although they have a plugin interface) would do the same.
Perhaps sometime I will recount my experience with Microsoft and their MSN Messenger group. There are many interesting gems there... But I digress.
By now, it is all around the web - Google has launched the beta of Google Talk. As Joe Wilcox notes, there seems to be a lot of buzz about just another messaging client. After all, what is the big deal about another IM client? I agree, there is nothing exciting about adding a new client - however a new open platform is very exciting! Google Talk uses the Jabber/ XMPP protocol which is not new, but its use by a potentially large public service is new. Moreover, visit the Google Talk page and you will see a link describing client choice for connecting. So what you say? The page also states:
"The Google Talk service is built to support industry standards. You can connect to the Google Talk service using Google's own client, as well as many other IM clients developed by third parties."
Google Talk represents a new platform! If Google follows through on the openness indicated above, vendors will be able to roll their own applications and innovations for the XMPP platform for a (potentially) large top tier service. To my knowledge (although I have not checked in the last 8 months), MSN, AIM, Yahoo! etc. not only do not encourage third party use, in many cases they shut down the service to third parties. On rare occasions some aspects are opened up, but generally, a customer must connect with their client or an authorized client. Furthermore, each one of the aforementioned services have their own protocol and their own system - thus each client is capable of doing only what the service provider has developed. Of course being proprietary is their right, but this also makes using or finding third party innovations hard to find, hard to count on and a bit clunky because the services do not necessarily want third party software to work in the first place.