diff --git a/digests/README.md b/digests/README.md new file mode 100644 index 0000000..4e4acda --- /dev/null +++ b/digests/README.md @@ -0,0 +1,17 @@ +=== +Digests: A weekly digest for community mesh networking events +=== + +# Purpose + +The documents under this directory are digests by week of different +events in the community internet world (as far as @hurricos saw on +that week). @hurricos intends to publish these digests Friday morning +each week starting 29 Nov 2019. + +## How to get on a particular digest + +If you want to make sure you're on a particular digest, please send me +an email @ [hurricos@gmail.com](mailto:hurricos@gmail.com) before +midnight weekly on Thursday. You can always send me an email if you +want me to see something and put it in here. diff --git a/governance/coordination-structure.md b/governance/coordination-structure.md index 8739c82..6a2c2d7 100644 --- a/governance/coordination-structure.md +++ b/governance/coordination-structure.md @@ -11,9 +11,6 @@ We reflected and discussed on governance during the [November 12 Planning Meetin - Make use of our decentralized **collaboration tools**: - Applicable rooms on [our chat](https://chat.tomesh.net/) - Our [GitHub organization](https://github.com/tomeshnet). - -As per the 2018 November Planning Meeting: - - Only people who have been involved with Toronto Mesh for one cycle or longer will be assigned lead roles. ## Decision Making @@ -26,33 +23,81 @@ Toronto Mesh uses voting to determine whether we have reached consensus: ## Working Groups +### Responsibilities of Working Group Leads + +Central Org + - Organize meetups and planning sessions + - Post event details to the tomesh.net website + +Tools + - Maintain the following infrastructure services: + - tomesh.net website server + - chat.tomesh.net Riot UI server for Matrix chat + - matrix.tomesh.net Matrix server + - webmail.tomesh.net Email web client + - y.mirror.tomesh.net and h.mirror.tomesh.net mesh mirrors + +Deployment + - Coordinate node deployment efforts + +Website + - Maintain the tomesh.net website + - Review pull requests to the [tomesh.net](https://github.com/tomeshnet/tomesh.net) repo + +Outreach + - Identify outreach opportunities and share with the rest of the group + - Drive speaking and workshop events + +hello@tomesh.net Monitoring + - Respond to all messages that arrive to hello@tomesh.net address + +Code of Conduct Monitoring + - Monitor coc@tomesh.net and meetups to make sure members and attendees are following the Code of Conduct + +### Cycle VIII (2019 May) + +Working group leads established at the May 2019 Planning Meeting: + +| Working Group | Lead | +|--------------------------------------------|---------------------| +| **Central Org** (_ongoing_) | Tim | +| **Tools** (_ongoing_) | HeavyMetal | +| **Node Tech** (_ongoing_) | darkdragon2k | +| **Deployment** (_ongoing_) | Tim | +| **Website** (_ongoing_) | dasanchez | +| **Outreach** (_ongoing_) | benhylau, Tim, Ryan | +| **hello@tomesh.net Monitoring** (ongoing) | Hank,Tim | +| **Code of Conduct Monitoring** (_ongoing_) | Hank | + + + ### Cycle VII (2018 November) Working group leads established at the November 2018 Planning Meeting: -| Working Group | Lead | -| --- | --- | -| **Central Org** (_ongoing_) | dasanchez | -| **Tools** (_ongoing_) | HeavyMetal | -| **Deployment** (_ongoing_) | Pedro.S | -| **Website** (_ongoing_) | garry | -| **Outreach** (_ongoing_) | benhylau, Tim, Hank | -| **hello@tomesh.net Monitoring** (ongoing) | Hank, benhylau | -| **Code of Conduct Monitoring** (_ongoing_) | Hank | +| Working Group | Lead | +|--------------------------------------------|---------------------| +| **Central Org** (_ongoing_) | dasanchez | +| **Tools** (_ongoing_) | HeavyMetal | +| **Deployment** (_ongoing_) | Pedro.S | +| **Website** (_ongoing_) | garry | +| **Outreach** (_ongoing_) | benhylau, Tim, Hank | +| **hello@tomesh.net Monitoring** (ongoing) | Hank, benhylau | +| **Code of Conduct Monitoring** (_ongoing_) | Hank | ### Cycle VI (2018 May) Sixth working groups with leads established at May 17 Planning Meeting. Excerpted from [Planning Meeting Notes - May 17, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20180517_planning-meeting-notes.md) -| Working Group | Lead | -| --- | --- | -| **Central Org** (_ongoing_) | chrisbarless | -| **Tools** (_ongoing_) | chrisbarless | -| **Deployment** (_ongoing_) | Pedro.S | -| **Website** (_ongoing_) | garry | -| **Social Outreach** (_ongoing_) | Kumash | -| **Email Monitoring** (ongoing) | Hank | +| Working Group | Lead | +|---------------------------------|----------------| +| **Central Org** (_ongoing_) | chrisbarless | +| **Tools** (_ongoing_) | chrisbarless | +| **Deployment** (_ongoing_) | Pedro.S | +| **Website** (_ongoing_) | garry | +| **Social Outreach** (_ongoing_) | Kumash | +| **Email Monitoring** (ongoing) | Hank | | **Code of Conduct** (_ongoing_) | Hank, benhylau | ### Cycle V (2017 November) @@ -60,73 +105,73 @@ Excerpted from [Planning Meeting Notes - May 17, 2017](https://github.com/tomesh Fifth working groups with leads established at November 23 Planning Meeting. Excerpted from [Planning Meeting Notes - November 23, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20171123_planning-meeting-notes.md) -| Working Group | Lead | -| --- | --- | -| **Central Org** (_ongoing_) | dasanchez | -| **Tools** (_ongoing_) | benhylau | -| **Deployment** (_ongoing_) | darkdrgn2k | -| **Website** (_ongoing_) | garry | -| **Code of Conduct** (_ongoing_) | dcwalk | +| Working Group | Lead | +|---------------------------------|------------| +| **Central Org** (_ongoing_) | dasanchez | +| **Tools** (_ongoing_) | benhylau | +| **Deployment** (_ongoing_) | darkdrgn2k | +| **Website** (_ongoing_) | garry | +| **Code of Conduct** (_ongoing_) | dcwalk | ### Cycle IV (2017 April) Fourth working groups with leads established at April 24 Planning Meeting. Excerpted from [Planning Meeting Notes - April 24, 2017](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20170424_planning-meeting-notes.md) -| Working Group | Lead | -| --- | --- | -| **Central Org** (_ongoing_) | dasanchez | -| (Welcome/Intros) **Onboarding** (_ongoing_) | Pedro.S | -| **Tools** (_ongoing_) | co-lead benhylau, dasanchez, Pedro.S, udit | -| **Website** (_ongoing_) | dcwalk | -| **Virtual Mesh** (_ongoing_) | | -| **Deployment** (_ongoing_) | Pedro.S | -| **Hardware** aka **node.tech** (_ongoing_) | udit | -| **Code of Conduct** (_ongoing_) | dcwalk | +| Working Group | Lead | +|---------------------------------------------|--------------------------------------------| +| **Central Org** (_ongoing_) | dasanchez | +| (Welcome/Intros) **Onboarding** (_ongoing_) | Pedro.S | +| **Tools** (_ongoing_) | co-lead benhylau, dasanchez, Pedro.S, udit | +| **Website** (_ongoing_) | dcwalk | +| **Virtual Mesh** (_ongoing_) | | +| **Deployment** (_ongoing_) | Pedro.S | +| **Hardware** aka **node.tech** (_ongoing_) | udit | +| **Code of Conduct** (_ongoing_) | dcwalk | ### Cycle III (2016 November) Third working groups with leads established at November 12 Planning Meeting. Excerpted from [Planning Meeting Notes - November 12, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20161112_planning-meeting-notes.md) -| Working Group | Lead | -| --- | --- | -| **Central Org** (_ongoing_) | dcwalk | -| (Welcome/Intros) **Onboarding** (_ongoing_) | josh_o | -| **Tools** (_ongoing_) | benhylau | -| **Website** (_ongoing_) | garry | -| **Virtual Mesh** (_ongoing_) | benhylau | -| **Miniconf** (Jan deadline) | dcwalk | -| **Deployment** (Feb deadlines and _ongoing_) | udit | -| **Funding/Grants** (Jan to Mar deadlines and _ongoing_) | anastasia | -| **Code of Conduct** (_ongoing_) | dcwalk, anastasia | +| Working Group | Lead | +|---------------------------------------------------------|-------------------| +| **Central Org** (_ongoing_) | dcwalk | +| (Welcome/Intros) **Onboarding** (_ongoing_) | josh_o | +| **Tools** (_ongoing_) | benhylau | +| **Website** (_ongoing_) | garry | +| **Virtual Mesh** (_ongoing_) | benhylau | +| **Miniconf** (Jan deadline) | dcwalk | +| **Deployment** (Feb deadlines and _ongoing_) | udit | +| **Funding/Grants** (Jan to Mar deadlines and _ongoing_) | anastasia | +| **Code of Conduct** (_ongoing_) | dcwalk, anastasia | ### Cycle II (2016 August) Second working groups established at August 05 Planning Meeting. Excerpted from [Planning Meeting Notes - August 5, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20160805_planning-meeting-notes.md) -| Working Group | Members | -| --- | --- | -| **Prototype** | | -| **Deployment** | | -| **Code of Conduct** | Lee, Nick, Ben, Leandro, Dennis, David, Curtis, Michael, dcwalk | -| **Website** | | -| **Logo** | | -| **Vision Statement** | | +| Working Group | Members | +|----------------------|-----------------------------------------------------------------| +| **Prototype** | | +| **Deployment** | | +| **Code of Conduct** | Lee, Nick, Ben, Leandro, Dennis, David, Curtis, Michael, dcwalk | +| **Website** | | +| **Logo** | | +| **Vision Statement** | | ### Cycle I (2016 April) First working groups established at April 18 Planning Meeting. Excerpted from [Planning Meeting Notes - April 18, 2016](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20160418_meeting-notes.md) -| Working Group | Members | -| --- | --- | -| **Hardware** | Ben, Udit, dcwalk | -| **Software** | Ben, Garry | -| **Use Cases for the Mesh** | Udit, Ben, Garry | -| **Outreach** | Vince, Ben | -| **Literacy Development** | Yuri, Matt | -| **Knowledge Management** | Matt, dcwalk | -| **Design** | Matt | -| **Website** | dcwalk, Matt, Garry | +| Working Group | Members | +|----------------------------|---------------------| +| **Hardware** | Ben, Udit, dcwalk | +| **Software** | Ben, Garry | +| **Use Cases for the Mesh** | Udit, Ben, Garry | +| **Outreach** | Vince, Ben | +| **Literacy Development** | Yuri, Matt | +| **Knowledge Management** | Matt, dcwalk | +| **Design** | Matt | +| **Website** | dcwalk, Matt, Garry | diff --git a/images/20190221_meetup-drawings/benhylau.jpg b/images/20190221_meetup-drawings/benhylau.jpg new file mode 100644 index 0000000..58e9a8a Binary files /dev/null and b/images/20190221_meetup-drawings/benhylau.jpg differ diff --git a/images/20190221_meetup-drawings/dasanchez-1.jpg b/images/20190221_meetup-drawings/dasanchez-1.jpg new file mode 100644 index 0000000..a7948f2 Binary files /dev/null and b/images/20190221_meetup-drawings/dasanchez-1.jpg differ diff --git a/images/20190221_meetup-drawings/dasanchez-2.jpg b/images/20190221_meetup-drawings/dasanchez-2.jpg new file mode 100644 index 0000000..3ac9593 Binary files /dev/null and b/images/20190221_meetup-drawings/dasanchez-2.jpg differ diff --git a/images/20190221_meetup-drawings/garrying.jpg b/images/20190221_meetup-drawings/garrying.jpg new file mode 100644 index 0000000..8ba482e Binary files /dev/null and b/images/20190221_meetup-drawings/garrying.jpg differ diff --git a/images/20190221_meetup-drawings/makeworld.jpg b/images/20190221_meetup-drawings/makeworld.jpg new file mode 100644 index 0000000..31b36d0 Binary files /dev/null and b/images/20190221_meetup-drawings/makeworld.jpg differ diff --git a/images/20190221_meetup-drawings/shrinks99.jpg b/images/20190221_meetup-drawings/shrinks99.jpg new file mode 100644 index 0000000..80e44eb Binary files /dev/null and b/images/20190221_meetup-drawings/shrinks99.jpg differ diff --git a/images/20190221_meetup-drawings/tim.jpg b/images/20190221_meetup-drawings/tim.jpg new file mode 100644 index 0000000..63be65f Binary files /dev/null and b/images/20190221_meetup-drawings/tim.jpg differ diff --git a/index/Media.md b/index/Media.md new file mode 100644 index 0000000..b74c847 --- /dev/null +++ b/index/Media.md @@ -0,0 +1,8 @@ +=== +Media: Simple things you can share with almost anyone +=== + +# Sudoroom's propaganda repo +https://github.com/sudomesh/propaganda +- Plenty of links here for stuff like stickers + diff --git a/index/README.md b/index/README.md new file mode 100644 index 0000000..6ecf216 --- /dev/null +++ b/index/README.md @@ -0,0 +1,95 @@ +=== +Index: An index against over everything community mesh +=== + +# Preface +For now this is where @hurricos is dumping different lists of sites +and what they're up to. @hurricos intends in the long-run to create or +contribute to a Mediawiki-based wiki to act as an "index" or +"directory" for anyone to get anywhere in the space of community +network projects. + +## How should they be organized? +Put things into markdown by category (think: Mediawiki-based +Categories, like at the bottom of the [Mediawiki page for +categories](https://www.mediawiki.org/wiki/Help:Categories)) + +For now though I'm just stubbing in headers and listing the categories +below it in this readme. Organize it later. + +# Media +- Simple things you can share with almost anyone + +## Sudoroom's propaganda repo +https://github.com/sudomesh/propaganda +- Plenty of links here for stuff like stickers + +## Tomesh / dasanchez' Presentation resources +https://github.com/tomeshnet/tomesh.101/tree/master/presentations +- Great for presenting?? @hurricos hasn't checked this + +# Mailing lists + +## Sudoroom's mesh mailing list +https://sudoroom.org/pipermail/mesh/ +- Fairly active it appears! + +## Spinics linux wireless mailing list +https://www.spinics.net/lists/linux-wireless/ +- This is good for getting a pulse on how existing hardware is being + maintained under Linux + +## OpenWrt mailing list +https://lists.infradead.org/pipermail/openwrt-devel/ +- OpenWrt is very popular and this mailing list is used by everyone + for everything. + +# Hardware documentation + +## Wikidevi +https://wikidevi.com +- This is dead since Hallowe'en 2019. This was the best resource for + hardware info. The database logic that M86 created in it was + migrated by and large to TechinfoDepot. + +## Techinfodepot +http://en.techinfodepot.shoutwiki.com/wiki/Main_Page +- This is the inheritor of M86's + wikidevi. [DarkShadow](http://en.techinfodepot.shoutwiki.com/wiki/User:DarkShadow) + is the primary maintainer. +- @hurricos uses Firefox; he right clicked the search button on the + left and "Add Keyword for this Search..." to "tech" so that he could + search-bar "Tech Qualcomm Atheros" to get to [this + page](http://en.techinfodepot.shoutwiki.com/wiki/Qualcomm_Atheros). This + is incredibly useful whenever you need to find information about a + particular chipset, SoC, vendor, driver, architecture. This is where + everyone should put their data about hardware. + + +## Tomesh's stuff on Github +https://github.com/tomeshnet/documents/tree/master/technical +- These are mostly basically lab reports. Very very useful because + they show practical implementations. + +## (How to take pictures of hardware) +You should take pictures of hardware in very bright, very +point-source, very "angled" light. This makes it very clear to see the +stuff printed on the chip on top. See for example [this +picture](http://en.techinfodepot.shoutwiki.com/wiki/File:Meraki_MR24_PCB_Back.jpg) +taken by @hurricos on a Motorola Moto X Pure Edition (an $80 phone +these days). You can spot stuff even normal eyes can't see can't see. + +# Mesh groups + +## Tomesh +https://tomesh.net +- @hurricos / @darkdrgn2k / @benhylau, etc +- Toronto + +## Massmesh +https://massmesh.org/ +- @hurricos isn't sure what they're really up to + +## btvmesh +https://btvmesh.net/ +- @hurricos' project; Not really off the ground yet diff --git a/meeting_notes/20190516_planning-meeting-notes.md b/meeting_notes/20190516_planning-meeting-notes.md new file mode 100644 index 0000000..2fcfec9 --- /dev/null +++ b/meeting_notes/20190516_planning-meeting-notes.md @@ -0,0 +1,183 @@ +--- +title: Meeting Notes - May 16, 2019 +location: FREE GEEK TORONTO +attendees: 9 +date: 2019-05-16 +startTime: 18:30 +endTime: 21:15 +--- + +# Toronto Mesh Planning Session + +2019 May 16th +FREE GEEK TORONTO + +## Attendees +Attendees: +- **HeavyMetal** +- **ryan_f**: +- **dasanchez**: +- **kos**: +- **makeworld**: +- **DarkDrgn2k**: +- **Hank** +- **Tim** +- **Jeff**: + + +### Toronto Mesh Recap (7:00-7:30) + +- **TECH UPDATES** + - **Prototype Release v0.4 Highlights** + - Doc for modules in modules.md (moved from README) + - Notes on how to use cjdns and yggdrasil + - Profiles available during install time to avoid presenting too many options + - Yggdrasil officially added + - YGG IPv6 addresses for all access point clients + - Bumped IPFS version + - Mesh point and ad-hoc both work on 2 GHz + - RPi0 AP works now + - IPFS works on YGG + - Contrib module can be set during install + - Welcome/landing page + - Patch releases: 0.41 and 0.42 + - hostapd / cjdns DNS addresses + - patchfoo rolled back to working version + - ADVERTISE v0.4 RELEASE ON TWITTER! => dasanchez + + - **Prototype Release v0.5 Roadmap** + - Modularizing code for .deb packages readiness + - Being able to select networking protocol (not forcing cjdns) + - Multiple architectures supported (including x86/x64) + - IPFS will use less resources + - hostname will change depending on what platform is being used + - YGG tunnel + - Geolocation for pushing that along with the node info + - Grafana, IPFS, YGG, Prometheus updated + - Config files + - MAIN GOAL: PUBLISH TO DEB REPO for improved **USER EXPERIENCE** + +- **Org Updates (outreach / talks)** + - benhylau's workshop facilitation session + - Workshop highlights (Hank): + - Modularizing content, if we only want to present one section, that is possible. + - The workshop is essentially complete after current sprint and will not see further updates, for now. + - [Workshop repo](https://github.com/tomeshnet/p2p-internet-workshop) + - Thanks lynx & bennlich + - **CivicTechTO** + + - https://www.youtube.com/watch?v=Qg9-k7tguvI +- **Tools Updates** + - Upgraded droplets + - Matrix droplet was upgraded in D.O. after getting overloaded, but it wasn't enough + - Justin donated VM space for the Matrix and Riot servers + - Migration of Matrix server + - Mesh services are now running off proxmox (hypervisor) + - Script is in the Tools channel (WIP) + +### Governance (7:30-8:00) +- Have to be around for at least one cycle (6 months) +- Working group lead roles: + - Design/branding + - Hank - "Hard maybe for next cycle" + - Tim is up for contributing in this area + - Node tech (New role) + - Yurko + - Tools: HeavyMetal -> HeavyMetal + - Central Org: dasanchez -> Tim + - Organize meetups and planning sessions + - Post event details to the tomesh.net website + - Deployment: Pedro.S ? -> Tim + - For now, shift emphasis toward _Technical Literacy_ / _Technical Outreach_? + - Technical advocacy / public service approach. + - Pop up model for a talk / workshop / seminar + - Coordinate node deployment efforts + - Any (experimental) setup needs to be matched up with an appropriate outreach activity + - Clarify goals in respect of these activities + - Website: garry -> dasanchez + - Maintain the tomesh.net website + - Review pull requests to the tomesh.net repo + - Outreach: benhylau, Tim, Hank -> benhylau, ryan_f, Tim + - Identify outreach opportunities and share with the rest of the group + - Drive speaking and workshop events + - dasanchez will give moderator persmissions to Ryan and Tim + - Code of Conduct monitor: Hank -> Hank + - Monitor coc@tomesh.net and meetups to make sure members and attendees are following the Code of Conduct + - Email monitor: Hank -> Hank + - Respond to all messages that arrive to hello@tomesh.net address + - HeavyMetal will add Tim to the hello@tomesh.net list of recipients + +### Next Cycle Roadmap (8:00-9:00) + +- Meeting Schedule + - Meet & Greet + - : No more meet & greets scheduled past planning session + - : Schedule at least one meeting after the planning session + - Aug, Sep, Oct: Meet & Greet + - Nov: Planning session + - January: Meet & Greet + - Meeting in July + - Different space needed, FreeGeek will not be available + - Seneca, YLabs? + - Working groups (Update) Sync + - Removed as its own meeting, will get updates via Mesh Sync, Meet & Greets and Planning sessions (time allowing) + - Mesh Sync + - Originally bi-weekly video calls worldwide - more adhoc for the time being + - To connect and talk with with mesh people internationally + - Book times, talk, etc + - Need people to run them + - Dante, kos could run weekday evenings in rotation with others + +- Outreach Opportunities + - Content Moderation Symposium: + - https://contentmoderation.art + - dasanchez is doing a talk/workshop + - May 25 + - North York Central Library + - Talk about decentralization **by us** + - Cryptography activities afterward **not by us**, done by the library + - July 6th is the tentative + - Can change, but will likely be a Saturday afternoon + - dasanchez and makeworld cannot make that date + - DarkDrgn2k can come to help with tough questions + - dasanchez will request July 13 / 20 dates + - From Ryan - June 29: Multiculturalism + technology celebration @ FreeGeek + - We're invited, some grant money permitting food service + - Multicultural/ Technology themes - (like Picnic 2.0?) + - Toronto Mesh booth / table - node demos? + - What are we presenting? Discuss in chat. + +- Deployment + - Set a goal after discussion within the group + - Decide on how to acheive that goal + - Temporary deployment testing? + - Bring together ideas +- Branding + - Stickers / logo + - Logo document explaining usage + - [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) license? + - Add note / link to website with license from original creator + +- Website + - dasanchez will drive changes (🧠💩 together with Hank) + - Focus on documentation/info on mesh concepts + +- Node software stack + - See above: _have_ v0.5 released for next cycle + - Start Debian package work + - Make a documented roadmap, put on website with project? + +- Documentation + - Workshop + - Code repo docs are actively being worked on :white_check_mark: + +### Miscellaneous Notes: + +- ThinkPads from 2000's? +- N O D E zine: - https://n-o-d-e.net/zine/ +- [CANARIE](https://www.canarie.ca/) + - Provides cloud infra to technology groups +- Funding options + - How would funding/payment be handled (formal procedures/ orgs.)? +- Other Outreach Tasks + - Yurko will start looking into how to handle organization registrations to North York/Toronto library system diff --git a/mesh_sync/20190204_mesh-sync-notes.md b/mesh_sync/20190204_mesh-sync-notes.md new file mode 100644 index 0000000..4638cbe --- /dev/null +++ b/mesh_sync/20190204_mesh-sync-notes.md @@ -0,0 +1,123 @@ +--- +title: Mesh Sync Notes - Feb 4, 2019 +location: https://appear.in/tomeshnet +date: 2019-02-04 +startTime: 10:00 +endTime: 12:00 +--- + +📍 https://appear.in/tomeshnet +📅 Monday, February 4 + +| Timezone | Workshop | General | +|:---------|:---------|:---------| +| PST |`07:00 am`|`08:00 am`| +| EST |`10:00 am`|`11:00 am`| +| CEST |`04:00 pm`|`05:00 pm`| +| HKT |`10:00 pm`|`11:00 pm`| + +## What is this? + +Biweekly standing open-call for remote parties to sync up on topics of mutual interest. The hours are selected to make it possible for parties of different timezones to attend. + +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of six timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. + +The _Course_ hour is for topics relating to the [Building the Peer-to-Peer Internet workshop series](https://tomeshnet.github.io/p2p-internet-workshop/), such as discussing about workshop facilitation at a new location, the logistics of getting the hardware and software set up, funding opportunities for curriculum development, etc. + +The _General_ hour is for all other issues, such as [Prototype](https://github.com/tomeshnet/prototype-cjdns-pi) or [Mesh Orange](https://github.com/tomeshnet/mesh-orange) updates, IPFS live streaming discussions, showcasing your new project, or collective brainstorming of collaboration opportunities with Toronto Mesh. + +Lastly, please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of the things going on :satellite: + +## Attending + +📝 This person moves meeting notes to GitHub and resets the pad: +- benhylau + +👥 Please add your name to this list if attending: +- Hank +- DarkDrgn2K +- benhylau +- Tim +- Pam + +## Agenda + +| Start time | 20-min timeslot | Facilitator | +|:-------------|:----------------|:------------| +|`10:00 am EST`| Course 1 | Hank | +| | Course 2 | Pam | +| | Course 3 | | +|`11:00 am EST`| General 1 | | +| | General 2 | | +| | General 3 | | + +### Course 1: DX call & workshop slide updates +#### Objectives +- Discuss presenting @ DX workshops +- What does a workshop actually look like, do we have pictures? +- Workshop Remark overhaul update +#### Links +[Design Exchange](https://www.dx.org/) +[Remark Update Branch](https://github.com/tomeshnet/p2p-internet-workshop/tree/remark-module-1) + +### Course 2: Amber Initiative and People's Open +#### Objectives +- Updates on People's Open Mesh Group (Oakland) post Handshake grant +#### Links +[People's Open](https://peoplesopen.net/) + +## Meeting notes + +### Communications load balancing for Toronto Mesh (out-of-band) + +- Ben: Shifting communication tasks towards other people, now Ben is a central point of many relationships Toronto Mesh has with external parties (this has been discussed at roadmap meeting) +- DarkDrgn2k: Having an organization be the point of contact instead of a person makes it easier to shift communication from person to person +- Ben: Inbound is via `hello@` and that seems to work fine, but the connections that result from "marketing activities" (e.g. presenting at conferences, workshopping with groups) lead to a lot of centralized connections +- Hank: Perhaps this is an email probelm, people are getting replies from a personal account and now they contact that person instead of the org? +- Ben: Mesh Sync actually seems like a good place to do load balancing for communications, it gives external people more folks to talk to, and we can do a round of having people volunteer to become point contact for each relationship +- Tim: The follow up with people should be documented in the pad for each call + +### DX call & workshop slide updates + +- Hank: Design Exchange was asking about getting people to present parts +- Hank: Workshop overhaul is almost done! Will require help getting the build script working + - Ben to take care of script +- Pam: People's Open is looking into having workshops to onboard and teach new people +- [People's Open](https://peoplesopen.net/) will have a **Build your Own Internet** Workshop end of March (TBD) +- Looking into incorporating LibreRouter as a hardware module +- Create a more interactive experience, may partner with a local design group called [DynamicLand](https://dynamicland.org/) +- Inspired by Bret Victor and visual communication as interface in communicating concepts. [The Humane Representation of Thought](http://worrydream.com/#!/TheHumaneRepresentationOfThought/note.html) +- New education budget will also create stickers, brochures and community outreach material. Inclusion and diversity is important for the group and they want to invite participation. The goal is to train and educate future facilitators of different neighborhoods. Oakland is rich with diversity +- Mapping: Working on creating a 3d map/topography of the network to vizualize the nodes on the city scale +- Maybe it's helpful to visualize the "stack" of a mesh, from the physical to application layer... In architecture we have the foundation, structural, skin systems... that is visualized in layers +- Ben: Perhaps the workshop should be reworked to include these things as other modules? + +### Amber Initiative and People's Open + +- Ben: Loomio +1 (re: People's Open starting to use Loomio) +- Pam: + - Developing governance processes to allocate 100k Handshake grant to grow the project and increase sustainability. + - Education is a top priority for Peoples Open ~at least 10% of budget + - Reliability is another priority + - Recently partnered with the Internet Archive to install a [5Ghz Ubiquity Air Fiber](https://www.bhphotovideo.com/c/product/1239021-REG/ubiquiti_networks_af_5u_us_af_5u_airfiber_high_band_5.html/?ap=y&gclid=CjwKCAiA4t_iBRApEiwAn-vt-4c7v4mxJUxjxeHtw8sVP-1E3coR5nSHbEPehURjV80EDXli16Z6hhoCEckQAvD_BwE&lsft=BI%3A514&smp=Y) In Richmond,CA. 12 miles north of Oakland + +![](https://i.imgur.com/vDYz3nJ.jpg) + +![](https://i.imgur.com/J3LV7uv.jpg) + +- Ben: +1 on LibreRouter for workshop +- Ben: Open to reworking [P2P Internet Workshop](https://tomeshnet.github.io/p2p-internet-workshop/) and rebranding it as a collaborative effort with other mesh communities: + - More modular content + - More traditional mesh content (e.g. perhaps having LibreRouter as base hardware, this will also help engage existing communities behind LibreRouter) + - People's Open has a "station" model, what they planned at Our Networks 2018 + +## Communications load balancing + +| Organization | Toronto Mesh contact | Subject | Status | +|:-------------|:---------------------|:----------------|:-------| +| Toronto Public Library | @benhylau @dcwalk @darkdrgn2k | Mesh Workshop | Completed pilot, interested in next iteration | +| Florida Polytechnic | @Shrinks99 @darkdrgn2k @benhylau | Mesh Workshop | [Agreement to collaborate](https://hackmd.io/-9P_SzjKSROHUj8zEE_qqw?view), shipped some parts to Florida and got the group set up to facilitate module-1 | +| Guifi.net | @benhylau | Mesh Workshop | Completed module-1 facilitation + helped translate worksheet to _es_, discuss future opportunities | +| Palo Alto Library | @benhylau | Mesh Workshop | Introduction via Wendy (Internet Archive), had a [first call](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20181107_workshop-series-intro-for-city-of-palo-alto-library.md) | +| NYU Abu Dhabi | @benhylau | Mesh Workshop | Discussed with Michael about using syllabus at the university during Radical Networks 2018 | +| Design Exchange | Hank | Workshop collab | Had first call and relayed asks at February 4 Mesh Sync | diff --git a/mesh_sync/20190218_mesh-sync-notes.md b/mesh_sync/20190218_mesh-sync-notes.md new file mode 100644 index 0000000..d2c1f13 --- /dev/null +++ b/mesh_sync/20190218_mesh-sync-notes.md @@ -0,0 +1,200 @@ +--- +title: Mesh Sync Notes - Feb 18, 2019 +location: https://appear.in/tomeshnet +date: 2019-02-18 +startTime: 10:00 +endTime: 12:00 +--- + +📍 https://appear.in/tomeshnet +📅 Monday, February 18 + +| Timezone | Workshop | General | +|:---------|:---------|:---------| +| PST |`07:00 am`|`08:00 am`| +| EST |`10:00 am`|`11:00 am`| +| CEST |`04:00 pm`|`05:00 pm`| +| HKT |`10:00 pm`|`11:00 pm`| + +## What is this? + +Biweekly standing open-call for remote parties to sync up on topics of mutual interest. The hours are selected to make it possible for parties of different timezones to attend. + +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of six timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. + +The _Course_ hour is for topics relating to the [Building the Peer-to-Peer Internet workshop series](https://tomeshnet.github.io/p2p-internet-workshop/), such as discussing about workshop facilitation at a new location, the logistics of getting the hardware and software set up, funding opportunities for curriculum development, etc. + +The _General_ hour is for all other issues, such as [Prototype](https://github.com/tomeshnet/prototype-cjdns-pi) or [Mesh Orange](https://github.com/tomeshnet/mesh-orange) updates, IPFS live streaming discussions, showcasing your new project, or collective brainstorming of collaboration opportunities with Toronto Mesh. + +Lastly, please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of the things going on :satellite: + +## Attending + +📝 This person moves meeting notes to GitHub and resets the pad: +- Ben + +👥 Please add your name to this list if attending: +- Hank +- Ben +- Dante +- Tim +- Yurko +- Felix +- joeyxl +- CJD +- Pam + +## Agenda + +| Start time | 20-min timeslot | Facilitator | +|:-------------|:----------------|:------------| +|`10:00 am EST`| Course 1 | | +| | Course 2 | | +| | Course 3 | | +|`11:00 am EST`| General 1 | benhylau | +| | General 2 | dasanchez | +| | General 3 | | + +### General 1: Decentralized Web Camp 2019 +#### Objectives +- Brief on ideas being discussed in the organizing of DWeb Camp 2019 in July +- Discuss opportunities for event meshnet with local off-Internet applications +#### Links +- https://www.decentralizedweb.net + +### General 2: Toronto Mesh outreach things +#### Objectives +- Feb: Toronto Mesh monthly [Meet and Greet](https://tomesh.net/2019-02-21/meet-and-greet/) + - Drawing activity at our next one on Feb 21 + - General intro / onboard "package" previously discussed +- March: participate at [CodeAcross](https://www.eventbrite.ca/e/codeacrossto-2019-tickets-53330824933) +- April: opportunity to [speak at CivicTechTO](https://github.com/tomeshnet/documents/issues/112) +- May: opportunity to [organize activity at Pegah's UofT event](https://github.com/tomeshnet/documents/issues/111) + +## Meeting notes + +### Prototype updates + +- In process of releasing next version (final stages of testing) + - Adds yggdrasil (can give IP addresses to LAN devices not running yggdrasil, encryption done by Raspberry Pi) + - Cleaned up install scripts and added **Profiles** (finally!) + - Version bumps + other optimizations + - Welcome screen: + - cjdns + yggdrasil logical map + - live bandwidth numbers + - list of services running on the node + - ben: we can use this welcome screen for intro to new people + - yurko: help with testing https://github.com/tomeshnet/prototype-cjdns-pi/pull/291 + - yurko: next release will focus on debianizing modules + - ben: so we need https://github.com/tomeshnet/mesh-services/issues/8 + +### Decentralized Web Camp 2019 + +- https://www.decentralizedweb.net by Internet Archive +- 2019 conf: Camp @ Mushroom Farm - maybe + - Broken Internet as a "feature" +- 2018 had SSB, IPFS, and others, but not a lot of meshnet representation (backpack for hope was there) +- Offer some sort of "local services" stack- IPFS repository, SSB pub, etc. +- benhylau is looking into coordinating Toronto Mesh representation this year +- LibreRouter is nearing production- hopefully after Chinese New Year +- List of people to reach out to: + - [Aether](https://getaether.net) (Burak) + - [SSB](https://www.scuttlebutt.nz) + - [DAT](https://beakerbrowser.com) + - [IPFS](https://ipfs.io) + - [Yggdrasil](https://yggdrasil-network.github.io) (Arceliar + Neil) + - [CJDNS](https://github.com/cjdelisle/cjdns) (Caleb) + - [LibreRouter](https://librerouter.org) (Nico) + - [Manyverse](https://www.manyver.se) (Andre) + - [Cabal](https://cabal-club.github.io) (noffle) + - [Disaster Radio](https://disaster.radio) (People's Open) + - [Matrix](https://matrix.org) +- Cheap routers for access points: + - Meraki + OpenWRT + - Aruba Networks AP (Used a lot at other conferences) +- See [our meeting notes](https://github.com/dweb-camp-2019/organizing/pull/1/files) + +### Toronto Mesh outreach things + +- Feb: Toronto Mesh monthly [Meet and Greet](https://tomesh.net/2019-02-21/meet-and-greet/) + - Drawing activity at our next one on Feb 21 + - Prompt for drawing activity? + - **How do you think connectivity works** vs **how do you want it to work**? + - The former is already understood by tomesh people, but it would help identify pain points to improve upon. + - Focus can be on technical and non-technical aspects. + - What do we do with the output? Digitize and publish: + - On SSB + - Make a story/gallery with all the sketches + - Save media for OurNetworks exhibit + - hank: 11' x 17' scanner + - dante: bring papers + - tim: bring roll of paper + - ben: bring markers + - Outline: + - _Draw how internet works today, then... draw how do you want it instead?_ + - _Draw your cyber world, then... draw how to improve your pain points?_ + - Present afterwards + - Broad (draw whatever you want) vs. focused (draw your ideal node user interface and how you interact with it) + - ben: we should be able to string together a story from the drawings and put a SSB post + - hank: _maybe_ volunteering to "compose some stuff" with the drawing _at some point in time_ + - General intro / onboard "package" previously discussed + - What is tomesh and what does it do? A 5-10 minute intro would be good to introduce newcomers + - felix: Freifunk (since 2003): + - People come and want to set up router (usually) + - Depends on level of engagement + - pam: People's Open: + - First Tuesday of the month -- pizza, hangout, TCP/IP zines + - Sunday afternoon office hours (2-3 ppl organizers) -- Google Form for people who want to set up a node + - Mapping list of projects + - [tomesh project page](https://tomesh.net/projects/) + - pam is referring to a geographic map (project is a physical site, e.g. IA) + - pam: + - laptops for all (fixing up donated hardware) + - learning to set up a node (Sunday afternoon), a new person shows up, someone from People's Open will walk me thru setting up of a node + - _Steward_ assigned to a person to help them navigate "the mesh" + - ben: I think this is a great model that perhaps Toronto Mesh can use + - ben: Our project page shows "current" projects, but it's hard to navigate how pieces fit together + - Model of pairing up with someone (face-to-face or otherwise) would be great for onboarding newcomers: talk about our projects/help them set up a node/install Patchwork or Beaker Browser + - benhylau and ryan_fgt are working on a grant proposal for turning FreeGeek into a hackerspace on Sundays + - Current [tomesh workshops](https://tomeshnet.github.io/p2p-internet-workshop/) + - Less network focused than it is p2p focused + - felix: Internet is the number one service on our mesh network :) + - pam: p2p web, people are like _what_?? + - felix: go to bars, actually get internet (2 guys built a network that became 200+ nodes) + - Decouple "elaborate p2p stack" with "connectivity stack" + - yurko: backhaul over existing Internet connections (piggy off home Internet and VPN over somewhere) + - felix: this is how we do it + - ben: let's exit on felix's german infra + - ben: maybe using People's Open's stack is well-aligned with our near-term: + - dweb (meshnet + raspberry pis plugged in) + - educational curriculum co-development + - openwrt transition to librerouter hardware + - cjd: ipredator? goes thru sweden +- March: participate at [CodeAcross](https://www.eventbrite.ca/e/codeacrossto-2019-tickets-53330824933) + - ben is going, dante may go +- April: opportunity to [speak at CivicTechTO](https://github.com/tomeshnet/documents/issues/112) + - dante can go and speak, he will ping patcon to arrange dates +- May: opportunity to [organize activity at Pegah's UofT event](https://github.com/tomeshnet/documents/issues/111) + - Event centered around privacy and censorship as it pertains to artistic work + - Toronto Mesh-run Workshop? + - perhaps our "drawing activity" + - Email Pegah on activities we can run- dante will email Pegah re: dates + - Tim: [SWIFT network](http://swiftnetwork.ca/) could be a partner even if it's just for running a workshop + - ben: I wonder if it shares similarity with [XOC](https://www.xarxaoberta.cat) + - tim to reach out to find out more + - Tim: check out the [Development License](https://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf11373.html) option for radio spectrum work + +## Communications load balancing + +| Organization | Toronto Mesh contact | Subject | Status | +|:-------------|:---------------------|:--------|:-------| +| Toronto Public Library | @benhylau @dcwalk @darkdrgn2k | Mesh Workshop | Completed pilot, interested in next iteration | +| Florida Polytechnic | @Shrinks99 @darkdrgn2k @benhylau | Mesh Workshop | [Agreement to collaborate](https://hackmd.io/-9P_SzjKSROHUj8zEE_qqw?view), shipped some parts to Florida and got the group set up to facilitate module-1 | +| Guifi.net | @benhylau | Mesh Workshop | Completed module-1 facilitation + helped translate worksheet to _es_, discuss future opportunities | +| Palo Alto Library | @benhylau | Mesh Workshop | Introduction via Wendy (Internet Archive), had a [first call](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20181107_workshop-series-intro-for-city-of-palo-alto-library.md) | +| NYU Abu Dhabi | @benhylau | Mesh Workshop | Discussed with Michael about using syllabus at the university during Radical Networks 2018 | +| Design Exchange | @Shrinks99| Workshop collab | Had first call and relayed asks at February 4 Mesh Sync | +| Internet Archive | @benhylau | Decentralized Web Camp 2019 | Early planning started with notes on [dweb-camp-2019/organizing](https://github.com/dweb-camp-2019/organizing) | +| CivicTechTO | @dasanchez | April Hacknight | Getting dates from CTTO | +| Pegah @ UofT | @dasanchez | May event workshop | Will contact Pegah re:dates | +| SWIFT | Tim | not specific yet | Will ping and see what they are doing | diff --git a/mesh_sync/20190304_mesh-sync-notes.md b/mesh_sync/20190304_mesh-sync-notes.md new file mode 100644 index 0000000..a099f03 --- /dev/null +++ b/mesh_sync/20190304_mesh-sync-notes.md @@ -0,0 +1,221 @@ +--- +title: Mesh Sync Notes - Mar 4, 2019 +location: https://appear.in/tomeshnet +date: 2019-03-04 +startTime: 10:00 +endTime: 12:00 +--- + +📍 https://appear.in/tomeshnet +📅 Monday, March 4 + +| Timezone | Workshop | General | +|:---------|:---------|:---------| +| PST |`07:00 am`|`08:00 am`| +| EST |`10:00 am`|`11:00 am`| +| CEST |`04:00 pm`|`05:00 pm`| +| HKT |`10:00 pm`|`11:00 pm`| + +## What is this? + +Biweekly standing open-call for remote parties to sync up on topics of mutual interest. The hours are selected to make it possible for parties of different timezones to attend. + +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of six timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. + +The _Course_ hour is for topics relating to the [Building the Peer-to-Peer Internet workshop series](https://tomeshnet.github.io/p2p-internet-workshop/), such as discussing about workshop facilitation at a new location, the logistics of getting the hardware and software set up, funding opportunities for curriculum development, etc. + +The _General_ hour is for all other issues, such as [Prototype](https://github.com/tomeshnet/prototype-cjdns-pi) or [Mesh Orange](https://github.com/tomeshnet/mesh-orange) updates, IPFS live streaming discussions, showcasing your new project, or collective brainstorming of collaboration opportunities with Toronto Mesh. + +Lastly, please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of the things going on :satellite: + +## Attending + +📝 This person moves meeting notes to GitHub and resets the pad: +- benhylau + +👥 Please add your name to this list if attending: +- benhylau +- benny +- elon +- joseph +- nicopace +- yurko +- tim +- hank (part of meeting) +- garry (part of meeting) + +## Agenda + +| Start time | 20-min timeslot | Facilitator | +|:-------------|:-----------------------------------|:------------| +|`10:00 am EST`| Intros | benhylau | +| | General updates | yurko | +| | Mesh Workshop working group update | benhylau | +|`11:00 am EST`| Decentralized Web Camp 2019 | benhylau | +| | Nico's new role at APC | nicopace | +| | Network drawing activity | benhylau | + +### Session 1: Intros + +### Session 2: General updates + +### Session 3: Mesh Workshop working group update +#### Objectives +- Hank released [v0.12: The Remark-able Overhaul!](https://github.com/tomeshnet/p2p-internet-workshop/releases/tag/v0.12) +- Had our first [People's Open x Toronto Mesh workshop meeting](https://hackmd.io/NYlGNIx1TSe4igu3xUWJfQ) +- Roadmap for workshop with modular content based on material from People's Open and Toronto Mesh +#### Links +- http://buildyourowninter.net +- https://tomeshnet.github.io/p2p-internet-workshop/ + +### Session 4: Decentralized Web Camp 2019 +#### Objectives +- Area map and preliminary ideas +- Meshnet equipment for prototyping +#### Links +- https://github.com/dweb-camp-2019/organizing/ + +### Session 5: Nico's new role at APC +#### Objectives +- Introduce project Nico recently got involved in + +### Session 6: Network drawing activity +#### Objectives +- Share results from recent drawing activity at [Toronto Mesh Meet and Greet](https://tomesh.net/2019-02-21/meet-and-greet/) +#### Links +- https://github.com/tomeshnet/documents/tree/master/images/20190221_meetup-drawings/ + +## Meeting notes + +### Intros + +- yurko: developing Prototype + everything around tomesh +- joseph (aka. turco32): up for testing things and been helping with supporting new people get set up in chat +- tim: learning the tech, want to help with docs +- nico: part of Altermundi, recently joined APC, planning [Indigineous Connectivity Summit](https://www.internetsociety.org/events/indigenous-connectivity-summit/) +- benny: People's Open, worked with them about a year (firmware debug + exit nodes + workshop + IA antenna coordination) +- benhylau: Toronto Mesh + Our Networks + +### General updates + +- [Prototype v0.4](https://github.com/tomeshnet/prototype-cjdns-pi/releases/tag/v0.4) released! + - Lots of features such as Node Profile, Welcome Page, Yggdrasil integrations, etc. + - Ad hoc on Raspberry Pis tested on 3B/3B+ and Zeros +- LibreRouter + - Nico can find funding for open source developer for ac drivers +- [Our Networks 2019](https://ournetworks.ca) theme released! + +### Mesh Workshop working group update + +- Hank [released new theming](https://github.com/tomeshnet/p2p-internet-workshop/releases/tag/v0.12) for the [Mesh Workshop](https://tomeshnet.github.io/p2p-internet-workshop/)! It looks super nice. Now the websites and slides and worksheets are all consistent +- He also manually redrew all the diagrams -> svg +- We ditched gitbook for remark. Now we are generating pdf of slides for all course modules +- Everything is written in markdown (remark presentations, markdown-pdf handouts, jekyll website) +- Want to collaborate with People's Open on a website filled with modular mesh-related workshop activities +- tomesh's workshop is mostly based on Raspberry Pis, but thinking about adding stuff about OpenWRT routers (LibreRouter?) +- nico: Adding modules for LibreRouter sounds excellent! Should be: + - Practical and need oriented + - Translatable like [Altermundi docs](http://docs.altermundi.net) (LibreRouter has a translation system) +- yurko: excited :) +- benny: workshop facilitation budget +- benhylau: to share our earlier proposal about workshop facilitations (paying local facilitators) +- nico: responsible for the meshnet component in [techiocomunitario](https://techiocomunitario.net) + - 3 weeks ago, brought several groups together to learn from each other and it went realy well + +### Decentralized Web Camp 2019 + +- nico and ben went last year -- conference at the mint +- nico: I don't feel like the conversation there has been around decentralized internet infrastructure. Seems like the conversations were mostly around blockchain +- benhylau: Wendy and others mentioned some feedback they received: + - Too many keynote / sales pitches + - Not enough use of decentralized services for planning the conference + - Cost to attend / venue was super expensive +- benhylau: Participation at DWeb 2018: + - nico did many sessions + - tomesh did a mesh workshop and a tech demo to livestream with IPFS on Raspberry Pis and LibreRouters +- benhylau: going to create Call for Proposals soon +- This year the venue is a mushroom farm, not a mint, but cost isn't much cheaper because people will live there with meals covered + - Talking about making entry tier-priced (for people who are supported by organizations or rich on cryptocurrencies they can still pay, but sponsorship should cover cost for people who cannot pay $400) + - People who help build should get free admission +- nico: How inclusive will this space be? I guess it will be U.S. based, but what about communities in your area? + - Get in touch with local indigeneous communities + - Non-coders track + - Capacity building for non-technical people + - P2P _not_ D2D (developer 2 developer) or B2B (user in the centre) + - I think thats the big hurdle for distributed type systems - How do you get the geek-free people to embrace it? +- benny: what is the stated mission? + - benhylau: TBD this week +- nico: two approaches: + - Start with a technology, then find a need + - Start with a need, then work to solve that need +- nico: do it in Mexico next year :) -- this is where offline-living actually makes sense +- benhylau will keep people updated on progress, also [Planning Repo](https://github.com/dweb-camp-2019/organizing/) + +### Nico's new role at APC + +- Part of [APC](https://www.apc.org) now, responsible for supporting the growth of the community network movement +- [Community Network Project](https://www.apc.org/en/project/local-access-networks-can-unconnected-connect-themselves) with Altermundi and Rhizomatica +- Specific timeframe project +- Building the community network movement +- Include "human technologies": how do we coordinate? Manual and software +- Facilitate conversations around having more gender awareness +- APC Labs + - Fund and support members to develop and support "long-tail territory" of product development (the 20% polish and support that make things useful as products) + - Internet Archive and Altermundi are both APC members, so they can both participate in these funds +- InfraCon in BCN around Internet Freedom Festival +- Project has been ongoing for 3 months, mostly been onboarding +- Community peers will be announced +- Project regions: Latin America, Asia Pacific, Africa +- This is an opportunity to listen to communities with needs +- benny: Is there a way to listen without being there in person? + - Maybe a stack-overflow like thing for capacity building? + - Video documentation? +- nico: "Hacker In Residence" Project + - Hackers to live in rural communities + - Use skills to serve the rural community + - Prepare yourself to be a servant to someone else + - Nico will be the guinea pig + - benhylau: exciting! + +### Network drawing activity + +- The current prompt is _"Draw what your ideal network looks like"_ +- hank: maybe workshop group can start at that as an activity module? +- Sample prompts: + - benhylau: _"How do we want to build and access digital things"_ + - nico: _"Draw our lives now, then draw our lives with internet"_ +- benhylau: we lack spaces for this bidirectional knowledge exchange + - Community has knowledge of needs where designers have a knowledge gap + - Designers have skills to build tools which communities lack +- benhylau wants to make space for these exchanges to occur + - Physical space: challenging (e.g. DWeb at IA vs. at Mexico, either will be a challenge for one of two groups) + - Sync digital space: ideal but communities aren't online (e.g. Riot/Matrix, WhatsApp, too many platforms) + - Async digital space: some avenues exist but still limiting (e.g. SSB but hard to share out, nico's video docs) +- benhylau: I find these [Experiences from the ground](https://www.youtube.com/user/nicopace/videos) video docs from Nico helpful: + - [Yaviche Wireless Community Network NuestraNet](https://www.youtube.com/watch?v=X9womPVhwWg) + - [Online TV Station in Tlahuitoltepec, Oaxaca, Mexico](https://www.youtube.com/watch?v=Xh4x2PXf9Jw) +- benhylau feels making space for these conversations, and recognizing that the learning is bidirectional, is a shared goal of APC, Internet Archive, Our Networks... +- nico: + - >There is obviously a lot of smart and creative people in tech, but they suffer from an Achilles Heel trio of weaknesses: self-perceived idealism as excuse, overconfidence in their capabilities outside their own areas of expertise, and lack of attentiveness to details and harms. + > --[@zeynep](https://twitter.com/zeynep/status/1018459991127314432) + - Many people agree with this at this meeting +- benhylau: Lots of shared goals among our projects, how to update each other? + - [APC monthly letter](https://www.apc.org/en/community-networks-and-local-access-monthly-newsletter) from Nico + - Riot (everyone here is on Riot) + - Workshop working group will have weekly/biweekly meetings, anyone may join + - Continue syncing up at biweekly Mesh Syncs (same time for next one and make new schedule after March) + +## Communications load balancing + +| Organization | Toronto Mesh contact | Subject | Status | +|:-------------|:---------------------|:--------|:-------| +| Toronto Public Library | @benhylau @dcwalk @darkdrgn2k | Mesh Workshop | Completed pilot, interested in next iteration | +| Florida Polytechnic | @Shrinks99 @darkdrgn2k @benhylau | Mesh Workshop | [Agreement to collaborate](https://hackmd.io/-9P_SzjKSROHUj8zEE_qqw?view), shipped some parts to Florida and got the group set up to facilitate module-1 | +| Guifi.net | @benhylau | Mesh Workshop | Completed module-1 facilitation + helped translate worksheet to _es_, discuss future opportunities | +| Palo Alto Library | @benhylau | Mesh Workshop | Introduction via Wendy (Internet Archive), had a [first call](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20181107_workshop-series-intro-for-city-of-palo-alto-library.md) | +| NYU Abu Dhabi | @benhylau | Mesh Workshop | Discussed with Michael about using syllabus at the university during Radical Networks 2018 | +| Design Exchange | @Shrinks99| Workshop collab | Had first call and relayed asks at February 4 Mesh Sync | +| Internet Archive | @benhylau | Decentralized Web Camp 2019 | Early planning started with notes on [dweb-camp-2019/organizing](https://github.com/dweb-camp-2019/organizing) | +| CivicTechTO | @dasanchez | April Hacknight | Getting dates from CTTO | +| Pegah @ UofT | @dasanchez | May event workshop | Will contact Pegah re:dates | +| SWIFT | Tim | not specific yet | Will ping and see what they are doing | diff --git a/mesh_sync/20190318_mesh-sync-notes.md b/mesh_sync/20190318_mesh-sync-notes.md new file mode 100644 index 0000000..29b0ead --- /dev/null +++ b/mesh_sync/20190318_mesh-sync-notes.md @@ -0,0 +1,174 @@ +--- +title: Mesh Sync Notes - Mar 18, 2019 +location: https://appear.in/tomeshnet +date: 2019-03-18 +startTime: 10:00 +endTime: 12:00 +--- + +📍 https://appear.in/tomeshnet +📅 Monday, March 18 + +| Timezone | Start time | +|:---------|:-----------| +| PST | `07:00 am` | +| EST | `10:00 am` | +| CEST | `03:00 pm` | +| HKT | `10:00 pm` | + +## What is this? + +Biweekly open calls to sync up on topics relating to the global Community Network movement. The hours are selected to make it possible for parties of different timezones to attend. + +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of five session timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. You can see previous meeting notes on [tomeshnet/documents/mesh_sync](https://github.com/tomeshnet/documents/tree/master/mesh_sync) to get an idea of what type of topics have been discussed in the past. + +Please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview, then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of global initiatives relating to the Community Network movement :satellite: + +## Attending + +📝 This person moves meeting notes to GitHub and resets the pad: +- benhylau + +👥 Please add your name to this list if attending: +- ben (benhylau) +- caleb (cjd) +- yurko +- tim +- pedro (guifipedro) + +## Agenda + +| Start time | 20-min timeslot | Facilitator | +|:-------------|:------------------|:------------| +|`10:00 am EST`| Intros | | +| | cjdns update | caleb | +| | Session 2 | | +|`11:00 pm EST`| Guifi update | guifipedro | +| | DWeb Camp update | benhylau | +| | Future mesh syncs | benhylau | + +### Session 0: Intros +#### Objectives +- Introduce and connect with each other on the call + +### Session 1: cjdns update +#### Objectives +- Talk about recent progress on cjdns +#### Notes +- If supernodes are permissionless, what prevents them from flooding the network with routes and every supernode's memory blows up? +- Proof-of-work on route announcements by supernodes +- Source routing (cjdns) has an issue where someone can trash a link by bouncing a packet around two nodes indefinitely by crafting a route label that way +- TCP gives backpressure information for Yggdrasil +- Supernode resource usage: 1 core of a 3 GHz machine (but the supernode code is a nodejs prototype) +- Supernodes mine _announcements_ (like Aether) +- Block miners mine _blocks_ (gather data generated and make routes) +- Supernodes max out CPU resources +- Supernodes: Announcement miners for ETH, Block miners get a discount on PoW (both collecting announcemets) +- Supernodes: Gather data about peers, quality of nodes +- Supernodes communicate with each other operationally, block miners will want same info just to capitalize on for discounted routing. +- Radio metrics -> Supernodes (announce routes) -> Block miners (secure blockchain and through that make bandwidth leases) +- Supernodes buy from bandwidth market and resell that bandwidth to the local network, make money on mark-up in this competitive market +- Some analogies: + - Block miners are doing make work + - Supernodes are like ISPs without infrastructure + - Physical infrastructres are owned by anyone +- >We are separating ISP from their infrastructure and the infrastructure is owned by whoever + - ben: this shares a lot of similarity with guifi.net ISPs +- caleb: + - Watch out for pre-mines and ICOs + - But there are always winners and losers (people who came early) +- Promote to user audience / early adopter, but not cryptocurrency communities +- ben: Forks? + - caleb: Don't need to defend against that, we should have more credibility +- Thoughts about permissioned blockchain? + - Not decentralized, based on community trust + - As sidechain to do escrowed exchange (BTC <-> Mantle) + - e.g. Liquid +- tim: Dfinity, high transaction rate +- Blockchain may not be able to pay for its own development: + - Relying on generosity of miners + - Don't want ICO + - A Founder's fee (like zcash) better because it pays out overtime, but too centralized + - Can't democracy vote because we don't have IDs + - Don't really like any of the above, how to make people be held accountable? +- "most-money-wins" election: + - Vote for or against a neetwork steward (which is a key that gets to spend the tax) as part of a transaction + - If more than half the money is voting against the current steward, an election is triggered + - Network stewards cannot spend more than 3-month old funds (taxes collected have an expiry) + - Network stewards may finance software development, buying infrastructures, lobby for airwaves, etc. + +### Session 3: Guifi update +- Long time without contacting you, I have fresh news: these days guifi is in a crisis +#### Objectives +- Share our recent experiences with guifi. It's also a good moment to do a live Q&A about the project. +#### Notes +- Guifi is in crisis +- 90% of network traffic is managed by for-profit operators (https://es.wikipedia.org/wiki/Sociedad_de_responsabilidad_limitada), lacking biodiversity +- Guifi Foundation made the compensation system for operators to equilibrate between network usage and investment of the network as a strategy to prevent exploitions (or extractive economy) + - As a consequences, some operators joined efforts doing nearly monopolies on their region of operation +- There are evidences that guifi Foundation have problems implementing the model or operating over it (this is something that all agree). Big operators are exploiting this vulnerability because they want to grow more (and as they are big enough they need less and less help) +- Big operators want to change collaborative framework to be more "like Internet".: + - Limit the tighly collaboration-cooperation: Personal conflicts between core participants of the network are very present + - Large operators want to exit with majority of the network (they claim that their networks belongs to them; this is not clear and the situation could end in courts) + - They talk about operators, quitting participations to volunteer and user roles +- Concern: they are claiming the property of a shared infrastructure that may eventually be sold or participated by a major operator / they could be considering shared infrastructure as endorsement of their loans. +- This is like a hostile change from GPL -> MIT license (not by consensus) +- As operators grow they become different in character, started as volunteers but become more protective of enterprise over time (perhaps because of burdens of loans, etc.) +- caleb: Is there an infrastructure that generates the problem? + - pedro: + - With wireless is mostly fine, CAPEX is low, OPEX is high + - Problem is with optical fiber deployments (CAPEX) that involve lot of investment. The stuff that the ISPs are claiming ownership now. Because OPEX is low, and they want to speculate/regulate it as they want. (I see analogies here similar to water and energy after the infrastructure is already deployed) +- Currently, the big operators intent to continue collaborating, but concern they will eventually defect +- Top4, [operadors.cat](https://operadors.cat), is an example of operators that become monopolies within their region +- Looks like the Guifi agreement prevents operators from becoming rich; that's why they want to change fundamental rules +- Battlemesh in Paris in July :beers: https://framadate.org/12ORCCBq1H4b6fjy +- Now we (associations and cooperatives operators) are in negotiations between operators and guifi foundation +- Next month we have to present our proposal. Operators present a new proposal. Foundation present another one. In June we have to merge the three documents (if possible) +- caleb: It's possible that the current agreement is what keeps them (Operadors) in the first place +- Negotiator should realize that... probably if you guys defect you will all turn around and screw each other +- Change [FONN](https://benhylau.github.io/talks-and-workshops/talks/201810_nuug-hackeriet/#29) or economic model? + - ben: FONN is like your constitution and that's the bottom line? +- caleb: Is the proposed change to get rid of protection for users of network / small operators? + - pedro: Right now, "compensations" regulates decisions in zones "one operator one vote". The change want that only operators participate (not users or volunteers) and with a weighted vote based on investment. So yes, it favors big players. + - Looks like they want to get rid with some of the protections (to become more rich?). A good analogy is the origins of Internet, it started as a project where public administration, militaries and universities did heavy investment but the profit was for private parties. Transition from public to private end up (or it was a big step) when Internet God John Postel dead in 1997 heart operations caused by this privatization process/problems +- Continue conversation on matrix chat +#### Links +- guifi.net +- fundacio.guifi.net +- https://gitlab.com/guifi-exo/wiki/tree/master/info/2019-proposta-canvis-guifi +- https://operadors.cat + +### Session 4: DWeb Camp update +#### Objectives +- Update on DWeb Camp 2019 planning so far +#### Notes +- Made new repos and matrix channels +- Feel like building a new Internet? [Please comment on these issues](https://github.com/dweb-camp-2019/meshnet/issues) +#### Links +- https://github.com/dweb-camp-2019/organizing + +### Session 5: Future mesh syncs +#### Objectives +- Discuss post-March mesh syncs + - New time? + - New facilitator? +#### Notes +- ben is traveling in April and May and cannot facilitate Mesh Syncs +- No new facilitator at the moment for April and May, so we may pause +- tim _may_ take on facilitation +- We need to repoll for new time, and move to jitsi + +## Communications load balancing + +| Organization | Toronto Mesh contact | Subject | Status | +|:-------------|:---------------------|:--------|:-------| +| Toronto Public Library | @benhylau @dcwalk @darkdrgn2k | Mesh Workshop | Completed pilot, interested in next iteration | +| Florida Polytechnic | @Shrinks99 @darkdrgn2k @benhylau | Mesh Workshop | [Agreement to collaborate](https://hackmd.io/-9P_SzjKSROHUj8zEE_qqw?view), shipped some parts to Florida and got the group set up to facilitate module-1 | +| Guifi.net | @benhylau | Mesh Workshop | Completed module-1 facilitation + helped translate worksheet to _es_, discuss future opportunities | +| Palo Alto Library | @benhylau | Mesh Workshop | Introduction via Wendy (Internet Archive), had a [first call](https://github.com/tomeshnet/documents/blob/master/meeting_notes/20181107_workshop-series-intro-for-city-of-palo-alto-library.md) | +| NYU Abu Dhabi | @benhylau | Mesh Workshop | Discussed with Michael about using syllabus at the university during Radical Networks 2018 | +| Design Exchange | @Shrinks99| Workshop collab | Had first call and relayed asks at February 4 Mesh Sync | +| Internet Archive | @benhylau | Decentralized Web Camp 2019 | Early planning started with notes on [dweb-camp-2019/organizing](https://github.com/dweb-camp-2019/organizing) | +| CivicTechTO | @dasanchez | April Hacknight | Getting dates from CTTO | +| Pegah @ UofT | @dasanchez | May event workshop | Will contact Pegah re:dates | +| SWIFT | Tim | not specific yet | Will ping and see what they are doing | diff --git a/mesh_sync/20190710_mesh-sync-notes.md b/mesh_sync/20190710_mesh-sync-notes.md new file mode 100644 index 0000000..8c8fa2f --- /dev/null +++ b/mesh_sync/20190710_mesh-sync-notes.md @@ -0,0 +1,78 @@ +Mesh Sync +========= + +📍 https://appear.in/tomeshnet +📅 Wednesday, July 10, 2019 + +| Timezone | Start time | +|:---------|:-----------| +| EST | `07:00 pm` | + +## What is this? + +Biweekly open calls to sync up on topics relating to the global Community Network movement. The hours are selected to make it possible for parties of different timezones to attend. + +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of five session timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. You can see previous meeting notes on [tomeshnet/documents/mesh_sync](https://github.com/tomeshnet/documents/tree/master/mesh_sync) to get an idea of what type of topics have been discussed in the past. + +Please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview, then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of global initiatives relating to the Community Network movement :satellite: + +## Attending + +📝 This person moves meeting notes to GitHub and resets the pad: +- + +👥 Please add your name to this list if attending: +- @Darkdrgn2k +- @Hurricos +- @dasanchez +- @timtor + +## Agenda + +No preset agenda - Free Form + +#### Notes + +- Quick conversation about "Bell Fibe" ("FTTN") vs "Bell Fiber" ("FTTH") + - Gigabit speeds seem to only be attainable during Bell's speed test + - Rock64 connected to 1gbps only does ~500mhz on "speedtest-cli" + - iperf3 to vps node only hits ~110-150 + +- Discussion Around outreach projects to "ALT" isps + - Teksavvy, Beanfield, swift + - Need to have a more concrete concept to present +- State-of-the-art protocols vs low-resource ones + - CJDNS and YGG may be working against us + - Tons of computing power required because encryption + - Babel may not have addressing and encryption, but it works +- DWEB apps not "mesh friendly" + - lacks IPV6 support + - Built for "traditional" infustructure + - Example - IPFS not knowing topology + - Doesnt care who they take the data from from a topoplgy perspective + - ISPs carry the backhaul burden + - IE Level 3 probably only uses a small % of their capacity + - Meshes have to shoulder that burden + - Imagining a "caching" node for content on the roof of a Multi Dwelling Unit + - Encryption makes caching impossible + - Suggestion - perhaps homogeneous encryption has a place here +- Prototype and SSB for TPL + - SSB does listen for IPv6 announcement packets :( + - Work around are + - Invite to ipv6 cjdns peer + - Add ipv4 address to wlan0 interface to bypass cjdns ipv6 address +- Burlington, VT project for [The Ramble](https://theramble.org/) - MESH ice cast audio stream + - Long buffer to allow for roaming + - Pis runing 5v batteries + - MR16 mesh + +#### Important things for future Syncs +- Taking notes +- Making the output freely available + - That is to say, organize and publish the notes that come out of it, as before +- Advertise beforehand + - Decide on time earlier +- Improve chat + - Jitsi just wasn't working - would Mumble be better? What type of chat would be better? + - Suggestion: Multi-modal chat (attendees can talk chat in a voice chatroom, and a stream of the chat is published so people can involve themselves via a text chatroom) + diff --git a/mesh_sync/TEMPLATE-HACKMD.md b/mesh_sync/TEMPLATE-HACKMD.md index e495b6a..e6a98f1 100644 --- a/mesh_sync/TEMPLATE-HACKMD.md +++ b/mesh_sync/TEMPLATE-HACKMD.md @@ -5,24 +5,20 @@ Mesh Sync 📍 https://appear.in/tomeshnet 📅 Monday, -| Timezone | Workshop | General | -|:---------|:---------|:---------| -| PST |`07:00 am`|`08:00 am`| -| EST |`10:00 am`|`11:00 am`| -| CEST |`04:00 pm`|`05:00 pm`| -| HKT |`10:00 pm`|`11:00 pm`| +| Timezone | Start time | +|:---------|:-----------| +| PST | `07:00 am` | +| EST | `10:00 am` | +| CEST | `04:00 pm` | +| HKT | `10:00 pm` | ## What is this? -Biweekly standing open-call for remote parties to sync up on topics of mutual interest. The hours are selected to make it possible for parties of different timezones to attend. +Biweekly open calls to sync up on topics relating to the global Community Network movement. The hours are selected to make it possible for parties of different timezones to attend. -Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of six timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. +Anyone may propose a topic on [this open-edit pad](https://hackmd.io/HSOK15u7TnS6Oz1RH0McGg), taking one of five session timeslots by putting yourself as _Facilitator_ and filling the corresponding [_Agenda_](#Agenda) section. You can see previous meeting notes on [tomeshnet/documents/mesh_sync](https://github.com/tomeshnet/documents/tree/master/mesh_sync) to get an idea of what type of topics have been discussed in the past. -The _Course_ hour is for topics relating to the [Building the Peer-to-Peer Internet workshop series](https://tomeshnet.github.io/p2p-internet-workshop/), such as discussing about workshop facilitation at a new location, the logistics of getting the hardware and software set up, funding opportunities for curriculum development, etc. - -The _General_ hour is for all other issues, such as [Prototype](https://github.com/tomeshnet/prototype-cjdns-pi) or [Mesh Orange](https://github.com/tomeshnet/mesh-orange) updates, IPFS live streaming discussions, showcasing your new project, or collective brainstorming of collaboration opportunities with Toronto Mesh. - -Lastly, please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of the things going on :satellite: +Please scope your session within a 20 minute time block. If more time is needed, it is probably best to use the 20 minutes to give an overview, then schedule separate meetings with interested parties. The hope is that these standing hours can be well attended and everyone participating gets a general idea of global initiatives relating to the Community Network movement :satellite: ## Attending @@ -36,37 +32,44 @@ Lastly, please scope your session within a 20 minute time block. If more time is | Start time | 20-min timeslot | Facilitator | |:-------------|:----------------|:------------| -|`10:00 am EST`| Course 1 | | -| | Course 2 | | -| | Course 3 | | -|`11:00 am EST`| General 1 | | -| | General 2 | | -| | General 3 | | - -### Course 1: +|`10:00 am EST`| Intros | | +| | Session 1 | | +| | Session 2 | | +|`11:00 pm EST`| Session 3 | | +| | Session 4 | | +| | Session 5 | | + +### Session 0: Intros #### Objectives -#### Links +- Introduce and connect with each other on the call +#### Notes -### Course 2: +### Session 1: #### Objectives +#### Notes #### Links -### Course 3: +### Session 2: #### Objectives +#### Notes #### Links -### General 1: +### Session 3: #### Objectives +#### Notes #### Links -### General 2: +### Session 4: #### Objectives +#### Notes #### Links -### General 3: +### Session 5: #### Objectives +#### Notes #### Links -## Meeting notes +## Communications load balancing -... +| Organization | Toronto Mesh contact | Subject | Status | +|:-------------|:---------------------|:--------|:-------| diff --git a/service_setup/README.md b/service_setup/README.md new file mode 100644 index 0000000..265a80d --- /dev/null +++ b/service_setup/README.md @@ -0,0 +1,12 @@ +Toronto Mesh Infrastructural Services +===================================== + +| URL | Contact | Description | Set up instructions | +|:----|:--------|:------------|:--------------------| +| tomesh.net | @benhylau | Domain | Registered by @benhylau and managed from Digital Ocean Team | +| tomesh.net | @ASoTNetworks | Website | See [documents/service_setup](https://github.com/tomeshnet/documents/blob/infra-summary/service_setup/website.md) | +| alexandria.tomesh.net | @darkdrgn2k | Media server | See [Issue #108](https://github.com/tomeshnet/documents/issues/108) | +| chat.tomesh.net | @ASoTNetworks | Riot UI for Matrix chat | See [mesh-services/matrix-synapse-riot](https://github.com/tomeshnet/mesh-services/tree/master/matrix-synapse-riot) | +| matrix.tomesh.net | @ASoTNetworks | Matrix chat homeserver | See [mesh-services/matrix-synapse-riot](https://github.com/tomeshnet/mesh-services/tree/master/matrix-synapse-riot) | +| webmail.tomesh.net | @ASoTNetworks | Email web client | See [documents/service_setup](https://github.com/tomeshnet/documents/blob/master/service_setup/email.md) | +| y.mirror.tomesh.net h.mirror.tomesh.net | @ASoTNetworks | Distros mirror over the mesh | |