WebProNews

Tag: Flash

  • New Windows 10 Update Preemptively Kills Adobe Flash Player

    New Windows 10 Update Preemptively Kills Adobe Flash Player

    The latest Windows 10 update puts the nail in Adobe Flash Player’s coffin, permanently removing the software.

    Adobe Flash was one of the internet’s early means of creating and viewing multimedia. While innovative at the time, the software had a long history of being plagued with security issues—many of which were severe vulnerabilities that compromised computer systems.

    As the issues continued, the tide began to turn against Flash, with Apple deciding in 2010 to stop including the software on all new Macs. Eventually Adobe decided to end-of-life the software, making the announcement in 2017, throwing its weight behind standards such as HTML5.

    Although the software is not officially dead until December 21, 2020, Microsoft is preemptively killing it on Windows 10, according to a new support note.

    This update removes Adobe Flash Player that is installed on any of the Windows operating systems that are listed in the “Applies to” section. After you apply this update, it cannot be uninstalled.

    If a users need Adobe Flash Player, they will need to restore to an earlier system restore point and explicitly enable the feature, or completely reinstall Windows and forgo this latest patch.

  • Google Says No More To Flash Ads

    Google Says No More To Flash Ads

    Google announced that it is phasing out Flash from ads entirely. As of June 30th, advertisers will no longer be able to upload Flash ads into DoubleClick Campaign Manager, Bid Manager, or AdWords.

    Beginning on January 2nd, 2017, Flash ads won’t be able to run through DoubleClick Campaign Manager, DoubleClick Bid Manager, DoubleClick Ad Exchange, or the Google Display Network.

    Google has already given advertisers tools to help them build HTML5 ads, and HTML5 will be required as these dates approach.

    “Advertisers who currently use display ads built in Flash in their campaigns have several easy ways to navigate the transition, ensuring your creative continues to reach people successfully,” says DoubleClick product manager Karin Hennessy.

    Google encourages advertisers to check out this Mobile and HTML5 Overview site, which features Google Web Designer, AdWords Ready Ad Gallery, and DoubleClick Studio Layouts. These are considered “HTML5 authoring or plug-and-play solutions”.

    In other “death of Flash” news, Adobe launched Animate CC, killing off the Flash Professional name.

    Image via Google

  • Facebook Makes Videos HTML5 By Default

    Facebook Makes Videos HTML5 By Default

    Facebook announced that its videos will now use HTML5 by default as Flash continues its slow demise.

    The company’s chief security officer made headlines a while back when he called for the death of Flash, and even since then, Adobe dropped Flash from Flash Professional CC.

    Facebook’s Daniel Baulig says, “We recently switched to HTML5 from a Flash-based video player for all Facebook web video surfaces, including videos in News Feed, on Pages, and in the Facebook embedded video player. We are continuing to work together with Adobe to deliver a reliable and secure Flash experience for games on our platform, but have shipped the change for video to all browsers by default.”

    “From development velocity to accessibility features, HTML5 offers a lot of benefits,” he adds. “Moving to HTML5 best enables us to continue to innovate quickly and at scale, given Facebook’s large size and complex needs.”

    The company points to development velocity, testability and accessibility as the main benefits to HTML5.

    It also says that as a result of the switch, videos play faster on Facebook, and people like, comment on, and share more videos now.

    Read this post for some discussion about challenges Facebook had to overcome to make the switch.

    Image via Facebook

  • Adobe Drops the ‘Flash’ From Flash Professional CC (At Least in Name)

    Adobe Drops the ‘Flash’ From Flash Professional CC (At Least in Name)

    Adobe announced that it has shipped its latest Creative Cloud desktop updates and announced some new developments across its portfolio of tools and technologies.

    Most notably, Adobe is reanaming Flash Professional CC to Adobe Animate CC to “more accurately reflect the content-formats produced by this tool.”

    Explaining the move on the Adobe Flash Professional Team Blog, Rich Lee writes:

    For nearly two decades, Flash Professional has been the standard for producing rich animations on the web. Because of the emergence of HTML5 and demand for animations that leverage web standards, we completely rewrote the tool over the past few years to incorporate native HTML5 Canvas and WebGL support. To more accurately represent its position as the premier animation tool for the web and beyond, Flash Professional will be renamed Adobe Animate CC, starting with the next release in early 2016.

    Today, over a third of all content created in Flash Professional today uses HTML5, reaching over one billion devices worldwide. It has also been recognized as an HTML5 ad solution that complies with the latest Interactive Advertising Bureau (IAB) standards, and is widely used in the cartoon industry by powerhouse studios like Nickelodeon and Titmouse Inc.

    He notes that Animate CC will continue to support Flash (SWF) and AIR formats as “first-class citizens”. `

    “This has to do with Adobe’s successful pivot in the capability of its tools to support HTML5,” IDC software development research program director Al Hilwa tells WebProNews in an email. “The renaming of Adobe’s animation tools reflect that it now emits HTML5 and is widely used for this purpose and so the new name reflects this important change in the capability and usage patterns seen by its users. With respect to the other tools, it is good to see that some of the important features have found homes in Dreamweaver and other Adobe apps.”

    “With respect to the new wave of updates, I think Adobe is living up to its Creative Cloud promise of more regular feature enhancements and deliveries compared with a box program,” Hilwa adds. “They remain a successful case study of the transformation to cloud delivery for desktop software.”

    Adobe also introduced new desktop app features including precise Dehaze in Lightroom CC, expanded support for UltraHD in Premiere Pro, a new Shaper tool in Illustrator, and the ability to create realistic 3D models in Adobe Fuse CC (preview) and easily import and work on them in Photoshop CC.

    There is also news we have some news around the future of Adobe Edge Tools & Services, and Adobe is working on a new HTML5 video player for desktop browsers. More on all of this here.

    Image via Adobe (YouTube)

  • Google Is Implementing A Major Change On Tuesday

    Google is continuing its efforts of driving nails into Flash’s coffin. In June, the company announced it would start automatically pausing Flash in Chrome in an effort to save the battery life of users’ computers and improve performance. The company announced this week that this functionality will begin rolling out on Tuesday, September 1. With this in mind, there are some things that advertisers need to be aware of.

    Are you happy to see Flash on the way out or is Google going overboard? Share your thoughts in the comments.

    Over the course of the past few years, Google has been giving advertisers tools and encouraging them to use HTML5 for their ads so they can reach more audiences across devices. There are several ways that advertisers who use Flash can transition to HTML5.

    For one, Google announced back in February that AdWords would begin automatically converting Flash to HTML5, but this only works with eligible campaigns. Google talks all about eligibility guidelines in a help document here. They actually have a tool called Swiffy, which helps you test whether your ads can be automatically converted.

    Advertisers can also create HTML5 ads with Google itself. It has an AdWords Ad gallery that lets you create a Lightbox ad from existing HTML5 templates and get custom ad ideas on your site’s content and style. You can also download Google’s Web Designer, which is a free HTML5 authoring tool for building ads for uploading to your Google Display Network campaigns.

    Additionally, Google’s DoubleClick Studio lets you browse HTML5 templates and build your own ads using the company’s richmediagallery.com template database.

    Finally, you can simply upload your own HTML5 ads.

    “Whichever tool you choose, we recommend you take advantage of our best practices for building compelling display ads so you can reach prospective customers across all the browsers and devices they use,” Google says.

    You can find those here.

    As September 1 approaches, Google is urging advertisers to identify any Flash ads in their account that aren’t eligible for automatic conversion and to convert them to HTML5. The deadline is approaching.

    Advertisers can see in their AdWords reports whether or not ads were converted. Just segment the ad table by devices. If you see mobile or tablet impressions for a Flash ad, it was converted. Google noted when it first announced automatic conversion it would begin providing a notification on all converted Flash ads in late 2015.

    Google doesn’t allow Flash ads that don’t support the clickTAG variable, which is the tracking code Google assigns an individual ad and allows it to register where the ad was displayed when it was clicked. It says that on any click, the ads should redirect to the URL specified in the clickTAG argument, and there should be any other redirection in between. Note that the variable name has to be spelled exactly like “clickTAG” with the upper-case TAG and no space.

    Google has been doing everything it can to help phase out Flash for years. As mentioned, this is only the latest nail in its coffin. Early this year, the company announced that it is now defaulting to the HTML5 player on the web for YouTube embeds, moving to iframes. Additionally, it announced the deprecation of the old style of Flash <object> embeds and Flash API.

    Additionally, on the organic SEO side of things, as a result of Google’s mobile-friendly update in April, Flash content can now cost in you in search rankings.

    As the company tells webmasters in its mobile SEO guide, “Avoid common mistakes that frustrate mobile visitors, such as featuring unplayable videos (e.g., Flash video as the page’s significant content). Mobile pages that provide a poor searcher experience can be demoted in rankings or displayed with a warning in mobile search results.”

    Google has of course been warning against this for years.

    All the way back in 2013, the company said this in a Webmaster Central blog post: “Many websites embed videos in a way that works well on desktops but is unplayable on smartphone devices. For example, if content requires Adobe Flash, it won’t be playable on an iPhone or on Android versions 4.1 and higher.”

    “Instead of using a proprietary video player or putting content in unsupported formats, we recommend using HTML5 standard tags to include videos or animations,” Google says. “For animated content rendered using Flash or other multimedia players, consider using HTML5 animations that work across all web browsers. Google Web Designer makes it easy to create these animations in HTML5.”

    Of course, Google isn’t the only one encouraging people to move away from Flash. Bing is also moving to a more mobile-friendly search environment. Facebook’s security head recently called for the death of Flash after recent vulnerabilities came to light, and last week, Amazon announced that it is no longer accepting Flash ads (also as of September 1).

    Last month, we looked at a report from Sizmek, which found that advertisers are still running a ridiculous amount of Flash ads despite the fact that they default to static displays on mobile devices, which likely means fewer clicks. You can read about that here.

    Are you still using Flash in any way? For web content? Ads? If so, what is keeping you from moving on? Let us know in the comments.

    Image via Google

  • Amazon Puts An End To Flash Ads

    Flash-related news isn’t usually good news for Flash these days. The most recent bit comes from Amazon, which announced that it is about to stop accepting Flash ads.

    The company had this to say on its Technical Guidelines page for Amazon Advertising (via Digiday):

    Beginning September 1, 2015, Amazon no longer accepts Flash ads on Amazon.com, AAP, and various IAB standard placements across owned and operated domains.

    This is driven by recent browser setting updates from Google Chrome, and existing browser settings from Mozilla Firefox and Apple Safari, that limits Flash content displayed on web pages. This change ensures customers continue to have a positive, consistent experience across Amazon and its affiliates, and that ads displayed across the site function properly for optimal performance.

    Flash was in the spotlight last month when Facebook’s Chief Security Officer called for its demise.

    “It is time for Adobe to announce the end-of-life date for Flash and to ask the browsers to set killbits on the same day,” he said. “Even if 18 months from now, one set date is the only way to disentangle the dependencies and upgrade the whole ecosystem at once.”

    Then, Mozilla blocked all versions of Flash in Firefox after security researchers discovered vulnerabilities that affect various operating systems, that hadn’t been patched.

    From there, various media outlets called for Flash to be put out of its misery. The reality is, however, that many advertisers are still using it.

    We recently looked at a study from Sizmek, which called this a “major issue”.

    What’s happening is that Flash ads that would otherwise be dynamic are appearing as static images on mobile device, and this can ultimately cost the advertiser clicks and conversions.

    “This raises questions as to whether or not marketers are aware of how many of their ads are not being seen properly and how much ad spend they are wasting,” a spokesperson for the firm told WebProNews.

    As for Amazon, you can see what it wants from advertisers here.

  • Is It Time For Flash To Go Away?

    Is It Time For Flash To Go Away?

    The writing has been on the wall for quite a while. Flash is dying a slow death, yet it continues to gasp for air. After some new vulnerabilities were discovered, many have been calling for the plug to be pulled.

    Do you think there should be an industry-wide halt in Flash use? Let us know what you think.

    Facebook’s Chief Security Officer called for its demise the other day.

    “It is time for Adobe to announce the end-of-life date for Flash and to ask the browsers to set killbits on the same day,” he said. “Even if 18 months from now, one set date is the only way to disentangle the dependencies and upgrade the whole ecosystem at once.”

    Then, Mozilla blocked all versions of Flash in Firefox after security researchers discovered vulnerabilities that affect various operating systems, that hadn’t been patched.

    Yes, this was temporary. Adobe issued an update on Tuesday about a resolution for the vulnerabilities. Here’s the company’s statement in full:

    A few days ago we were notified of two vulnerabilities within the Flash Player that could potentially allow an attacker to take control of an affected system. Upon investigation, we confirmed and fixed the issues, and took steps to ensure that this class of attack cannot be used as a future attack vector.

    We released an update to Flash Player this morning, and are proactively pushing the update out to users. We are also working with browser vendors to distribute the updated player.

    We would like to thank Dhanesh Kizhakkinan of FireEye and Peter Pi of TrendMicro and slipstream/RoL for reporting the issues and working with us to help us quickly address them.

    Flash Player is one of the most ubiquitous and widely distributed pieces of software in the world, and as such, is a target of malicious hackers. We are actively working to improve Flash Player security, and as we did in this case, will work to quickly address issues when they are discovered.

    We continue to partner with browser vendors to both improve Flash Player security as well as invest in, contribute to and support more modern technologies such as HTML5 and JavaScript.

    Nothing in there about killing Flash. Still, the calls for its death continue.

    Wired, one of the most well known magazines in tech, published an article on Wednesday called, “Flash. Must. Die.” In that, the technology is called “That insecure, ubiquitous resource hog everyone hates to need.”

    The headlines related to Flash are rarely positive. Earlier this year, YouTube deprecated Flash embeds and its Flash API. Then Google started automatically converting Flash ads to HTML5. Flash can potentially hurt websites in search rankings. Google even announced that it would try to save people’s laptop batteries by pausing Flash in Chrome.

    Despite the wide disdain for Flash, it’s still being very heavily used in advertising. We recently looked at a study from Sizmek, which called this a “major issue”.

    What’s happening is that Flash ads that would otherwise be dynamic are appearing as static images on mobile device, and this can ultimately cost the advertiser clicks and conversions.

    “This raises questions as to whether or not marketers are aware of how many of their ads are not being seen properly and how much ad spend they are wasting,” a spokesperson for the firm tells WebProNews.

    “As mobile inventory grows, the channel is also changing, particularly in the realm of rich media. The days of Flash-supported inventory on mobile devices are numbered,” the report says. “iOS devices have never had native Flash support, and it’s been six full operating system versions since Android devices supported Flash. This means that only 11% of Android devices are capable of supporting Flash, and those devices are running significantly out-of-date software. Because mobile support for Flash inventory is nearly extinct, rich media ad formats that rely on Flash are likely to default – or revert to a single, static image – nearly 100% of the time. This means 5.35 billion rich media impressions served to mobile devices were squandered in Q1 of 2015 alone.”

    According to Sizmek’s findings, only 8.3% of HTML5 impressions defaulted, while these formats represent less than half of rich media ads served to mobile devices.

    “The Flash mobile default problem isn’t exclusive to just a few advertisers,” the report notes. “Among campaigns that served at least 1 million impressions in Q1, the average default rate was 35.2%. Many advertisers had it much worse than that – 36% of the advertisers in this sample defaulted much more than average, including the 12% of advertisers that never successfully served a rich media ad to a mobile device. The rate of rich media failure was much lower on desktop inventory, where 60% of advertisers defaulted at a rate of less than 3%.”

    You can take a look at the full report here.

    Are you still using Flash for ads? Should Flash continue to be supported? Share your thoughts in the comments.

  • Facebook’s Security Head Calls for the Death of Flash

    In 2010, Steve Jobs famously tore down Adobe Flash. Facebook’s new Chief Security Officer wants Flash to die.

    “It is time for Adobe to announce the end-of-life date for Flash and to ask the browsers to set killbits on the same day,” said Alex Stamos in a recent tweet.

    “Even if 18 months from now, one set date is the only way to disentangle the dependencies and upgrade the whole ecosystem at once.”

    Facebook still relies on Flash for a lot of its video, but the site also uses HTML5, browser permitting.

    Stamos is far from the first to call for an end to what many feel is a buggy, constant security nightmare.

    Stamos joined Facebook a few weeks ago, moving over from Yahoo.

  • Advertisers Are Using A Nearly Obsolete Technology Way Too Much

    Flash is bordering on obsolete at this point thanks to the rise of mobile and HTML5, yet advertisers are still running a ridiculous amount of Flash ads despite the fact that they default to static displays on mobile devices, which likely means fewer clicks.

    Sizmek has released a new study, which illustrates just how common this is and notes that it’s a “major issue”.

    “This raises questions as to whether or not marketers are aware of how many of their ads are not being seen properly and how much ad spend they are wasting,” a spokesperson for the firm tells WebProNews.

    “As mobile inventory grows, the channel is also changing, particularly in the realm of rich media. The days of Flash-supported inventory on mobile devices are numbered,” the report says. “iOS devices have never had native Flash support, and it’s been six full operating system versions since Android devices supported Flash. This means that only 11% of Android devices are capable of supporting Flash, and those devices are running significantly out-of-date software. Because mobile support for Flash inventory is nearly extinct, rich media ad formats that rely on Flash are likely to default – or revert to a single, static image – nearly 100% of the time. This means 5.35 billion rich media impressions served to mobile devices were squandered in Q1 of 2015 alone.”

    According to Sizmek’s findings, only 8.3% of HTML5 impressions defaulted, while these formats represent less than half of rich media ads served to mobile devices.

    Screen shot 2015-07-09 at 11.38.28 AM

    “The Flash mobile default problem isn’t exclusive to just a few advertisers,” the report notes. “Among campaigns that served at least 1 million impressions in Q1, the average default rate was 35.2%. Many advertisers had it much worse than that – 36% of the advertisers in this sample defaulted much more than average, including the 12% of advertisers that never successfully served a rich media ad to a mobile device. The rate of rich media failure was much lower on desktop inventory, where 60% of advertisers defaulted at a rate of less than 3%.”

    Screen shot 2015-07-09 at 11.40.11 AM

    As the report points out, a lot of advertisers may see the defaults as not a big deal since viewers are still seeing the ad in some form via a static image, but it also points to data showing that HTML5 ads get much better click and interaction rates.

    You can take a look at the full report here.

    Images via Sizmek

  • Chrome Tries To Keep Flash From Draining Your Laptop Battery

    Chrome Tries To Keep Flash From Draining Your Laptop Battery

    Google made a pretty interesting and unexpected announcement about how Chrome will start working to save the battery life of your laptop. How will it do this? By pausing Flash.

    Google software engineer Tommy Li explains:

    Adobe Flash allows web pages to display rich content—but sometimes that can put a squeeze on your laptop’s battery. So we’ve been working with Adobe to ensure that your experience on the web can be power-efficient as well as rich and interactive—and today, we’re introducing an update to Chrome that does just that.

    When you’re on a webpage that runs Flash, we’ll intelligently pause content (like Flash animations) that aren’t central to the webpage, while keeping central content (like a video) playing without interruption. If we accidentally pause something you were interested in, you can just click it to resume playback. This update significantly reduces power consumption, allowing you to surf the web longer before having to hunt for a power outlet.

    The feature will be rolling out immediately on the Chrome desktop beta channel release, and to everyone else on desktop soon. It will be enabled by default, but you can adjust the settings on it in Chrome’s content settings by going to “Detect and run important plugin content.”

    Image via Google

  • Using Flash Can Really Cost You In Google Now

    Using Flash Can Really Cost You In Google Now

    Google advising websites to use HTML5 instead of Flash for multimedia is nothing new. What is new is that it can directly cost you search rankings now.

    As you’ve probably hears by now, Google announced a new ranking signal based on websites’ mobile-friendliness. This went into effect beginning earlier this week, though it may take a week or to to completely roll out.

    There are a lot of reasons your webpages may register as non-mobile-friendly, but one that is sure to be a problem is the use of Flash.

    “Avoid common mistakes that frustrate mobile visitors, such as featuring unplayable videos (e.g., Flash video as the page’s significant content),” Google tells webmasters. “Mobile pages that provide a poor searcher experience can be demoted in rankings or displayed with a warning in mobile search results.”

    Google has of course been warning against this for years.

    All the way back in 2013, the company said this in a Webmaster Central blog post: “Many websites embed videos in a way that works well on desktops but is unplayable on smartphone devices. For example, if content requires Adobe Flash, it won’t be playable on an iPhone or on Android versions 4.1 and higher.”

    “Instead of using a proprietary video player or putting content in unsupported formats, we recommend using HTML5 standard tags to include videos or animations,” Google says. “For animated content rendered using Flash or other multimedia players, consider using HTML5 animations that work across all web browsers. Google Web Designer makes it easy to create these animations in HTML5.”

    More on Google Web Designer here.

    To learn more about Google’s new mobile-friendly signal and what you can do to get your site mobile-friendly, read this.

    And for what it’s worth, Bing employs a similar philosophy.

  • Flash Continues To Die As Google Automatically Converts Ads

    Flash Continues To Die As Google Automatically Converts Ads

    Google announced on Wednesday that it will start converting all Flash ads to HTML5 automatically. The company presents this as an opportunity for advertisers to access more inventory.

    In a post on Google+, Google says, “Over half of time spent online is now spent on mobile devices. This presents a tremendous opportunity for marketers to reach their customers throughout the day, whenever they may be browsing. But there is an all-too-common barrier: many mobile devices and some browsers do not currently support Flash. That’s why we’re introducing a way to automatically convert Flash ads to HTML5, giving advertisers better access to the portion of Google Display Network inventory that is HTML5-only.”

    Last fall, Google announced interactive HTML5 backup tools for when Flash isn’t supported for both the Google Display Network and DoubleClick Campaign Manager. These tools would automatically create HTML5 versions of Flash ads, and when they’re served on devices or browsers that don’t support Flash, they show the interactive HTML5 ad instead of a static image backup.

    Now, Google says, “Eligible Flash campaigns, both existing and new, will now be automatically converted to HTML5 when uploaded through AdWords, AdWords Editor, and many 3rd party tools. “With this new tool plus our best practices and versatile mobile ad formats, we’re making it easier for marketers to deliver beautiful display ads that just work — regardless of screen or device — ensuring a better experience for both consumers and brands.”

    As Google notes in its help center, not all Flash ads can be converted to HTML5. The company recommends uploading your ad to the Swiffy tool to see if it will convert. If the tool can convert it, it will be automatically converted when it’s uploaded to AdWords.

    You can also see in your AdWords reports whether it was converted. Just segment the ad table by devices. If you see mobile or tablet impressions for a Flash ad, it was converted.

    Google says that in late 2015 it will begin providing a notification on all converted Flash ads.

    Google doesn’t allow Flash ads that don’t support the clickTAG variable, which is the tracking code Google assigns an individual ad and allows it to register where the ad was displayed when ti was clicked. It says that on any click, the ads should redirect to the URL specified in the clickTAG argument, and there should be any other redirection in between. Note that the variable name has to be spelled exactly like “clickTAG” with the upper-case TAG and no space.

    Google mentioned “best practices”. It refers to a document called Smart Phone Tips: An Advertiser’s Checklist for Getting Mobile Right. This provides guidance on mobile creatives and extensions, mobile targeting, mobile measurement, mobile bidding, and working without mobile-optimized sites.

    Google has been doing everything it can to help phase out Flash for years. This is only the latest nail in its coffin. Last month, the company announced that it is now defaulting to the HTML5 player on the web for YouTube embeds, moving to iframes. Additionally, it announced the deprecation of the old style of Flash <object> embeds and Flash API.

    Image via Adobe

  • YouTube Deprecates Flash Embeds, Flash API

    YouTube Deprecates Flash Embeds, Flash API

    Google announced that it is now defaulting to the HTML5 player on the web for YouTube embeds, moving to iframes. Along with this, they’re deprecating the “old style” of Flash <object> embeds and their Flash API.

    The company is encouraging all embeddes to use the iframe API, which as it notes, can inelligently use whichever technology the client supports. Google says in a blog post:

    Four years ago, we wrote about YouTube’s early support for the HTML5 <video> tag and how it performed compared to Flash. At the time, there were limitations that held it back from becoming our preferred platform for video delivery. Most critically, HTML5 lacked support for Adaptive Bitrate (ABR) that lets us show you more videos with less buffering.

    Over the last four years, we’ve worked with browser vendors and the broader community to close those gaps, and now, YouTube uses HTML5 <video> by default in Chrome, IE 11, Safari 8 and in beta versions of Firefox.

    The benefits of HTML5 extend beyond web browsers, and it’s now also used in smart TVs and other streaming devices.

    Google credits technologies like MediaSource extensions the VP9 codec, encrypted media extensions and common encryption, WebRTC, and Fullscreen with progressing HTML5 video. As it notes, other companies like Netflix, Vimeo, Microsoft, and Apple have all embraced HTML5.

    Google also credits HTML5 with enabling new classes of devices such as Chromebooks and Chromecast.

    The company tells developers to support HTML5 by using the iframe API everywhere you embed videos on the web.

  • Flash Player 16 Includes Important Updates

    Flash Player 16 Includes Important Updates

    Adobe released Flash Player 16 last week. It comes with important bug and security fixes, and adds stand alone installation and plugin support for the PPAPI (“Pepper”) version of Flash Player.

    Before, this was only available as an integrated component of Chrome.

    “With the upcoming changes to Chromium, making the PPAPI version of Flash Player available was critical for our customers and a top priority for our team,” Adobe said in a blog post. “With Flash Player 16, customers can now download Flash Player PPAPI for Chromium based applications and developers have access to the official PPAPI content debugger.”

    Chrome users don’t have to make any changes or download anything.

    In version 14 of the Runtime Adobe has dded the new Standard profile to desktop systems.

    “This improvement in 3D graphics brought massive improvements to both Flash Player and AIR. In Version 15 we expanded that to mobile devices in AIR,” it says. “In Flash Player 16 we’ve added a new Standard Constrained profile. Like Baseline Constrained, Standard Constrained targets older and lower powered GPUs on both desktop and mobile devices.

    “While Standard profile reached a little over 20% of all iOS devices, the new Standard Constrained profile can now reach more than 85% of iOS devices!” Adobe adds. “Developers can access this new mode by using the new STANDARD_CONSTRAINED constant in Context3DProfile.”

    You can see a chart here, which breaks down the differences between the different profiles that are currently available.

    You can find the full release notes here.

    Image via Adobe

  • Flash Player Update Fixes A Bunch Of Vulnerabilities

    Adobe recently released updates to Flash Player and Air across all platforms, fixing a total of twelve security issues.

    “Adobe has released security updates for Adobe Flash Player for Windows, Macintosh and Linux. These updates address vulnerabilities that could potentially allow an attacker to take control of the affected system,” the company said on September 9th.

    The latest versions and affected versions are as follows (as listed on the Adobe site).

    Latest Versions

    Users of the Adobe Flash Player desktop runtime for Windows and Macintosh should update to Adobe Flash Player 15.0.0.152.

    Users of the Adobe Flash Player Extended Support Release should update to Adobe Flash Player 13.0.0.244.

    Users of Adobe Flash Player for Linux should update to Adobe Flash Player 11.2.202.406.

    Adobe Flash Player installed with Google Chrome, Internet Explorer 10 and Internet Explorer 11 will be automatically updated to the current version.

    Users of the Adobe AIR desktop runtime, SDK and SDK and Compiler should update to version 15.0.0.249.

    Users of Adobe AIR for Android should update to Adobe AIR 15.0.0.252.

    Affected software versions

    Adobe Flash Player 14.0.0.179 and earlier versions

    Adobe Flash Player 13.0.0.241 and earlier 13.x versions

    Adobe Flash Player 11.2.202.400 and earlier versions for Linux

    Adobe AIR desktop runtime 14.0.0.178 and earlier versions

    Adobe AIR SDK 14.0.0.178 and earlier versions

    Adobe AIR SDK & Compiler 14.0.0.178 and earlier versions

    Adobe AIR 14.0.0.179 and earlier versions for Android

    For specific instructions related to the versions you’re running, and for additional details, go here.

    Image via Adobe

  • Google To Note When Pages May Not Work In Mobile Results

    Google is going to start letting mobile searchers know when results include pages that may not work on their devices. On a device that doesn’t support Flash, for example (which includes iOS and Android versions 4.1 and higher), Google will include a message with the result that says, “Uses Flash. May not work on your device.”

    “A common annoyance for web users is when websites require browser technologies that are not supported by their device,” write Google’s Keita Oda and Pierre Far. “When users access such pages, they may see nothing but a blank space or miss out a large portion of the page’s contents.”

    Here’s what one of the results may look like:

    “Fortunately, making websites that work on all modern devices is not that hard: websites can use HTML5 since it is universally supported, sometimes exclusively, by all devices,” the Googlers say. “To help webmasters build websites that work on all types of devices regardless of the type of content they wish to serve, we recently announced two resources: Web Fundamentals (a curated source for modern best practices); and Web Starter Kit (a starter framework supporting the Web Fundamentals best practices out of the box).”

    You can find Web Fundamentals here. On the site it’s described as a comprehensive resource for multi-device web development. It includes sections on multi-device tools, multi-device layous, forms and user input, images/audio/video, optimising performance, and device access.

    Web Starter Kit is here. From the site, you can download the beta kit, which includes a responsive boilerplate, a style guide, cross-device sync, live browser reloading, performance optimization, a built-in HTTP server, PageSpeed Insights reporting, and Sass support.

    Google also notes that you should not block crawling of any Googlebot of CSS, JavaScript or images with robots.txt or otherwise.

    Image via Google

  • Shockwave Found To Bundle Outdated, Dangerous Version Of Flash

    Shockwave Found To Bundle Outdated, Dangerous Version Of Flash

    It was recently discovered that Adobe Shockwave has been bundling a version of Flash Player that is over fifteen months old, and behind on important security updates.

    From the Vulnerability Notes Database at kb.cert.org:

    Adobe Macromedia Shockwave Player is software that plays active web content developed in Macromedia and Adobe Director. Shockwave Player is available as an ActiveX control for Internet Explorer and as a plug-in for other web browsers. Shockwave is also available in “Full” and “Slim” installers. The “Slim” installer provides fewer Xtras, which may be installed on an on-demand basis when a Shockwave movie attempts to use them.

    The “Full” installer for Shockwave player 12.1.1.151 provides Flash version 11.5.502.146, which was released on January 8, 2013.This version of Flash contains several exploitable vulnerabilities. Note that Shockwave uses its own Flash runtime, provided by the file Flash Asset.x32, rather than using a Flash runtime that may be installed on a system-wide basis.

    It says that by convincing a user to view s specially crafted Shockwave content, such as a web page or HTML email message attachment, an attacker could execute arbitrary code “with the privileges of the user.”

    It then said it’s currently unaware of a practical solution to the problem.

    “This author has long advised computer users who have Adobe‘s Shockwave Player installed to junk the product, mainly on the basis that few sites actually require the browser plugin, and because it’s yet another plugin that requires constant updating,” wrote Brian Krebs on the KrebsOnSecurity blog. “But I was positively shocked this week to learn that this software introduces a far more pernicious problem: Turns out, it bundles a component of Adobe Flash that is more than 15 months behind on security updates, and which can be used to backdoor virtually any computer running it.”

    The story was also picked up by popular tech blog Ars Technica, which points to an uninstall tool from Adobe.

    Image via Adobe

  • Here’s What Adobe Is Doing With Flash Runtime

    Here’s What Adobe Is Doing With Flash Runtime

    Adobe recently posted an update on the Flash Runtime on its official blog in hopes of addressing questions people have been asking on various forums.

    Product manager and customer advocate for the Flash Runtime product team, Chris Campbell, who has spent a lot of time in the forums, talks about what the team has been up to.

    He says they’ve made “massive improvements” to their iOS packaging engine (Halfmoon AOT) with reduced packaging times up to 10x. This, he says, lays the foundation for future features like iOS workers, and has been in the beta builds for quite a while. It was out in the public AIR 4.0 release.

    He then talks about ActionScript concurrency for Android, noting that it has been a priority. They had an extended beta, and it became public in AIR 3.9 with additional fixes in 4.0.

    Next up is support for new versions of OSX, Windows, iOS and Android. Campbell says they’ve made sure that the Runtime supports these, and that they’ll make sure this continues in the future.

    He then goes into some new features they’re working on this year, which include: ActionScript concurrency for iOS, improvements to Stage3D, PPAPI debugging, and game discovery (more details about each in the post).

    “It’s certainly true that we have increased our investments on HTML technologies, but Adobe and the Flash product team are dedicated to pushing the Flash runtime platform forward,” says Campbell. “We believe that AIR and Flash Player are excellent solutions for both the video and gaming markets.”

    He notes that Adobe’s PR efforts have mostly been about Creative Cloud and Marketing Cloud, but says they’re working on: redesigning and making regular updates to the game development site; creating a new Flash Runtime showcase site; reaching out to the community and promoting their games; and finding additional ways to let the community evangelize the use of Flash Runtime.

    They’ll be retiring the gaming.adobe.com site, and making updates to adobe.com/devnet/games.html

    Image via Adobe

  • Waiting In Line 3D, The Worst Video Game Ever?

    Can’t wait to get your hands on the latest videogame? Do you like shooters like Doom and Duke Nukem 3D? Why not try Waiting in Line 3D, a first-person punching game about a man waiting outside in a queue. There are no enemies in the game, but in the long wait of what’s to be anticipated, the player must stay awake by punching themselves in the face. Punch yourself too often, and you’ll die – too little, and you’ll ultimately fall asleep. The goal is to stay awake.

    The game’s style is similar to that of Wolfenstein 3D, Road Rash, and other 90’s games that took heavily pixelated pictures of real world settings and overlaid them to create a virtual reality. You’ll notice that the level design looks similar to early PlayStation games.

    The game is made by Rajeev Basu, an interactive artist from London, known for having humor being “a big part of” his “work.”  He’s made such pieces like a brash set of “greeting” cards that were rejected from various card publishing companies, as well as a concept album called EEP EEP EEP EP, which is composed entirely with alarms. Appropriately, Basu copyrights his game circa 1991.

    Basu told Wire.co.uk that it’s an “anti-game”, which means it “deliberately undermines the very idea of what a game is meant to be”.

    Basu teamed up with Alex Anderson (AKA ManCub), a musician based in Denver Colorado who incorporated his first single, “Friends Listen” in the game. Anderson’s tracks match the echoic distant sound and feel of the 90’s – a kind of new age and experimental music style that sounds like a more upbeat version of Moby’s early work combined with Jesus Jones. Basu said that he and Anderson “shared a similar kind of thinking,” adding that both of them liked “creating things that are a bit ‘off’ and messing with people.”

    “The game isn’t interesting, exciting or fun.”

    “I think we succeeded.”

    And yet, despite the game being so mundane, there have been “tens of thousands” of internet users playing Waiting in Line 3D with a total of 48 hours. While most players only last for a couple minutes, one player managed to stand in line for 27 minutes.

    Go and give it a shot at WaitingInLine3D.com.

    (Pictures via Rajeev Basu, WaitingInLine3D.com)

     

  • Kathy Griffin Gives Gloria Estefan an Eyeful

    Kathy Griffin is always one for a good laugh, and her most recent comedic banter is just that. Last Wednesday, Griffin stopped by “The Tonight Show” to pay Jay Leno a visit. As with any interview, the two held a light-hearted discussion, covering a number of topics from life to business.

    However, Leno had another topic he wanted to discuss. He wanted to know the details about her over-the-top behavior at Gloria Estefan’s event in September.

    Last month, Griffin attended Gloria Estefan’s release party for her new album, “The Standards.” As a favor to her friend, Griffin also hosted the party. However, that’s not all she did. Griffin made the executive decision to put on a show that no one would forget, sharing everything under her dress. Of course, Griffin had no qualms about doing so and there was definitely no regrets – just laughs.

    Griffin took the liberty of filling Leno in on the details. “I was actually doing a one-nighter in Miami and my good friend Gloria Estefan introduced me. I thought, I’d like to keep these celebrities on their game so… I just for no reason lifted my dress and the look on her face I think says it all… [but] I don’t know what I was thinking wearing the granny panties.”

    The seven-time Grammy award-winning singer also took a moment to weigh in on the hilarious moment with Renee Bargh when she visited Extra TV. Estefan said that the sight was ‘very disturbing’ and that Griffin’s underwear were huge, and almost “10 sizes too big.” “My face says it all in that picture,” remarked Estefan.

    Of course Griffin took the liberty of sharing the picture on Twitter.
    https://twitter.com/kathygriffin/statuses/382949681761751040

    Estefan also offered a warm response.

    Image via Wikimedia Commons

  • Firefox To Soon Block Plugins By Default

    Plugins are a necessary evil of the Internet. The often vulnerable software plugins that enable video and audio streaming on Web browsers are regularly exploited by hackers. To stop the spread of malware, Mozilla is now moving to change how Firefox handles plugins.

    Mozilla announced today that Firefox will soon block most third-party plugins by default. This means that future versions of Firefox will ask your permission to display plugin-enabled content. There permissions will be handled on a per-site basis so enabling Microsoft Silverlight to run on one Netflix video will ensure that all of Netflix will be whitelisted in the future.

    It should be noted that Firefox will not be blocking all third-party plugins. It won’t block for Adobe Flash because it’s “so common on the Web.” Mozilla also notes that blocking Flash by default would confuse many users due to the fact that many Web sites use hidden Flash instances all throughout a Web page.

    Wait, that’s a little unfair, right? Flash is just as vulnerable as any other plugin, so why does it get special treatment? For starters, Flash is still everywhere on the Web, and a blanket blockade would ruin a lot of Web pages for a lot of people. Besides, Firefox already blocks older versions of Flash while reminding users to upgrade to the latest secure version.

    Mozilla may be trying to protect users with this latest move, but that’s not the only reason it’s blocking plugins. The non-profit is known as a strong proponent of Web technologies like HTML5 and has been encouraging developers to dump plugins in favor of it. While HTML5 has certainly made some great strides over the last year, it still can’t match the performance of a plugin like Flash or the Unity Web Player. Until it can, plugins are here to stay.

    If you want to try the new plugin blocker for yourself, just download the latest Firefox Aurora release.