Add modules with initial notes #3

benhylau · 2018-01-06T09:55:45Z

This PR is worked on by: @benhylau @dcwalk @darkdrgn2k @uditvira @ansuz and is work-in-progress. Although at some point when the task separation is more clear we should think about merging this and move to a more sane pull model :)

dcwalk · 2018-01-06T10:22:47Z

🐘👟🎉 will review in a bit!

…

On Jan 6, 2018 10:55, "Benedict Lau" ***@***.***> wrote: @benhylau <https://github.com/benhylau> requested your review on: tomeshnet/p2p-internet-workshop#3 <#3> Add modules with initial notes. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEebYjfDpBLvGim-tTbRAuOFfvaMYGDaks5tH0MpgaJpZM4RVQrC> .

dcwalk

Nice start, I'll make a round of commits tomorrow most likely to fill in the bits I mentioned :)

dcwalk · 2018-01-07T18:06:45Z

module-1.md

+
+## 2: Hands-on and material exploration
+
+- Introduce yourself, why you are interested in this workshop


Would aim to have the intros before a lecture.

Remember our conversation about giving a little bit of context first (to surface ideas) vs. intro at the start? A while back.

I don't remember, I think there are tradeoffs, but a round of names from the start and like a one sentence intro makes things feel less lecture, more participatory from the start.

I almost always follow that format.

dcwalk · 2018-01-07T18:12:33Z

module-1.md

+## 2: Hands-on and material exploration
+
+- Introduce yourself, why you are interested in this workshop
+- Activity for audience to "run their own app" on pre-configured nodes, where the apps are relatable with those we are familiar with from the Internet (e.g. Facebook, Dropbox, Whatsapp, Twitter, Spotify)


I think we need to figure out the best way to specify an activity, my sense:

format (e.g. group, pairs)

materials (including slides etc...)

objectives

Makes sense to me. Let's add to template.

dcwalk · 2018-01-07T18:12:57Z

module-1.md

+
+## 1: Topic introduction
+
+- Discuss familiar topics like net neutrality, internet service providers, and internet censorship


Should link to materials somewhere (incl. slide deck/site?), these could be contained within this repo

dcwalk · 2018-01-07T18:13:29Z

module-1.md

+
+## 4: Wrap-up and week ahead
+
+- Video on basic networking concepts (Metamesh intro videos)


Think we could rough these in with a link + short description

Yup will do.

benhylau · 2018-01-12T11:53:21Z

module-6.md

+## 2: Hands-on and material exploration
+
+- Build a 900 MHz LoRa sensor network with WiFi mesh network as backhaul
+- Use case for a community network that functions without internet connectivity


@uditvira hey can you add details to this one please

uditvira · 2018-01-14T21:16:02Z

module-6.md

+  * How does LoRa work? What are some alternatives?
+  * ISM band and spectrum allocation in Canada
+
+- Low Power Microcontrolers


@benhylau it could be possible to do a hands-on demo of Pi-to-Pi communication over LoRa instead of using Arduino's. That may be easier for people because they would already be familiar with Pi's at this point - however it won't be with low power micro-controllers anymore. Thoughts?

Just be careful logic levels are different between Arduino and the pi... Depending on what you do you may need a logic level. Converter..

I don't think not using low level micro processors is an issue in an educational setting.. It's more to intrude a concept to lora. We can note that there are low powered processors but I think the learning curve would be maybe to high to throw Arduino into all this to.

I don't think it is necessary to use Arduinos. It is sufficient to workshop LoRa transmission between two Raspberry Pi nodes, and then perhaps show an Arduino node with a power consumption comparison (just mentioning the numbers).

benhylau · 2018-01-22T20:47:18Z

module-1.md

