darkKlor

This is annoying.. I always tell people to refresh, wait 30 seconds, and refresh again. It shouldn't be necessary though. The indexer knows when it's complete, so it should be able to trigger the refresh.

Well, now I understand why a lot of users on my hub lose their share all the time. A lot of them own laptops with small internal drives, so they get 500GB or 1TB externals for all their stuff. I agree that it doesn't take much effort to re-add a folder, but it does mean people have to notice and take action, which is not as seamless as it could be. If the data has to be rehashed, and the share is large, then it could take half a day. The issues with remembering hash data for inaccessible files are that: - the client must check if a root folder in the share exists when it creates a file list from the hash data, and - the client must check if a file exists when a TTH root is requested via search, and - the hash data may bloat over time with unnecessary data. The refresh file list command should take care of the latter issue. The first two add a bit of overhead, but probably not much.

I see this issue too with the new version. The Annoucer Bot on my hub sends a message on connection with the last 5 releases, but Apex 1.2.2 only detects the first magnet link. The other four are displayed as plain text. It was fine on 1.2.1.