File System Addition.
The insertion of files needs to have a category flag system in place with it with at least the initial first few flags being a forced issue related to being able to insert the files. The file system in many of the P2P systems lacks a structure beyond that of a massive root directory which is dumped into and a total mess. This can be handled with a couple bytes to allow for flagging the files for basic organization with a hard coded structure, then maybe some additional space for user breakdowns. The benefit I can see of this would be to bring essentially a few directories into the file system and allow for the break down of the file listings into a more specific chunks suited to the category being sought. With even a 100,000 files the approach of a root directory catch all is easy enough to work with. When it approaches 20 million or 100 million files given the exchange of file data I have seen taking place and the time this takes it will becomes much more of a problematic issue. Even with the large news servers streaming full it can take an hour or two for a header list to come in and Free-Net does not make that process something that can be streamed direct at high speed. a Two ? Byte flag system would allow breaking those 16 bits into an initial category system to allow for some organization. With the use of a hard coded breakdown of that the forcing of the initial organization could be made. The debate would be establishing the hard code structure as to be able to make use of this and once implemented it would serve as permanent with in Free-Net. For it to be universally used the first part does have to be hard coded into the system at a core level To start off the structuring of it the initial debate would be in the breakdown of the bit pattern. To work with a possible idea for the bit mask breakdown is this: 1bits/3bit /4bits/4bits/ 1bits/3bit/ for a total of 16 bits/2 bytes Flags Description Flags First 4 Bits ? used as 1/1/2 First bit being a flag for System File Second Bit Default Too Lazy to say what the file is Third Bit being a flag for essentially Hidden File or Not like on a HD file system Fourth Bit being Personal or not Second 4 Bits being 16 category choices..... FreeNet-Internal, Video, Audio, Book, Game, Application, Picture, OS, News, Sit-Rep, Other, Misc .... Personal Third Set of 4 Bits a Secondary Description Classification Educational, Entertainment, Informative, Reference Material, Porn, Urgent, Misc, ...... Personal The option with the third set would be hard coding a sub category for each of the first choice, or coming up with a generalized list of 16 items that would fill the general need for a secondary descriptor for the file describing the first level. Fourth Set of Bits potentially being broken into 3/1 3 bits being a Content Rating 1 being N/A and the remaining 7 choices a content rating scale as to age 2 for all ages to 8 being adult 1 bit being Descriptor is Locked if its a public file this is by a polling vote. If its a private file this is by owner .................................................. This adds a step to the insertion procedure and adds an additional 2 bytes to the file key length. With the use of a Hard Coded System at the very core level this become something that can be used universally used and can have some level of being enforced. Failure to describe the file results it in being dumped in the ?I Was Too Lazy DIR? The Comments, Keywords, and so forth in the file insertion process that require a user to actually type in various data is by its very nature something that people will by pass in the process as it does take time and more importantly thought. Hard Coding a set of flags that function on a few radio button choices would result in better usage IMO as it is faster and it does not take much thought. The benefit of this system is one that benefits all !!!! First Benefit: Bandwidth Savings and easing of congestion is one factor this saves, in terms of there being a file storage system present within FreeNet this gives at least some structure to it. A Person looking for reference materials with in the system are then getting only those file lists. Essentially Some one looking for a Video File likely has no interest in the latest Operating System files that are available. This structure allows for the overhead of all those elements in a file list to be removed from the transmissions till called upon. Second Benefit: Better Presentation !!! Every System that has ever been used that provides for a singular list function for all services or provided what ever leads to the use of computer native sort organization attempts to bring a form of order and grouping to it. Structuring the file system with a hard coded category function in this fashion allows for better presentation along with better system resource use. The Fight to be the first on the list seems to be present in all public list functions and in a file system this happens as well, be this intentional or by nature of the chosen naming conventions. The nature of the Freenet is not traceable and non removable Data, a means to filter that then at least must be present. The Internet its self is about being able to put on a set of rose colored glass's and not see reality. This allows for the opening of the file sharing programs to be one that allows for a more PG view on the entire contents.
