Hacker Newsnew | past | comments | ask | show | jobs | submit | bjc's commentslogin

not true, BitBlt is still able to access screen content on Win10 & 11


Specifically, it can access screen content, but not window content. As in, passing in the desktop hwnd gets you a picture, passing in a different hwnd gets you a bunch of black. At least as of when I tried it a few months ago on Windows 10.


I was curious about this so I just tested it... some windows are able to be captured and some are black


Does the screen content contain all the windows that are visible, or is it the desktop image?


All of the windows visible on screen. For my use case, I was taking a screenshot of my app (for automated testing), so I ended up taking a full desktop screenshot and cropping it to the window.


Me too. I'm currently watching the emulator hacking playlist https://www.youtube.com/playlist?list=PLMOpZvQB55bfk92aBKZ8p...


write a HFT bitcoin bot


The exchanges charge 0.5% per trade. This isn't feasible once you look at the numbers.


Why wouldn't it work if the spread was high enough?


Sure. It would also help if the exchange took less than 10 minutes to execute trades.


Exactly. I'm writing a (low-frequency) arbitrage program in Clojure for fun, but the long confirmation time for BTC and the inability to move non-BTC currencies between exchanges greatly limits this in practicality.


throw-enough-sh*t-at-the-wall-and-something-will-eventually-stick method of software development :)


anyone know the font used in the example images?


[deleted]


It doesn't have the crazy f of Inconsolata. It's one of the Bitstream/DejaVu Sans Mono derivatives - I think it's Menlo.


the updater is self updating


but then doesn't this mean that parent^4's point is still valid? i.e.

  > What if an update silently breaks the update process? Hrm!
If the updater is self updating an update may break it so that no further updates are possible.


Sorry for slow response. I sure wish HN would mail me when people comment.

Sure, the updater can break itself. But in practice, you rarely update the updater because the majority of the features you might want to update are in the app, not the updater.

So you update the updater very rarely and cautiously, and you update the app quickly and fearlessly. It's not 100% foolproof, but it's a lot better than the alternative: Any crash bug anywhere in the application having the capacity to disable updates.


We use it. The server isn't open source, but it wasn't difficult to follow the protocol and create a Google App Engine app.


approx 11300miles for me, for last 4 years and loving it


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: