No Release Tomorrow!

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: 2c64f7ee1f92938⋯.gif (1.11 MB, 288x208, 18:13, 2c64f7ee1f92938ad4823bdab1….gif)

No Release Tomorrow! hydrus_dev ## Board Owner 02/15/17 (Wed) 01:14:01 acb6c9 No.5157

I had a great week with a lot of work, but the network rewrite has proved much bigger than I thought. I am completely neck deep in it right now. There will be no release tomorrow.

I am 80% confident I will have everything ready by Feb 22nd. As well as the reduced and smarter network data usage, there will be improvements to how bandwidth rules and account permissions are managed.

Anonymous 02/16/17 (Thu) 06:52:51 efbb7e No.5164

File: fdd4b339a684dd9⋯.jpg (37.17 KB, 382x462, 191:231, 3c9844233197e64596a4143a6e….jpg)

Can't wait!

Anonymous 02/16/17 (Thu) 10:55:36 96fa24 No.5167

Thanks doc.

Take as long as you need.

P.S. I was looking over some duplicate pairs in the prototype dupe search and I thought of something, just in case it's not already on your mind - a "merge group/file B's tags into group/file A's tags and then delete group/file B" function is going to be pretty much necessary for sorting purposes. Also in addition to resolution, filetype, etc, a handy way to sort dupes would be by date added to database.

Anonymous 02/17/17 (Fri) 01:22:49 ffd8ae No.5169

File: 83184903ee3bccb⋯.jpg (175.04 KB, 517x630, 517:630, 2bd07292e818475f42995919cf….jpg)

Keep it up man. Thanks for your hard work.

hydrus_dev ## Board Owner 02/18/17 (Sat) 19:51:53 d849c7 No.5176

>>5167

Thanks. Yeah, this is the hope. I want to balance several process actions with a simple interface. I'd like there to be several buttons on either side, with one for instance being exactly as you describe–copy all tags/ratings from A to B, and then delete A. Others would probably be 'merge tags/ratings' and 'A>B, delete A' and 'A>B, do nothing'. And then a bunch for B>A on the other side.

I'd also like to 'help' the user by saying 'A has higher resolution' and so on, although we may have to revisit it if there are many false positives. File size might be helpful as well, but I'll have to filter out png vs jpg for instance.

Anonymous 02/20/17 (Mon) 00:11:33 226f78 No.5180

>>5176

> I'd also like to 'help' the user by saying 'A has higher resolution' and so on, although we may have to revisit it if there are many false positives.

AFAIK, there will be.

What you can usually do with reasonable reliability is eliminate the images that have been more lossily compressed. You can do this by running them through some of the better modern codecs (BPG, WEBP or something like that).

A decision between an original image and one with a more or less obvious effect or watermark or whatever applied and all these things is probably not something you can realistically program at this point.

I don't think there is any realistic method other than what many *boorus do: Let registered human users tag image versions as better as others and kinda share that information while letting an editor resolve contradictory reports.

Anonymous 02/20/17 (Mon) 00:30:24 8d88ba No.5182

>>5180

PS: Sharing this information is also the main mechanism by which you can somewhat reliably keep variants of images safe: Mark these as known alternatives to the other related image sets.

[At some point we may wish this all was running on Apache Spark backed in other DBs rather than SQLite, but hey, it's all good fun…]