Hi, I would like to propose a talk.

Title:

Visualising third-party website trackers

Abstract:

In this talk we shall look into the lessons learned from migrating a legacy privacy add-on using ES6 from SVG to Canvas, synchronous to asynchronous data capture & storage, with performance being the key factor. Canvas comes with its own challenges and we shall look into practical examples of how we tackled them. We shall also look into the concepts behind JavaScript physical simulations in order to understand the graph networks & hierarchies and the web-worker based approach for better graph performance. Lastly, let's see how all of this can be converted to an immersive virtual reality experience using A-Frame!

This is also an attempt to gain insights into web tracking and spark curiosity into the world of data privacy 😊

Slides:
https://docs.google.com/presentation/d/1V6XG7rK3c8YcMRrIUGuA217UhWee4PSuYr1nyQlfIfY/edit?usp=sharing

Notes:

• https://medium.freecodecamp.org/what-you-should-know-about-web-tracking-and-how-it-affects-your-online-privacy-42935355525
• https://princiya777.wordpress.com/category/lightbeam/

Title: Cover Your Apps While Still Using npm

Abstract:
In the front-end and Node.js ecosystems, we’ve had two extinction-level events: left-pad and pinkie-promise.

These events were both caused by something simple - a module became temporarily unavailable. Something seemingly innocuous caused thousands of developers and businesses builds to break and installs to fail. They weren’t prepared, and many were eager to blame npm as the single point of failure of the entire JavaScript ecosystem.

In reality, npm has made it dead-simple for developers and organizations to make sure their modules and highly available. The majority of the ecosystem isn’t aware of this, nor do they implement it effectively.

In this talk, we’ll go over how the dependency tree works at a high level, how you can get bitten by it, and how you can cover your apps - both as developer and as a business.

Audience:
Attendees will leave with an understanding of the more obscure parts of npm and what they're actually getting when they install a module. They'll learn how to set up safeguards - at a personal and professional level - against the common issues that npm has as a platform, so they don't get bitten by the next left-pad incident or registry outage.

Hey folks 🤗

I would love to talk about how to get started with hardware hacking as a JavaScript developer :)

Abstract

For many web developers the world of hardware is very intimidating. There is no easy way to go back from a broken to a working project state. You break something, you replace it — there is no Ctrl/Cmd + z. However, getting a project to work is incredibly fun and rewarding.

From an API for your coffee machine to a Porg that screams every time your Webpack build fails to playing games with hundreds of people at the same time, the only limit is your imagination*.

You might not leave this talk with a degree in Electrical Engineering**, but you'll learn useful basics to help you enter the wonderful world of hardware. We'll look at different ways to combine JavaScript and hardware, from APIs all the way to JS enabled microcontrollers. All tied up with some live demos. At the end you won't be able to wait to start your own hardware adventure!

*and maybe your patience
**unless you already have one

Title: Building Foundations of the Node.js Community

Abstract:
Node.js is an amazing project in terms of code - it’s evolved rapidly to cover an immense landscape, from web apps, desktop apps, APIs, IoT, robotics, and beyond. There’s something else that Node has also been absolutely killer with, though: the community.

One really awesome thing is that the Node.js community has an established community for building the Node community. How meta is that? The Node.js project is sectioned off into different Working Groups (WGs) that are tasked with different objectives - the one that was tasked with building the community was the Evangelism WG.

That said, there’s a transition happening. The Evangelism WG planted the seed Node.js Community efforts. Now, the Community Committee has taken this a step further and is mobilizing to start exploding the awareness and understanding of Node and its diverse ecosystem.

Attendees will gain an understanding of what the Node.js Community Committee is, what it's goals are, and how they can start getting involved.

Audience:
Node.js is going through a community revolution right now, and people across the world are interested in the discussions happing around Node.js + Community.

As chairperson of the Node.js Community Committee, I'm working to help empower anyone who is interested in Node.js and cares about enabling people of all kinds to contribute to OSS, build awesome applications, learn to code, or otherwise engage with Node.js.