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

Conversation

@fsdiogo
Copy link
Contributor

@fsdiogo fsdiogo commented Dec 5, 2018

cc #790

@ghost ghost assigned fsdiogo Dec 5, 2018
@ghost ghost added the status/in-progress In progress label Dec 5, 2018
@fsdiogo
Copy link
Contributor Author

fsdiogo commented Dec 5, 2018

Can I get push access to this repo so I don't have to fork?

// cc'ing as I can't assign reviewers: @olizilla @lidel @hacdias @alanshaw @terichadbourne


- @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

- 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

@daviddias daviddias merged commit fcedf37 into ipfs:master Dec 12, 2018
@ghost ghost removed the status/in-progress In progress label Dec 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants