• Blockchain definition and use cases
• Chain's blockchain infrastructure and UTXO model
• Double-spend problem and validation of transactions
• Distributed ledger systems and non-UTXO blockchains
• Chain Core implementation and hosted version
• Testnet and development of blockchain networks for financial institutions
• Chain Core's potential applications for businesses outside of traditional financial institutions
• Validating assets on a private blockchain network
• Differences between public and private blockchain networks
• Federation-based consensus protocol in Chain Core
• Customizable asset issuance and validation processes
• IBM's business-oriented blockchain announcement and its differences from Chain Core
• Distributed consensus algorithms in blockchain technology
• Practical Byzantine Fault Tolerance (PBFT) as a backbone for some blockchains
• Limitations of PBFT in production environments
• Implementation of a single node "generator" or "block proposer" for consensus
• Comparison with Proof of Work used by Bitcoin
• Open sourcing project and licensing choices, specifically AGPL license
• Concerns about AGPL's network usage requirements
• Balancing permissive vs restrictive licenses to protect business interests
• Discussion on the importance of people and business knowledge in creating a successful company
• Benefits of using Go for cross-compiling and ease of use
• Tess Rinearson's experience learning Go and its impact on her interest in systems programming
• Chain Core open sourcing process and guidelines for project structure and implementation
• Comparison of open source vs non-open source codebases and considerations for structuring projects
• GopherCon milestones and the community's shared understanding of time measurement
• Discussion about open sourcing code and writing documentation
• Personal anecdotes about Brian Ketelsen releasing his own code on GitHub despite initial reluctance
• Side project of Tess Rinearson connecting her apartment buzzer to Twilio for grocery delivery service
• Use cases and future plans for the side project, including auditing and dashboard development
• Discussion about working with Twilio in Go, including using XML tooling and encoding structs
• Early web development and browser compatibility issues
• Old browsers such as Lynx, Netscape, and IE 6
• Console-based web browsing with Lynx
• Early internet experiences and dial-up connections
• Hacking and security vulnerabilities in old systems
• Basics of web security (SQL injection, cross-site scripting)
• Social engineering and human error in security breaches
• The host has problems with isolated Wi-Fi networks and accidentally putting guests on his regular network.
• The group celebrates Bill Kennedy's birthday by singing "Happy Birthday" over a bad internet connection, leading to humorous discussion about the lag and potential post-production fixes.
• Review Dog software, a Go application that automates code reviews and adds comments to Git pull requests, is discussed as a useful tool for maintaining clean codebases.
• The default Go path for Go 1.8 has been set to /go in the user's home directory, eliminating the need to specify a path explicitly.
• The change is seen as a significant improvement for beginners, making it easier to get started with Go.
• The difficulty of setting up environment variables in programming languages
• Making language tooling more approachable for beginners
• Comparisons to other programming languages (Ruby on Rails) to identify challenges in learning Go
• The importance of accessibility and community involvement in making programming easier for new learners
• Discussion of the workspace tool idea that Andrew Gerrand presented
• Shoutouts to free software projects, including go-torch and the Go Tour
• Encouragement to contribute to open source projects, specifically the Go Tour
• Cory LaNou's "OSS help wanted" repository for listing projects in need of help
• Projects can be categorized and listed by level of expertise and ease of contribution
• Go Tour project discussed as a potential addition to the repository
• Discussion of wrap-up and goodbyes, thanking sponsors and listeners