Quote:
Originally Posted by JimmXinu
How many downloads/updates were you doing?
|
I tend to update in batches so I can keep up with tag maintenance (I add a lot of custom tags and updating erases them). Initially I tried to do 10 at a time, which has historically been my go to, and when that failed I pared it down to 5, and when that didn't work, to 1. None worked with the archiveofourown.gay method. Actually, it was worse than the transformativeworks.org method, as the .gay one wouldn't even download unlocked works, which transformativeworks can still do.
Cache method slows things down because I have to do them one at a time or it makes using my browser nigh-impossible, as I have to use the 'open page' method to make it work. It's not some insurmountable thing, more of a convenience thing since I can't really walk away to do other things what with the tag updates I do. That's my own fault, though.
Quote:
Originally Posted by JimmXinu
While one could argue that individual named threads for each issue would prevent duplication of reporting, the fact I can have 2 or 3 people open github issues for the same problem argues against it. Ditto all the duplicate threads that happen on MR in general.
There are pros and cons and I don't currently seen enough to motivate a change.
|
Understandable, there is no perfect solution that will work for everyone and every problem that happens. I do think having a set location for issues regarding the most common issues/sites makes sense, though, for casual readers of the thread who just want fixes and not necessarily want to understand the how/why discussion. I imagine the average reader is not programming/web savvy enough to parse everything said in this thread but is somewhat capable of following instructions (like me).