Editing Hide Overshare
From EMule Wiki
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to cut-n-paste the text into a text file and save it for later.
The administrator who locked it offered this explanation: site maintenance
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
''Hide Overshares'' is a feature designed to balance the upload of chunks within a file. It is especially useful for releasers who wish to spread the file in as few uploads as possible, but it could be useful for any responsible uploader. | ''Hide Overshares'' is a feature designed to balance the upload of chunks within a file. It is especially useful for releasers who wish to spread the file in as few uploads as possible, but it could be useful for any responsible uploader. | ||
− | == | + | == HideOS == |
Abbreviation : hideOS | Abbreviation : hideOS | ||
Line 11: | Line 11: | ||
If overshares is set to 1, each chunk will only be uploaded once until the file has been completely uploaded, and then the process restarts. | If overshares is set to 1, each chunk will only be uploaded once until the file has been completely uploaded, and then the process restarts. | ||
− | Note that the measure of whether a chunk is overshared is done | + | Note that the measure of whether a chunk is overshared is done compared to the least uploaded chunk. This means, on one hand, that an overshared chunk does not remain permanently hidden, but becomes visible again once the rest of the file has been uploaded. On the other hand, it means that if a file is only partially uploaded, it is not enough to make an overshared chunk visible, since the file has to be fully uploaded. |
− | Newer implementations of the feature ignore chunks that cannot be uploaded when looking for the least shared chunk. These include unavailable chunks from an incomplete file, and chunks the downloading clients already have. This is to ensure at least one chunk that can actually be uploaded would | + | Newer implementations of the feature ignore chunks that cannot be uploaded when looking for the least shared chunk. These include unavailable chunks from an incomplete file, and chunks the downloading clients already have. This is to ensure at least one chunk that can actually be uploaded would be visible. |
It simply preserves balance within the part of the file that can be uploaded, while allowing that part to become unbalanced compared to the part that cannot be uploaded. | It simply preserves balance within the part of the file that can be uploaded, while allowing that part to become unbalanced compared to the part that cannot be uploaded. | ||
The actual measurement of how many times a chunk has been uploaded is based on the spread bars information, so this feature cannot exist without spread bars. | The actual measurement of how many times a chunk has been uploaded is based on the spread bars information, so this feature cannot exist without spread bars. | ||
− | |||
− | |||
This feature was originally created by SlugFiller. | This feature was originally created by SlugFiller. | ||
Line 26: | Line 24: | ||
This strengthened version of Hide Overshares reveals only a single chunk to the user. When more than one chunk is sharable, a random chunk is chosen to be shown to the user. | This strengthened version of Hide Overshares reveals only a single chunk to the user. When more than one chunk is sharable, a random chunk is chosen to be shown to the user. | ||
− | + | It also ensures that each user is shown a different chunk, if possible, and when a chunk must be shown twice, the least-shared chunks get first priority. | |
− | + | This makes sure users are forced to download various parts of the file, so the end result is the file becoming shared in a balanced manner. It is more pre-emptive compared to standard Hide Overshares, since Hide Overshares only ensures balance after the file is uploaded partially, while Selective Chunk Sharing makes sure that the file is downloaded in a balanced manner from the start. | |
Like Hide Overshares, it ensures the revealed chunk can be uploaded to the downloading client. | Like Hide Overshares, it ensures the revealed chunk can be uploaded to the downloading client. | ||
Line 34: | Line 32: | ||
You should also look at [[Share Only the Need]] as well if you are planning on using HideOS. | You should also look at [[Share Only the Need]] as well if you are planning on using HideOS. | ||
− | [[ | + | [[category:features]][[Category:stullemulefeatures]][[Category:Morphxtfeatures]] |