spoilers

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 8 MB. Max image dimensions are 10000 x 10000. You may upload 1 per post.

File: 1428788757499.png (17.72 KB, 320x320, 1:1, 1418568589441.png)

spoilers Anonymous 04/11/15 (Sat) 21:45:57 No.622

Had an Idea I would REALLY like to see, spoilers

There should be an option to set spoiler covers on certain tags, so any image with that tag, when browsing your hydrus catalog, you will only see a spoiler tag. There should be options to make different spoiler lists, for different tags, potentially requiring multiple tags for certain spoilers to pop up, and make them look different, so perhaps you have a list for "spoilers" that pops up on any images with the spoiler tag, and another for "nsfw" that pops up over anything with the nsfw or lewd tags probably needs a way to display multiple spoiler lists

I don't always want to look at porn when browsing my galleries lol

This feature would be an enormous help, I hope its not too hard to impliment

Anonymous 04/12/15 (Sun) 00:40:57 No.623

You can solve this issue in one of two ways:

Tag all porn with a common tag (eg "porn", "nsfw", and/or "hentai"), make the default session filter to -nsfw, -porn, -hentai, etc.
-or-
Run a separate instance of hydrus for your porn collection.

I do both. I have a collection of pictures I fap to, which I have a separate copy of hydrus dedicated to. In my main picture database, there are pictures that I don't necessarily want to show the world, but I don't intend to fap to them. I tag them as nsfw so they may be easily filtered out.

Sorry, but I think a spoiler feature would just get in the way and be otherwise useless.

Anonymous 04/12/15 (Sun) 00:50:19 No.624

>>623
I use a seperate instance for my fap collection, but there are items in the main collection that are nsfw as well

last time i tried entering -nsfw as a tag and it didnt work, lemme try again

Anonymous 04/12/15 (Sun) 00:54:34 No.625

nevermind, its working again, no idea what went wrong, old version error maybe?

*shrug*

Thanks, that works just fine

hydrus_dev ## Board Owner 04/14/15 (Tue) 19:19:06 No.635

File: 1429039145976.gif (2.76 MB, 427x220, 427:220, b20b79e46d397fec15f031c98d….gif)

>>622
>>623

At the moment, I am advising people to make different instances of hydrus in these cases. If there are no private images on your 'sfw' client, then it doesn't matter how much someone looks over your shoulder, or how general your searches are, you won't be seeing/showing what you don't want to.

I am generally open to the idea of adding 'sfw' modes, but I can't figure out a way to make it both comprehensive (i.e. no slip ups, no false positives or negatives), and also convenient and fast enough to work in real time. For instance, even if I spoiler/hide a set of images, their tags will still show up in the autocomplete tags dropdown. I can try to make a system to hide 'bad' tags, but that's a rabbit hole that'll add lag and likely be a pain in the ass for the user to maintain.

I think of it like some regime's internet censorship, I guess? No matter how much some bureaucrats try to block porn/dissent, it'll always get through, by accident if nothing else. The best way to guarantee a pure search is by having a pure db, I think.

If running with -nsfw doesn't work for you, I've designed hydrus to be able to work well as multiple instances. Please let me know if you need any help setting it up.

Anonymous 04/15/15 (Wed) 01:56:32 No.637

File: 1429062992797.jpg (18.94 KB, 413x300, 413:300, 40215667_p2.jpg)

>>635
With the other posters mentioned -nsfw option I should be fine, just have to set it up to default to having those on all the time, going to have to look at how to do that

I have my unrelated porn seperate in another instance (I really need to update lol, its like, 5 updates behind), but for purposes of the desu repo, ALL desu goes in, so there's even some unpleasant stuff i want to filter thats not porn, but, that - function should do the trick, i must have entered something wrong in an earlier instance. The tags being visible even if the image isn't doesn't seem like it would be a big inconvenience however, if you did end up implementing something like that

unrelated, but my crashing error when full screen tagging went away, seems to be working fluidly now, still need to test with page up and down (anyway to add an archive button next to the delete button perhaps? or am I forgetting a hotkey)

hydrus_dev ## Board Owner 04/19/15 (Sun) 22:05:09 No.647

File: 1429481109040.jpg (128.67 KB, 896x672, 4:3, a65ed179954bbd6597ba6fd2f8….jpg)

>>637

I think adding a simple file censorship system should be doable. I will think about it more.

I fixed a subtle but critical initialisation bug in the fullscreen code a week or so ago–that is probably what fixed your crashes.

Also, I've added a bunch of toolbar buttons for v154, and I want to copy them to the manage tags dialog so you can do lots of things with it open, and in a clean way. Maybe not this week, but certainly by v155.