OFF SYSTEM Store all digital content and allow only the people authorized to use it
Download

OFF SYSTEM Ranking & Summary

OFF SYSTEM Tags

store content secure secure storage content storage online storage

OFF SYSTEM Description

Store all digital content and allow only the people authorized to use it The OFFSYSTEM (Owner Free File System) for content storage and retrieval, lets you store all digital content and allows only the people authorized to use it to do so.The OFF System is the proof of concept for "bright nets" and will allow anyone to easily and securely share digital data legally.As in any local File System, you can store and retrieve files. In the OFFSYSTEM is that done online, which means, any user having acess to the internet, can store or upload and download own, foreign or public files. All files, which you upload to the OFFSYSTEM, are cutted into a kind of small pieces, bits and bytes which are then stored by peer-to-peer-technology into the machines of other users.NOTE: OFFSYSTEM is licensed and distributed under an OSI-Approved Open Source License. What's New in This Release: CRITICAL: · Fixed bug that could cause corrupt inserts if mis-sized block files were chosen as randomisers. These blocks are now checked and discarded just as they are during retrieve. · Fixed bug that resulted in a corrupt insert if regenerating a block failed when repairing an insert from the source file. ADDED: · The web interface shutdown is now disabled by default (as we assume most people will not use it) It can be enabled with the checkbox in Options->Network or with "toggle_web_shutdown" under command line. OFF will also return a page to the browser saying that the client is closing, or that web shutdown is disabled. · The Local URLs context menu now contains an option to "Disperse Descriptors Only" which disperses the descriptors and any hashmap blocks, but not the file blocks. · Added an option to slow the filling of the bucket for newer nodes, the idea is to reduce the amount of bandwidth used when the bucket radius is large. This is enabled by a checkbox in the Behaviour tab. The only current effect is to advertise the TBR instead of the actual bucket radius if it is the smaller of the two. Other effects will be added if this turns out to be insufficient, but it drastically reduces the number of block pushes received. The option defaults to off for existing nodes but is turned on when the startup wizard is run for new nodes. IMPROVEMENTS: · Implemented a manually buffered file class for reading ascii config file, to reduce disk accesses when reading large files. This does not make much difference on a fast disk, but seemed to speed up reading on slower or external drives. Only currently used for the blockcache database file. · Nodes are now written to the known_nodes.txt file in order of online time, this means that on startup the nodes that have been online the longest will get checked first (on the assumption that these are the ones most likely to still be contactable). This speeds up connecting to nodes on startup especially for large nodelists. FIXES: · Fixed bug where disperse pushes were miscounted when a new disperse push upgraded an existing push block that was in the active or busy-wait queues. · Fixed bug where a node would not be added to the contactable nodes list if it came online, did not ping back (i.e. the first node was walled) and no pool cnxn was added. · Fixed bug where nodes with no pool cnxn would not be removed from the contactable nodes list on some connection fails. · Fixed bug where a node would become a "zombie" if it was firewalled, had no pool cnxn and came online with a connection that was not a ping. In this case it would sit in the nodelist with status "online - firewall unchecked" and not every go offline. The fix was to schedule a pingback for any connection when the firewall status was unchecked, previously this was done only for ping connections. · Fixed bug in 2way comms that caused "time out on non pool cnxn" errors. · Fixed bug in 2way srches that could occasionally cause bogus results to appear in the srch tab when no srches had been started by the user. CHANGES: · The max allowed active requests for a download is now 10% of the total number of blocks needed instead of the remaining blocks needed. · If the "Trim Now" button is pressed, the max cache size is no longer checked and the cache will be trimmed even if it is within the limit (but not if the bucket is not full). · Increased the limit at which pushes, block reqs, etc start from 20 nodes to 40 nodes. 20 was a lot when the limit was set.

OFF SYSTEM Related Software