Zeronet: [Question] How to manually seed big file

[DaniellMesquita]

I uploaded this video to KopyKate on a proxy, but the upload failed and video listed.
I manually renamed video and moved to my user folder, but on my ZeroNet it yet shows 0 peers and seed button doesn't works, even I having the file. How to manually pin/seed it?

[imachug]

Try changing data.json of your user directory -- it should contain the old filename. After you change it, sign&publish your content.json and try pressing Seed again.

[DaniellMesquita]

The filename is same, but republish for enable seeding is a good idea.
Thanks!

[DaniellMesquita]

I'll enable multiuser then login in the account where I posted the video.

[vRobM]

what if someone else posted it and left. You wanted it, but couldn't find any peers, so you go to clearnet, search engine the filename and find it, then replace it in the local filesystem.
How do we tell ZeroNet that it is now complete if we don't own the site or the file posting?

[satoshisfriendz]

Yeah how?

[DaniellMesquita]

Only who posted the video can manually seed it, by signing its content.json file

[Balancer]

Only who posted the video can manually seed it, by signing its content.json file

https://github.com/HelloZeroNet/ZeroNet/issues/1617#issuecomment-421758128

Often nothing helps. I don't know how to fight it. If I put my file with the same name manually and try to publish it, it even on the machine where the publication was, trying to download the file from the network (where it is not), and not to distribute my local file.

[HelloZeroNet]

There is a Check files option at the site on ZeroHello. If you press that, then it should check all files on your hdd

[Balancer]

There is a Check files option at the site on ZeroHello.

I know this option. It allows you to download newly corrupted files. But it does not allow you to connect to the distribution of the correct file, if ZeroNet believes that this file has not been downloaded. I don't know how ZeroNet thinks the file is already downloaded and how It isn't, but to fix this error, you have to repeatedly republish the file from different computers under different names :)