Share size

[Ophite 0]

When adding files to the share after a /refresh or restart (and after they have hashed), the share size posted to the hub isn't updated on an NMDC hub until the client is reloaded or you reconnect to the hub.

I'm not sure if that's a bug as such, or simply an intended oversight to avoid info-flooding NMDC hubs, but felt you should be aware of the behaviour because another /refresh (after the hashing, and after the filelist has actually been updated and the files are available) still doesn't update the value.

Disconnecting from the hub and reconnecting does seem to update the value.

I haven't tested with ADC yet.

[Big Muscle 1]

It depends on hub whether it accepts your new info immediately. It can accept it but sends it to all users (including you) after some time.

[mcravener 0]

A bit irritating yes, but it's not a new bug, and perhaps not even a bug as Big Muscle says but dependent on the hubsoft settings.

[Lee 84]

It depends on hub whether it accepts your new info immediately. It can accept it but sends it to all users (including you) after some time.

This can't be right, since when not connected to any hubs you must refresh multiple times to display the correct share size still.

It seems like after hashing, it simply doesn't recount the share size.

[Big Muscle 1]

I have never had such problems. It always update my share size immediately.

[Lotus 0]

This can't be right, since when not connected to any hubs you must refresh multiple times to display the correct share size still.

It seems like after hashing, it simply doesn't recount the share size.

Do you mean: start SDC, disconnect all hubs, add new files to share, wait until hashing is complete, refresh file list, then connect to a new hub and your share size is wrong ?!?

But if you are connected to a hub, BM is right, most of hubs(ofts) implements a sort of flood-protection, ignoring your new MyInfo strings if they are too fast. The DC protocol states that when a myinfo changes the hub must send the new myinfo to all the users to keep them up to date. But doing so opens doors to flood as you may connect with a bot and send countless myinfo... and the hub must send each of them to all users. So, some hubs kicks you if you change myinfo too fast, most of them simply ignore you or wait for a certain amount of time expecting more myinfo changes, and only after an interval of time send to all users your last myinfo.

The easy solution if you want to make your new shared files accessible right away is to simply reconnect... or perhaps to tell your friend(s) to reconnect himself... but I'm not so sure about that...