Line 1: |
Line 1: |
| + | <noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> |
| + | |
| ==Introduction== | | ==Introduction== |
| | | |
Line 22: |
Line 24: |
| # Various Wireless operating modes other than mesh and connected to external AP. In particular I want to add an ad-hoc wireless mode for compatibility with how I wish to use this system on regular PCs and laptops and a neat mode where the system acts as its own wireless access point with all DNS entries pointing to the web interface, so these devices can be used to serve up information and access to the system to many users at once that don't themselves have a copy of the software. also to reduce network congestion an offline mode that does not broadcast the system as available for syncup or sync to other hosts should be available (but it should still map out current users on the network so we can view their wiki pages etc) that way they can decide when they want to do the transfers and possibly ease up writes to the flash. | | # Various Wireless operating modes other than mesh and connected to external AP. In particular I want to add an ad-hoc wireless mode for compatibility with how I wish to use this system on regular PCs and laptops and a neat mode where the system acts as its own wireless access point with all DNS entries pointing to the web interface, so these devices can be used to serve up information and access to the system to many users at once that don't themselves have a copy of the software. also to reduce network congestion an offline mode that does not broadcast the system as available for syncup or sync to other hosts should be available (but it should still map out current users on the network so we can view their wiki pages etc) that way they can decide when they want to do the transfers and possibly ease up writes to the flash. |
| # If I can figure out how I would like to implement some form of private encrypted electronic mail and a tool for managing those accounts on each node. | | # If I can figure out how I would like to implement some form of private encrypted electronic mail and a tool for managing those accounts on each node. |
− | # Possibly move to the telepathy system rather than my crude UDP broadcast system and integrate this into sugar so it can all show up on the network screen (Ideally I would like either an icon to show up that allows the browse utility to be opened to that host or to be able to hover over the hosts XO icon and see a list of exported web services on that machine and be able to click direct to each one) I would also like to add an activity Icon to open up direct to the localhost webpage. | + | # Possibly move to the telepathy system rather than my crude UDP broadcast system and integrate this into sugar so it can all show up on the network screen (Ideally I would like either an icon to show up that allows the browse utility to be opened to that host or to be able to hover over the hosts XO icon and see a list of exported web services on that machine and be able to click direct to each one) I would also like to add an activity Icon to open up direct to the localhost web page. |
− | | |
− | | |
− | Other than that I want to fine tune the existing configuration and find a much more efficient way of syncing the news spools than the heavy handed and very simplistic suck package, even if that means writing my own tool to do so. (avoiding all temporary files and writes to the flash other than transmitting or recieving articles we do not yet have, or have expired)
| |
| | | |
− | I also will move from the tradspool storage format (lots of files and directories) to the CNFS news filesystem which is a single file of arbitrary size managed by INN that operates like a ring buffer. once it will write past the end of the file instead of growing it writes to the beginning, overwriting the oldest articles. | + | * Other than that I want to fine tune the existing configuration and find a much more efficient way of syncing the news spools than the heavy handed and very simplistic suck package, even if that means writing my own tool to do so. (avoiding all temporary files and writes to the flash other than transmitting or receiving articles we do not yet have, or have expired) |
| + | * I also will move from the tradspool storage format (lots of files and directories) to the CNFS news file system which is a single file of arbitrary size managed by INN that operates like a ring buffer. once it will write past the end of the file instead of growing it writes to the beginning, overwriting the oldest articles. |
| + | * Other than all of that, I need to, of course, write documentation once the design is more solid. |
| | | |
− | other than all of that I need to of course write documentation once the design is more solid.
| |
| ==Feedback== | | ==Feedback== |
| * I downloaded tn. I got in yesterday evening and posted one news item. But going to the neighborhood I get a page load error trying to connect to Bilbo's news or wiki: 'The connection was refused when attempting to contact nnn.nnn.nnn.nnn.' Seems like a certificate/security problem of some sort. --[[User:FGrose|FGrose]] 15:54, 26 June 2009 (UTC) | | * I downloaded tn. I got in yesterday evening and posted one news item. But going to the neighborhood I get a page load error trying to connect to Bilbo's news or wiki: 'The connection was refused when attempting to contact nnn.nnn.nnn.nnn.' Seems like a certificate/security problem of some sort. --[[User:FGrose|FGrose]] 15:54, 26 June 2009 (UTC) |