wm: doc

Download patch

ref: 5bbb84720ad91a68531ffd1754ae29425fbddc6c
parent: 171d25493dcc51fbcb0e21aebaf018e74bfebe2b
author: glenda <glenda@9pi4>
date: Fri Sep 6 21:19:49 EDT 2024

fix formatting of 9pideas.ms

--- a/9pideas.ms
+++ b/9pideas.ms
@@ -1,29 +1,43 @@
-# 9pideas
+.TL 9pideas
+.HTML 9pideas
 
-    troff->html,troffdown->markdown, postscript thing->web layout engine, 9p->http
+.PP
+troff->html,troffdown->markdown, postscript thing->web layout engine, 9p->http
     
-
+.PP
 9p could hyperlink all our man pages. A single mouseclick would let you browse documentation (and research papers written in troff) from anywhere in the world. 
 
+.PP
 Automatic archival of all 9p content via cwfs. Make dumps like the internet archive but applied to every file, giving you a wayback machine snapshot of everything on 9p. Is this the web we have all been waiting for? 
 
+.PP
 If the publisher is responsible for making the dump, what if the publisher dies? Then his 9p file hierarchy \*and\* his backups go offline simultaneously, giving us zero redundancy. Cwfs gives you this nice /n/dump/2023/0829/ snapshot, just like internet archive does. Ideally a daily snapshot should be distributed among the reader base to avoid a single fault system. I suspect Cwfs could easily make its dumps to a remote file server. We would then be able to pull up really old archives of books, journal articles, research papers, and man pages -- drm free 
 
+.PP
 A new filesystem that takes daily snapshots like cwfs but stores it over torrents. Poor man's FS -- PMFS 
 
+.PP
 CGI for files and directories ([FNS][1] would be handling dynamic generation of file paths). Perhaps see [execfs][2]. 
 
+.PP
 Imagine if a single file had 3 different views: /path/to/file.{c,lua,lisp} . These 3 source files could be generated dynamically by some compiler from a single source file. Or perhaps three texts /path/to/blog/{chinese,spanish,french}, all generated from /path/to/blog/english. 
 
+.PP
 Binaries can also be generated dynamically over the network so that users do not need to compile the software. 
 
+.PP
 Because 9 can boot from a remote filesystem, developers can work easily with dumb terminals. 
 
+.PP
 The remove filesystem may enable a universal hardware lab, since it should be possible to easily cross compile software for every architecture on the distributed grid. 
 
+.PP
 Both p9p and 9fork (ircnow's custom fork) could be written mostly in lua to speed up development.
 
+.PP
 Provide an overlay filesystem on top of the normal filesystem that stores itself as encrypted files (see duplicity https://duplicity.gitlab.io, maybe stashfs http://shithub.us/cinap_lenrek/stashfs/HEAD/info.html).
 
- [1]: https://wiki.ircnow.org/index.php?n=9.FNS
- [2]: http://felloff.net/usr/cinap_lenrek/execfs.tgz
\ No newline at end of file
+.FS
+[1]: https://wiki.ircnow.org/index.php?n=9.FNS
+[2]: http://felloff.net/usr/cinap_lenrek/execfs.tgz
+.FE