• The history and planning of GopherCon
• The creators of GopherCon, Erik St Martin and Brian (not mentioned by name), first discussed the idea in May 2013
• The first GopherCon took place in 2014 with over 700 attendees
• The conference has since grown to over 2,000 in-person attendees and offers a virtual option
• GopherCon's attention to detail is highlighted through its provision of equipment for speakers to improve their online presentations
• Mark Bates mentions that he received equipment from GopherCon to enhance his own online presentation
• Planning challenges for conferences, including unexpected costs
• Importance of submitting talks early and registering in advance
• Logistics of conference organization, including venue management and catering
• The role of experienced teams, such as Convention Designs, in facilitating smooth events
• Adapting to changes due to COVID-19, including shifting from in-person to online events
• GopherCon adapting to online format and trying to recreate conference experience
• Difficulty in replicating in-person interactions and experiences online
• Exploring new ways to facilitate community interaction, such as voice channels and Discord
• Utilizing Twitch for live lightning talks and hallway track-style conversations
• Understanding that a virtual conference will not be the same as an in-person one
• Discussing potential solutions to create a more immersive experience for attendees
• Lightning talks logistics: technical issues with laptops and projectors
• Method for selecting talk topics: "chicken system" (humorous reference)
• Blind CFP process for speaker selection: anonymous submissions reviewed by multiple reviewers
• Diverse speaker line-up: ensuring a range of subjects, companies, and expertise levels
• Supporting speakers: paying all costs, providing care packages, and treating them well
• Improving virtual presence for speakers at conferences
• Balancing the quality of conference resources to avoid overshadowing other events
• The origin and effectiveness of diversity initiatives in the Go community, particularly GopherCon
• Promoting organizations that support diversity, such as GoBridge and Women Who Go, through merchandise sales
• Analyzing the influence of GopherCon on the Go community's diversity efforts
• Discussion of community values and leadership styles (e.g., putting people first, being supportive) 
• Erik St. Martin's work with Rust programming language
• Rust used for Kubernetes node agent project
• WebAssembly features and benefits discussed
• Erik St. Martin worked on a demo project recreating The Martian scene
• Learn TV (Microsoft) and online events challenges addressed by Erik
• Online broadcast platform built to solve problems with switching between streams and maintaining linear feed
• GStreamer library used for video processing, with Rust bindings available
• Rust language features discussed, including borrow checker, error handling, and generics
• Discussion of Rust programming language and its design
• Erik St. Martin's opinions on why full-stack developers are a myth
• Mark Bates' unpopular opinion that developers tend to prioritize building over buying solutions
• Mark Bates' joke about not liking bacon and his children's antics
• Mention of upcoming events at GopherCon, including live Go Time recordings and a game show
• Plans for a game show-style reveal of contestants at GopherCon
• Discussion about the prizes for the game show contest
• Joking about Mat Ryer-based products (Go on the go toilet paper)
• Announcement that AMAs will be open to the general public
• Plan to turn GopherCon into a Week of Go with live events and announcements
• Debate about pre-recording talks vs. live streaming at GopherCon
• Discussion about challenges of relying on reliable internet connections for live streaming
• Confirmation that lightning talks will be 100% live and streamed