GITHUB . COM {}

Detected CMS Systems:

Wordpress (2 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/w3c/epub-specs/issues/2516.

Title:
Wrong media type for Opus audio · Issue #2516 · w3c/epub-specs
Description:
The current draft lists audio/opus as media type for "OPUS audio using OGG container" and references RFC 7845 ("Ogg Encapsulation for the Opus Audio Codec"). While RFC 7845 is the correct reference and indeed defines how Opus audio is en...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {📚}

Video & Online Content
Telecommunications
Technology & Computing

Content Management System {📝}

What CMS is github.com built with?

Github.com operates using WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month

Based on our best estimate, this website will receive around 10,000,019 visitors per month in the current month.
However, some sources were not loaded, we suggest to reload the page to get complete results.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 4,989,889 paying customers.
The estimated monthly recurring revenue (MRR) is $20,957,532.
The estimated annual recurring revenues (ARR) are $251,490,385.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

opus, rfc, media, ogg, type, audio, epub, issue, mattgarrish, audioopus, audioogg, container, file, rtp, format, spec, sign, wrong, sewe, codecs, codecsopus, core, types, commented, issues, projects, reference, section, parameter, defined, member, comment, point, adding, parameters, revision, include, navigation, pull, requests, actions, security, closed, current, draft, lists, codec, defines, encapsulated, inside,

Topics {✒️}

wrong media type type projects ogg media type media types describe valid media types recommended mime-type epub document referred projects milestone core media types sequentially multiplexed segments authoritative ietf list define audio/opus audio/opus describes recommendation type ogg opus stream ogg opus files read audio/ogg opus audio codec support audio/opus media type codecs=opus describes ongoing rtp transmission mattgarrish mentioned comment metadata assignees ogg opus file rtp payload format 3 revision spec-epub3 current draft codecs parameter defined core epub 3 epub file epub container opus audio audio/opus epub spec audio codec audio/ogg opus file deployed implementations codecs=opus opus streams opus speech audio expert rtp transmission issue affects ogg container file format codecs parameter ogg encapsulation ogg encapsulated

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
Would the issue be solved if the EPUB document referred to RFC7587 instead of RFC7845?
Would the issue be solved if the EPUB document referred to RFC7587 instead of RFC7845?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Wrong media type for Opus audio
      articleBody:The [current draft](https://www.w3.org/TR/2023/CRD-epub-33-20230104/) lists `audio/opus` as media type for "OPUS audio using OGG container" and references [RFC 7845](https://www.rfc-editor.org/rfc/rfc7845) ("Ogg Encapsulation for the Opus Audio Codec"). While RFC 7845 is the correct reference and indeed defines how Opus audio is encapsulated inside an Ogg container, it does **not** define `audio/opus` as a media type for it. Instead, [Section 9 of RFC 7845](https://www.rfc-editor.org/rfc/rfc7845#section-9) recommends `audio/ogg`: > An "Ogg Opus file" consists of one or more sequentially multiplexed > segments, each containing exactly one Ogg Opus stream. The > RECOMMENDED mime-type for Ogg Opus files is "audio/ogg". Moreover, it even gives the following example: > If more specificity is desired, one MAY indicate the presence of Opus > streams using the codecs parameter defined in [[RFC6381](https://www.rfc-editor.org/rfc/rfc6381)] and > [[RFC5334](https://www.rfc-editor.org/rfc/rfc5334)], e.g., > > audio/ogg; codecs=opus > > for an Ogg Opus file. The RFC which does define `audio/opus` is [RFC 7587](https://www.rfc-editor.org/rfc/rfc7587.html) ("RTP Payload Format for the Opus Speech and Audio Codec"), but AFAIK this media type is for the RTP payload format, which is not Ogg encapsulated and not what one would typically find in an `.opus` **file**. In other words, [Section 3.2 of the current draft](https://www.w3.org/TR/2023/CRD-epub-33-20230104/#sec-core-media-types) ("Core media types") lists the wrong media type for Opus audio.
      author:
         url:https://github.com/sewe
         type:Person
         name:sewe
      datePublished:2023-01-08T11:31:16.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:4
      url:https://github.com/2516/epub-specs/issues/2516
      context:https://schema.org
      headline:Wrong media type for Opus audio
      articleBody:The [current draft](https://www.w3.org/TR/2023/CRD-epub-33-20230104/) lists `audio/opus` as media type for "OPUS audio using OGG container" and references [RFC 7845](https://www.rfc-editor.org/rfc/rfc7845) ("Ogg Encapsulation for the Opus Audio Codec"). While RFC 7845 is the correct reference and indeed defines how Opus audio is encapsulated inside an Ogg container, it does **not** define `audio/opus` as a media type for it. Instead, [Section 9 of RFC 7845](https://www.rfc-editor.org/rfc/rfc7845#section-9) recommends `audio/ogg`: > An "Ogg Opus file" consists of one or more sequentially multiplexed > segments, each containing exactly one Ogg Opus stream. The > RECOMMENDED mime-type for Ogg Opus files is "audio/ogg". Moreover, it even gives the following example: > If more specificity is desired, one MAY indicate the presence of Opus > streams using the codecs parameter defined in [[RFC6381](https://www.rfc-editor.org/rfc/rfc6381)] and > [[RFC5334](https://www.rfc-editor.org/rfc/rfc5334)], e.g., > > audio/ogg; codecs=opus > > for an Ogg Opus file. The RFC which does define `audio/opus` is [RFC 7587](https://www.rfc-editor.org/rfc/rfc7587.html) ("RTP Payload Format for the Opus Speech and Audio Codec"), but AFAIK this media type is for the RTP payload format, which is not Ogg encapsulated and not what one would typically find in an `.opus` **file**. In other words, [Section 3.2 of the current draft](https://www.w3.org/TR/2023/CRD-epub-33-20230104/#sec-core-media-types) ("Core media types") lists the wrong media type for Opus audio.
      author:
         url:https://github.com/sewe
         type:Person
         name:sewe
      datePublished:2023-01-08T11:31:16.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:4
      url:https://github.com/2516/epub-specs/issues/2516
Person:
      url:https://github.com/sewe
      name:sewe
      url:https://github.com/sewe
      name:sewe
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:4
      interactionType:https://schema.org/CommentAction
      userInteractionCount:4

External Links {🔗}(13)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
Lodash

Emails and Hosting {✉️}

Mail Servers:

aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com

Name Servers:

dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk
ns-421.awsdns-52.com
ns-520.awsdns-01.net

8.98s.