ChatGPT is now broken. Drats. (Can't do anything in Goanna on ChatGPT)

[Kxeon]

Weird. Something seems to have slipped.
I originally found this on Pale Moon, but instead of reporting it, I thought that it would probably be fixed later, so I used Waterfox instead for it.
Now I'm on Basilisk, testing it out. I try to go to ChatGPT to test it there; doesn't work. It's been a while though.
And so only now am I reporting it.
I went to Pale Moon again to see the error when signed in, I got the stuff you see down at the bottom. (I'm not signed in on Basilisk)

Code: Select all

SyntaxError: invalid regular expression flag d  
b5wtmoh4inpzei0d.js:90:3506
	openModalWindow resource://gre/components/nsPrompter.js:364:17
	openPrompt resource://gre/components/nsPrompter.js:585:9
	confirmEx resource://gre/components/nsPrompter.js:726:14
	confirmEx resource://gre/components/nsPrompter.js:79:18
	_onWindowsRestored/< resource://app/components/nsBrowserGlue.js:736:23
	<anonymous>

[Moonchild]

It's a known, open issue. We currently don't support the "indices" regex flag (/d)
Issue #2305 (UXP)

[Kxeon]

It's a known, open issue. We currently don't support the "indices" regex flag (/d)
Issue #2305 (UXP)

Well then, oops. I didn't know you already knew about this; but then again it's pretty big so there's that.
Well, at least I made the post so now if people search for the error they'll find your link. Sooo at least there's a good side to this accident.

[vannilla]

Well, at least I made the post so now if people search for the error they'll find your link. Sooo at least there's a good side to this accident.

Off-topic:
Yes, generally it's good to report issues for every website even if the error is known. The trouble is reporting multiple times the same website, as that would create a lot of noise and sometimes confuse everything unnecessarily. That's why it's always best to look up the problematic URL before posting.

[adoxa]

Removed the d flag (not used), but then there was a problem with DOMRect not supporting toJSON, which was also easy enough to work around. Here's the Modify HTTP Response filter (again, specific to this version, should perhaps relax the path test).

Code: Select all

[["cdn.oaistatic.com",["/assets/b5wtmoh4inpzei0d.js",["$/d","$/","/(g\\.getBoundingClientRect\\(\\)|p\\[0\\])\\.toJSON\\(\\)/g","JSON.stringify($1)"]]]

[Kxeon]

Code: Select all

[["cdn.oaistatic.com",["/assets/b5wtmoh4inpzei0d.js",["$/d","$/","/(g\\.getBoundingClientRect\\(\\)|p\\[0\\])\\.toJSON\\(\\)/g","JSON.stringify($1)"]]]

When one problem appears, another pops up.
Can anyone else scroll?

[adoxa]

That seems to be a script not creating a CSS class (not really sure how to track that down). Add a custom style this time:

Code: Select all

@-moz-document domain("chatgpt.com") {
  .h-full {
    overflow-y: auto
  }
}

[Moonchild]

For the record, just adding support for the flag (I'm working on the issue right now) seems to make it work, so even if specified, ChatGPT doesn't actually seem to use it and just causes incompatibility with browsers for no reason.

[back2themoon]

Can't AI sort this out itself? Being an expert in code and all. Or is it herself? Usually portrayed as female, for some reason.

[back2themoon]

Sorry, just had to:

Why aren't you compatible with the Pale Moon browser?
ChatGPT said:

Pale Moon is a lightweight, open-source web browser that originated as a fork of Mozilla Firefox. However, Pale Moon diverged significantly from the Firefox codebase after version 28. Because of this divergence, it has a different rendering engine (Goanna instead of Gecko) and lacks support for many modern web standards and features.
Here are the likely reasons for incompatibility:

Modern Web Technologies:
I use advanced web features like WebSockets, Web Components, and Service Workers. Pale Moon may not support these or implement them differently, causing compatibility issues.

JavaScript and ECMAScript Features:
I rely on up-to-date JavaScript (ECMAScript 6+), which includes features like async/await, arrow functions, and modern array methods. Pale Moon often lacks full support for these newer JavaScript features.

Limited Web APIs:
Pale Moon has a different implementation of web APIs and may not support certain APIs required for handling real-time interactions and dynamic content effectively.

Outdated or Custom Rendering Engine:
Pale Moon's Goanna engine does not include many of the updates found in modern engines like Chromium's Blink or Firefox's Gecko. This can lead to layout and rendering issues.

Browser Extensions and Polyfills:
While most modern browsers can use polyfills or extensions to handle unsupported features, Pale Moon's extension system (based on the older XUL architecture) may not support the necessary modern extensions.

What You Can Do

Switch to a Modern Browser: Using browsers like Firefox, Chrome, Edge, or Safari will provide the best experience and full compatibility.
Enable Compatibility Mode: Sometimes enabling "Compatibility Mode" in Pale Moon can help, but this is limited.
Update Pale Moon: Ensure you are using the latest version, as it may have improved support for certain features.

Let me know if you need more specific help!

You said:
You (not Pale Moon) seem to be having a problem with the d flag.

ChatGPT said:

Ah, I see what you're referring to! The d flag often refers to the "Do Not Track" (DNT) setting that some browsers, including Pale Moon, can send with HTTP requests to signal a preference for privacy.
Why There Might Be a Problem

Strict DNT Enforcement in Pale Moon:
Pale Moon respects the DNT header strictly, and if you have it enabled (d=1), it signals that you don't want tracking or certain types of user data processing. This may interfere with certain features that rely on user data, like session handling or analytics.

How I Handle DNT:
I prioritize privacy and don't track users in a conventional sense. However, the application might use real-time features, cookies, or session data that could be affected if the browser blocks or modifies requests based on the DNT header.

Compatibility Mode:
If Pale Moon is operating in a legacy or privacy mode that alters headers or blocks certain scripts, it could cause unexpected behavior.

Possible Solutions

Check Browser Settings:
Disable "Do Not Track" temporarily and see if the compatibility improves.

Switch User Agent:
Use an extension or browser setting in Pale Moon to change the user agent string to mimic a more modern browser (e.g., Firefox or Chrome). This might bypass certain compatibility checks.

Check Console for Errors:
If you can, open Pale Moon's Developer Tools (F12) and look at the Console tab for any specific errors or blocked requests. This can provide more details about what's failing.

Let me know if you need further help troubleshooting!

You said:
No, I meant the RegExp Match Indices (/d)

ChatGPT said:

Ah, got it! You're talking about the /d flag for RegExp match indices in JavaScript, introduced in ECMAScript 2022. This flag allows regular expressions to return the start and end indices of matched groups, which can be extremely useful for precise substring extraction.
Why This Causes Issues in Pale Moon

Pale Moon does not support ECMAScript features introduced after ES6 (ECMAScript 2015). The /d flag was added in ES2022, which is far beyond the JavaScript engine capabilities of Pale Moon. As a result:

Syntax Error:
If a script or code snippet uses the /d flag, Pale Moon's JavaScript engine will throw a SyntaxError because it doesn't recognize the flag.

No Fallback:
JavaScript engines that do not support the /d flag have no way to handle it gracefully. The entire regex expression fails if it includes unsupported flags.

Example of the Issue

const regex = /hello(\w+)/d;
const result = regex.exec("hello world");
console.log(result.indices); // This line will cause an error in Pale Moon

In Pale Moon, the above code will throw:

SyntaxError: Invalid regular expression flag 'd'

How to Handle This

Avoid Using /d in Code for Older Browsers:
Check browser compatibility before using modern JavaScript features. Avoid the /d flag if you intend to support older browsers like Pale Moon.

Feature Detection:
You can use feature detection to check if the /d flag is supported:

let supportsDFlag = false;
try {
new RegExp('', 'd');
supportsDFlag = true;
} catch (e) {
supportsDFlag = false;
}
console.log(`/d flag support: ${supportsDFlag}`);

Polyfill:

There is currently no standard polyfill for the /d flag, but you can manually capture start and end indices using string methods:

const str = "hello world";
const match = /hello(\w+)/.exec(str);
if (match) {
const start = match.index;
const end = start + match[0].length;
console.log(`Start: ${start}, End: ${end}`);
}

Summary

The issue lies with Pale Moon's outdated JavaScript engine, which doesn't support modern features like the /d flag for RegExp match indices. To ensure compatibility, either avoid using this flag or use feature detection and provide fallbacks.

[Moonchild]

Sorry, just had to:

And if you go by its answers (taken obviously from various posts written by people who weren't involved in the project) then any casual reader will think Pale Moon is completely unusable.

Thanks, I guess?

[moonbat]

I have zero faith in LLMs as a substitute for search engines and finding more about a topic (they're fine for processing text/images that you supply, or simple code that you again have to verify afterwards) ever since their extreme political bias through altering the input data was first known. OpenAI does it, and Google Gemini proved itself to be surreal comedy where this is concerned. If they pick pushing narratives instead of the truth on any given topic, there's no way you can trust anything it says.

[BenFenner]

Off-topic:

ChatGPT said:
Pale Moon does not support ECMAScript features introduced after ES6 (ECMAScript 2015).

This is of course obnoxiously wrong, and if I were one of the devs who spent time implementing any ECMAScript features introduced after ES6 for Pale Moon I'd be furious.

ChatGPT said:
Switch to a Modern Browser: Using browsers like Firefox, Chrome, Edge, or Safari will provide the best experience and full compatibility.
<snip>
Avoid the /d flag if you intend to support older browsers like Pale Moon.

Older browsers? Pale Moon is newer than Firefox, Chrome, and Safari you useless sack of LLM trash.

[Moonchild]

Off-topic:

ChatGPT said:
Pale Moon does not support ECMAScript features introduced after ES6 (ECMAScript 2015).

This is of course obnoxiously wrong, and if I were one of the devs who spent time implementing any ECMAScript features introduced after ES6 for Pale Moon I'd be furious.

I'm not furious because I know you can't use ChatGPT for any serious research.

The problem is that ChatGPT's model is trained on a lot of old data. Once upon a time, that statement was true. But things change.
Which brings me to the glaring Achilles' heel of LLMs: It is not possible to update existing models by updating their training or remove incorrect data once it has been incorporated. So the moment anything changes, which is the case here, the model's knowledge becomes incorrect, and the only way to correct it is to retrain the model from scratch, excluding every single instance of old data it was previously trained on.
In other words: LLMs can only be trained on a snapshot of data, and you can never learn them new things that it already has an "opinion" about. It cannot unlearn associations, unlike humans. One of the reasons LLMs are a pretty crude tool, even though they can help lower barriers for people.

This means that using an LLM for web search is pointless: web data changes constantly.
Using an LLM for academic research is pointless: the academia constantly discover new things or change established knowledge as new theories are tested.
Using an LLM for generic text is risky as well: if it has been trained on a lot of old data, you'll get issues with writing styles, incorrect meanings of words, etc.
... unless you are constantly re-training new models from scratch using new, vetted, accurately-tagged data (that one example of eating a rock from an Onion article being used for a serious answer, for example, was a good demonstration how unvetted data leads to poisoned models that don't understand separating truth from fiction)

[noellarkin]

Code: Select all

[["cdn.oaistatic.com",["/assets/b5wtmoh4inpzei0d.js",["$/d","$/","/(g\\.getBoundingClientRect\\(\\)|p\\[0\\])\\.toJSON\\(\\)/g","JSON.stringify($1)"]]]

When one problem appears, another pops up.
Can anyone else scroll?

I tried adding this filter but am getting the error message:
Filter Error!
SyntaxError: JSON.parse: end of data when ',' or ']' was expected at line 1 column 152 of the JSON data

[adoxa]

Oops, I missed the closing bracket. Here's an update that does relax the path test.

Code: Select all

[["cdn.oaistatic.com",["/\\/assets\\/.{16}\\.js/",["$/d","$/","/(g\\.getBoundingClientRect\\(\\)|p\\[0\\])\\.toJSON\\(\\)/g","JSON.stringify($1)"]],["/root.*\\.css/",["/min\\(.*?,/g","calc("]]]]

[noellarkin]

this worked, thanks!

[BenFenner]

Anyone with PM v33.5.0 check to see if ChatGPT is working as intended now?
According to the release notes our issues with the RegEx "match indices" (/d) feature should be behind us.

[back2themoon]

Couldn't log in with my main profile (ad/content blockers, etc.), I soon get: "Oops, an error occurred!"

On clean PM portable, I did log in and noticed in-between, automatic Cloudflare checks which weren't visible/present above.

However, when trying to type just one character in the AI text box after the login is complete, the Oops message appears. So, it doesn't seem to work. All tests on Nuck-TH's 33.5.0 SSE2 builds, which I guess doesn't make any difference in Web Compatibility issues.

Error Console (clean PM Portable):

AI Errors.png

[Mæstro]

I have zero faith in LLMs as a substitute for search engines and finding more about a topic (they're fine for processing text/images that you supply, or simple code that you again have to verify afterwards) ever since their extreme political bias through altering the input data was first known. OpenAI does it, and Google Gemini proved itself to be surreal comedy where this is concerned. If they pick pushing narratives instead of the truth on any given topic, there's no way you can trust anything it says.

Off-topic:
Trouble comes even with politically neutral matters. On a lark, I asked DuckDuckGo’s instance of Mixtral to describe Peano arithmetic, which I would consider common knowledge to anyone who knows about the foundations of mathematics. The result follows.

Peano arithmetic is a formal system for the natural numbers, which are the numbers 0, 1, 2, 3, and so on. It was developed by the Italian mathematician Giuseppe Peano in the late 19th century.

Peano arithmetic consists of a set of axioms, or basic assumptions, about the natural numbers, and a set of rules for manipulating these axioms to prove theorems. The axioms of Peano arithmetic include:

0 is a natural number.
Every natural number has a successor, which is also a natural number.
0 is not the successor of any natural number.
Two natural numbers are equal if and only if their successors are equal.
The successor of a natural number is unique.
Using these axioms, it is possible to prove a wide variety of theorems about the natural numbers. For example, one can prove that there is no smallest natural number greater than 0, and that the set of natural numbers is infinite.

Peano arithmetic is a fundamental system in mathematical logic, and it has been extensively studied by logicians and mathematicians. It is a key example of a formal system, and it has been used to prove important results about the foundations of mathematics.

For laymen who might not see the problems, the last axiom is redundant given the other four, the actual fifth axiom (that permitting mathematical induction) is missing and it is alleged that Peano arithmetic can prove a patent falsehood, which would be fairly awkward (to put it mildly) for mathematics as we know it if it were so. I have already seen machine-generated articles in the wild guessing the length of books like The Screwtape Letters and varying by ten thousand words. This software (I have come to speak of any instance as a ‘salad tosser’) produces plausible-sounding nonsense. In 2020–21, my circle of friends amused itself with the dreamlike rambling that ChatGPT’s ancestor could spew when given inside jokes or other bizarre prompts. That was fun and silly, much like toying with Microsoft Sam twenty years ago. The succeeding software of 2024 is worthless for the layman.