[wp-trac] [WordPress Trac] #38172: Enable Video Headers in Custom Headers

WordPress Trac noreply at wordpress.org
Fri Oct 14 19:58:17 UTC 2016


#38172: Enable Video Headers in Custom Headers
----------------------------+--------------------
 Reporter:  davidakennedy   |       Owner:
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  4.7
Component:  Themes          |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:
----------------------------+--------------------

Comment (by mor10):

 I'm concerned about this feature because it puts the onus on the host to
 serve up video, and most hosts are not properly equipped to do so.

 Even if we limit the upload size of a video file to 8mb, its inclusion on
 the front page of a site hosted on a standard shared host can easily
 result in that site going down due to bandwidth overages or excessive data
 transfers.

 If such a feature is to be added, it should rely on dedicated video
 hosting services to ensure proper support for all users. At present time,
 the required optimization features can't be offered by WordPress core
 because they are server-based.

 The baseline recommended requirements for video hosting we've operated
 with for the past year are:

 a. Cross-browser support through OGG and MP4 (and in some cases WebM)
 b. Dynamic scaling based on bandwidth, screen width, and screen resolution
 c. Dynamic streaming based on current active viewport

 a requires the admin to generate two different files that are then
 referenced in the `video` element separately. WordPress could handle the
 actual management of the files, but the conversion and compression must be
 done elsewhere.

 b and c both require dedicated server software and service.

 Without these features, the video file will put undue strain on both the
 host and the visitor, and at present I don't think the necessary
 technologies are in place to get around the issues with WordPress alone.

 My suggestion would be to offer this as a feature, but restrict it to
 oEmbeds from dedicated video hosting providers (Vimeo, WordPress.TV,
 Brightcove, Akamai, YouTube, etc) to offload the handling to specialized
 servers. If not I fear a lot of users will experience problems and blame
 them on WordPress.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38172#comment:39>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list