Author(s):	Erin Zimmer
Location	A1
Date	jan Thu 24	Days Raw Files
Start	11:35	First Raw Start	11:12
Duration	0:45:0	Offset	0:22:38
End	12:20	Last Raw End	12:42
Chapters	00:00 0:08:17 0:38:16 0:43:19
Total cuts_time	43 min.

https://2019.linux.conf.au/schedule/presentation/139/
raw-playlist raw-mp4-playlist encoded-files-playlist host public tweet mp4 svg png

assets release.pdf Autopsy_of_a_Browser.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:	Before there was the Internet of Things, there was the Internet of Webpages. And, unless you're really committed to Curl, you probably access the Internet of Webpages using a browser. But browsers are a bit like digestive systems - everyone has one, but you don't really know how it works, and sometimes it makes weird noises or bad smells. Doctors learn about bodies by performing autopsies, so let’s try the same thing with a browser. We’ll find some browsers that died of natural causes, and have a poke around inside. We’ll start with a primitive browser, that only has the ability to display text and follow hyperlinks. From there, we can follow the evolution of images, layouts, CSS and JavaScript. Along the way, we’ll gain some insights into the historical circumstances that led to modern browsers being the way they are, and hopefully end up with a better understanding of some of their quirks. *No browsers were harmed in the making of this talk markdown
Comment:	production notes