Eza's Image Glutton

Redirects to high-res images on gallery sites, skipping past descriptions and comments

< Feedback on Eza's Image Glutton

سوئال / ئىنكاس

§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

Fixes

// @include     http://youhate.us/*page=post&s=view*
// @include     https://youhate.us/*page=post&s=view*

=

// @include     http*://youhate.us/*page=post&s=view*

and so on

§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

// @include http*://www.gelbooru.com/s=view // @include http*://gelbooru.com/s=view

=

// @include     http*://*gelbooru.com/*s=view*
§
يوللانغان ۋاقتى: 2018-05-11

// @include http://gelbooru.com/page=post&s=view

=

// @include     http*://*gelbooru.com/*s=view*
§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

corrected http*

// @exclude     http*://www.deviantart.com/users/outgoing?*
§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

resume: all http replace to http* all https replace to http* all insertions replace to *

§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

lost break; in case 'jabarchives.com'

§
يوللانغان ۋاقتى: 2018-05-11
تەھرىرلەنگەن ۋاقتى: 2018-05-11

VAR modified_url = window.location.href + '#dnr';

§
يوللانغان ۋاقتى: 2018-05-11

var ugoku_link = pixiv.context.ugokuIllustData.src; undefined

§
يوللانغان ۋاقتى: 2018-05-11

use Tampermonkey and it's syntax checker, my padawan, and may the Force be with you

§
يوللانغان ۋاقتى: 2018-09-02

hello, did you hear me?

Ezaliasئاپتور
§
يوللانغان ۋاقتى: 2018-09-03

Yes, I did, and corrected the one bug that was genuinely a bug: the missing break in the select block.

Wildcards before the domain allow execution on arbitrary domains. Since this script is innately about blind redirection I'd like to eliminate those vulnerabilities, not proliferate them - and doing so in a human-readable format is nontrivial. The @include mechanism is too simple for its own good.

The pixiv object was not declared because it was provided by the page.

§
يوللانغان ۋاقتى: 2018-09-03
تەھرىرلەنگەن ۋاقتى: 2018-09-03

ok, better to replace 'http*' to 'https?'

Ezaliasئاپتور
§
يوللانغان ۋاقتى: 2018-09-03

Some sites require both http:// and https://. I've avoided duplicating all of them because best practices do call for minimizing @include count.

Obviating the sites with wildcard subdomains really requires regexes, which are gibberish to concerned users and also a pain to debug.

§
يوللانغان ۋاقتى: 2018-09-09

but 'https?' is working normally on http

§
يوللانغان ۋاقتى: 2019-01-07

for( x in illust_ids ) { // For each string split on illustId,

'x' is not defined!

for( var x in illust_ids ) {            // For each string split on illustId,
§
يوللانغان ۋاقتى: 2019-01-07

modified_url = window.location.href + '#dnr'; // add do-not-redirect tag to current URL

'modified_url' is not defined

    var modified_url = window.location.href + '#dnr';       // add do-not-redirect tag to current URL

جاۋاب قايتۇرۇش

جاۋاب قايتۇرۇش ئۈچۈن كىرىش.