[FFmpeg-devel] [PATCH 1/2] doc/protocols: Remove third party server

[Derek Buitenhuis]

We do not endorse or recommend specific third party servers or companies
that users' data will be funneled through.

It is also incorrectly describing how FFmpeg currently works.

Should have been part of 412922cc6fa790897ef6bb2be5d6f9a5f030754d but was
missed.

Signed-off-by: Derek Buitenhuis <derek.buitenhuis at gmail.com>
---
 doc/protocols.texi | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/doc/protocols.texi b/doc/protocols.texi
index 5e9198e67c..b9c9485646 100644
--- a/doc/protocols.texi
+++ b/doc/protocols.texi
@@ -622,9 +622,6 @@ This protocol wraps the IPFS native protocols (ipfs:// and ipns://) to be sent
 to such a gateway. Users can (and should) host their own node which means this
 protocol will use one's local gateway to access files on the IPFS network.
 
-If a user doesn't have a node of their own then the public gateway @code{https://dweb.link}
-is used by default.
-
 This protocol accepts the following options:
 
 @table @option
@@ -632,7 +629,7 @@ This protocol accepts the following options:
 @item gateway
 Defines the gateway to use. When not set, the protocol will first try
 locating the local gateway by looking at @code{$IPFS_GATEWAY}, @code{$IPFS_PATH}
-and @code{$HOME/.ipfs/}, in that order. If that fails @code{https://dweb.link} will be used.
+and @code{$HOME/.ipfs/}, in that order.
 
 @end table
 
-- 
2.38.1