On Wed, Dec 28, 2022 at 3:00 PM Ken Pettit <[email protected]> wrote:
> On 12/28/22 2:52 PM, John R. Hogerhuis wrote: > > > > So to facilitate sharing of programs, RAM images possibly bundled with > > config/launch instructions, the bundles need to be published on the > > web. Google Drive supports sharing content via URL. HTTP, HTTPS, FTP > > servers were of course built for that though I think most people don't > > want the hassle of managing their own servers, even with something > > like WebDAV which in my experience can be a pain. Another store might > > be Github links or similar... since then your URL could always provide > > a link to your current hopefully least buggy version. > > > > Another thought would be to (somehow) code up access to files in the > Club100 Personal Libraries section. Not sure what that would look like > at the moment though. > > Yeah. For sharing personal library files, the main thing it would require is supporting normal MIME types. Currently files that are exposed in the personal libraries, for example " http://club100.org/memfiles/index.php?action=downloadfile&filename=DETOKE100.exe&directory=John%20Hogerhuis/Utilities&; " present headers 1. Content-Disposition: attachment; filename="DETOKE100.exe" 2. Content-Transfer-Encoding: binary 3. Content-Type: application/force-download; name="DETOKE100.exe" Designed to cause a download and save local by the browser. This might work as is, since the javascript can probably do whatever it wants as long as CORS issues are addressed. In fact, using Personal Libraries gives a route to solving CORS issues since CloudT from Bitchin100 just needs to explicitly trust Club100, I think. I already have some trust set up for Club100 to allow http / ftp links from the Club 100 BBS library. The normal thing for such an application would be to expose real MIME types... text/plain for manifest and DO files, and octet-stream for RAM image, BA, and CO files. Content could be managed using the current interactive interface. Saving direct from CloudT to Club100 would be a whole other matter. Then it needs to be a web API with authentication and logic to protect Club100 from shenanigans. If I get that far... no particular need at the moment. -- John. If we Content-Type: application/force-download; name="DETOKE100.exe" Content-Type: application/force-download; name="DETOKE100.exe" Ot
