OFF System 0.18.14 released

Quote:

---

What is OFF?

The Owner-Free Filesystem (or OFF) is a distributed filesystem in which everything is stored in reference to randomized data blocks, as opposed to a 1:1 copy of the original data being inserted. The creators of the Owner-free Filesystem have coined a new term to define the network: A brightnet. Nobody shares any copyrighted files, and therefore nobody needs to hide away.

How does it Work?

Files “inserted” into the OFF System are turned into randomized blocks of data through a process known as “multi-use encoding” (a way in which you give one object multiple meanings or representations). No data stored in the system is encrypted, compressed, or split into chunks, because it does not represent the data inserted to begin with. When storing a file, an appropriate number of blocks (containing randomly generated junk, 128KiB in size) are created and referenced to in a URL which contains the instructions needed to assemble these randomized blocks back into the form that it was prior to being stored. Without the URL, the blocks cannot be re-assembled into any "useful" form (for us humans). OFF blocks are arbitrary locator keys, similar to radio triangulation. The data is stored not as a block, but between several blocks which serve as locators for an indefinitely large number of other files.

---

Quote:

---

0.18.14

Toggle listctrl lines from the view menu caused a crash under GTK, the
wxw listcrtl sample seemed to have similar problems so the option is
disabled under linux for now.

Implemented a PtrMultimapH class which is similar to PtrMapH but allows
colliding hash keys.

The global srch results are now contained in a PtrMultiMapH object instead
of a linked list. The filehash is used as the map key.

Fixed bug where a paused download would not really be destroyed if cancelled
and would reappear on restart.

Search results for primary (user) srches are now stored in a PtrMultimapH
object. These use the first descriptor hash as a key - may change to the
filehash later.

Each local URL now has an entry in the global srch results list, this means
we don't need to access the local URLs whenever we receive a srch request
and the local urls can be looked up in the same map as the srch results.
However it does mean that list list needs to be kept updated as to the
protected and searchable status of the locals.

Srch records are now stored in PtrMap classes.

Srch result owner ids are now held in an std::set<int> instead of a
linked list.

Fixed another bug that could prevent download blocks being preserved when
the first hashmap tuple was missing.

Fixed occasional crasher in mapping of concatenated inserts.

CRITICAL: fixed crasher that affected only release builds with verbose
mode on. Many thanks go to the user who put several hours effort into
helping us find this shallow, yet hard to spot, bug.

Downloads where corruption is detected in the descriptor hash will
now be suspended with a warning in the status column. We'll handle this
more intelligently later.

New src files added:
ptr_map.cxx,
ptr_map.h (actually a version or two ago)

---

Projekt website
OFFSYSTEM: Owner Free File System
SourceForge.net: OFF System
wiki:
The OFFSystem - OFFWiki

Latest version:
SourceForge.net: Files

What the.... is that for ? explain ur stuff...

Quote:

---

Originally Posted by $SnoopDo2G$

What the.... is that for ?

---

It's a filesharing system in which you first create blocks out of files.
Those blocks are multiple-use encoded, so you can build different files out of them, it depends which description you use.

The advantage of this should be that you are allowed to download multiple-use blocks, as it's not sure what they are for, they have no copyright.
At least in theory by that way you can fetch those blocks without problem with the law and then get your warez out of those blocks locally.

The problem is that you don't only need the file to share itself, but you need storage for the blocks created from that file. Those blocks are usually 2x as big as the original file I think. It's a p2p program so you only get the speed of other present users serving the blocks you need. Also there has never been a trial if a multiple-use block is actually copyright-free. What you usually do is just using file A and file B and then mix them somehow into blockset C (basically). So is this block C actually copyright free? Some say yes, because neither copyright holder A nor B has the exclusive right. Others doubt if this is the ultimate solution. One is for sure, it's an interesting idea.

How many people are using this stuff ? coz it looks interesting only if load of people will be using it.