![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
Already exist, it’s called hdr and almost all modern camera supports them. But they take more time.
Already exist, it’s called hdr and almost all modern camera supports them. But they take more time.
Probably airforce.
There are interviews with Ukrainian soldiers who said they stay away from civilians so that when Russians bombard them the civilians will not be affected.
I think the combat style and priorities are a bit different so a comparision cannot be made in this case.
It’s hard and expensive. The us-mexico border has the same problem and US spends like crazy to find tunnels. If the tunnel is bellow 5-10 meters I think it’s almost imposible [1]
In Gaza from what I heard they also only use hand tools to avoid making a lot of noise.
I manage to break 2 usb conectors in 1 year.
Israel os a Nazi state /s
It’s so simple when you can just say bullshit.
There have been concerts in war zones before(like ‘Screeam for me, Sarajevo’). And a small dance festival near an almost ‘peaceful’ border does not sound that bad.
Install mitmproxy and set the proxy settings to mitm. Maybe it will work.
For WASM you can probably use tools like ghidra to decompile and read.
Minified js not a lot better then raw ASM, single letter names and crazy optimisation patterns will make your life hell. Patching both I think is out of the question, maybe just inject some new js that interact with the DOM.
Did a bit of reverse engineering on binaries in my life, and also spent too much time reading the youtube minified js. Both are hard as hell.
There is one thing to not help a movie that you don’t agree with, and another to ban it. Apocalypse Now was made without the support of us military band was a success.
For comparision in the Genius of Carpathian Mountains’s country (Romania), everything had to pass censor’s.
https://www.military.com/off-duty/7-crazy-facts-about-vietnam-war-film-apocalypse-now.html
Probably its just a snapshot at some point, with maybe downloading new stuff when its published. At least thisbis how i’d do it.
Will have more when the sun explodes.
I mostly write rust now, but this workflow was finetuned over years. Use 2 terminals each on a diferent monitor, one runs neovim and the other is for building/running. If the project is a bit more complex, I will run it in a docker container( maybe mount the /etc/shadow and frieds so all artefacts are created using the same user as in the outside) . Developed a bunch of tools over the years to optimise this:
At my old job had to work on a remote vm so I setup sshfs for a while, but was slow and just moved all my tools there.
I have a pattern where i put all my projects in ~/dev/<project><branch> and all info related to a task in ~/dev/<project>/bugs/<issue_nr>. This is usefull because I can have scripts the work similar for different projects with small changes. For example to run my binary with the config for a issue i just do
ndock <branch>
nr <issue nr>
This will start docker or connect to an existing one for that branch if available, compile the code, run my binary with the config present in the bug folder. In the last few month started running it with rr to be sure i can debug any random issue.
Probably is a camera.