41 lines
1.6 KiB
ReStructuredText
41 lines
1.6 KiB
ReStructuredText
Federation
|
|
==========
|
|
|
|
Each Funkwale instance can federates its music library with other instances
|
|
of the network. This means that an instance A can acquire music from instance B
|
|
and share its own library with an instance C.
|
|
|
|
We support various levels of controls for federation-related features.
|
|
|
|
Acquire music via federation
|
|
----------------------------
|
|
|
|
Instance libraries are protected by default. To access another instance
|
|
library, you have to follow it. This follow request will be sent to
|
|
the other instance which can accept or deny it. Once your follow request
|
|
is accepted, you can start browsing the other instance library
|
|
and import music from it.
|
|
|
|
By default, we do not duplicate audio files from federated tracks, to reduce
|
|
disk usage on your instance. When someone listens to a federated track,
|
|
the audio file is requested on the fly from the remote instance, and
|
|
store in a local cache. It is automatically deleted after a configurable
|
|
amount of time if it was not listened again in the meantime.
|
|
|
|
If you want to mirror a remote instance collection, including its audio files,
|
|
we offer an option for that.
|
|
|
|
We also support an "autoimport" mode for each remote library. When enabled,
|
|
any new track published in the remote library will be directly imported
|
|
in your instance.
|
|
|
|
Share music via federation
|
|
--------------------------
|
|
|
|
Federation is enabled by default, but requires manually approving
|
|
each other instance asking for access to library. This is by design,
|
|
to ensure your library is not shared publicly without your consent.
|
|
|
|
However, we offer a configuration option to alter this behaviour and
|
|
disable the manual approval part.
|