tag:blogger.com,1999:blog-42641242305037200562024-09-06T16:55:13.332-08:00Django based file transfer systemwhardierhttp://www.blogger.com/profile/14705990681790573861noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4264124230503720056.post-42987669552381910852007-09-14T18:01:00.000-08:002007-09-14T18:07:52.755-08:00Looking for a good method to view local users via LDAP search, as well as cache user information into the local data store for quick information retrieval. Any takers?<br /><br />I assume I could just inherit the django user modules into a new module and populate the user data and hijack authentification requests. Would it be evil of me to cache the passwords in the local user interface just in case the LDAP server is down? I think not....whardierhttp://www.blogger.com/profile/14705990681790573861noreply@blogger.com0tag:blogger.com,1999:blog-4264124230503720056.post-28000530959830942962007-09-14T16:28:00.001-08:002007-09-15T09:13:32.093-08:00I'm hoping to make fizbiz (<span class="blsp-spelling-error" id="SPELLING_ERROR_1">FB</span>) into a simple and easy to use system for sharing files via a web browser. Authorized user accounts can use <span class="blsp-spelling-error" id="SPELLING_ERROR_2">FB</span> to generate file request tokens called <span class="blsp-spelling-error" id="SPELLING_ERROR_3">FIZ</span>.<br /><br />Each <span class="blsp-spelling-error" id="SPELLING_ERROR_4">FIZ</span> is a short unique identifier which can be used as a file upload token. For example, an <span class="blsp-spelling-error" id="SPELLING_ERROR_5">FB</span> server should have an easy to remember domain name like http://fb.company.com/. To access <span class="blsp-spelling-error" id="SPELLING_ERROR_6">FIZ</span> ID PR5347D the <span class="blsp-spelling-error" id="SPELLING_ERROR_7">url</span> you would hand somebody you wanted to get or send a file to would be http://fb.company.com/PR5347D.<br /><br />Each <span class="blsp-spelling-error" id="SPELLING_ERROR_8">FIZ</span> is highly configurable and allows for the following options<br /><ul><li>Upload expiry (for limiting uploads to a slim amount of time)<br /></li><li>Files expiry (defaults to the upload expiry until changed)</li><li>Multiple files support<br /></li><li>Upload file(s)<br /></li><ul><li>WebDAV Server Integration</li></ul><li>File size limitations<br /></li><li>Upload and retrieve notifications for all <span class="blsp-spelling-error" id="SPELLING_ERROR_10">FIZ</span> participants<br /></li><ul><li><span class="blsp-spelling-error" id="SPELLING_ERROR_11">RSS</span></li><li><span class="blsp-spelling-error" id="SPELLING_ERROR_12">SMS</span><br /></li></ul><ul><li>Instant Messages</li></ul><ul><li>E-Mail</li></ul><li>Server based <span class="blsp-spelling-error" id="SPELLING_ERROR_13">GPG</span> Encryption</li><ul><li>Recipients can add their own key which is moderated by the owner</li><li>Owner can select from list of existing keys</li><li>Preexisting keys can be related to recipient notification database</li></ul><li>Set a simple password</li><li>Require <span class="blsp-spelling-error" id="SPELLING_ERROR_14">captcha</span> verification</li><li>Require registered local user</li><li>Require registered recipient<br /></li><ul><li>Simple registration interface</li></ul><ul><li>Recipients can be upgraded to local users through the administration interface.</li></ul><li>Newly registration recipient expiry<br /></li></ul>Administrators of an <span class="blsp-spelling-error" id="SPELLING_ERROR_15">FB</span> site have control over which options are configurable and what value ranges are acceptable.<br /><br />To share a set of files with multiple people just share the <span class="blsp-spelling-error" id="SPELLING_ERROR_16">FIZ</span> URL, if the data is not <span class="blsp-spelling-corrected" id="SPELLING_ERROR_17">sensitive</span> a <span class="blsp-spelling-error" id="SPELLING_ERROR_18">FIZ</span> URL should be quite secure for simple file sharing, especially if it has a short expiration time.<br /><br /><span class="blsp-spelling-error" id="SPELLING_ERROR_19">FB</span> is ideal in situations where it is important to be notified file is downloaded. By requiring a recipient to be registered before downloading a file referenced by a <span class="blsp-spelling-error" id="SPELLING_ERROR_20">FIZ</span> you can track who downloaded the file by registration ID.<br /><br />In short, I'm not reinventing any wheels here. Initially I wanted a system like <span class="blsp-spelling-error" id="SPELLING_ERROR_21">FB</span> so that I could instruct my local mail server to reject messages over a few megs, then email the recipient with a request to issue a <span class="blsp-spelling-error" id="SPELLING_ERROR_22">FIZ</span> to the sender.whardierhttp://www.blogger.com/profile/14705990681790573861noreply@blogger.com0