Skip to content
This repository was archived by the owner on Feb 8, 2023. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
130 changes: 130 additions & 0 deletions meeting-notes/2018/2018-12-05--gui-and-in-web-browsers-weekly.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,130 @@
# GUI & In Web Browsers Weekly Sync 2018-12-05

- **Moderator:** olizilla
- **Notetaker:** @fsdiogo
- **Attendees:**
- @hacdias
- @lidel
- @olizilla
- Jason Zhou
- @terichadbourne
- @alanshaw

**Moderator checklist**

- Ensure that there is a notetaker
- Start recording
- Call for additional agenda items

**Agenda**

- Moving notes to Google Doc (you are here ;^))
- Should make it easier for people to submit agenda items
- After each call we covert to Markdown and publish to https://github.com/ipfs/team-mgmt/tree/master/meeting-notes
- Super easy conversion via https://github.com/Mr0grog/google-docs-to-markdown
- Team Updates and Demos
- @olizilla - 10 mins - ipfs-share-files - Experiment with websocket-star in js-ipfs fallback (https://github.com/ipfs-shipyard/ipfs-share-files/issues/63#issuecomment-444437359)
- @olizilla - 5 mins - Reach out to other IPFS file sharing services (https://github.com/ipfs-shipyard/ipfs-share-files/issues/52)

**Team Updates**

- @lidel
- Done:
- Spent big chunk of time on reviewing IPFS and libp2p Roadmaps, added some comments and questions
- Provided some knowledge transfer about WebExtension stores to Discussify team :)
- [RFC: Support ArrayBuffer as an alternative to Buffer input argument](https://github.com/ipfs/interface-ipfs-core/issues/404)
- Added ipfs-share-files to Transifex: https://www.transifex.com/ipfs/ipfs-share-files/
- Origin Trial for Signed HTTP Exchanges is enabled for ipfs.io Gateway – details in https://github.com/ipfs/infrastructure/issues/453#issuecomment-442944274 & https://github.com/ipfs/in-web-browsers/issues/121#issuecomment-442952118
- Fixed local build of blog.ipfs.io - https://github.com/ipfs/blog/pull/199
- Fixed ipfs-companion’s API access in Chrome 72 - https://github.com/ipfs-shipyard/ipfs-companion/pull/631
- Confirmed js-ipfs repo can be shared by multiple pages when embedded via iframe
- Blocked:
- Waiting for cert from Digicert (for SXG experimentation)
- Companion fails to build after dependency bump, looking into it (webpack/terser)
- Next:
- Release new Companion Beta release with fix for Chrome Beta
- Blog post about Signed HTTP Exchanges at ipfs.io
- Finish capabilities preload via window.ipfs.enable and ship to Beta


- @terichadbourne
- Done:
- Opened an issue proposing a workshop using the file API (rather than DAG API) for ProtoSchool. (All current workshops use the DAG API so it’s not being surfaced that file transfer is possible.) Open to suggestions and feedback at https://github.com/ipfs-shipyard/proto.school/issues/91
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would be great! A lot of people get confused between the Files API with the DAG API and the Block API

- Was guinea pig in usability test of Web UI with Oli
- ProtoSchool updated to use the new CID link API (about to be merged from https://github.com/ipfs-shipyard/proto.school/pull/88)
- Taught ProtoSchool to save state of code in editor box and completion status of each lesson (to be merged this week from<https://github.com/ipfs-shipyard/proto.school/pull/86>)
- Conducted usability test of ProtoSchool


- @olizlla
- Done:
- Short week, was off thurs / friday
- 3x Useability interviews for Web UI - https://github.com/ipfs-shipyard/ipfs-webui/tree/master/docs/usability/notes
- cleanup repository before starting up IPFS PR reviews
- Kick off “add Desktop to ipfs.io website” https://github.com/ipfs/website/issues/281 to honour it’s upcoming new release.
- Get specton test working for ipfs desktop - https://github.com/ipfs-shipyard/ipfs-desktop/pull/730
- Docs PR review https://github.com/ipfs/docs/pull/67
- Blocked:
- N/A
- Next:
- 2 more usability testing session for webui. write up the common issues. Propose next round of improvements to webui
- Replace distribution of peers graph in webui with repo size information. Limit geolocations to peers page to avoid gratuitous system load.
- Cut a release of Web UI
- PR go-ipfs to add webui link to ipfs daemon output.
- GET DESKTOP RELEASED 🚢 ✨
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

YEEEAASSSSS!!!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this happen?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. Most of the time available has gone on

  • Dealing with errors where a previous ifps deaemon wasn't shutdown properly feat: cleanup repository before starting up IPFS ipfs-desktop#722 - this ment the app would fail to start if the user previously ran ipfs daemon manually, and didn't wait for the process to shutdown gracefully when exiting.
  • Dealing with issues related to CORS that was raised during reviews of the unclean startup PR. We were initially editing the users node config to include a CORS origin for webui://- which is the fake scheme under which we serve the webui from within the electron app. We then decided that we didn't want to leave the user with a node config that included a CORS origin that would live on beyond the life of the app, as we can't predict how it could be abused in the future.
    • So @hacdias refactored to proxying ipfs but a quick test showed that it crashed the electron webview on large files. This is probably fixable, but we decided to keep things simple and disable CORS checks for the webview, as we are in control of the window and the webui code. As a precuation we are enabling the other electron security recommendations in feat: improve security of electron app ipfs-desktop#741

I'd like to have a pre-release this afternoon, though it looks like it will have to be tomorrow now, and get it installed on gui team machines, so we can test out the auto-update mechanism, and then invite the IPFS org to give it a go.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the super complete status update. ❤️ @olizilla



- @alanshaw
- Done:
- Progress on [async iterators endeavour](https://github.com/ipfs/js-ipfs/issues/1670)
- interface-datastore https://github.com/ipfs/interface-datastore/pull/25
- datastore-level https://github.com/ipfs/js-datastore-level/pull/12
- Many reviews for [js-ipfs 0.34](https://github.com/ipfs/js-ipfs/issues/1721)
- Switched to octobox for all github notifications
- [email protected] -[streaming ls](https://github.com/ipfs/interface-ipfs-core/blob/master/SPEC/FILES.md#fileslsreadablestream)!
- Benchmark tests matrix was created
- https://gist.github.com/alanshaw/e8f49ff1875f0e256e7c45ddeef31498
- More test ideas are here needed!?
- Blocked:
- N/A
- Next:
- Implement CID version agnostic get
- Implement addFrom\* methods in js-ipfs
- Release candidate for js-ipfs 0.34 🚢


- @hacdias
- Done:
- Fixed some IPFS Desktop related issues.
- Progresses on ECONNREFUSED issue: https://github.com/ipfs-shipyard/ipfs-desktop/pull/722
- Blocked:
- N/A
- Next:
- Work on removing the need for CORS headers for IPFS Desktop
- https://github.com/ipfs-shipyard/ipfs-desktop/issues/728
- Decide whether or not to remove React from IPFS Desktop menubar
- https://github.com/ipfs-shipyard/ipfs-desktop/issues/732
- Release Desktop 0.6


- @fsdiogo
- Done
- Finalised and shipped app copy
- https://github.com/ipfs-shipyard/ipfs-share-files/pull/57
- Added project to Transifex
- https://github.com/ipfs-shipyard/ipfs-share-files/pull/61
- Updated the readme
- https://github.com/ipfs-shipyard/ipfs-share-files/pull/62
- IPFS website new section proposal
- https://www.figma.com/file/RLVmj3C8fy84KrdaFLPuHbvX/ipfs.io?node-id=0%3A1
- Blocked:
- N/A
- Next:
- Finish IPFS website new section
- Work on Share Files to use a signalling server


**Notes**

- After [this discussion](https://github.com/ipfs-shipyard/ipfs-share-files/issues/63) we reached consensus and we’re moving forward to using a websocket-star server as a centralised discovery server.
- Before releasing Share Files we must [reach out to other IPFS file sharing services](https://github.com/ipfs-shipyard/ipfs-share-files/issues/52), being as starting a direct conversation or opening issues in their repos. This should be collaborative and educational for both parties.