Confirm
656
edits
Changes
no edit summary
* Wei is traveling and has an afternoon to kill. He visits a local library, where he has a great idea for a web page that shows a map of where he's been along with some photos. He visits nimble.webmaker.org, and specifies that he's using an untrusted computer. He is able to access his old files, where some of his images live. He creates a new web page, uses a Map API in JS, saves and publishes everything before emailing his friends the link to his make. When he's done he closes the browser he's been using, which deletes all the files he was accessing locally (they are saved in Webmaker's server).
* Hope is at her brother's house. He's working on a project for school, and struggling to get a piece of JavaScript to work. Hope knows she's done something similar in the past, and pulls out her phone. She's able to view her old Webmaker files using MakeDrive, and finds exactly what she wants. She shares a URL with her brother, and he's able to open her JS file, and they use it to solve his problem.
==Technology==
* S3 is our backend
* MakeDrive is a few things:
** a node.js backend to proxy S3 requests using Webmaker auth
** a client-side library that mixes Filer, node/S3 communication, Webmaker auth, sync
* We need to sort out how MakeDrive integrates with makes.org for publishing (2 separate buckets for now)
* The node/S3 proxy can use S3's API, and probably we can reuse an existing node.js module that does a bunch of this (knox?)
* Need to figure out push notifications so that S3 proxy can let local filesystem know when things are saved or changed
==Questions==
