Hypermedia - less hype, more media please
summary
GitHub treats hypermedia as pragmatic experimentation: the API returns link relations (status URL on the status endpoint) and supports multiple media types (application/vnd.github raw for README, diff/patch for pull requests), uses URI templates and the URI Template gem for parametric links, and builds a Ruby Sawyer hypermedia agent on Faraday plus an Octokit hypermedia branch. Clients benefit from Link headers for pagination, ETags/304s that don’t consume rate limit, and must handle 302 redirects; some approaches prove useful, others add overhead.
AI-written summary · about
chapters (9)
- 0:00Start
- 4:25WHAT THE HECK IS HYPERMEDIA?
- 7:43A SIMPLE EXAMPLE
- 17:02Specs are a pain to write.
- 18:38URI TEMPLATES
- 21:51SAWYER
- 28:018 API #REALTALK
- 32:46DEVELOPERS DON'T READ YOUR DOCS
- 35:19How GitHub uses the GitHub API.
