PeerTube Backstage video/PeerTube Backstage video — English @ Weblate: allows servers

	Key	English	Actions
	00:06:49.254-->00:06:51.158	that's to say on something that gathers
	00:06:51.273-->00:06:54.092	features and important contributions
	00:06:54.178-->00:06:55.911	such as project memory
	00:06:56.262-->00:06:58.278	including
	00:06:58.335-->00:07:00.868	all the users' and feature requests
	00:07:00.976-->00:07:03.928	and bug reports…
	00:07:04.138-->00:07:06.494	When we upload a video on PEERTUBE
	00:07:06.519-->00:07:09.010	many mechanisms are working.
	00:07:09.214-->00:07:11.075	When we're entering
	00:07:11.100-->00:07:12.780	the video metadata,
	00:07:12.833-->00:07:14.769	the server has to transform the video,
	00:07:14.794-->00:07:16.904	and transcode it in various definitions
	00:07:18.024-->00:07:20.579	to make sure that the video is visible
	00:07:20.604-->00:07:23.498	by any browser and device.
	00:07:23.520-->00:07:25.374	Federation
	00:07:25.422-->00:07:26.929	allows servers
	00:07:26.954-->00:07:28.236	and <i>in fine</i> users
	00:07:28.318-->00:07:30.258	to connect with each other.
	00:07:30.496-->00:07:31.496	In fact,
	00:07:31.639-->00:07:33.677	PEERTUBE's advantage
	00:07:33.744-->00:07:36.667	was this federation
	00:07:36.877-->00:07:41.048	where big web giant servers weren't needed
	00:07:41.201-->00:07:43.692	but where you could create many small servers
	00:07:43.873-->00:07:45.202	which once federated
	00:07:45.227-->00:07:46.754	and interconnected together,
	00:07:47.207-->00:07:48.711	the servers…
	00:07:48.826-->00:07:51.588	offer a huge video catalogue even if the videos
	00:07:51.613-->00:07:54.374	are divided in many people's homes.
	00:07:54.644-->00:07:57.330	Chocobozzz's huge intuition
	00:07:57.559-->00:08:00.816	was to add something else to the federation:
	00:08:00.987-->00:08:03.635	peer-to-peer video streaming.

	Key	English	Actions
	00:06:49.254-->00:06:51.158	that's to say on something that gathers
	00:06:51.273-->00:06:54.092	features and important contributions
	00:06:54.178-->00:06:55.911	such as project memory
	00:06:56.262-->00:06:58.278	including
	00:06:58.335-->00:07:00.868	all the users' and feature requests
	00:07:00.976-->00:07:03.928	and bug reports…
	00:07:04.138-->00:07:06.494	When we upload a video on PEERTUBE
	00:07:06.519-->00:07:09.010	many mechanisms are working.
	00:07:09.214-->00:07:11.075	When we're entering
	00:07:11.100-->00:07:12.780	the video metadata,
	00:07:12.833-->00:07:14.769	the server has to transform the video,
	00:07:14.794-->00:07:16.904	and transcode it in various definitions
	00:07:18.024-->00:07:20.579	to make sure that the video is visible
	00:07:20.604-->00:07:23.498	by any browser and device.
	00:07:23.520-->00:07:25.374	Federation
	00:07:25.422-->00:07:26.929	allows servers
	00:07:26.954-->00:07:28.236	and <i>in fine</i> users
	00:07:28.318-->00:07:30.258	to connect with each other.
	00:07:30.496-->00:07:31.496	In fact,
	00:07:31.639-->00:07:33.677	PEERTUBE's advantage
	00:07:33.744-->00:07:36.667	was this federation
	00:07:36.877-->00:07:41.048	where big web giant servers weren't needed
	00:07:41.201-->00:07:43.692	but where you could create many small servers
	00:07:43.873-->00:07:45.202	which once federated
	00:07:45.227-->00:07:46.754	and interconnected together,
	00:07:47.207-->00:07:48.711	the servers…
	00:07:48.826-->00:07:51.588	offer a huge video catalogue even if the videos
	00:07:51.613-->00:07:54.374	are divided in many people's homes.
	00:07:54.644-->00:07:57.330	Chocobozzz's huge intuition
	00:07:57.559-->00:08:00.816	was to add something else to the federation: