Vivaldi, Firefox & The Guardian; what is V's "Special Sauce"?
I'd love it if someone similarly curious about this, & with some time to burn, might have any illuminating insights. I'm really interested in this mini-mystery.
Summary: For The Guardian website [typically i use the Oz one, but afaik it's probably not region-specific], in V [Snapshot, but afaik it's identical in Stable] i can read an unlimited number of articles without being blocked by the cookie-induced "You need to register to keep reading. It’s still free to read - this is not a paywall" article-fadeout thingie. Conversely, in FF [Nightly, for me, but iirc it's a ditto problem in vanilla FF] i can only read ~3-6 articles before being blocked by that thingie.
For a while i assumed this might be a uBO consequence. Though i use notionally the same uBO config in both browsers, for fundamental design reasons already discussed elsewhere in the forum, uBO gives notably superior protection in FF than in chromia. Tonight however, i've eliminated that hypothesis by replicating the differential behaviour in virgin-profile windows of V & FF.
This UX arises with cookies not being explicitly blocked by me in either browser [because significant page malfunctions & shortcomings occur with blocked TG cookies]. I know this behaviour is somehow cookie-related, simply coz the workaround i deduced in FF is to clear site cookies for TG once i reach the reading-limit, then reload the page. No such "trick" is ever needed with V.
We all know that our V has numerous benefits, but this extra one seems quite unexpected IMO. Anyone have any insights pls?
Oh, my praise of V seems, in this case anyway, to have been a little unwarranted. I've just found that equally in Chromium i can also read unlimited TG articles. Hmmmmm, as much as i don't like chromia, it seems to have some fundamental big benefit UX specifically for TG site.
Pathduck last edited by
I've just retested FF with https://www.theguardian.com/uk?INTCMP=CE_UK, https://www.theguardian.com/us?INTCMP=CE_US, & https://www.theguardian.com/international?INTCMP=CE_INT ... all these work! In all these i have unlimited access!
Then, i returned to Straya, but not [yet] with my bookmarked https://www.theguardian.com/au, instead by using the same region-picker used to access the other sites above:
This did not return me to my expected url, but instead to https://www.theguardian.com/au?INTCMP=CE_AU ... and this variant also gives me unlimited access.
Finally i retested my BMd url ... sigh, this is insane, now it's also giving me unlimited access.
Geez i hate unreliable data!
@guigirl Do you block 3rd-party cookies? It seems like ticking that option in settings gives "unlimited" access to articles on that website.
@pafflick I block 3PC by default in V & FF. In my earlier post when i mentioned blocking cookies for TG, i carelessly omitted to explicitly mention that i meant TG's 1PC [but as i said, that significantly breaks site functionality, so is impractical].
Last night & again now this morning, i've inched a bit closer to understanding this [i think... maybe... ]. It seems to be a strongly region-based phenomenon... but nonetheless chromium browsers remain impervious whereas FF is affected. The following pertains to FF [coz, as i just said, V et al somehow magic their way thru sans-limits].
- When i use one of my Oz VPN servers, & my bookmarked https://www.theguardian.com/au site, those severe limits kick in, always.
- When i use an overseas VPN server [eg, atm, Netherlands on Lappy & Spain on Tower], AND if i use any of https://www.theguardian.com/uk?INTCMP=CE_UK, https://www.theguardian.com/us?INTCMP=CE_US, https://www.theguardian.com/international?INTCMP=CE_INT, https://www.theguardian.com/au?INTCMP=CE_AU, i get unlimited access.
- When i use an overseas VPN server, & my bookmarked https://www.theguardian.com/au site, those severe limits kick in, sometimes not always [eg, atm, it's good, but historically this ain't always so] - this is arguably the most confusing scenario.
Given #2, it seems that might be a viable ongoing workaround for me, when i'm in FF. Of course, it still doesn't resolve the basic initial question of this thread... what is V's [= chromium's] special sauce that lets them avoid these fun & games for TG?
@guigirl It looks like I've been wrong about the 3rd-party cookies blocking giving you the "unlimited" access. Frankly, I can't figure it out either. It looks like deleting cookies for both
www.theguardian.comseems to disable that "Sign-in gate" (as they call it) because if I try to delete just one of them, that message remains.
But I'm still confused as to how you manage to not get that "Sign-in gate" in Vivaldi since I get it here all the time, no matter what settings I use.
@pafflick Yes, manual cookie-clearing does temporarily allow TG pages to fully load, but after only a few such iterations, the block returns & the clearing has to be repeated --> in Firefox [whereas V & Chromium continue to wield their magic here].
I'm still confused as to how you manage to not get that "Sign-in gate"
It's possible that my accumulated uBO filters i've built up over time will account for some of our currently differing UX:
www.theguardian.com##.hide-until-mobile.new-header__cta-bar www.theguardian.com##.css-1lactnp ||www.theguardian.com/email/form/footer/today-uk$subdocument www.theguardian.com##div.colophon__list ||www.theguardian.com/email/form/footer/today-au$subdocument www.theguardian.com##.css-1p35o95 > span ! 2021-04-29 https://www.theguardian.com www.theguardian.com##.css-1xgdlo7-container-Container www.theguardian.com##.css-f9il16 ! 2021-05-04 https://www.theguardian.com www.theguardian.com##.css-19uwdba-container-Container ! 2021-05-20 https://www.theguardian.com www.theguardian.com##.css-1uiaxdu ! 2021-05-26 https://www.theguardian.com www.theguardian.com##.css-5thnkd > .css-0 www.theguardian.com##.css-1rdcmvp > span www.theguardian.com##.css-xh3eg0 > .css-1axlrpj www.theguardian.com##span.css-1bn3p0w > .css-1axlrpj ! 2021-05-29 https://www.theguardian.com www.theguardian.com##.new-header__cta-bar > div ! 2021-06-03 https://www.theguardian.com www.theguardian.com##.css-1fkcqhk www.theguardian.com##.css-jjd5tl ! 2021-07-20 https://www.theguardian.com www.theguardian.com##.css-1pt3sfn ! 2021-08-05 https://www.theguardian.com ||uploads.guim.co.uk/2020/10/02/Digisubs_MPU_c1_my_opt.png$image ! 2021-08-23 https://www.theguardian.com www.theguardian.com##.australian-moment-2021.thrasher-inner ! 2021-09-01 https://www.theguardian.com www.theguardian.com##.dcr-10kio6u
PS: I cannot keep up with this incomprehensible variability. For me, today, in FF [both vanilla & Nightly], TG has not enforced the block at all. I've just finished testing dozens of contiguously opened TG tabs, both via an Oz & an overseas VPN server, using both https://www.theguardian.com/au & https://www.theguardian.com/au?INTCMP=CE_AU. Score = 100% success.
Now i no longer know if i can accurately keep claiming that V & Chromium truly were immune as i'd thought, ie, maybe my prior tests of them merely happened to coincide by simple dumb luck with other periods when TG site was not enforcing its limits?