Add a moqbs blog post.

[kixelated]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@kixelated has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 41 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

Walkthrough

This pull request adds a new blog post article to the documentation. The blog post is titled "libmoq + OBS = MoQBS" and includes content about a temporary fork of OBS, with instructions for downloading and building the software, usage guidance for publishing to moq-relay servers, and information about supported codecs, transports, and formats. The post also includes acknowledgments to contributors. The file is a static MDX entry with front matter metadata, headings, code blocks, figures, links, and bullet lists. No API changes or interactive logic are introduced.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No description was provided by the author, making it impossible to evaluate relevance to the changeset.	Add a brief description explaining the purpose and content of the moqbs blog post for better context and documentation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add a moqbs blog post' clearly and directly describes the main change: adding a new blog post file for moqbs content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch obs-blog

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/pages/blog/moqbs.mdx`:
- Around line 32-35: The markdown contains hardcoded, versioned download URLs
(e.g., links labeled "Mac (ARM)", "Mac (Intel)", "Linux (x86_64)" that embed
`32.1.0-rc1-35-g98607152d-9860715` and the "Windows (x64)" link that embeds
`32.0.4`) which will 404 if artifacts rotate; update these links in
src/pages/blog/moqbs.mdx to point to a canonical release or "latest" redirect
(e.g., the project's GitHub Releases page or an OBS “latest” endpoint) instead
of the build-hash URLs, and add a brief inline note next to the "Windows (x64)"
link calling out the differing version (`32.0.4`) so readers are aware of the
mismatch.
- Line 91: Fix the typo in the sentence "Go pay them if you're a big coro using
React Native... or wait until its open source." by replacing the possessive
"its" with the contraction "it's" so the sentence reads "...or wait until it's
open source."; locate this text snippet (the line starting with "Go pay them...
React Native...") in the blog content and update the word accordingly.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Hardcoded version-specific binary URLs will silently break.

The download links embed a specific build hash (32.1.0-rc1-35-g98607152d-9860715). If the CDN artifacts are rotated or the fork gains further builds, these links will 404 with no indication to readers. Consider pointing to a GitHub releases page or a canonical "latest" URL instead.

Also note that the Windows artifact uses a different base version (32.0.4) than the Mac/Linux ones (32.1.0-rc1), which may be worth a brief inline callout for readers.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pages/blog/moqbs.mdx` around lines 32 - 35, The markdown contains
hardcoded, versioned download URLs (e.g., links labeled "Mac (ARM)", "Mac
(Intel)", "Linux (x86_64)" that embed `32.1.0-rc1-35-g98607152d-9860715` and the
"Windows (x64)" link that embeds `32.0.4`) which will 404 if artifacts rotate;
update these links in src/pages/blog/moqbs.mdx to point to a canonical release
or "latest" redirect (e.g., the project's GitHub Releases page or an OBS
“latest” endpoint) instead of the build-hash URLs, and add a brief inline note
next to the "Windows (x64)" link calling out the differing version (`32.0.4`) so
readers are aware of the mismatch.