very cool.
-
@ariadne @lina i ship an FPGA toolchain in the browser. it can* use multithreading. it needs to know how many threads to run to not contend on resources uselessly
* currently not built in that configuration for a variety of reasons that is not specifically tied to the web
@whitequark @ariadne @lina Uh - cool, but it tells me "web assembly JSPI is not enabled". After enabling it in Firefox' about:config, it still says it's not enabled. Any ideas?
-
@whitequark @mcc @ariadne @lina Flatpak has a bunch of permissions one can grant, just saying ...
@hruske @whitequark @mcc @ariadne @lina
yeah and everything just gets full read write access to your home directory making because devs are lazy and body cares -
very cool. this is why i hate the modern web.
@ariadne oh that's nothing. Check this out
-
@whitequark @mcc @ariadne @lina Flatpak has a bunch of permissions one can grant, just saying ...
@hruske @whitequark great, now you can ship your app to… desktop Linux users (but NOT to Ubuntu systems which are the most common ones)
-
@hruske @whitequark @mcc @ariadne @lina
yeah and everything just gets full read write access to your home directory making because devs are lazy and body cares@tthbaltazar @hruske @whitequark @mcc @ariadne @lina regarding fingerprint metrics imma just throw in https://amiunique.org/fingerprint
-
@whitequark @mcc @ariadne @lina Flatpak has a bunch of permissions one can grant, just saying ...
@hruske flatpak takes granular permissions but it does not make them usable. Unless you expect the user to understand what "uses a legacy window system" means in terms of permissions. Sandboxing isn't easy, nor is seamlessly injecting permission prompts into applications which weren't designed for it, but the actually hard part is the permissions model. It needs to somehow be comprehensible by ordinary folks, while not overly constricting for 'power users'.
-
@whitequark @ariadne @lina why is webrtc locked behind the microphone permission. i know what the web browsers *claim* is the answer to this question but imo the real reason is that they set out to make a fully granular permissions model, immediately discovered that had downsides, and have been backpedaling ever since
(I acknowledge the fully granular model is what works best for your goal of shipping an FPGA programmer)
@mcc @whitequark @ariadne @lina I haven't really paid attention to what android and apple are doing these days, but i think a lot of this would be solvable by having some permissions be aggregates. e.g. "The web page wants to get the video calling and streaming permissions (fine print: which expand to blah blah blah and blah)". You unfortunately can't really let the application control the aggregate, but I think you could do a good job of simplifying the common use-cases for both apps and users.
-
undefined oblomov@sociale.network shared this topic