From 07bf43a314fe65ccd9c7cb663c3c6134a47cc269 Mon Sep 17 00:00:00 2001 From: Zhiming Wang Date: Mon, 4 May 2015 18:45:17 -0700 Subject: edit posts and (mostly) figured out the theme Also wrote pyblog that currently can generate parts most of the blog. --- source/blog/2014-11-20-dropbot-for-geeks(r).md | 5 ----- 1 file changed, 5 deletions(-) (limited to 'source/blog/2014-11-20-dropbot-for-geeks(r).md') diff --git a/source/blog/2014-11-20-dropbot-for-geeks(r).md b/source/blog/2014-11-20-dropbot-for-geeks(r).md index e46ec401..74faf730 100644 --- a/source/blog/2014-11-20-dropbot-for-geeks(r).md +++ b/source/blog/2014-11-20-dropbot-for-geeks(r).md @@ -6,15 +6,10 @@ date-display: November 20, 2014 I propose the following cloud storage and syncing service model of the future. I call it **Dropbot for Geeks®**, and it totally rules. It's designed for geeks who are tired of the highly limited, miserably unproductive traditional services (based on clicking around). It has the following features: * Standard Unix file system commands exposed as an API, e.g., `cat`, `cd`, `cp`, `du`, `df`, `file`, `find`, `head`, `ln`, `ls`, `mkdir`, `mv`, `pwd`, `rm`, `rmdir`, `tail`, `touch`, etc. - * A rudimentary shell emulator through the web interface exposing the commands above. - * Secure shell access to the file system, also exposing the commands above. Provide two-factor auth for SSH. Clearly, `scp` should also be supported. - * Checksums. Expose, for instance, `md5sum` or `sha1sum`, in the API. Provide checksums on download pages, probably on demand. - * Programmable selective syncing, down to per file level. - * Scriptability. Allow clients to run custom scheduled jobs or daemons with the API above. To prevent the service from becoming full-featured IaaS, though, clients might be limited in CPU time, memory, or command selection. This bullet point is arguable. --- -- cgit v1.2.1