Feature Request: Semi-Hidden Things

Name
Email
Subject
Comment *
File	Select/drop/paste files here
* = required field	[▶ Show post options & limits] Confused? See the FAQ.

Embed	(replaces files and can be used instead)
Options	Do not bump (you can also write sage in the email field) Spoiler images (this replaces the thumbnails of your images with question marks)
Password	(For file and post deletion.)
Allowed file types:jpg, jpeg, gif, png, webm, mp4, swf, pdf Max filesize is 12 MB. Max image dimensions are 10000 x 10000. You may upload 5 per post.

File: 1470869323929.jpg (558.08 KB, 1280x800, 8:5, 135403.jpg)

Feature Request: Semi-Hidden Things Anonymous 08/10/16 (Wed) 22:48:43 899ce1 No.3456

The blacklist as it is seems to be more about filtering out blindly imported files than controlling your own files. There are two extensions of the hiding idea in general that I'd love to see.

1) Dark-grey list. :P Rather than forbidding the display of a file with a certain tag/namespace altogether, the ability to have it be hidden UNLESS it's explicitly referenced in the search. (With or without autocomplete enabled for the given tag/namespace,)

2) The ability to disable autocomplete on certain namespaces, but without actually hiding anything. As an example, I use wallhaven:* to store the id numbers of images found on that site, but these ids are not something autocomplete would help with, and it only creates clutter to have them show up there.

Anonymous 08/11/16 (Thu) 22:44:44 682d7e No.3464

As far as I'm concerned the blacklist only filters tags, not files with a certain tags.

I tried to tag my images with rating:explicit and then blacklist that, but those files were still there.

I haven't used Hydrus in 5 weeks tho since I'm on vacation, maybe I'm wrong.

hydrus_dev ## Board Owner 08/12/16 (Fri) 21:22:50 eaa466 No.3469

File: 1471036971086.jpg (1.8 MB, 2000x1476, 500:369, b7dd80fc5791d6ac4bbad25a02….jpg)

As far as I can figure, there's no technically good and reliable way to hide nsfw (or otherwise private) tags or files from a shared file domain. There are too many complicated ways that undesired words or thumbnails can pop up when you don't want them.

So, my current plan is to expand the 'local files' domain into multiple editable domains. Having completely separate partitions means all my tag autocomplete counting code and general searching code can guarantee stuff in the 'nsfw' partition won't pop up on a 'sfw' search.

This project will be on the next 'big things to work on next' poll, which will come after suggested tags and a faster dupe search algorithm are done. Please look out for it then!

For now, if this is very important for you, I recommend you run multiple separate clients, one for each distinct file domain you want to have.

Anonymous 08/14/16 (Sun) 03:56:05 fb2f28 No.3487

I can live with a wait. Good to know there's something in the pipeline.

It's not SFW vs NSFW that I would want that sort of hiding for, though, so much as for working on filtering in batches over time. After pulling things from subscriptions, I go over to make sure unwanted junk didn't get in, but unless I'm very very sure, I try not to full-on delete things on a first pass, and just mark them for closer inspection before complete removal. Until I've decided if such probationary files stay or go, I don't want them popping up unless I'm specifically going through them, but the second client solution doesn't really make sense for that, without taking i ta pretty big step further and using a separate copy for all subscriptions, and then exporting/importing when complete, but… damn. Yup, I can live with the wait. :P

Anonymous 08/15/16 (Mon) 16:23:48 e90f0e No.3501

>>3469

For those of us who use multiple clients. I remember a while back you said that you were thinking about getting the db fully portable so we could maintain a single installation of hydrus and use command line switches to point to the right db when starting the program.

I thought that was a really good idea, even if it's suppose to be replaced later by the multiple domains idea, because updating many clients every Wednesday is a bit of a pain.

Anyway, my question is, is this still in the works? Or have you completely scraped the idea in favor of the multiple domains idea?

hydrus_dev ## Board Owner 08/16/16 (Tue) 16:47:02 eaa466 No.3510

File: 1471366022493.jpg (126.82 KB, 525x700, 3:4, 705baf17b081aababa8f24ce35….jpg)

>>3501

Both are in the works. They are both ultimately simple changes but will require extensive background code cleanup before I can flick the big switch. The multiple-dbs-with-one install is simpler and will come quicker.