I am currently still using Qiqqa v79s...Why sniffer is not working since few days?

[emanelbanna]

[GerHobbelt]

v79 is the last Commercial Qiqqa release, where I never had access to its source code, so I don't know why this happens. Qiqqa did include usage data collection code so the sniffer may be adversely affected by the qiqqa.com site being shut down in Q4 2021 (see also #358), but be aware this is conjecture as I don't have source code access to that one.

Meanwhile, the Sniffer uses some components (XULrunner to be specific) which are becoming more outdated as we speak (see also #2) so it may run into other obscure issues.

Please try this again with an OSS version (preferrably latest v82, not v83) and let me know how it goes. Thanks! 👍

[emanelbanna]

Hi, I want to tell you that I used v82 and Sniffer is not working... Actually, Qiqqa browser can't open Google Scholar page... thus I can't import bibtex to my Qiqqa library Thanks

[GerHobbelt]

The overview answer re Qiqqa Sniffer issues is:

Google (and thus Google Scholar) is making every effort to kick out and keep out any Scholar access that might look like it's tool-supported, i.e. any access that's not from an unadorned Chrome browser and actual user manual activity.

And then, *even when you are a 'good user' like that, Scholar will limit your access to the source by throwing up roadblocks to slow you down, e.g. CAPTCHA checks, etc.

All these checks by Google are looking for any signal that yours is not the latest Chrome browser and that's one data point where Qiqqa fails horribly, as it's still using an (old) Firefox embedded browser for web access (a.k.a. 'XULrunner').

Work has been done (research) about resolving this, but Google keeps this an intentionally moving target and it's very much like an arms race.

Regrettably, there are currently no easy answers to this. 😭

Cross-referencing: #2, #113, #225, #363 (and any fix hinges on #289 making serious strides, which is an all-or-nothing challenge thanks to historic choices that made sense at the time.

[emanelbanna]

Hi,

Thanks a lot for your answer. Please keep me updated if there’ll be any way to use again sniffer tool perfectly with Qiqqa search.

Thanks Regards

On Saturday, September 3, 2022, Ger Hobbelt @.***> wrote:

The overview answer re Qiqqa Sniffer issues is:

Google (and thus Google Scholar) is making every effort to kick out and keep out any Scholar access that might look like it's tool-supported, i.e. any access that's not from an unadorned Chrome browser and actual user manual activity.

And then, *even when you are a 'good user' like that, Scholar will limit your access to the source by throwing up roadblocks to slow you down, e.g. CAPTCHA checks, etc.

All these checks by Google are looking for any signal that yours is not the latest Chrome browser and that's one data point where Qiqqa fails horribly, as it's still using an (old) Firefox embedded browser for web access (a.k.a. 'XULrunner').

Work has been done (research) about resolving this, but Google keeps this an intentionally moving target and it's very much like an arms race.

Regrettably, there are currently no easy answers to this. 😭

Cross-referencing: #2 https://github.com/jimmejardine/qiqqa-open-source/issues/2, #113 https://github.com/jimmejardine/qiqqa-open-source/issues/113, #225 https://github.com/jimmejardine/qiqqa-open-source/issues/225, #363 https://github.com/jimmejardine/qiqqa-open-source/issues/363 (and any fix hinges on #289 https://github.com/jimmejardine/qiqqa-open-source/issues/289 making serious strides, which is an all-or-nothing challenge thanks to historic choices that made sense at the time.

— Reply to this email directly, view it on GitHub https://github.com/jimmejardine/qiqqa-open-source/issues/363#issuecomment-1236184275, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM54PTYNHM65CRASBNAZWJTV4OPNDANCNFSM5FSIDHXQ . You are receiving this because you authored the thread.Message ID: @.***>