use firefox, block most javascript
if shit doesn’t work because it’s garbage, try safari
if shit still doesn’t work because it’s unimaginably garbage, try chromium
if shit STILL doesn’t work because it’s beyond salvageable garbage, well it’s unsalvageable find a new solution: never use chrome
some APIs just aren’t available… i’m not sure about web bluetooth for example, but when i had a play with that a while back (because it was the easiest way to connect to a bluetooth device to hack around), i wrote some control software that was chromium only because firefox didn’t support that API
same goes for some of the crypto APIs
and when firefox blocked cross-origin cookies and a bunch of SSO solutions stopped working… they weren’t garbage, they just were built on technologies that other peoples abused and were later deemed insecure - but not for their use-case
it’s acceptable to write software that doesn’t support firefox if it’s for a good reason
use firefox, block most javascript
if shit doesn’t work because it’s garbage, try safari
if shit still doesn’t work because it’s unimaginably garbage, try chromium
if shit STILL doesn’t work because it’s beyond salvageable garbage, well it’s unsalvageable find a new solution: never use chrome
I’d say you’re being too lenient. Anything that doesn’t work in Firefox is unsalvageable garbage.
some APIs just aren’t available… i’m not sure about web bluetooth for example, but when i had a play with that a while back (because it was the easiest way to connect to a bluetooth device to hack around), i wrote some control software that was chromium only because firefox didn’t support that API
same goes for some of the crypto APIs
and when firefox blocked cross-origin cookies and a bunch of SSO solutions stopped working… they weren’t garbage, they just were built on technologies that other peoples abused and were later deemed insecure - but not for their use-case
it’s acceptable to write software that doesn’t support firefox if it’s for a good reason