>>22179
>>22191
No worries, and thanks for the feedback. Actual feedback on real-world workflows is always useful. Glad it is working better now.
>>22180
Glad you like the program!
>>22181
How are you generating a random filename? I half-remember adding this somewhere but cannot find it now.
Btw just as a side thing, if you are worryied about fingerprinting, the hydrus sha256 filenames are the same for all hydrus users (they are based only on file byte content, no salt or anything), so the info that leaks, if someone recognises your filenames, is that you are
a hydrus user (or an 8chan user, it uses the same filenames), not that you are a particular user.
>>22184
Great idea, I will add this to the options. Can you also check out
help->debug->profiling? This wasn't originally my code, but I think if you turn that mode on and do some test searches, I think the profiling will catch it. We can see what the hell is taking so long.
>>22185
Although I don't like the idea, if you are desperate and just want to paste some ephemeral example of a 28MB png or something to discord, you should have the option to copy a 1024x1024 bitmap under 'share->copy source lookup bitmap'.
>>22192
>>22193
>>22194
>>22195
I didn't know myself, either (I didn't write this code originally), but yeah it does a background right-click on the current page and then harvests that menu for actions to fire. So, if you have a selection (maybe by ctrl+a or something), you can now type 'my files' and you'll get 'from my files (delete)'. On any empty selection you might be able to typing 'in' for 'inbox (select/remove)' and such. A bit dangerous, and basically prototype, which is why it was behind advanced mode before.
Let me know if and how you use it, and what if anything should be filtered out. Sounds like the first step is to label it better in the UI.
>>22196
There is no good solution for this right, now, I'm sorry to say. In future we'll have clients dialing into each other via the Client API and this will be possible, but for now you have to go with a jank solution to do this sort of thing.
Best answer at the moment, I think, is to have something like freefilesync sync the database out of the central network store to a local location with a local hydrus install, run the client there, and then commit back if you make changes.
>>22200
Pic related in one way or another, it seems. Many such cases.