RayJW

Amazing work, that is exactly what I was talking about. Thanks, for looking into this! Looks like it's definitely worth considering. :)

I'll have a go at this if that's fine with everyone :) Can't promise a time frame though, I'll have to learn to deal with GTK first.

I was able to reproduce this issue for days over multiple packages, different networks, and different machines. I think is definitely Binstall related since turning off Portmaster results in immediate...

I built the binary with the options you mentioned added to the binstalk-downloader Cargo.toml. I did however leave the `optional = true` in hickory-resolver because it wouldn't compile otherwise. However...

> sorry we have some misunderstanding, I'm suggesting that this could be a hyper/reqwest bug, and @RayJW I recommended you to create a new crate, with the reqwest dependency: Sorry,...

@NobodyXu I did have to add the -S option to the Shebang, otherwise it won't run extra flags. It seems that actually works fine, the output looks like this: ```...

> I wonder if the reqwest options we set in binstalk-downloader makes any difference So, I did change the script to the following: ```Rust #!/usr/bin/env -S cargo +nightly -Zscript ---...

Wouldn't the best way to handle this be the [DynamicLauncher portal](https://docs.flatpak.org/en/latest/portal-api-reference.html#gdbus-org.freedesktop.portal.DynamicLauncher) to create the desktop entries? Also, the `TryExec` field can be handled in Flatpak. This is how the MS...

> Possibly, but that would have to be implemented separately from the ground up. Knowing how other portals work it's probably more involved and not a simple change to make...

> So from what I can tell it tries loading an existing desktop file and if none exists (or one exists but has no `TryExec`), it hardcodes the `TryExec` to...