mega.nz auto-redirecting to an error page Topic is solved

[KlarkKentThe3rd]

This could have been a private message, but perhaps a thread is better. Whoever decides things at MEGA have programmed the site to redirect Pale Moon to a "choose a different browser" page. So no option to log in. Please include a user agent spoof for MEGA in Pale Moon 23.4.0.2

[moonbat]

This could have been a private message, but perhaps a thread is better.

Why wouldn't a thread in this board be a better option to report a broken site?

[sidology]

Please include a user agent spoof for MEGA in Pale Moon 23.4.0.2

Not gonna happen, use this awesome extension: https://addons.palemoon.org/addon/ua-status/

[moonbat]

Not gonna happen

Why not?

[back2themoon]

Issue reported. They have fixed issues in the past so let's wait.

This could have been a private message, but perhaps a thread is better.

Contacting MEGA should be the primary action.

[sidology]

Why not?

Sorry, I read-understand it wrong. Spoof will come, if mega doesn't fix it.

[KlarkKentThe3rd]

Please include a user agent spoof for MEGA in Pale Moon 23.4.0.2

Not gonna happen, use this awesome extension: https://addons.palemoon.org/addon/ua-status/

That is actually really cool, getting that.

EDIT: not terribly useful, unless I know which exact text to put in the text box (and I do NOT know the exact text for the right user agent) it is not usable.

[4td8s]

This could have been a private message, but perhaps a thread is better. Whoever decides things at MEGA have programmed the site to redirect Pale Moon to a "choose a different browser" page. So no option to log in. Please include a user agent spoof for MEGA in Pale Moon 23.4.0.2

this is more of a site problem and not just with Palemoon
the mega.nz site also redirects to the "choose a different browser" page with Seamonkey and a few other "old" browsers as well

[Moonchild]

There's also no guarantee that a UA override will satisfy their check, whatever it is, for a "permitted" browser on their short list.
it's also possible they they are doing some new "voodoo" to "download" files, like they've done in the past, i.e. not offering downloads but doing some manipulation through JS on arbitrary/proprietary data they send over instead of the actual file, and reconstructing it locally. Mega has always been weird like that.

[KlarkKentThe3rd]

MEGA may be weird, but they are extremely useful. To me, anyway. I suggest any users here to contact them about the issue (I already did).

[artenaki]

Until recently, the site worked even in Firefox 60.

[back2themoon]

Now it's trying to open (no 'outdated' message) but it doesn't. Gets stuck to "Requesting account data". Post your findings, perhaps it works for you?

[KlarkKentThe3rd]

Now it's trying to open (no 'outdated' message) but it doesn't. Gets stuck to "Requesting account data". Post your findings, perhaps it works for you?

You beat me to it. I did contact them (using proper email this time), and they will hopefully fix this soon.

[back2themoon]

As a part of our latest releases we have bumped minimum browser versions required to those supporting ES2020. Consequently Pale Moon is no longer supported - sorry for the inconvenience. The most compatible browsers that provide full HTML5 support we need currently are: Google Chrome (from v67), Mozilla Firefox (from v68), Edge (from v78), and Opera (from v54).

...but they no longer display the "incompatible" page?

[Moonchild]

We support the ES2020 spec, though. We have all the spec features of ES2020 and before. Of those, BigInt was the last we still needed and that's implemented now. There's one small omission in our implementation of it that will be addressed with the upcoming release, but otherwise we have complete coverage to the best of my knowledge. If Mega.nz still thinks we're missing something then by all means, let them provide details (similar to what Proton Mail did) so we can address any shortcomings.

[Moonchild]

For the record, as of this writing, this is our technology support:

Full ES5/ES6 support

2016 features

exponentiation (**) operator Yes
Array.prototype.includes Yes

2016 misc

generator functions can't be used with "new" Yes
generator throw() caught by inner generator Yes
strict fn w/ non-strict non-simple params is error Yes
nested rest destructuring, declarations Yes
nested rest destructuring, parameters Yes
Proxy, "enumerate" handler removed Yes
Proxy internal calls, Array.prototype.includes Yes

2017 features

Object static methods Yes
String padding Yes
trailing commas in function syntax Yes
async functions Yes
shared memory and atomics Yes
RegExp "u" flag, case folding Yes
arguments.caller removed Yes

2017 annex b

Object.prototype getter/setter methods Yes
Proxy internal calls, getter/setter methods Yes
assignments allowed in for-in head in non-strict mode Yes

2018 features

object rest/spread properties Yes
Promise.prototype.finally Yes
(dotAll) flag for regular expressions Yes
RegExp named capture groups Yes
RegExp Lookbehind Assertions Yes
RegExp Unicode Property Escapes * Yes
Asynchronous Iterators Yes

Regex unicode property escapes do not support the entire range of really exotic scripts that keep getting tacked on with unicode revisions at this point, but otherwise it is fully supported.

2018 misc

template literal revision Yes

2019 features

Symbol.prototype.description Yes
Object.fromEntries Yes
string trimming Yes
Array.prototype.{flat, flatMap} Yes

2019 misc

optional catch binding Yes
Function.prototype.toString revision Yes
JSON superset Yes
Well-formed JSON.stringify Yes

2020 features

String.prototype.matchAll Yes
BigInt Yes (issue with ++/-- operators, will be solved)
Promise.allSettled Yes
globalThis Yes
optional chaining operator (?.) Yes
nullish coalescing operator (??) Yes

And we also, looking ahead, have the following later support:

2021 features

String.prototype.replaceAll Yes
Promise.any Yes
WeakReferences No -- also completely undesired, and officially urged not to use by mainstream. We may put in a stub for sites that want to use it without fallback.
Logical Assignment (&&= ||= etc) Yes
numeric separators Yes
instance class fields Yes
static class fields Yes
private class methods Yes
Ergonomic brand checks for private fields Yes
.at() method on the built-in indexables Yes
Object.hasOwn Yes
Class static initialization blocks Yes
Error.cause property No (low priority, only useful for debugging)
RegExp Match Indices No (planned)

2023 features

Array find from last Yes
Hashbang Grammar No (not sure why we'd want this... it seems to be pushed by someone who particularly loves the oddball top-line type markers in textual files... we have this wonderful MIME system for file types, why introduce a potentially conflicting FT marker? Seems really out of place for a web spec)

2024 features

RegExp `v` flag No (probably something for the future too)

[back2themoon]

Thanks - I will forward and post back with any news.

[back2themoon]

Received a response, in the same vein as the previous one: "these are now the compatible browsers, please use these to access..." etc. Too bad, since I was about to start a paid plan with them.

Time to name some good alternatives.

[Echedelle]

Received a response, in the same vein as the previous one: "these are now the compatible browsers, please use these to access..." etc. Too bad, since I was about to start a paid plan with them.

Time to name some good alternatives.

Off-topic:
Perhaps a little NextCloud instance with S3-type storage could be better for your needs.

[back2themoon]

Looks like MEGA is working now, perhaps because of the 32.5.0 update? Give it a try.

Perhaps a little NextCloud instance with S3-type storage could be better for your needs.

Thanks, that's interesting. Never heard of it, will have to dig up a bit.