Show HN: Run, learn, and debug x86-64 Assembly code directly from your browser https://ift.tt/2hndxRi

By Mustansir Malik
Show HN: Run, learn, and debug x86-64 Assembly code directly from your browser I recently created this project to teach assembly, and to have an assembly playground in the style of codepen/jsfiddle to embed in my blog posts. It's based on a wasm version of the blink x86-64 emulator, so everything runs client side with no backend server and with a runtime of only ~200Kb https://x64.halb.it/ October 18, 2024 at 11:02PM

Comments

Post a Comment

Popular posts from this blog

Show HN: Create a “rogue” WiFi AP & Captive Portal with a Raspberry Pi https://ift.tt/2AvGXHQ

By Mustansir Malik
Show HN: Create a “rogue” WiFi AP & Captive Portal with a Raspberry Pi This project makes a Raspberry Pi pretend to act as a WiFi hotspot with a captive portal. It does not actually provide an internet connection to connected clients, but simply triggers their captive portal detection, which causes them to present users with a browser window containing content of your choosing. I created this for security tinkering purposes, but also because I found the documentation for similar projects lacking. I've attempted to document and explain the salient points of the entire Raspberry Pi Linux configuration relating to the captive portal. https://ift.tt/P5Ycw94 March 24, 2023 at 03:20AM
Read more

Show HN: One API Key – Third-Party API Integrations with Zero Setup https://ift.tt/ivNOAB6

By Mustansir Malik
Show HN: One API Key – Third-Party API Integrations with Zero Setup Hey HN, we’ve been working on a way to simplify authentication with third-party APIs. This started because my co-founder andreterron ( https://ift.tt/vPZsm2A ) and I both built personal dashboards to track different health and productivity metrics, but it’s such an annoying chore to integrate with new APIs. First you read their docs to learn their authentication method, then build and deploy a custom server to receive OAuth callback requests or deal with CORS, register an app with them, then finally you can send the first request to their API. After the initial integration is done, you now have to refresh expired tokens, make sure that you’re respecting rate limits, and update the code if the underlying API changes. The solution we came up with is a proxy server, it forwards requests to the respective API with up to date auth tokens. Because of this: - Devs can use the full range of capabilities of the underlying APIs....
Read more