beussery, I think you're mistaken. It doesn't return a different set
of URLs at all. It's the same exact URL no matter what type of user
views the page. Furthermore it's the same content as well. There is no
cloaking at all, and there is no attempt being made to send different
content to different clients.

The only difference is that the URL has data after the hash/anchor,
which is used for to tell Flash what page the user is viewing and
consequently allows you to send a deep-linked page to a friend, or to
bookmark it. This is no different than  query string parameters.

Again, it's about giving the users the same user experience that they
come to expect in their web browser from a non-Flash site.

And just to reiterate with pittsburgh_joe said "How is sIFR different
from SWFObject?"

The page you linked to talking about sIFR has this to say:

A technique like sIFR still lets non-Flash readers read a page, since
the content/navigation is actually in the HTML -- it's just displayed
by an embedded Flash object

That is _PRECISELY_ what our method is doing. No more, no less. I'm
not sure how you can see it any other way.

And you're right, I was talking about searchenginewatch, but that
thread was locked, so I came here to have an open and honest
discussion with the development community without the need to worry
about censorship.

On Jul 11, 12:21 am, beussery wrote: