all ports above 1024 are by default blocked
Not on localhost at least no it isn’t.
And why the hell would you be using ftp in currentyear. Newsflash: They also ditched gopher.
What actually annoys me about all browsers are the policies around loading certain stuff from file://
. Try getting something wasm to run without serving the thing from a web server or, *shudder*, base64-encoding bitcode into html. I understand there’s some valid gripes around …/ and softlinks and whatnot but, wait, here me out: What about zipping everything up and calling it a webapp, treat the file as a domain.
Anti_Face_Weapon@lemmy.world 11 months ago
That’s really strange, I haven’t encountered either of those problems. The ladder you can blame your distro for. If Firefox was bundled with all of the codecs it would be really big for no reason, and it would be redundant on nearly every system.
earmuff@lemmy.dbzer0.com 11 months ago
Kinda agree, sure it is also a distro issue. Chromium-like browsers worked out of the box, though. In the end, the user should not really experience easy-to-fix problems like „I can‘t watch any Twitch streams“, and I‘m not really on a uncommon distro (OpenSUSE Tumbleweed).
lemmyvore@feddit.nl 11 months ago
Neither
network.security.ports.banned
nornetwork.security.ports.banned.override
are defined by default in Firefox so I suspect the distro set them for you. Same for FTP. And I’ve never had any issues playing Twitch streams.earmuff@lemmy.dbzer0.com 11 months ago
Generally curious how that would work. So how/why should a distro do that?
The port issue is a common one if you google it and I even had it in windows. The variable is empty because you set the exceptions there. No value = all ports are blocked.
Anti_Face_Weapon@lemmy.world 11 months ago
I recommend that you can play to the OpenSUSE forums.