How to Install & Enable Flash Player for Google Chrome or Chromium Browser
seen from United States
seen from United States

seen from Australia

seen from TĂźrkiye
seen from Germany

seen from Singapore

seen from Singapore

seen from United States

seen from Slovakia
seen from United States

seen from United States

seen from Netherlands
seen from United States
seen from China

seen from Malaysia
seen from China

seen from T1
seen from Malaysia
seen from Hong Kong SAR China
seen from China
How to Install & Enable Flash Player for Google Chrome or Chromium Browser

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch ⢠No registration required ⢠HD streaming
PPAPI
Am I the only one concerned about PPAPI?
While standardizing, updating and bringing the Browser Plugin architecture closer to the new technologies is ostensibly a Good Thingâ˘, I though the whole point of HTML5 was moving away from plugins and towards platform agnostic web applications.
Certainly I can see the benefits. An universal API for native plugins, enabling plugins to work consistently in all browsers. And certain plugins are definitely useful, like handler for various uncommon media-types. But the whole problem with the latter, is the âFlash-problemâ. Due to plugins, the web became littered with proprietary formats requiring plugins, and plugins went from âusefulâ to âmust-haveâ extensions to be able to properly surf the net when said media formats became âde-factoâ standards. Just try to navigate to a random restaurant webpage with your iPad, odds are youâll not get very far before being instructed to download the newest version of Flash.
It would not be a problem if people followed the best practices, e.g something like1:
<object data="/images/photo.exr" type="image/x-exr" width="640" height="480"> <!--OpenEXR not supported, use JPEG fallback--> <img src="/images/photo.jpg"/> </object>
Unfortunately, what you generally find in the wild is something like:
<object data="/flash/site.swf" type="application/x-shockwave-flash" width="640" height="480"> <p>Y U NO HAVE FLASH? GO INSTALL NOW, OR YOU WILL GET NO SOUP!</p> </object>
Not only canât I view the content in any form, I risk not being able to use the page at all, even to get content which would be perfectly presentable in the most basic of text-browsers.
HTML5 promised us an escape from this, by providing richer semantics and capabilities, as well as well-defined fall-back paths. A page written in HTML5, should be viewable in any HTML5 capable browser.
But wouldnât a cross-browser/platform API mean that plugins would be available for anybody whoâd need them? In theory yes, but youâd still have to compile the plugins for a target platform, and people wonât. If youâre lucky, plugins would be compiled for the most common OSâes (Windows, MacOSX and Linux), and of course those devices pushed by Google. But most other platforms are unlikely to have the plugins compiled for them, and since many plugins are bound to be proprietary, the community canât pick up the slack. It would be no different from the âflash-problemâ today.
Iâm afraid that by promoting PPAPI, Google is sending a message that itâs okay to provide main content using plugins, thus propagating the âflash-problemâ. And while this would be good for Google, as it would give Google backed devices supporting PPAPI an edge, it would not be good for anybody else. It would just maintain the status quo, perhaps with less buggy plugins, rather than moving towards an more open web.
As an aside, in an ideal world you could take this one step further. In the HTML5 draft, it allows the img element to display images in any formats as long as theyâre non-interactive. You should therefore be able to just use <img src="/images/photo" />, and have the server return an image in an appropriate format based on the Accept header of the HTTP request.
E.g. the browser tells the server âI want this image, and I can display it in âPNGâ, âJPEGâ, âGIFâ and (through plugin) âOpenEXRâ. I would prefer it in âOpenEXRâ.â The server then returns an image in an appropriate format based on the image source and available output filters.
Unfortunately, browsers are really bad at using proper Accept headers, probably because so few people know how to properly handle HTTP-headers. I did a quick check (IE, Chrome and Opera), it seems browsers either tell the server theyâll accept anything (*/*) and/or just send the default accept values they use for webpages. âŠ