Author(s):	Silvia Pfeiffer
Location	MCC3
Date	jan Wed 30	Days Raw Files
Start	10:40	First Raw Start	error-in-template
Duration	0:45:00	Offset	None
End	11:25	Last Raw End
Chapters
Total cuts_time	None min.

http://lca2013.linux.org.au/schedule/30040/view_talk
raw-playlist raw-mp4-playlist encoded-files-playlist mp4 svg png

assets release.pdf Code_up_your_own_video_conference_in_HTML5.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:	In the last year, the specifications of WebRTC (real-time communication) have improved massively and first implementations of the PeerConnection API are available in Google Chrome and Opera. Web developers are now able to imple­ment video con­fer­en­cing in Web pages with just a few lines of JavaS­cript code - given a server that provides connection setup functionality. The Medi­aStream and Peer­Con­nec­tion objects provide some­thing fun­da­ment­ally dif­fer­ent from the tra­di­tional web: peer-to-peer con­nec­tions without an inter­me­di­ate relay. This present­a­tion will explain the new objects, dig into the challenges that had to be overcome to make this happen, and show a demo of their (still experimental) imple­ment­a­tion in the Chrome and Opera Web browsers. By the time of LCA, Mozilla may have experimental implementations, too. markdown
Comment:	production notes