There was an error while loading. Please reload this page.
docs: explain that API keys and OAuth are optional levels, not requirements The addon pages implied credentials were part of setting a server up. They are not: every one of the sixteen works with none, and an API key or OAuth connection expands what the addon can do rather than enabling it. Three levels, now stated on Server-Addons, on Help-server, in the audio and video guide, and per-addon on the four that have credentials: 1 nothing embed and play -- all sixteen addons 2 key or token browse your library, pull metadata in, statistics 3 OAuth write back to the platform -- YouTube only The per-addon capability matrix is read from the supports* declarations rather than described in prose, and it carries the caveat that four addons advertise description sync without implementing it (#1920). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
docs: a help page for each of the sixteen server addons Server help stopped at a one-line-per-type table, which is where the real setup work actually lives: YouTube alone has thirteen server fields including OAuth and quota, and every addon adds fields to the media file form as well as the server form. Each addon now has its own page covering both forms, with setup walkthroughs for the four that need credentials -- YouTube, Vimeo, Wistia and Resi -- and honest short pages for the ones that need nothing. Server-Addons compares all sixteen and routes by where the media actually lives. Field names, labels and descriptions are read from each addon's own XML and language files, so the tables say what the form says. Also corrects two rows that would have sent people the wrong way: Vimeo and Wistia were described as oEmbed auto-detection, implying no setup, when both have API credential fields for browsing your own library. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>