virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2025-08-10 06:10:52 +02:00
Code Issues Releases Activity

doc/protocols: Remove third party server

Browse Source 
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 412922cc6f but was
missed.

Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
This commit is contained in:
Derek Buitenhuis
2022-12-09 15:21:31 +00:00
parent 048f369f1b
commit 27b5ce2805
1 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
doc/protocols.texi
View File

@@ -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 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. 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: This protocol accepts the following options:
@table @option @table @option
@@ -632,7 +629,7 @@ This protocol accepts the following options:
@item gateway @item gateway
Defines the gateway to use. When not set, the protocol will first try 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} 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 @end table