journal

Google is now using Adobe’s Search Engine SDK technology.  To summarize what’s going on for developers, you can run a program called swf2html and will output all of your text in the swf’s to an html doc.  From there you can see what text Google is picking up.  For more info check out the links here…

Google reads Flash text, so optimize it
http://blogs.cnet.com/8301-13530_1-9844989-28.html

Matt Cutts on how you can help Googlebot “see” your Flash content.
http://blogs.cnet.com/8301-13530_1-9834708-28.html

Search Engine SDK FAQ
http://www.adobe.com/licensing/developer/search/faq/

First off, sorry, I’ve been OBE for a while but I’ve been keeping up with the latest. Just no time to voice them. Well… until I came across this little snippet. Which talks about Google’s new offline storage solution and how they’ve opened it up to other developers and how this is going to bring offline storage to their web apps. So I try it out in Safari and it doesn’t support Safari. Yes, Safari is my new IE6. If it doesn’t support Safari, its not worth it, maybe in the future but just not now. So this cuts into my whole ‘retrofitting’ mantra when it comes to RIA development. Why does Google think that continually pushing html development, a markup that was never designed for internet applications worthwhile? They keep trying to push it to new limits without ever thinking is there another way we should be looking at this? Adobe, Microsoft and Sun seem to agree, why not us? So I ask myself, what are they thinking man?!?!?!?