I just reviewed the official documentation and it appears to confirm this, but it feels like such a glaring functional omission I have to ask again:
rscollection files - index of individual files that make up a collection, great. You can open it up, select which of the complete index you want, click 'go', and it fires off n-independent file requests in your typical leech queue.
Here's the gap: That's it. It's a one-way map to file links, but otherwise there is no kind of capability to measure status against the full collection. If there were 500 files in a collection, you have to wait and manually scan your inqueue to ensure you've got every file, then have to manually eyeball filesizes, filenames, etc and validate you've got a complete collection. There is no RS functionality that does so.
Is this true? Doesn't it seem like a partial solution to anyone else? My use-case is the lustomic collection. Every comic consisting of individual pages / pics. That's a shit-tonne of files. You're practically guaranteed to snapshot off thinking you're done and go back later, find out you've seeded bad copies to others...
Need help fixing my retroshare, Its stuck at "30% (Loading networkstatus consensus)" does anyone have a fix for it?
I am having the same problem.
"Loading networkstatus consensus" seems to be a part of starting up tor.
On the internet I found a few mentions that this might happen when one uses an old tor version.
Since there was no update on retroshare for quite a while I am wondering if this only happens when using RS with tor built in?
Anyone else experiencing this?
Are there nightly builds of retroshare that might be newer then the version 0.6.7a?
I am running RS on linux...
