going to https://nextdoor.com/
SeaMonkey hangs while "waiting for analytics.google.com..."

identifying as "seamonkey"
2.53.16

--
..

meagain wrote on 28/7/23 9:06 pm:
> going to https://nextdoor.com/
> SeaMonkey hangs while "waiting for analytics.google.com..."
>
> identifying as "seamonkey"
>  2.53.16
>
That site came up pretty quickly for me and my SM 2.53.16 on Linux.

It draws stuff from several sites to finish drawing itself. Didn't
particularly notice analytics.google.com but I'm guessing it's there!
--
Daniel

Daniel65 <daniel47@nomail.afraid.org> wrote:
> meagain wrote on 28/7/23 9:06 pm:
> > going to https://nextdoor.com/
> > SeaMonkey hangs while "waiting for analytics.google.com..."
> >
> > identifying as "seamonkey"
> >  2.53.16
> >
> That site came up pretty quickly for me and my SM 2.53.16 on Linux.

> It draws stuff from several sites to finish drawing itself. Didn't
> particularly notice analytics.google.com but I'm guessing it's there!

For my 64-bit SM v2.53.16 in updated 64-bit W10 Pro, it shows white
blank web page on https://nextdoor.com with and without Firefox
compatibility and uBlock Origin. :(
--
"Some of the Jews were persuaded [by the preaching of the Gospel] and joined Paul and Silas, as did a large number of God-fearing Greeks and quite a few prominent women." --Acts 17:4. Will Christopher Nolan's Oppenheimer nuke this already hot ant from orbit soon?
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

-------- Original Message --------
> Daniel65 <daniel47@nomail.afraid.org> wrote:
>> meagain wrote on 28/7/23 9:06 pm:
>>> going to https://nextdoor.com/" rel="nofollow" target="_blank">https://nextdoor.com/
>>> SeaMonkey hangs while "waiting for analytics.google.com..."
>>>
>>> identifying as "seamonkey"
>>>  2.53.16
>>>
>> That site came up pretty quickly for me and my SM 2.53.16 on Linux.
>
>> It draws stuff from several sites to finish drawing itself. Didn't
>> particularly notice analytics.google.com but I'm guessing it's there!
>
> For my 64-bit SM v2.53.16 in updated 64-bit W10 Pro, it shows white
> blank web page on https://nextdoor.com with and without Firefox
> compatibility and uBlock Origin. :(
>

My
64-bit SM v2.53.16 in updated 64-bit W10 home
shows white blank, but other browsers get past the blank page.

I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.

-------- Original Message --------
> -------- Original Message --------
>> Daniel65 <daniel47@nomail.afraid.org> wrote:
>>> meagain wrote on 28/7/23 9:06 pm:
>>>> going to https://nextdoor.com/" rel="nofollow" target="_blank">https://nextdoor.com/
>>>> SeaMonkey hangs while "waiting for analytics.google.com..."
>>>>
>>>> identifying as "seamonkey"
>>>>    2.53.16
>>>>
>>> That site came up pretty quickly for me and my SM 2.53.16 on Linux.
>>
>>> It draws stuff from several sites to finish drawing itself. Didn't
>>> particularly notice analytics.google.com but I'm guessing it's there!
>>
>> For my 64-bit SM v2.53.16 in updated 64-bit W10 Pro, it shows white
>> blank web page on https://nextdoor.com with and without Firefox
>> compatibility and uBlock Origin. :(
>>
>
> My
> 64-bit SM v2.53.16 in updated 64-bit W10 home
> shows white blank, but other browsers get past the blank page.
>
> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.
>

Restart (one SM crash) and now the above issue is working!

--
.

On 7/28/2023 12:23 PM, meagain wrote:
> -------- Original Message --------
>> Daniel65 <daniel47@nomail.afraid.org> wrote:
>>> meagain wrote on 28/7/23 9:06 pm:
>>>> going to https://nextdoor.com/" rel="nofollow" target="_blank">https://nextdoor.com/
>>>> SeaMonkey hangs while "waiting for analytics.google.com..."
>>>>
>>>> identifying as "seamonkey"
>>>>    2.53.16
>>>>
>>> That site came up pretty quickly for me and my SM 2.53.16 on Linux.
>>
>>> It draws stuff from several sites to finish drawing itself. Didn't
>>> particularly notice analytics.google.com but I'm guessing it's there!
>>
>> For my 64-bit SM v2.53.16 in updated 64-bit W10 Pro, it shows white
>> blank web page on https://nextdoor.com with and without Firefox
>> compatibility and uBlock Origin. :(
>>
>
> My
> 64-bit SM v2.53.16 in updated 64-bit W10 home
> shows white blank, but other browsers get past the blank page.
>
> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.
>

I've had weeks of Nextdoor loading to an empty page. After reading your
post I tried it again and (with no change on my part) everything seems
to work perfectly. Go figure.

Lem Johnson

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16

Ant wrote:
>> It draws stuff from several sites to finish drawing itself. Didn't
>> particularly notice analytics.google.com but I'm guessing it's there!

> For my 64-bit SM v2.53.16 in updated 64-bit W10 Pro, it shows white
> blank web page onhttps://nextdoor.com with and without Firefox
> compatibility and uBlock Origin. :(

I'm used to seeing this in my primary profile in Windows 10, enough that
I've stopped trying to get to nextdoor.com from Seamonkey. I also use
both uBlock Origin and NoScript, and even with whitelisting in NoScript,
that doesn't make any difference.

I made another try on a untweaked profile on another machine (that one
happens to be Ubuntu Linux), and had no problems getting all the
display. I then made another check of an untweaked profile on another
Windows 10 machine, and also getting through there.

Having piqued my curiosity, I went back to my primary profile, and I'm
able to get in there, and the only scripting hosts that I have to enable
are nextdoor.com itself as well as one of two CDN hosts at
cloudfront.net. I haven't tested all the functionality extensively, but
I'm not seeing the need to whitelist any other scripting, including
googletagmanager, googletagservices, google.com, cookielaw.org,
consensu.org, and others.

I will note that I don't believe that I've seen the opportunity to
enable/block analytics.google.com, although I have permanently
blacklisted google-analytics.com. However, NoScript is not showing me
that google-analytics.com is active here.

I noted that I have had enough problems with nextdoor.com in Seamonkey
that I've given up on that combination, under the assumption that
they're doing scripting that Seamonkey can't handle. If I want to get
there, I will switch over to another browser. However, this kind of
issue isn't always permanent, and this example is illustrative of the
idea that just because a particular site starts using problem scripting,
that may not be permanent. Large sites like this frequently change
their scripting, and even if they start doing something that breaks
Seamonkey, that doesn't mean that later on, they may change their
scripting again, in a way that makes Seamonkey possible again.

Smith

meagain wrote:
> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.

Best to use 0.0.0.0 as 127.0.0.x will still take time to timeout
Dave

Dave Yeo wrote:
> meagain wrote:
>> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.
>
> Best to use 0.0.0.0 as 127.0.0.x will still take time to timeout
> Dave

I have a few sites set to 127.0.0.something in my "hosts", that
alternative suggestion is going to get tested one of these days.

Don Vito Martinelli wrote:
> Dave Yeo wrote:
>> meagain wrote:
>>> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no change.
>>
>> Best to use 0.0.0.0 as 127.0.0.x will still take time to timeout
>> Dave
>
> I have a few sites set to 127.0.0.something in my "hosts", that
> alternative suggestion is going to get tested one of these days.

I just did a quick test, with no services running locally, they're both
pretty well instant. Perhaps it is only if you do have some services
running.
If you look at some of the ones for ad blocking such as
https://github.com/StevenBlack/hosts they do use 0.0.0.0
Dave

Dave Yeo wrote:
> Don Vito Martinelli wrote:
>> Dave Yeo wrote:
>>> meagain wrote:
>>>> I've tried to bypass "analytics" using 127.0.0.x in Hosts but no
>>>> change.
>>>
>>> Best to use 0.0.0.0 as 127.0.0.x will still take time to timeout
>>> Dave
>>
>> I have a few sites set to 127.0.0.something in my "hosts", that
>> alternative suggestion is going to get tested one of these days.
>
> I just did a quick test, with no services running locally, they're both
> pretty well instant. Perhaps it is only if you do have some services
> running.
> If you look at some of the ones for ad blocking such as
> https://github.com/StevenBlack/hosts they do use 0.0.0.0
> Dave

I have analytics blocked since yesterday morning, no ill-effects so far.

Another site complains intermittently that servedby.flashtalking.com is
down - I have had that one in my "hosts" for over a week - but it lives
with the pain. I had that site as 127.0.0.3 before but changed it after
your post. Thanks.