Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Create 2018-11-21--gui-and-in-web-browsers-weekly.md #771

Merged
merged 2 commits into from
Nov 28, 2018
Merged

Create 2018-11-21--gui-and-in-web-browsers-weekly.md #771

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c40683
Create 2018-11-21--gui-and-in-web-browsers-weekly.md
lidel Nov 22, 2018
0bf7cfe
Update meeting-notes/2018/2018-11-21--gui-and-in-web-browsers-weekly.md
fsdiogo Nov 23, 2018
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
127 changes: 127 additions & 0 deletions meeting-notes/2018/2018-11-21--gui-and-in-web-browsers-weekly.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,127 @@
# GUI & In Web Browsers Weekly Sync 2018-11-21

- **Lead:** @olizilla
- **Notetaker:** @lidel
- **Attendees:**
- @terichadbourne
- @olizilla
- @lidel
- @alanshaw
- @hacdias
- fsdiogo
lidel marked this conversation as resolved.
Show resolved Hide resolved

## Before the Sync

- Write down your updates
- What have you accomplished since the last Weekly?
- Were there any blockers? If so, which ones? Is it still blocked? Why?
- What is the next important thing you should focus on?
- Read updates of others
- Any questions, requests to communicate?
- Ask everyone to put their name into the list of attendees and add any last minute agenda items
- Go over everyone's updates and ask if there are any questions or things to discuss
- Everyone can demo something!

## Agenda

- PSA: Upate IPFS Working Group Capacity Planner (link in Action Items at the end)
- Q4 mid quarter scoring - should we skip the mid quarter self assesment this time?
- IPFS KPIs
- metrics to track how the project is doing.
- A lightweight tool to let different teams set their own prorities, but still pull in the same direction.

## Notes

### Team Updates

