Author(s):	John Feminella
Location	Room CR7
Date	jul Sat 16	Days Raw Files
Start	16:30	First Raw Start	error-in-template
Duration	00:55:00	Offset	None
End	17:25	Last Raw End
Chapters
Total cuts_time	None min.

https://2016.pygotham.org/talks/262/distributed-consensus-with-raft
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Distributed_Consensus_with_Raft.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:	--------- borked edit encode push to queue post richard review 1 email review 2 make public tweet to-miror conf done
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	Unknown Yes No has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	Getting people to agree to things is sometimes hard. But getting computers to agree is even harder -- this is the "consensus problem". When the computers are far apart, we need to achieve distributed consensus, which is especially pernicious. How do we do it, why is this important for many Python applications, and how can an algorithm called Raft help us out? markdown
Comment:	production notes