Internet Engineers have defined the Internet as a network of networks, providing connectivity for all users, at all times, for any content. Internet connectivity increases the capacity for individuals to exercise their rights, the core of the Internet, its architectural design is therefore closely intertwined with the human rights framework. However, the assertion that technology and the design of standards and protocols is a ethically neutral task are still commonplace. The series of interviews recorded during the 92nd meeting of the Internet Engineering Task Force (IETF), held in Dallas, Texas, in March 2015, demonstrated that this belief in the neutrality of standards and protocols is starting to change. It is becoming more apparent that promoting an open, secure, unfiltered and reliable Internet is essential for the rights to privacy, expression and assembly. But how can these concepts be addressed on the protocol level?

Without taking human rights into account while developing protocols, the human rights-enabling characteristics of the Internet are at risk. While the Internet was designed with freedom and openness of communication as core values, as the growth in scale and commercialization of the Internet have caused a shift in those values. The influence of such world-views started to compete with other values. The rights-enabling characteristics of the Internet will be endangered if they are not properly defined, described and protected. The reverse is also true: if we don’t protect human rights online, we risk loss of functionality and connectivity of the Internet itself.

Direction
Joana Varon

Production
Niels ten Oever

Research and script for interviews
Niels ten Oever and Joana Varon

Interviewer
Niels ten Oever

Editing
Marina Oriente

Script writing
Daniel Castro, Niels ten Oever, Joana Varon and Camila Agustini

Camera
Marina Oriente

Sound Design
Iuri Oriente

Animations
Fabio Cacossi

Narration
Carla Matero

Featuring
Adrian Farrel
Diego Lopez
Elliot Lear
Stéphane Bortzmeyer
Dan Harkins
Fred Baker
Nathaniel Borenstein
Suresh Krishnan
Ted Lemon
Daniel Kahn Gillmor
Stephen Farrell
Wendy Seltzer
Mark Nottingham
Spencer Dawkins
Aaron Falk
Kathleen Moriarty
Ben Campbell
Jari Arkko
Laura DeNardis

This film is released under a Creative Commons Attribution 4.0 International license.

Imported from https://www.youtube.com/watch?v=m1U0Ebix-aQ

When you’re just starting out in Rust, you start by building small programs. As we all know though, medium and large projects can have very different, unique kinds of problems that smaller projects never encounter. As our projects grow in size, we need to be increasingly concerned about code organization, separation of concerns, implementation hiding, and other techniques to manage growing complexity.

Most languages have tools and patterns to deal with this, and Rust is no exception. However, the patterns that we learned from other languages, especially in mainstream OO languages, are often unhelpful when applied to Rust, and this can lead to a roadblock when trying to transition to building moderate or large Rust programs.

This talk will cover a case study of a moderate sized game engine written in Rust and Lua, and show strategies for implementing things in Rust where common implementations in other mainstream languages are a poor fit. I’ll also discuss some examples of problems unique to Rust that ended up with very nice —but sometimes not obvious— solutions.

Along the way, I’d also like to discuss working with Rust in game development generally, and what it’s like getting Rust to run on mainstream game consoles.

Slides at https://kyren.github.io/rustconf_2018_slides/index.html

The blog post mentioned in this talk is at https://kyren.github.io/2018/09/14/rustconf-talk.html