Signed content.json publish failed (if the changed zite are larger than 10MB)

### Step 1: Please describe your environment

* ZeroNet version: 0.6.5 (rev 3864)
* Operating system: Windows 10
* Web browser: Firefox 67.0
* Tor status: always
* Opened port: no
* Special configuration: Proxy forTracker connections goes tourgh Tor

### The problem:

If the existing seeded by other users zite are under 10MB. And i completly update the zite. All files get updated. And its larger than 10MB. Content.json if i set up a larger limit than 10MB are accepted. And Signed. But when i try publish the zite are not getting updated. And when i try download the zite the outdated files are downloaded from another users. And its impossible to get the new usrs the updated files. Zeronet know the zite limite are highter when i try domwnload the zite. But the outdated content.json and files are downloaded from another users.The connection are OK. The proplem was another users client not accept the update. Under 10MB everything works fine.

#### Steps to reproduce:

1. Make a zite with more files under 10MB (make shure its seeded many user important)
2. Update all files this time more largen than 10MB (Try 50MB)
3. Set up the limit
4. Sign content.json file
5. Publish the file

#### Observed Results:

The outdated content.json and files are downloaded. ZeroNet accepted the highter zite limit when i tryed download the zite.But the zite are never get updated.

#### Expected Results:

Content.json sign are OK. Content publish failed error MSG. If i make a test download the old files are downloaded and never updated!

Reproduce the issue using a zite that is first under 10MB and then updated beyond 10MB, following the listed signing, limit, and publish steps. Trace the content.json publish and peer download paths to determine why other users continue serving the old content. Done means an oversized signed update is accepted by peers and new downloads receive the updated files.

Written by the indexing model from the issue text.