Search results

Alas we have to balance global perms with specific countries' regulations; and locking that behind being logged in even when using a direct link didn't seem fine to us. Maybe we can eventually review this again. In this case it makes sense, because it's an HTTP 200 (ie wasn't an error as far as...

Best of luck with the reboot, looking forward to it!

First, thanks a lot for the very detailed report, and while it might not be the case for everyone affected, running MD has certainly opened my eyes as to how often ISPs themselves have issues, and this is nice confirmation. Hopefully the other affected users will also see resolution on their end...

What, already? :qq: :qq:

Now this is truly something else

your guesses were all very reasonable, and that's what I checked for the people on discord, to no avail :/ also our rate-limit system does have a cooldown and a grace period both, to handle both bursts and clients that stop misbehaving... :/ also if you get caught, refreshing the page would show...

Brave already explained to you why that’s not a viable indicator All of them run on Cloudflare, so they are, from a networking perspective, all the exact 1 same site. Yes clearly we engineered the site to screw with you in particular every now and then. We also obviously really like the site...

This left me more confused than anything else 😐

In Toudou we trust… maybe :dogkek:

Letsgooooo

Great end; feels like the past few chapters passed in a second! Thanks a lot for the translations too and see you around!

That face :hearts:

Nice! :) You will probably want to update the poor soul in https://forum.palemoon.org/viewtopic.php?f=70&t=29482 about it

Ah that would certainly explain it yes! I’ll give that a try later then Unfortunately that’d be difficult as our frontend isn’t meant to be open-source at the moment… maybe there’s a way to selectively add source maps in specific files only. For now we should probably just wait for the fix...

Trying to put a breakpoint in the line just above however causes PM to instantly crash without any error message though. Not sure if PM has some kind of coredump feature. Putting the breakpoint on the line of failure itself causes: If I replace it with if ($auth?.loggedIn) { I do get a...

So the error still remains but isn't quite a type error; here's what's going on (testing your latest build): import { useNuxtApp, useRoute } from "/_nuxt/node_modules/nuxt/dist/app/index.js?v=bd4495ba"; ... const _sfc_main = /* @__PURE__ */ _defineComponent({ __name: "app", async...

If it helps, here's the entire file https://pastebin.com/41uCqKgU

This is the next parsing error I get (trying to run against a local non-minified build) after enabling the dynamic import flag Also @AlexEliot it seems like it does At least grepping our prod client-side output I see: $ rg -o 'BigInt' . ./entry.d2925253.js 1:BigInt 47:BigInt 47:BigInt...

Something we could consider is trying this out ourselves on a local non-minified version of the site in case it's relatively easy for us to fix. Let us know once a release with that patch is in (or if there's officially sanctioned trunk binaries somewhere we could use; trying to avoid figuring...

As moon himself noted in the thread, this is a tech change by Nuxt themselves, not us; we can't really provide a fallback ourselves Would be good to see the minified JS on which things are failing here; even if minified it might give us a hint as to what's wrong exactly? I don't believe our...