802396 have been cut.
@Sopel, are you still working on this pack please?
Yes, someday it will be done - it's not like people are fighting over this, right?
And is this someday any close to arriving?
Kidding apart, I would imagine that at least some of the images have been cut elsewhere by now, so do check if they're still needed before cutting them
Well, you got me, I misjudged my time again and what's more, I completely forgot about it, I'm going to unassign myself now
Real life is piling up, I've learned my lesson to not go all gung-ho on the requests so no I don't take any and just upload them when I finish them, I hope this is the last time you have to remind me, sorry mons
Oh, I completely understand - believe you me. For example, I wish I had a spare day or two to cut all the lovely pending requests we have, sad as that may appear!
When the site is redesigned, I'm giving some serious thought to not allowing teampack and mixpack requests as they're too time-consuming for cutters to take on and cutters end up, as in your case, putting them off until they end up forgetting all about them. It's much easier for cutters to find the time to cut a handful of pending individual requests at a time of their choosing, rather than taking on a bigger pack
From my part the priorities look something like this - normal, singular requests are more important because a) most of them are easy and b) you're minimizing the size/rate of another mixpacks. Singular is the moving traffic, packs are the clog that isn't moving anywhere so they can be finished anytime. The only problem with that is how long the packs sit there - if someone would like to cut out a request from 2016 it's most likely already is obsolete.
My point exactly. I'm just sad that somebody will have taken the time and trouble to collect all those images, most of which would fill a gap in the megapack, without ever having seen the fruit of their work.
I'm excited about the redesign I still think that a system in which while uploading a pack you'd have to simply choose ID of the faces inside or even better - link each photo to the ID. Then if someone makes another request with that ID it would be one of these options a) redirect to the already requested pack b) when the individual would be cut a photo from the pack would be automatically removed c) the new upload would be added to the pack as another version for that ID
It's still very much in the pipeline and not particularly near to release tbph but that's not too far off the envisaged final product.
It would be a self-controlling system, cutting down on the redundant requests. Or (came to me while writing) a system in which you upload a pack and link them to their ID, but every singular photo creates its own request - a pack is - in theory - being completed by various cutters, but is eventually completed and the photos are always up to date. Also, since the requests are tied to the ID a possibility to filter based on nationality/league would be probably useful for cutters who are mostly cutting faces from their own league/country (understandably )
I understand that from a coding perspective the filtering proposal wouldn't be too hard to implement, but it would be quite bandwidth-intensive which would raise operating costs considerably. But some sort of bridging feature along those lines is, I believe, under consideration
Those mixpack requests never get done