- @lidel
- Done:
- Moved meeting notes to [team-mgmt](https://github.com/ipfs/team-mgmt/pull/760) and added Zoom Call URL to [IPFS Calendar (UTC)](https://calendar.google.com/calendar/embed?src=ipfs.io_eal36ugu5e75s207gfjcu0ae84@group.calendar.google.com&ctz=UTC) with Oli as co-host.
Copy link
Member

Choose a reason for hiding this comment

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

Thaank you ❤️

- Issue updates related to foreign fetch being removed from ServiceWorker
- Summary: [in-web-browsers/issues/55](https://github.com/ipfs/in-web-browsers/issues/55#issuecomment-439255498) | Details: [arewedistributedyet/issues/32](https://github.com/arewedistributedyet/arewedistributedyet/issues/32)
- Fixed up basic Service Worker demo to work with latest js-ipfs - [ipfs-service-worker/pull/16](https://github.com/ipfs-shipyard/ipfs-service-worker/pull/16)
- Started looking into js-ipfs in service worker shared over iframe - [service-worker-gateway/issues/30](https://github.com/ipfs-shipyard/service-worker-gateway/issues/30)
- Removed suggestion to set `Access-Control-Allow-Credentials` from GUIs, docs and scripts as a part of [HTTP Headers Cleanup](https://github.com/ipfs/in-web-browsers/issues/132)
- `window.ipfs.enable()` is now used by `window.ipfs-fallback` if available ([#2](https://github.com/ipfs-shipyard/window.ipfs-fallback/pull/2))
- Next:
- publish API drafts as PR for comments
- finish sw+iframe demo/poc to test feasibility of [service-worker-gateway/issues/30](https://github.com/ipfs-shipyard/service-worker-gateway/issues/30#issue-381410578)
- @alanshaw
- Done:
- Files API refactor (MERGED NOT YET RELEASED)
* `ipfs.files.add` => `ipfs.add`
* `ipfs.files.addPullStream` => `ipfs.addPullStream`
* `ipfs.files.addReadableStream` => `ipfs.addReadableStream`
* `ipfs.files.cat` => `ipfs.cat`
* `ipfs.files.catPullStream` => `ipfs.catPullStream`
* `ipfs.files.catReadableStream` => `ipfs.catReadableStream`
* `ipfs.files.get` => `ipfs.get`
* `ipfs.files.getPullStream` => `ipfs.getPullStream`
* `ipfs.files.getReadableStream` => `ipfs.getReadableStream`
* --- New core files API methods (js-ipfs) / moved from `ipfs.util` (js-ipfs-api):
* `ipfs.addFromStream`
* `ipfs.addFromUrl`
* `ipfs.addFromFs`
* See https://github.com/ipfs/js-ipfs/pull/1720
- `ipld-dag-pb` refactor (MERGED NOT RELEASED) TLDR; no `multihash` or `cid` properties
- [`--cid-base`/`?cid-base` PR](https://github.com/ipfs/js-ipfs/pull/1552) is ready for review!
- `window.ipfs.enable()` is now used by `window.ipfs-fallback` if available ([#2](https://github.com/ipfs-shipyard/window.ipfs-fallback/pull/2)) thanks @lidel!
- Pair programming with [@pkafei](https://github.com/pkafei)
- [0.34](https://github.com/ipfs/js-ipfs/issues/1721) is coming end of Nov/beginning of Dec
- Blocked:
- [Object API breaking change to return CIDs](https://github.com/ipfs/interface-ipfs-core/pull/388#issuecomment-437866965) "soft blocks" a release of js-ipfs-api.
- Next:
- Implement `addFrom*` methods in js-ipfs
- Write interop tests for CIDv0/1 put and get
- @fsdiogo
- Done:
- Share Files working without public gateways
Copy link
Member

Choose a reason for hiding this comment

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

Could it use the Service Worker Gateway?

Copy link
Contributor

Choose a reason for hiding this comment

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

It could. Right now it's using ipfs-redux-bundle that chooses the best available connection and fires up a js-ipfs instance as a fallback.

Copy link
Member

Choose a reason for hiding this comment

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

woa! I didn't know about that!

Can someone do a video tutorial pleaaase?

Copy link
Member Author

@lidel lidel Nov 24, 2018 •
edited
Loading

Choose a reason for hiding this comment

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

ipfs-redux-bundle is React-specific lib we use internally for R&D in WebUI/Companion/Desktop, API is not stable yet :)
In the following weeks we will extract the fallback logic into a separate, framework-agnostic lib and make tutorials for that.

- https://github.com/ipfs-shipyard/ipfs-share-files/pull/44
Copy link
Member

Choose a reason for hiding this comment

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

Just gave share.ipfs.io a spin. Was intrigued by

image

Copy link
Member

Choose a reason for hiding this comment

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

Btw, this is kind of the same as https://filenation.io. What is different in this app that justifies creating and maintaining another codebase?

Copy link
Member

Choose a reason for hiding this comment

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

@fsdiogo

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure I follow the question in the image. This is not supposed to mimic a gateway, the visible url and # is for the app internal routing.

It's similar in the way that is an app to share files, yes.

  • FileNation sends an email with a link where you can download the file, it doesn't provide a direct link for you to share instantly with anyone. In Share Files you get a direct link to the app where you can see the files listing and download them.
  • Share Files takes advantage of a local daemon if you're running one, works great with IPFS Companion too and uses js-ipfs as fallback if needed.
  • Share Files is going to be integrated in Web UI and in IPFS Companion.
  • In my opinion Share Files is a lot more appealing and ready-to-use to quickly get a link to share with anyone.
  • We own the Share Files code and it's UI direction, as we're trying streamline the UI across our apps.

Copy link
Member Author

Choose a reason for hiding this comment

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

To compliment Diogo's points, there is a relevant background discussion in ipfs/ipfs-gui#34 (Design: Share files via IPFS).

IIRC historical reasoning for ipfs-share-files was along these lines:

  • It is a good opportunity for dogfooding our upload and fallback APIs (we squashed a lot of bugs while working on upload in ipfs-companion, ipfs-webui and now pushing boundaries even further with ipfs-share-files)
  • Lack of a good Sharing App that "is always there and just works" could hurt IPFS in the long run because general public often associates bad UX with low quality software.
    Third party solutions come and go and are not robust enough. Some require a writable gateway, use centralized backend or don't use js-ipfs fallback at all etc.
  • Apart from technical reasons we wanted a branded Sharing App as a platform to gently introduce IPFS concepts to the general public.

- Enable dir listing and downloading folder structures
- https://github.com/ipfs-shipyard/ipfs-share-files/pull/47
Copy link
Member

Choose a reason for hiding this comment

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

It would be cool to have channels just like the exchange files example has

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that is something that is being discussed (ipfs/ipfs-gui#52, ipfs/ipfs-gui#36) but probably will fall under the Web UI.

Copy link
Member Author

Choose a reason for hiding this comment

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

There is also ipfs/ipfs-gui#57 ("hackpad for file sharing" ) which is exactly about taking the "exchange files example", refining the UX and integrating it with ipfs-webui (directly or via ipfs-share-files).

The wow factor of doing this right could be massive. This will happen for sure, but we want to get MVP with basic sharing out of the door, and iterate from there.

- Next:
- Integrate Share Files in Web UI and Companion
- IPFS UI Component Library ✨
- @olizilla
- Done:
- Design Systems London Conf
- Error modal design
- share files planning
- Next
- Define what's todo in Desktop
- Fix resource utilization in webui
- cut webui release
- @hacdias
- Done:
- Merge 'The PR' of IPFS Desktop
- https://github.com/ipfs-shipyard/ipfs-desktop/pull/662
- Still working on:
- IPFS Desktop settings on Web UI
- https://github.com/ipfs-shipyard/ipfs-webui/pull/883
- Error handling on Desktop:
- https://github.com/ipfs-shipyard/ipfs-desktop/pull/697

### Discussion Highlights ✨

- Some js-ipfs in Service Worker updates: [in-web-browsers/issues/55](https://github.com/ipfs/in-web-browsers/issues/55#issuecomment-439255498)
- js-ipfs 0.34 coming at the end of Nov/beginning of Dec with [nice API cleanup/refactoring](https://github.com/ipfs/js-ipfs/pull/1720)
- IPFS Desktop: improving UX for [error handling, built-in issue reporting](https://github.com/ipfs-shipyard/ipfs-desktop/pull/697)
- IPFS Share App: wip on improvements for users without ipfs-companion (embedded js-ipfs + gateway)
- Proto School: wip on saving state to local storage between learning sessions
- Open discussion: working hours / open-door-policy to provide support for people with questions about GUI/websites?
- PSA: Working Group Capacity Planner (@all: see Action Item below)
- We did Milestone Evaluation Exercise ([notes](https://hackmd.io/haC8c6tPQYiBHJp09KzbMQ))
- Review of [IPFS Project KPI Draft](https://docs.google.com/document/d/1r2Ng8Ura9yg63Aq8sXpJQ-PKFhDzJADoHRxZUESUugg/edit#) (will be made public in following weeks)
- Everyone grabbed one Milestone and picked one Awesome and one Meh milestone and we discussed what makes them that way.
- Brief discussion about the need for explaining basic concepts "just in time", so users are not overwhelmed. Both [docs.ipfs.io](https://docs.ipfs.io/guides/concepts/) and [proto.school](https://github.com/ipfs-shipyard/proto.school/pull/59) try to address this.
- Creating websites with IPFS is a good opportunity to onboard users with IPFS concepts.

### By The Way! ✨

- @Gozala (Research Engineer at Mozilla) joined us last week during [All Hands Call](https://github.com/ipfs/team-mgmt/issues/756) and gave a talk about [mozilla/libdweb](https://github.com/mozilla/libdweb). [Recording](https://www.youtube.com/watch?v=0fT9HC2Crqw) and [Meeting Notes](https://github.com/ipfs/team-mgmt/blob/master/meeting-notes/2018/2018-11-12--all-hands.md#main-presentation) are available.


### Action Items

- @all: Fill your estimated availability for 2019 in J column of [IPFS Working Group Capacity Planner - 2019 Roadmapping](https://docs.google.com/spreadsheets/d/1M7vSGfQyHZFQ0D-WpBcbjLCZrNT0x-qiRcR_7qzgyJo/#gid=2055723494). If you don't have write access, just message @lidel or @olizilla.
- @all: Read [IPFS Project KPI Draft](https://docs.google.com/document/d/1r2Ng8Ura9yg63Aq8sXpJQ-PKFhDzJADoHRxZUESUugg/edit#) and provide comments