Better Open All In Tabs queue management

Simon-Tesla / RaccoonyWebEx

A WebExtension that adds shiny features to art sites

MIT License

40 stars 4 forks source link

Better Open All In Tabs queue management #177

Open Simon-Tesla opened 3 months ago

Simon-Tesla commented 3 months ago

Right now the way this works is fairly opaque and not easily user controllable (especially now that we no longer use placeholder tabs). Some thoughts on how this can be made better:

A UI for managing the queue of tabs to open
- Minimum: pause and abort/clear global queue - probably would make sense to have this as a keyboard shortcut as well
- Pause/abort individual batches of items
- Reorder queue items?
Add jitter to the tab delay to make the behavior look less bot-like.
Ability to automatically throttle the queue if a tab (or multiple tabs) are returning error responses (e.g. 503/427/etc, detection either by page scraping or by webRequest.onResponseStarted listener
Ability to retry a tab if it has an error? (Probably not a good idea)

Joebugg commented 1 week ago

I've been using BUO and Link Gopher to deal with lists of URLs, and delaying the opening of them. Like, run it unattended with a minute+ each tab.

Bulk URL Opener is one of the ones that lets you add a delay (Open From Clipboard is defunct). Yeah, if you're having to add jitter, it might not make more sense to add a lonnnnnnnnnng delay to your load times. The "slow down" 429 or similar status codes should definitely be honored, to be fair. Those are another way to get blocked for abuse.

What would be nice to also be able to just export the URLs instead of opening them, so you can use another tool like BUO or curl/wget.

Simon-Tesla commented 1 week ago

I feel like once I get to the point of exporting a URL list, people are going to be better served by gallery-dl. For me at least the point of open all in tabs is to be able to review the full-res artwork and interact with it as desired (e.g. download/fav/comment/etc.); the automatic download isn't something I use but was added as it's a relatively obvious feature that wasn't much work to implement.

Generally speaking it's fairly rare for me to trigger bot detection with Raccoony with it's built-in delays which is one of the reasons this hasn't been a higher priority, but on occasion if (for example) FA is under load and spitting out 503s or Cloudflare errors, or e621 throws up its 'prove you're a human' screen, it'd be nice to respond more intelligently to that. I honestly don't think I've ever seen a site explicitly return me a 429.

Joebugg commented 3 days ago

I honestly don't think I've ever seen a site explicitly return me a 429. I know for a fact that Pixiv does.

Simon-Tesla commented 3 days ago

Heh, one of these days I'll implement pixiv support :P