MySpace changes their Flash/embed filtering again
Mashable reports on MySpace’s new <embed> tag changes. It looked like MySpace was disabling all embed tags, but it seems that they were rolling out this big change. It’s explained better in Chris Bennet’s comment to that post, which I reproduce below (I hope he doesn’t mind):
14. Chris Bennett - January 18, 2007
Before:
MySpace required embed tags to embed Flash content. The preferred method was to embed via the object tag, but that was completely stripped out by MySpace.This morning:
MySpace began rolling out a change that would block embed tags, but allow object tags for embedded content. This caused some users to report stickers as “not working.”This morning + n hours:
MySpace finished the change that converted a user’s embed tags to properly formatted object tags and therefore allowed.Soon, all embedded objects on MySpace will be using object instead of embed. The previous restrictions such as “allownetworking = internal”, “allowScriptAccess = never”, “enableJSURL = false”, and “enableHREF = false” all remain. One new FlashVar I do not recognize is “saveEmbedTags = true” which is probably an internal flag to MySpace.
This is probably part of a larger, more-intelligent Flash filtering solution that would lend itself to a situation where MySpace acts as a gatekeeper to Flash stickers (as discussed).
I wrote about some of MySpace’s previous changes to embedding code in my old tech blog.
I am wondering about the possible technical implications of this change. According to Drew McLennan’s Flash Satay article, the form of the <object> tag that MySpace is using does not stream large Flash movies! To quote the article:
After testing with some largish movies, I noticed something amiss. While every other browser was getting it right, IE/Windows was not streaming—it was waiting for the entire movie to download before playing it. This is fine for small movies, but for anything serious, the lack of streaming is unacceptable.
I haven’t tested this to see if this is still true with the latest versions of IE6 and IE7. If so, this kind of sucks
Progress bars will not work in such a world, unless everything is “satayed” as described in McLennan’s article.
I guess we shall see what other effects this might have, and what other changes MySpace might make in the near future. If the past is any indication, there will be zero official word from MySpace about this.



Howdy, I’m also unsure what the effect of OBJECT-only tagging would be across the range of today’s commonly-used browsers.
That oddly-named “Flash Satay” article didn’t really test how consistently browsers back then handled plugins with OBJECT instead of EMBED. Dru’s main goal was to satisfy the W3C Validator routines, rather than to display something successfully out in the world. Geoff Stearns pulled together the actual side-effects in different browsers… summary and link here:
http://weblogs.macromedia.com/jd/archives/2005/06/browser_object.cfm
IE/Win was always the browser that *wanted* OBJECT tags — Microsoft used this different tag instead of the EMBED that other browsers used, and later its fork was accepted by the W3C’s HTML 4.0 spec.
Have we heard anything from anyone at MySpace yet? They should have the best idea of what they’re attempting to do…..
jd/adobe