+- USB WiFi radio that is ad-hoc or 802.11s-capable (e.g. TP-Link TL-WN722N)
+- SD card with [mesh-orange](https://github.com/tomeshnet/mesh-orange) pre-configured to mesh wirelessly with cjdns
+- Tools to discover node identity in the ad-hoc network and share human-readable names with others (e.g. [ssb-dns](https://github.com/ansuz/dnssb))
+- Contain Docker image for Secure Scuttlebutt and multiple Patchwork clients (i.e. [scuttlebot](https://github.com/ssbc/scuttlebot), [patchwork](https://github.com/ssbc/patchwork), [patchbay](https://github.com/ssbc/patchbay), [patchfoo](https://github.com/ssbc/patchfoo))


@ansuz Do you know if patchwork and patchbay can be installed on a Raspberry Pi and accessed over browser from a laptop client?

Patchwork is an electron app, and I don't think there is a way to access it remotely except by X11 Forwarding.

patchbay, patchfoo, and several other clients are written to run in the browser, so they'd just need a means of restricting access to maybe a single cjdns ip.

Initial sync with ssb can be a bit heavy for the CPU, so I'd recommend that nobody start with an existing ssb feed.

scuttlebot can be installed on an raspberry-pi, and it's all you need to access the network at a basic level. A basic UI could be made targeting this platform for whatever display you have. In my case, I plan to show basic (mainly connectivity) details of the ssb nodes attached to my mesh network on the installed sensehat. More details on getting started with sbot: https://www.scuttlebutt.nz/guides/cli-first-steps.html

@vuldin Do you know if Patchbay can be run on the Pi as well, and then exposed on some port and accessed through browser of a NAT client? The command line is cool, but since this is the first workshop for a general audience, where cli is usually unfamiliar, it's best to start at the browser and then cli to show this is the actual message that is exchanged.

@benhylau I'm not sure about patchbay since I haven't tried it. My plan is to just create a websocket wrapper for sbot that allows a webapp to communicate with the service. Then I can have that webapp run on any other more graphically capable device such as my phone or laptop.

It would be cool to have the Pi connect to the mesh and then provide that connection to my phone (along with connection to the secure-scuttlebutt network). This connection could be done either with the built-in Pi wifi (if available) or bluetooth. All this along with a battery-powered Pi means an entirely mobile mesh-connected system with ssb (and any other P2P app/service you run on the Pi).

Are you also building the webapp UI that talks to the ssb websocket? RE: mesh connection, yes the Raspberry Pi 3 configures the on-board WiFi as hostap and all ipv6 NAT traffic is passed to the cjdns tun interface: https://github.com/tomeshnet/prototype-cjdns-pi/blob/master/scripts/hostapd/nat.sh#L11

@benhylau I'm working on the UI, yes. I'm only at the point of having the framework in place, and it has basic connectivity/communication with the server. Once I have sbot sending data to websocket channels that are successfully displaying on the client I'll push the initial commit of the web project. Keep in mind that that level of functionality will be far from being a patchwork alternative, but it will be a good start.

By the way @benhylau , that's awesome that cjdns can be the provider for the IPv6 address for mesh networking, and that you are still also able to connect to the broader network provided by cjdns (when connected to an access point). I will still need to do testing since I'm unfamiliar with how this all works... I'll share any notes.

benhylau · 2018-01-22T20:48:42Z

module-1.md

+
+- Individuals
+
+### Activity


@ansuz Thoughts re: this as a workshop activity? Do you know how peer/friend discovery works over LAN?

I tried the other day and was able to sync another feed, while the other person could not see my posts.

It might work better if everyone is using the same hardware and software.

benhylau · 2018-01-22T20:50:03Z

module-1.md

+
+- USB WiFi radio that is ad-hoc or 802.11s-capable (e.g. TP-Link TL-WN722N)
+- SD card with [mesh-orange](https://github.com/tomeshnet/mesh-orange) pre-configured to mesh wirelessly with cjdns
+- Tools to discover node identity in the ad-hoc network and share human-readable names with others (e.g. [ssb-dns](https://github.com/ansuz/dnssb))


@ansuz Can ssb-dns allow us a reasonable way to address each other via names instead of cjdns IPv6 addresses?

There's some work involved to change your DNS to resolve to your ssb records, and I'm not sure it would be easier than passing around IPv6s. Theoretically, it's designed to work especially well for in offline environments.

Being worked on by @ansuz and @benhylau here: https://cryptpad.fr/code/#/1/view/Sc1Ktuf+APhkoFqbMhTp2Q/b4E11ypiIRno0MMKm6KJj5QU-q0CIqKz+Yfp5o29A0I/

benhylau · 2018-01-24T22:50:18Z

module-2.md

+    - Manually `echo`ing plaintext and HTTP messages into `netcat` is like you performing the task of an application (including our day-to-day ones, and the peer-to-peer ones we were playing with the week before)
+- End the group stage and take four volunteers to form a more-than-two-node network using the network switch
+    - Point out two people in different groups may have selected the same IPv4 address, like how two previously disjoint communities gave the same street name and house number, which only becomes a problem when we bridge these two communities (talk about NAT and self-assignment of IPv6)
+- Show how we can talk to multiple addresses from one node


@darkdrgn2k Only here we start using cjdns. Earlier parts are over clear IPv4s.

darkdrgn2k · 2018-01-25T15:05:36Z

module-2.md

+- An even number of Raspberry Pi 3s
+- SD cards with mesh-orange images with all necessary interfaces pre-configured and programs pre-installed (e.g. ifconfig, netcat, cjdns)
+- Ethernet cables equaling the number of Raspberry Pis
+- Laptops that can make a SSH session to each Raspberry Pi (each running a Host AP with unique SSID)


One issue we may have is as all these nodes come up there will be so many SSIDs with default passwords floating around that it may be difficult to identify which one is yours.

We will need a way to "lock in" the ssid for each node and record it with a label on the box.

Without using configs perhaps we can tie the ssid to the MAC address of the onboard wireless adapter? or maybe even Ethernet?

Yes I think we must drop a unique ssid in conf.d for each node. I already have to do this for two nodes otherwise I don't know which test2 I am connected to.

dcwalk · 2018-01-25T19:52:02Z

Okay I'm feeling like having a single PR might be too big to really dig in on each lesson, is there a date after which we aim to merge this in, and separate out remaining work?

Module 2 looks pretty far along, but I have some questions about how the initial intro and discussion will be handled (e.g. I think we don't want to just say "discuss" but also create materials, or identify arguments and perspectives?)

benhylau · 2018-01-25T23:17:07Z

@dcwalk As noted here I am hoping to merge this in asap :) perhaps we should just merge this then have separate PR for each module?

Module 2 looks pretty far along, but I have some questions about how the initial intro and discussion will be handled (e.g. I think we don't want to just say "discuss" but also create materials, or identify arguments and perspectives?)

Yes those sections are not yet done and I have not had time to think about them. Once we divide up the work perhaps we will have people contribute to those sections.

jkms · 2018-01-26T01:25:27Z

module-1.md

+_Preference to those that require minimal steps (e.g. exchanging keys, after `docker start`) and have a familiar UI._
+
+    - Secure Scuttlebutt / Patchwork (need to pin public keys)
+    - IPFS (auto peer but need to share content hash)


https://hub.docker.com/r/jkms/rpi-go-ipfs/

this is tested and working using HypriotOS on my RPI3. GH here: https://github.com/jkms/go-ipfs

benhylau · 2018-01-26T13:57:41Z

module-1.md

+
+## 3: Discussion and reflection activity
+
+- Reflect on the role of technology in society


Perhaps a short version of this? https://communitytechnology.github.io/docs/intro-ct/investigate-tech/

benhylau · 2018-01-26T14:03:09Z

module-2.md

+
+## 3: Discussion and reflection activity
+
+


Something fun? http://networks.land/activities/i-think-therefore-icann/
Not sure if enough time for this.

@dcwalk to follow up

benhylau · 2018-01-31T04:06:35Z

As discussed during meeting, we are merging this in and will have per module PRs to continue future work. See https://github.com/tomeshnet/tpl-workshop/milestone/1

Add modules with initial notes

c1b91a8

benhylau requested a review from dcwalk January 6, 2018 09:55

dcwalk reviewed Jan 7, 2018

View reviewed changes

Add details to some activities and week-ahead material

42338e4

benhylau commented Jan 12, 2018

View reviewed changes

Expanded low-power section in module 6

d652fde

uditvira reviewed Jan 14, 2018

View reviewed changes

benhylau added 3 commits January 18, 2018 17:25

Add Activity for Module 2

03deb3c

Change template and update modules

ca468fa

Format edits for modules-1

787d4ad

benhylau commented Jan 22, 2018

View reviewed changes

benhylau commented Jan 24, 2018

View reviewed changes

darkdrgn2k reviewed Jan 25, 2018

View reviewed changes

jkms reviewed Jan 26, 2018

View reviewed changes

benhylau commented Jan 26, 2018

View reviewed changes

Update modules with high level descriptions drawn from planning meeting

84f5421

benhylau merged commit 708ee68 into master Jan 31, 2018

This was referenced Jan 31, 2018

Investigate ssb #13

Closed

Investigate ipfs #14

Closed

benhylau deleted the modules branch February 24, 2018 15:24


		## 2: Hands-on and material exploration

		- Introduce yourself, why you are interested in this workshop


		## 1: Topic introduction

		- Discuss familiar topics like net neutrality, internet service providers, and internet censorship


		## 4: Wrap-up and week ahead

		- Video on basic networking concepts (Metamesh intro videos)


		## 3: Discussion and reflection activity

		- Reflect on the role of technology in society

Add modules with initial notes #3

Add modules with initial notes #3

Conversation

benhylau commented Jan 6, 2018 • edited

dcwalk commented Jan 6, 2018 via email

dcwalk left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

uditvira Jan 14, 2018 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dcwalk commented Jan 25, 2018

benhylau commented Jan 25, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

benhylau commented Jan 31, 2018 • edited

benhylau commented Jan 6, 2018 •

edited

uditvira Jan 14, 2018 •

edited

benhylau commented Jan 31, 2018 •

edited