91–96 of 96 posts
Earlier quoted context omitted.
Not a full time apple user but how does third party orion browser supports Firefox addons on apple but Firefox itself doesn't support their own addons?
Orion had re-implemented support for the browser extensions APIs in WebKit. Though WebKit more recently opened up its built-in addons support to third-party browsers that use it.
Earlier quoted context omitted.
Orion had re-implemented support for the browser extensions APIs in WebKit. Though WebKit more recently opened up its built-in addons support to third-party browsers that use it.
My question is, why doesnt firefox support them
Earlier quoted context omitted.
The worry is real: there has historically not been a meaningful security barrier between a USB device and software running on the machine it's connected to. Firmware hasn't been developed with the assumption that the machine is malicious, there's probably lots of firmware which you can get RCE on by sending a weirdly formatted USB packet. Lots of devices have pretty unrestricted firmware update via USB functionality.…
But that isn't how it works, it's not a prompt like asking permission to use the camera allow/deny. The user gets presented with list of compatible devices and they have to select one themselves. An attacker could try to convince users to select something specific but that depends on the actual devices that are present and the "default" option to a confused non-technical person is to just cancel out of the list.
Earlier quoted context omitted.
> Unfortunately Firefox doesn't support the FileSystem API so to do this you need to resort to uploading the entire source code directory each time you change a source file. Right, it's so much less onerous to have people download and set up an entirely separate fickle toolchain—and needing to trust that the install triggers in the package.json of some transitive dependency won't exfiltrate your personal data or inst…
You seem very angry and I clearly don't understand what you are talking about. > And you're not really responding to the substance of the comment anyway, which is that JS programmers—frequently writing for browser runtimes, even—are demanding that you install NodeJS, Bun, or Deno (because they hardcode the build scripts against those runtimes' APIs). Do you mean things like the Typescript + Webpack/whatever toolchain…
Earlier quoted context omitted.
> Unfortunately Firefox doesn't support the FileSystem API so to do this you need to resort to uploading the entire source code directory each time you change a source file. Right, it's so much less onerous to have people download and set up an entirely separate fickle toolchain—and needing to trust that the install triggers in the package.json of some transitive dependency won't exfiltrate your personal data or inst…
You seem very angry and I clearly don't understand what you are talking about. > And you're not really responding to the substance of the comment anyway, which is that JS programmers—frequently writing for browser runtimes, even—are demanding that you install NodeJS, Bun, or Deno (because they hardcode the build scripts against those runtimes' APIs). Do you mean things like the Typescript + Webpack/whatever toolchain…
Luckily you managed to frame it so that the failure comes across like something that I got wrong and messed up and am responsible for, and that's the most important thing.