Difference between revisions of "Fake"
(ed2k hash history razorback2) |
m (typo) |
||
| Line 5: | Line 5: | ||
Sadly, fakes are hard to detect and the [[FAQ_ed2k|ed2k]] network provides little (in some aspects it is even correct to say ''none'') protection against fakes. | Sadly, fakes are hard to detect and the [[FAQ_ed2k|ed2k]] network provides little (in some aspects it is even correct to say ''none'') protection against fakes. | ||
| − | Anyway, [[aMule]] provides two ways to detect | + | Anyway, [[aMule]] provides two ways to detect these fake files: |
#By taking a look at the [[comment]]s submitted by other [[client]]s. | #By taking a look at the [[comment]]s submitted by other [[client]]s. | ||
#By using one of the following resources (right-click on the download -> FakeCheck): | #By using one of the following resources (right-click on the download -> FakeCheck): | ||
Revision as of 01:59, 22 January 2007
Fake files are those which are intended to look like a file, but are in fact something else or just nothing at all.
Sadly, fakes are hard to detect and the ed2k network provides little (in some aspects it is even correct to say none) protection against fakes.
Anyway, aMule provides two ways to detect these fake files:
- By taking a look at the comments submitted by other clients.
- By using one of the following resources (right-click on the download -> FakeCheck):
- http://donkeyfakes.gambri.net (closed October 2005)
- http://www.jugle.net
As a tip, it is commonly useful to take a look at the download's details (right-click on the download -> Show file details) and see if someone has set some filename which refers to some different content. If such is the case, you might suspect if the real content is what you assume it is, what that other client has set as it's filename or none of those.
Tip 2, you can check the history of a file on *http://stats.razorback2.com/ed2khistory to see if the file release date is feasible or if file names are correct or consistent.
Do not confuse fake with corrupt.
