a pair of dedicated clients for plan 9 would be straightforward. the client would need to authenticate the user (oauth2), then switch the session to websocket over which 9p messages travel. a plan 9 import client (in go) would post the 9p connection to /srv; it can then be mounted anywhere. exporting would be similar; after a successful auth, it would start exportfs and relay 9p messages between the exportfs fd and the websocket. it is something i would like to do at some point.
on 9pcloud, in the local file explorer (panel on the left side) each file name has an "X" icon next to it; clicking the X will delete the corresponding file from the local html5 filesystem. also, the html5 filesystem on the browser that 9pcloud creates is temporary; if you restart your browser the 9pcloud fs in the browser is wiped clean. btw, this chrome extension ( https://chrome.google.com/webstore/detail/html5-filesystem-explorer/nhnjmpbdkieehidddbaeajffijockaea?hl=en-US) lets you view any local html5 filesystem when you visit the site that created it. On Sun, Aug 16, 2015 at 7:36 PM, Shane Morris <edgecombe...@gmail.com> wrote: > Hi 9fans, > > Just working with 9PCloud today, made a backup of some files I'm going > to 3D print in the next four weeks - ended up making two copies, one > in a specific folder, one in the parent folder... > > Was wondering if I'd be able to connect to the 9PCloud via my Mac9P > (Finder interface) to do some management on the files rather than > through the web interface? This may work for people who wish to have a > "Dropbox alike" interface. > > Failing that, how can I delete the second copy of the files from 9PCloud? > > Many thanks! > > Shane. > >
