Update meta.sr.ht OAuth docs

Delegated OAuth is an internal implementation detail and is no longer
going to be made available to end-users.

1 files changed, 2 insertions, 12 deletions

diff --git a/meta.sr.ht/oauth-api.md b/meta.sr.ht/oauth-api.md
index 966dc21..cff5357 100644
--- a/meta.sr.ht/oauth-api.md
+++ b/meta.sr.ht/oauth-api.md
@@ -1,7 +1,7 @@
 # meta.sr.ht OAuth API
 
-The meta.sr.ht OAuth implementation is similar to other OAuth implementations,
-but has some extensions - notably, support for *delegated authentication*.
+Authentication with all sr.ht services is done with OAuth and is governed by
+meta.sr.ht.
 
 # Supported authentication profiles
 
@@ -98,9 +98,6 @@ recognized:
 - `man.sr.ht`
 - `dispatch.sr.ht`
 
-For third-party services using delegated authentication, the service should be
-set to their OAuth client ID.
-
 ### The application redirect
 
 Once the user consents, they will be redirected to your `redirect_uri`, or the
@@ -155,13 +152,6 @@ You will receive a response like this:
 You can now use this token for [Authenticating API
 requests](#authenticating-api-requests).
 
-## Delegated OAuth
-
-Delegated OAuth is where you delegate authentication for your application
-entirely to meta.sr.ht, both for logins *and* your own API. This is used
-internally between sr.ht services but is also available to third parties.
-[Delegated OAuth](delegated-oauth.md) is documented on its own page.
-
 # Authenticating API requests
 
 Authenticating your API request is simple once you have an access token. You