Timeline for Flash is peppered with ambiguity
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 10:12 | history | edited | CommunityBot |
replaced http://meta.superuser.com/ with https://meta.superuser.com/
|
|
| Mar 17, 2017 at 10:12 | history | edited | CommunityBot |
replaced http://meta.superuser.com/ with https://meta.superuser.com/
|
|
| Aug 24, 2016 at 10:20 | vote | accept | Raystafarian | ||
| May 25, 2016 at 15:28 | answer | added | hobbs | timeline score: 1 | |
| May 23, 2016 at 2:05 | comment | added | Insane | Suggested edited title: peper-flash is peppered with ambiguity | |
| May 20, 2016 at 16:22 | history | edited | Raystafarian | CC BY-SA 3.0 |
added 207 characters in body
|
| May 19, 2016 at 16:48 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
The reference changed, etc.
|
| May 18, 2016 at 12:07 | history | tweeted | twitter.com/super_user/status/732905430503051265 | ||
| May 18, 2016 at 9:05 | comment | added | Andrew T. | Here is the help center regarding Pepper Plugin API vs Native Plugin API used on Chrome: support.google.com/chrome/answer/6213033: "Plugins that use a newer, more secure system called Pepper API (PPAPI) still work. That includes plugins that come with Chrome, like Adobe Flash. There's no need to install anything extra because PPAPI plugins will update when Chrome does." | |
| May 16, 2016 at 12:06 | comment | added | Raystafarian | @DanielB helpx.adobe.com/flash-player/kb/flash-player-google-chrome.html might indicate that as well; obviously the pepper flash thing is confusing enough that at least we need a synonym | |
| May 16, 2016 at 10:53 | comment | added | Daniel B | No, just anecdotal evidence: In about:plugins and when right-clicking on a Flash applet, it’s still called “Adobe Flash Player”. | |
| May 16, 2016 at 9:53 | comment | added | Raystafarian | @daniel is there a document with the correct description? | |
| May 16, 2016 at 9:45 | comment | added | Daniel B | Pepper Flash is still made by Adobe, though. The Debian description is wrong. It just uses a different API to integrate with Chrome. So the way I see it, just combining [flash-player] with [google-chrome] is the way to go. | |
| May 12, 2016 at 8:15 | comment | added | fixer1234 | Just looking at the excerpts, [adobe-flash] is about the creator, [flash-player] is about the player (and [flash] is about the genre/files). Really poor choices of tag names--non-intuitive, confusing, asking to be misused, including flash drives, compact flash format, flashing firmware, non-Adobe products, etc. Usage is a mess. Needs cleanup. | |
| May 12, 2016 at 7:55 | history | asked | Raystafarian | CC BY-SA 3.0 |