>>11929
Hey, this looks fantastic!
Yeah, I only have basic tag support in atm. Wildcard searches are actually dealt with in hydrus with a different search object, so what is being searched for there is literally the asterisk character rather than 'anything'. Namespace searches are the same–they use different code to run faster. It is unusual that 'namespace:' would work as a fixed tag but the same negation wouldn't, but this is an edge case anyway that isn't expected to ever run. I expect to add namespace and wildcard searches to the Client API in my future weekly work.
I will be adding more system search predicates as well.
Supporting tag autocomplete search sounds good as another extension. Perhaps until then you could have a 'favourites' list or similar to make quick-entry easier?
Unfortunately, hydrus does not support paginated searches like a booru would. It returns everything in one go, without sorting. If you have a technical limit to the number of thumbs you can display, I recommend you break the results list into chunks of your own preferred page size. Sorting results is unfortunately not (yet) possible at the db level, so you will have to do it yourself using data from the file_metadata calls.
Please keep me updated on how you get on here.
>>11932
I can't speak confidently for exactly how his system works, but yeah, you would have to have the client on for this to work, and maybe set up NAT port forwarding or use hydrus's in-built UPnP port forwarding, and then point your account settings in his phone app at either your fixed IP address and port or get yourself a no-ip.org kind of deal, like I do for the PTR.