docs: add IPFS weekly notes for March 2020 (#1131)

ipfs · May 11, 2020 · 34541bc · 34541bc
1 parent 2249b59
commit 34541bc
Show file tree

Hide file tree

Showing 5 changed files with 490 additions and 0 deletions.
diff --git a/meeting-notes/2020/Q1/2020-03-02--ipfs-weekly.md b/meeting-notes/2020/Q1/2020-03-02--ipfs-weekly.md
@@ -0,0 +1,42 @@
+# IPFS All Hands Call Mar 02, 2020
+
+-   **Moderator:** @alanshaw
+-   **Notetaker:** @alanshaw
+-   **Attendees:**
+    -   __@jessicaschilling__
+    -   __@jennturner__
+    -   __@ribasushi__
+    -   __Dustin Long__
+    -   __Brendan O’Brien__
+    -   __Rico Gardaphe__
+    -   __@jaycarpenter__
+    -   __Matt Ober__
+    -   __@achingbrain__
+    -   __Kasey Huizinga__
+    -   __John Kane__
+-   **Video:** https://youtu.be/aY6sJYIgMoc
+
+**Agenda**
+
+-   (Brendan & Dustin, 20mins) What's new with qri.io in 2020
+
+**Notes**
+
+-   QRI launched Desktop
+-   Starting to get issues with perf - means people are using it and things are going well!
+-   Perf problems turned into CI scripts to test perf is good
+
+    -   And graphs!
+    -   Benchmarks go into google datasets search
+
+-   In the pipe
+
+    -   Diffing UI
+    -   Dataset patching
+    -   Dataset versioning and out of date-ness
+    -   Starting to use IPFS/libp2p testground
+
+-   QRI do not use MFS
+
+    -   Manual DAGs, bespoke versioning
+    -   Want to move to MFS, waiting for UnixFS v2
diff --git a/meeting-notes/2020/Q1/2020-03-09--ipfs-weekly.md b/meeting-notes/2020/Q1/2020-03-09--ipfs-weekly.md
@@ -0,0 +1,160 @@
+# IPFS All Hands Call Mar 9 2020
+
+-   **Moderator:** @alanshaw
+-   **Notetaker:** @autonome
+-   **Attendees:**
+    -   __RobM__
+    -   __@jennturner__
+    -   __@jaycarpenter__
+    -   __@chafey__
+    -   __@jessicaschilling__
+    -   __@ribasushi__
+    -   __@lidel__
+    -   __@daviddias__
+-   **Video:** https://youtu.be/wvmZj7IE9Bo
+
+**Agenda**
+
+-   Fission
+
+**Notes**
+
+-   Remote team
+-   IPFS can be a rough conversation starter
+-   What if front-end code was all you needed?
+-   Front-end not going away
+-   Browsers getting more powerful
+-   And we have public infra
+-   And edge computing is rising
+-   Many words, just starting to come to focus
+-   All apps are hard
+-   But lamp is 30yo now
+-   Front and back end, plus devops
+-   Lots of breaches
+-   Great local dev env, but deployment is hurty for devs
+-   Million choices, million different things to learn
+-   How to build web-native apps?
+-   Fission building a framework for “web-native” apps
+-   Building hosting too, but should run local
+-   User accounts, data priv, auth
+-   DNS still needed
+-   And IPFS features built-in for cdn, access control, encryption
+-   Making web apps more like native desktop or mobile apps
+-   Web, have to push stuff to som eserver
+-   For edge, mirro code, etc
+-   We’re making these bits location independent
+-   The dragon: LLVM
+-   Compiler and runtime infra on ios
+-   Leveraging js, v8, webassembly on top of ipfs
+-   Nice experience w/o having to worry about devops
+-   Your production server is now the network
+-   Build an entire app while offline on a plane
+-   Add first user account offline
+-   Should work in all browsers w/o plugins
+-   Webauthn
+-   Lets your browser hold keys for you
+-   For passwordless login
+-   Built into fission sdk
+-   Integration is the big thing
+-   What’s built so far…
+-   Web api (REST) for IPFS
+-   Similar to pinning svc but we don’t think of ourselves that way
+-   Pinning is least interesting
+-   More like app hosting
+-   Heroku addon
+-   Dns automation
+-   Automatically get subdomain
+-   Renewal
+-   Domain purchases from cmd line later
+-   Cli, all in one
+-   Used ipfs-deploy
+-   But all over http
+-   Want ot use ipfs natively
+-   Devs install ipfs
+-   Then fission
+-   And then do everything via cli
+-   \> fission up
+-   Ipfs does the syncing
+-   Fission register
+-   Fission watch
+-   Live reload
+-   Updating top level dag
+-   And dns txt record
+-   Next:
+-   pub/priv key based accounts
+-   For account portability
+-   Accounts can add apps
+-   Have domains
+-   Encryption
+-   Web login (webauthn)
+-   FFS fission file system
+-   Identity
+-   (or just below)
+-   Loosely based on DIDs and verifiable credtls
+-   Identity as pubkey
+-   Jwt auth and macaroons
+-   Can delegate across domains
+-   whitepaper.fission.codes/identity
+-   Similar to oauth/jwt today but decentralized
+-   Based largely on google macaroons
+-   RSA b/c browser support
+-   Cli is edwards curve
+-   FFS
+-   Store dag hash in dns -> boris.fission.name
+-   Today is public
+-   Next is private
+-   Each file in each dir has header w/ symmetric key
+-   And has keys all the way below it
+-   Can take subtree and share it w/ someone by sharing key
+-   Key rotated on index and key exchange for symmetric keys for read
+-   Write key is auth into fission svc to pin new dag
+-   “Just works” is primary goal
+-   Api is “store privately this file”
+-   Can try drive now
+-   Drive.fission.codes
+-   Launched in preview in feb
+-   Built on top of fission
+-   Who uses dotfiles
+-   App data
+-   Boris.fission.name
+-   Have per-app storage client side
+-   Works w/ any public ipfs files today
+-   Private coming
+-   Image previews
+-   Feels zippy
+-   Built by steven, client side
+-   Elm
+-   Quickly iterate, easy to refactor
+-   Rendermedia
+-   Not open source yet, but planned
+-   Get-ipfs
+-   Like ipfs provider
+-   Es6
+-   Haskell on backend
+-   Ipfs-haskell for local node or remote http
+-   Hired a dev to do ipfs ignore cmd
+-   Have a PR to go-ipfs
+-   Please look and review
+-   Want to get more files into ipfs
+-   Integrations and sync
+-   Eg drive on desktop but managing attachments on ghost, discourse, etc
+-   Heroku + ghost + ipfs for one-click deploy
+-   Heroku has no fs, so upload directly to ipfs
+-   Ghost storage adapter
+-   Same for Discourse
+-   Discourse-ipfs-filestore
+-   Get into discuss.ipfs.io?!?!
+-   QUESTIONS
+-   Are people using it?
+-   ~200 accounts
+-   Used at some hackathons
+-   Origin protocol poking around for making fe portable
+-   Not pushing hard on adoption until identity and private files
+-   Key for having 100% client side
+-   Where to contact you?
+-   Can ask here<https://events.fission.name/2020/ipfs-community-call>
+-   Discord chat
+-   <https://fission.codes/discord>
+-   https&#x3A;//talk.fission.codes forum
+-   Planning to offer paid service
+-   Interesting options like Filecoin
diff --git a/meeting-notes/2020/Q1/2020-03-16--ipfs-weekly.md b/meeting-notes/2020/Q1/2020-03-16--ipfs-weekly.md
@@ -0,0 +1,93 @@
+# IPFS All Hands Call Mar 16 2020
+
+-   **Moderator:** @alanshaw
+-   **Notetaker:** @jessicaschilling
+-   **Attendees:**
+    -   __@jessicaschilling__
+    -   __@jaycarpenter__
+    -   __@willscott__
+    -   __Matt Ober__
+    -   __@chafey__
+    -   __@obensource__
+    -   __@lidel__
+    -   __@blockchainbrett__
+-   **Video:** https://youtu.be/XCsNQFxIqvQ
+
+**Agenda**
+
+-   Terminal.co on how to build and deploy ipfs-hosted apps using Terminal!
+-   Brett Shear (COO/co-founder), Harrison Hines presenting, Janison Sivarajah
+-   Terminal is a modern web dev tool to deploy sites and apps onto IPFS
+-   Version 1 release is about hosting the app and pointing domains
+-   Deploying the app happens in a few quick steps:
+
+    -   Connect your GitHub account
+    -   You can configure whatever repos you want
+    -   Third step: set your build settings. It reads your package.json already for settings you have there
+
+        -   Also option for advanced deployment settings, including Docker images (that’s unusual even in the non-IPFS world!)
+
+    -   More documentation on all of this in Terminal’s docs
+    -   Click “deploy”, you’re done. There’s a monitoring screen so you can watch it all happen
+    -   Sample site takes about 2-3 mins to deploy. Looking at the logs and it’s standard stuff: yarn/npm commands, etc
+
+-   Very performant! Why? They do a few things:
+
+    -   They run their own nodes
+    -   They’re using Pinata, Temporal for additional redundancy
+    -   They upload the files to the same gateway they point the requests to, so a very low propagation time
+    -   As soon as done deploying, make a request to that domain to cache the files to a CDN: currently using something standard but they’ll have their own IPFS-based CDN soon in a major release
+
+-   SSL cert automatically issued through Let’s Encrypt
+-   Now it’s time to set up your domain
+
+    -   Purchase one via Terminal.co UI
+    -   Or add one you already have
+    -   Then change your CNAME or ANAME records (based on if it’s a domain or a subdomain)
+    -   “Add a custom domain to your site” workflow is very similar to Netlify, UI-wise
+    -   If you buy the domain through Terminal it sets up the DNS for you automatically
+
+-   Next steps will be the IPFS-based CDN and “other really cool stuff”
+-   QUESTION TIME!
+
+    -   Are ENS domains coming soon?
+
+        -   Yep, they hope to make it a seamless experience
+
+    -   Who’s your domain registrar?
+
+        -   GoDaddy, but also looking at some more decentralized domain services out there (in addition to .ens etc)
+
+    -   Can I import a site from somewhere on IPFS, like “I have this hash, can you host this for me?”
+
+        -   They’ll be creating a CLI soon - right now it’s just the GitHub interface - and that’ll have more granular commands for uploading and deploying via a hash
+        -   Also Gitlab support soon
+
+    -   Is DNSLink set up for default domains automatically?
+
+        -   Yes. And updated every time a build happens.
+
+    -   How’s the SSL setup?
+
+        -   They’re using Cloudflare as the default domain, wildcards point there
+        -   For custom domains, there’s an HA proxy that every time you add a custom domain, they verify the domain, add a certificate, and use CertBot to automatically generate Let’s Encrypt SSL certificates
+
+    -   When is estimated launch?
+
+        -   The product is live now, so anyone who requests early access … onboarding a dozen or so a day
+        -   Public opening probably in the next few weeks, or in conjunction with the next version (which includes the IPFS CDN etc); still deciding
+        -   But if you’re on this call, sign up for early access … in a few days or a week max
+
+    -   Re GitHub integration: would it be possible to to grant access to an entire account, not just a specific repo? Is this an API limitation?
+
+        -   You can grant an entire account, or specific repos within an account. Its up to the user.
+
+    -   Why did you choose IPFS?
+
+        -   Been in the web3 space for a while, working a lot on ethereum and dapps and it just started a rabbit hole down “what’s a dapp? Does a dapp require smart contracts?” and thinking about how web3 might actually happen for real people. What pieces of the web stack are going to need to be distributed or decentralized in order to make that happen? IPFS was a good backbone for a web3 - no token, so it’s easy to natively integrate into the web - and most things people need to do with websites can be built with IPFS as a backbone. Plus impressed with the IPFS team and community. Didn’t think there was enough being built with IPFS and wanted to help make that happen!
+
+    -   How do I learn more?
+
+        -   [Slack channel](https://join.slack.com/t/terminal-public/shared_invite/enQtOTM1MjQ3NTExMDU3LTNkYjU1ZGJhZGUyYjgwN2I3OThjY2U5OThlMGY2MGY0OGYxMDI1OWIwMTMwYzViZGY4ZGU0NDA0YmY4ZjVhOTg)
+        -   Direct email
+        -   You can do all that from the “community” link on terminal.co
diff --git a/meeting-notes/2020/Q1/2020-03-23--ipfs-weekly.md b/meeting-notes/2020/Q1/2020-03-23--ipfs-weekly.md
@@ -0,0 +1,97 @@
+# IPFS All Hands Call Mar 23 2020
+
+-   **Moderator:** @alanshaw
+-   **Notetaker:** @willscott
+-   **Attendees:**
+    -   __@jaycarpenter__
+    -   __@lidel__
+    -   __@willscott__
+    -   __Matt Ober__
+    -   __@andrew__
+    -   __@jessicaschilling__
+-   **Video:** https://youtu.be/08zD9L3hBLg
+
+**Agenda**
+
+_General discussions, decisions, etc._
+
+-   Connecting the Metaverse with IPFS - Jin[@dankvr](https://twitter.com/dankvr)
+
+    -   <https://hackmd.io/@XR/motivation>
+
+        -   We’re getting closer to living in a massive, persistent digital reality adjacent to our own. That digital reality is often owned by a single corporate entity. An open metaverse is a moral imperative.
+        -   They’re starting off on trying to extend the web / internet. There are points of centralization there in both unity (for 3d rendering) and chrome for web.
+        -   99.9% of “social VR” is currently built with a non-free engine.
+
+    -   WebXR is positioned as an open answer to this problem space
+
+        -   <https://developer.mozilla.org/en-US/docs/Web/API/WebXR_Device_API>   
+            <https://www.w3.org/TR/webxr/>
+        -   Can open portals to IPFS hosted worlds
+        -   IPFS assets - images, models, etc, can be used within the spaces
+        -   Demo: dragging an IPFS-backed asset out of the web UI into a VR world
+
+            -   JanusXR:[https://janusxr.org/](https://janusvr.com/)
+
+        -   Demo: spacialize a 2D conference presentation into a 3d world.
+
+            -   [@jacobheun presenting on libp2p circuit relays](https://vimeo.com/312827390)
+
+        -   Group: m3 (metaverse makers mixer)
+
+            -   <https://github.com/M3-org/research#research>
+            -   <https://github.com/M3-org/awesome-metaverse>
+            -   33 people met a virtual reality modeled off of eth denver physical space
+
+    -   Connecting metaverse & IPFS
+
+        -   Virtual worlds currently try to do everything (api, avatar, world, storage, market), and create their own silos
+        -   VR Chat is the largest social VR platform at the moment
+        -   <https://exokit.org/> - Tools for virtual worlds in the browser. Works on all headsets.
+        -   The imagination is different overlays for the different layers - an avatar layer, etc.
+        -   Imagine AR goggles for the social layer on top of a virtual reality world
+        -   You can see holograms of people that are chiming in from the browser into your VR world without modifying the client.
+        -   They’ve got all the tech: WebXR, OpenXR, GLTF, Wasm, IPFS, ETH. but they haven’t completed ‘the webaverse’ yet.
+
+            -   discussions occurring in mozilla hubs (<https://hubs.mozilla.com>)
+            -   A japanese XR event coming up soon - to replace canceled conferences due to covid
+
+                -   6 months ago they had an ‘expo’ with 600 exhibitors across 14 worlds. Provided templates. Mostly commerce for avatars and wearables.
+
+                    -   Had 125,000 visitors
+
+                -   “Virtual market 4” in one month. 1,400 exhibitors
+                -   Jin will be hosting a virtual field trip.
+                -   Don’t need VR, can visit in ‘desktop mode’
+                -   These occur in ‘VR Chat’
+
+            -   IPFS provides the data layer
+            -   Already good enough to act as a shared whiteboard
+            -   Consider: a virtual expo for the IPFS ecosystem
+            -   Advantage: can teleport back to the conference world from 6 months ago.
+            -   Currently many booths have QR codes for a backend payment processor. Jin wants to more seamlessly integrate eth for the web3 community.
+            -   WebXR can be both the creation and distribution platform.
+
+
+**Q&A, Help Wanted**
+
+_Ask questions, get answers. Announce issues that need help, get people to help._
+
+-   What is WebXR browser support like now?
+
+    -   Oculus / other headsets out at the moment - you can visit a link and go into ‘VR mode’. It connects headsets to the browser. There should always be desktop support as well.
+
+-   EXOkit - is that like VRChat?
+
+    -   It’s a ‘meta’ layer - with exokit in any VR world, it’s like you have AR on in your virtual world. To go to a different world would be a different experience. Exokit is trying to treat everything as a holographic layer that can composite together.
+
+-   Should we do a VR meetup?
+
+    -   It takes a couple days of planning
+    -   Meeting up in hubs is a good first step.
+    -   If companies need booths, the model can be providing templates, and then offering services to customize - but that asset can then be re-used at other events.
+
+-   Best way to contact Jin:
+
+    -   Discord: jin#6455
+    -   Twitter:[@dankvr](https://twitter.com/dankvr)