[wp-meta] [Making WordPress.org] #7490: Add Wistia shortcodes to be able to add Wistia videos to plugin readme.txt files

[Making WordPress.org]

#7490: Add Wistia shortcodes to be able to add Wistia videos to plugin readme.txt
files
-------------------------------+---------------------
 Reporter:  alekv              |       Owner:  (none)
     Type:  feature request    |      Status:  new
 Priority:  lowest             |   Milestone:
Component:  Plugin Directory   |  Resolution:
 Keywords:  close 2nd-opinion  |
-------------------------------+---------------------

Comment (by alekv):

 > I've never heard of Wistia

 Looking at a market share report, depending on which metrics you look at,
 Wistia is around place 10: https://www.similartech.com/categories/audio-
 video-media with approx. 1% market share.

 Some of those services are open-source technologies, not hosted video
 platforms. If you remove the technologies and only keep the hosted video
 platforms, Wistia is approximately number 5.

 Is it large? No. But the more popular Vimeo has only a 3 to 4% market
 share. So relatively seen, Wistia is popular.

 > We don't want alterations of the UI selected by plugin developers,...

 The alterations available are very limited. It is just the background
 color and the rounded corners. I don't see how that can be a big problem.

 > nor do we want the potential of different content shown to different
 users.

 I do see how it **could** become more difficult to govern the content very
 closely. (But, do you really do this already??)

 And, a plugin developer could change the YouTube video daily and alternate
 between two videos. This would come close to an AB test. Not that I would
 want to do it. That would be too tedious for me. But it is technically
 possible.

 With Vimeo, you could do the same, but easier. Vimeo, which you already
 support, doesn't offer AB testing, but replacing the videos under the same
 URL is supported. So, reviewers don't have control over Vimeo embeds,
 either.

 For YouTube videos, you've got at least the changelog. But for Vimeo, you
 don't. So, following your logic, now you must at least consider removing
 support for Vimeo embeds.

 > It's benefit is overwhelmingly for the plugin developer, rather than the
 end-user

 This is a matter of opinion. And I don't see the logic behind your
 statement. You already allow plugin developers to embed videos and write
 the text.

 Why would you not want the plugin developers to be able to understand if
 the content they provide is good or bad for their audience?

 If the plugin developer gets a better understanding of what content is
 relevant for the audience of a plugin, then yes, that information benefits
 the developer. And when the developer makes changes based on that data, it
 benefits the audience because they get more relevant information from the
 developer.

 Can this be abused? That may be the question that you're after. I'm not
 sure if it can. At least not for long. If a plugin developer overpromises
 or does something bad (I can't imagine what, though), then the plugin will
 get bad ratings, and people will point that out in the support forum. So,
 the reviewers will get pointed to that and can take action.

 > Additionally; any embed would have to be supported by the in-dash
 WordPress plugin installer.

 As far as I can see, the in-dash WordPress plugin installer supports
 neither YouTube nor Vimeo embeds. So why should Wistia be supported?

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7490#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org