Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > alt.comp.software.seamonkey > #8658 > unrolled thread

JS error at https://xcancel.com/ElonMusk/

Started byDavid H Durgee <dhdurgee@privacy.net>
First post2026-07-26 08:10 -0600
Last post2026-07-30 16:01 -0600
Articles 4 — 2 participants

Back to article view | Back to alt.comp.software.seamonkey


Contents

  JS error at https://xcancel.com/ElonMusk/ David H Durgee <dhdurgee@privacy.net> - 2026-07-26 08:10 -0600
    Re: JS error at https://xcancel.com/ElonMusk/ Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-28 08:38 +0100
      Re: JS error at https://xcancel.com/ElonMusk/ David H Durgee <dhdurgee@privacy.net> - 2026-07-28 09:05 -0600
        Re: JS error at https://xcancel.com/ElonMusk/ David H Durgee <dhdurgee@privacy.net> - 2026-07-30 16:01 -0600

#8658 — JS error at https://xcancel.com/ElonMusk/

FromDavid H Durgee <dhdurgee@privacy.net>
Date2026-07-26 08:10 -0600
SubjectJS error at https://xcancel.com/ElonMusk/
Message-ID<ncmiqfFhrerU1@mid.individual.net>
I am now encountering an error with the latest antibot JS at xcancel.com:

> Timestamp: 7/26/26, 6:34:56 AM MDT
> Error: SyntaxError: bad method definition
> Source File: https://xcancel.com/antibot/assets/cap.min.js
> Line: 1, Column: 11984
> Source Code:
> _idle=[],this._queue=[]}}class w extends HTMLElement{static formAssociated=!0;#e=null;#t=navigator.hardwareConcurrency||


Is there a way to work around this?  Is it possible this will be 
supported in the new release coming up?

I can still access the page by going through their image path, but it is 
annoying and tedious.

Dave

[toc] | [next] | [standalone]


#8659

FromNuno Silva <nunojsilva@invalid.invalid>
Date2026-07-28 08:38 +0100
Message-ID<1149m9e$3rtur$1@dont-email.me>
In reply to#8658
On 2026-07-26, David H Durgee wrote:

> I am now encountering an error with the latest antibot JS at xcancel.com:
>
>> Timestamp: 7/26/26, 6:34:56 AM MDT
>> Error: SyntaxError: bad method definition
>> Source File: https://xcancel.com/antibot/assets/cap.min.js
>> Line: 1, Column: 11984
>> Source Code:
>> _idle=[],this._queue=[]}}class w extends HTMLElement{static
>> formAssociated=!0;#e=null;#t=navigator.hardwareConcurrency||
>
>
> Is there a way to work around this?  Is it possible this will be
> supported in the new release coming up?

I think that may be the private fields, or at least it uses private
fields. IIRC that's part of what is being added in the WIP branch.

> I can still access the page by going through their image path, but it
> is annoying and tedious.

nitter.net still works (or works *again*, given for some time it wasn't
usable here?) for me without JS, if that helps. But it seems in recent
days it has had occasional problems accessing the twitter upstream, so
there may be something going on...

>
> Dave

-- 
Nuno Silva

[toc] | [prev] | [next] | [standalone]


#8660

FromDavid H Durgee <dhdurgee@privacy.net>
Date2026-07-28 09:05 -0600
Message-ID<ncruqfFd32dU1@mid.individual.net>
In reply to#8659
Nuno Silva wrote:
> On 2026-07-26, David H Durgee wrote:
> 
>> I am now encountering an error with the latest antibot JS at xcancel.com:
>>
>>> Timestamp: 7/26/26, 6:34:56 AM MDT
>>> Error: SyntaxError: bad method definition
>>> Source File: https://xcancel.com/antibot/assets/cap.min.js
>>> Line: 1, Column: 11984
>>> Source Code:
>>> _idle=[],this._queue=[]}}class w extends HTMLElement{static
>>> formAssociated=!0;#e=null;#t=navigator.hardwareConcurrency||
>>
>>
>> Is there a way to work around this?  Is it possible this will be
>> supported in the new release coming up?
> 
> I think that may be the private fields, or at least it uses private
> fields. IIRC that's part of what is being added in the WIP branch.
> 
>> I can still access the page by going through their image path, but it
>> is annoying and tedious.
> 
> nitter.net still works (or works *again*, given for some time it wasn't
> usable here?) for me without JS, if that helps. But it seems in recent
> days it has had occasional problems accessing the twitter upstream, so
> there may be something going on...
> 

I heard back from xcancel support and he indicated that the changes that 
are giving me the problems are due to measures he had to take to deal 
with increased bot activity.  This might relate to your occasional 
problems with nitter as well.

Dave

[toc] | [prev] | [next] | [standalone]


#8665

FromDavid H Durgee <dhdurgee@privacy.net>
Date2026-07-30 16:01 -0600
Message-ID<nd1vtoFbdhvU1@mid.individual.net>
In reply to#8660
David H Durgee wrote:
> Nuno Silva wrote:
>> On 2026-07-26, David H Durgee wrote:
>>
>>> I am now encountering an error with the latest antibot JS at 
>>> xcancel.com:
>>>
>>>> Timestamp: 7/26/26, 6:34:56 AM MDT
>>>> Error: SyntaxError: bad method definition
>>>> Source File: https://xcancel.com/antibot/assets/cap.min.js
>>>> Line: 1, Column: 11984
>>>> Source Code:
>>>> _idle=[],this._queue=[]}}class w extends HTMLElement{static
>>>> formAssociated=!0;#e=null;#t=navigator.hardwareConcurrency||
>>>
>>>
>>> Is there a way to work around this?  Is it possible this will be
>>> supported in the new release coming up?
>>
>> I think that may be the private fields, or at least it uses private
>> fields. IIRC that's part of what is being added in the WIP branch.
>>
>>> I can still access the page by going through their image path, but it
>>> is annoying and tedious.
>>
>> nitter.net still works (or works *again*, given for some time it wasn't
>> usable here?) for me without JS, if that helps. But it seems in recent
>> days it has had occasional problems accessing the twitter upstream, so
>> there may be something going on...
>>
> 
> I heard back from xcancel support and he indicated that the changes that 
> are giving me the problems are due to measures he had to take to deal 
> with increased bot activity.  This might relate to your occasional 
> problems with nitter as well.

A final post on this. Support got back to me indicating that they had 
modified the code to support older Firefox and SeaMonkey.  I confirmed 
that this is now working, but you might need to clear your cache.

Problem solved.

Dave

[toc] | [prev] | [standalone]


Back to top | Article view | alt.comp.software.seamonkey


csiph-web