PeerTube/server/core/models
Chocobozzz b4f4432459
Viewers federation protocol v2
More efficient than the current one where instance is not fast enough to
send all viewers if a video becomes popular

The new protocol can be enabled by setting env
USE_VIEWERS_FEDERATION_V2='true'

Introduce a result field in View activity that contains the number of
viewers. This field is used by the origin instance to send the total
viewers on the video to remote instances. The difference with the
current protocol is that we don't have to send viewers individually to
remote instances.

There are 4 cases:
 * View activity from federation on Remote Video -> instance replaces
   all current viewers by a new viewer that contains the result counter
 * View activity from federation on Local Video -> instance adds the
   viewer without considering the result counter
 * Local view on Remote Video -> instance adds the viewer and send it to
   the origin instance
 * Local view on Local Video -> instance adds the viewer

Periodically PeerTube cleanups expired viewers. On local videos, the
instance sends to remote instances a View activity with the result
counter so they can update their viewers counter for that particular
video
2023-12-20 10:55:47 +01:00
..
abuse Update server dependencies 2023-10-11 11:06:34 +02:00
account Fix client URLs for channels and accounts 2023-12-08 08:57:14 +01:00
actor server/server -> server/core 2023-10-04 15:13:25 +02:00
application server/server -> server/core 2023-10-04 15:13:25 +02:00
oauth server/server -> server/core 2023-10-04 15:13:25 +02:00
redundancy server/server -> server/core 2023-10-04 15:13:25 +02:00
runner server/server -> server/core 2023-10-04 15:13:25 +02:00
server server/server -> server/core 2023-10-04 15:13:25 +02:00
shared server/server -> server/core 2023-10-04 15:13:25 +02:00
user Ensure user is owned by plugin before updating it 2023-12-06 08:43:19 +01:00
video Viewers federation protocol v2 2023-12-20 10:55:47 +01:00
view Fix views events with lives 2023-12-14 11:12:18 +01:00