<p>A year or so ago I wrote the shell of a (PHP) website which would allow a user to browse various selected modules, "purchase" one, create a unique encryption key for that user and encrypt the module for them.</p>
<p>It would then give the user a single download which could be installed with a Python/Qt app I wrote, which would also accept the user's encryption key and enter it into the module conf file.</p>
<p>It never went anywhere because of various non-technical reasons, but adding user upload and giving a user the chance to release their own modules, etc, would be easy extra functionality.</p>
<p>Note: everything about the site was a temporary hack designed to prove the technical aspects could be done and not to actually be used. E.G. It did not actually require money and there was no user sign up and the like. But those are trivial and off topic from point of view of the SWORD functionality.</p>
<p>--Greg</p>
<div class="gmail_quote">On Nov 5, 2010 4:45 PM, "Matthew Talbert" <<a href="mailto:ransom1982@gmail.com">ransom1982@gmail.com</a>> wrote:<br type="attribution">> rote:<br>>> "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> writes:<br>
>>> Matthew Talbert had a great suggestion on IRC last night to simply add<br>>>> a 'prep for publishing' (or in his words simply "publish") option to<br>>>> the InstallMgr interface...<br>
>><br>>> It's great, but funny, to see all the sudden interest in publishing<br>>> users' content. I've talked about it a couple times here in<br>>> sword-devel, but the idea never got any traction before. Why now?<br>
>><br>>> Nearly 3 years ago:<br>>> <a href="http://www.crosswire.org/pipermail/sword-devel/2008-January/026736.html">http://www.crosswire.org/pipermail/sword-devel/2008-January/026736.html</a><br>> <br>
> Part of this concept of "publish" was not really pushing to a remote<br>> repository, but the idea that we could (say using the Xiphos module<br>> manager) pick a subset of installed modules, and prepare them for<br>
> remote access. If, for example, we were to agree that an HTTP<br>> repository could consist of a single file listing the contents<br>> (really, no different than mods.tar.gz) + a set of zipped files, then<br>> this "publish" would create this whole directory, ready for simply<br>
> copying to any http-accessible location.<br>> <br>> The other part of the publish would be publishing a single module to a<br>> remote location where a user has an account. This would be very<br>> similar, but it would just be pushing a single zip file, and the<br>
> remote server would be responsible for putting it in the correct<br>> location, and updating the repository listing.<br>> <br>> Part of why I'd like very much to see a repository able to consist of<br>> this directory listing + zipped modules is that it makes the whole<br>
> idea of remote publishing much easier. With FTP, it's a pain to set up<br>> various directories with different permission schemes on the fly,<br>> while using HTTP would allow typical server-side software (eg, PHP,<br>
> django, etc) to handle rather complex schemes easily. It would be<br>> relatively simple on the same server to have a system that allowed a<br>> user to come sign up for an account, and suddenly that user has<br>
> publish capability unique to him. Then, if he wanted to publish to a<br>> more shared and publicly visible location, a simple flip of the switch<br>> would allow him to publish there as well. This would allow everyone to<br>
> quickly share with their friends, but require interaction with a<br>> repository owner before being allowed to publish there.<br>> <br>> Matthew<br>> <br>> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br></div>