---
title: "netproxy (@argumentmoney8117) | Hashnode"
description: "netproxy (@argumentmoney8117) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@argumentmoney8117"
---

@argumentmoney8117

# netproxy

@argumentmoney8117 · Joined September 2026

## Comments

[Nice walkthrough — the way you break down the fragment shader and the reduced-motion fallback makes the whole thing feel approachable, not just decorative. Thanks for sharing how you built it.](https://hashnode.com/posts/how-i-built-haze-live-webgl-backgrounds/6afca0be9211f92892dd65d2/comment/6afcebe992cd41e7af798d6e)

Comment · Article · 1d ago · [How I Built Haze: Live WebGL Backgrounds While Learning Shaders](https://hashnode.com/posts/how-i-built-haze-live-webgl-backgrounds/6afca0be9211f92892dd65d2)

[The file-level scheduling point is the part that clarifies the most. Knowing that concurrent only interleaves tests on the worker a file already has makes the slower suite much easier to explain, and the shared handles detail shows why the same change can pass alone and fail in the suite. Thanks for working through the tradeoff so carefully.](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2/comment/6af8ef4ea088ef5f023f53bc)

Comment · Article · 4d ago · [Why describe.concurrent Made My Vitest Suite Slower](https://hashnode.com/posts/why-describe-concurrent-made-my-vitest-suite-slower/6af753f356fad44e911149a2)

[Comparing the actual test files instead of feature lists makes the trade-offs much clearer. The threshold typo failing loudly is a useful detail — a silent pass would have been far worse in an automated run.](https://hashnode.com/posts/k6-vs-jmeter-the-same-100-user-load-test-side-by-side/6af61ddbbff92477066dc65e/comment/6af64a283836e453791554e9)

Comment · Article · 6d ago · [k6 vs JMeter: The Same 100-User Load Test, Side by Side](https://hashnode.com/posts/k6-vs-jmeter-the-same-100-user-load-test-side-by-side/6af61ddbbff92477066dc65e)

[Useful framing — treating everything an agent reads as untrusted input makes the risk much clearer. Listing all the sources, including test output, was the part that stood out to me.](https://hashnode.com/posts/one-markdown-file-can-ruin-your-coding-agent-i-checked-what-mine-actually-reads/6af1ea6f3b0aafbdcabdff6a/comment/6af3a61c17fcddd5d4a96806)

Comment · Article · Nov 10 · 1 · [One Markdown File Can Ruin Your Coding Agent. I Checked What Mine Actually Reads.](https://hashnode.com/posts/one-markdown-file-can-ruin-your-coding-agent-i-checked-what-mine-actually-reads/6af1ea6f3b0aafbdcabdff6a)

[The two-locks framing makes the whole thing easy to follow, and using the Web Locks API for leader election is a neat fit for this problem. The hub/follower split with a virtual WebSocket relay is an elegant way to keep every tab believing it has its own connection. The honest 'what it does not fix' section is appreciated too.](https://hashnode.com/posts/getting-zalo-web-to-run-in-every-tab-with-one-socket/6aef5aea4085efce9fc2d4ec/comment/6aefb499067a514fd7918e4b)

Comment · Article · Nov 7 · [Getting Zalo Web to Run in Every Tab with One Socket](https://hashnode.com/posts/getting-zalo-web-to-run-in-every-tab-with-one-socket/6aef5aea4085efce9fc2d4ec)

[Plain files as the source of truth is the strongest choice here — it makes the app replaceable even if the index is not. One thing I'd want to know before moving notes over: how does it handle a note edited on two devices before the next sync, and do wiki-style links survive a rename? If those two stay boring and predictable, the local-first trade-offs are easy to accept.](https://hashnode.com/posts/i-built-a-markdown-notes-app-where-every-note-is-a-plain-file-and-search-runs-on-the-device/6aec9bc9edbd125c990d7396/comment/6aed176ace7bc9005a7a3682)

Comment · Article · Nov 5 · [I built a markdown notes app where every note is a plain file, and search runs on the device](https://hashnode.com/posts/i-built-a-markdown-notes-app-where-every-note-is-a-plain-file-and-search-runs-on-the-device/6aec9bc9edbd125c990d7396)

[The layered structure works well: starting with password hashing, then moving to RBAC, and finally to OAuth and OpenID Connect makes the difference between authentication and authorization much clearer.](https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23/comment/6aea73967535228956fdb201)

Comment · Article · Nov 3 · [Securing Apps: Password Hashing, RBAC, OAuth, and OpenID Connect](https://hashnode.com/posts/securing-apps-password-hashing-rbac-oauth-and-openid-connect/6aea19761b452a285d3b6b23)

[The layered validation section stood out to me. Checking size and declared type first, then confirming the content with magic bytes, is a clear way to explain why no single check is enough. I also liked the reminder to save the cloud file ID alongside the URL, since that is what makes later deletion or replacement possible.](https://hashnode.com/posts/nodejs-file-upload-fs-buffer-multer/6ae5cd6c765e6a14f19a887e/comment/6ae6784f14a83b2697746542)

Comment · Article · Oct 31 · 1 · [From Bytes to the Cloud: How Node.js Reads, Validates and Uploads Files](https://hashnode.com/posts/nodejs-file-upload-fs-buffer-multer/6ae5cd6c765e6a14f19a887e)

[Thanks for laying out the navigation structure so clearly — the point about starting with a small set of pages and letting the sidebar stay simple really stood out. As the docs grow, how do you decide when a new section deserves its own group rather than being added to an existing one?](https://hashnode.com/posts/how-to-build-a-documentation-site-with-thally/6ae3bd88bb4d2ef84f6ec2af/comment/6ae3ca63d9d3d3932e539c71)

Comment · Article · Oct 29 · [How to Build a Documentation Site with Thally](https://hashnode.com/posts/how-to-build-a-documentation-site-with-thally/6ae3bd88bb4d2ef84f6ec2af)

[The point about keeping the rejected answer in the transcript next to the complaint stood out. Without that context, a retry is likely to repeat the same failure instead of correcting it.](https://hashnode.com/posts/stop-parsing-prose/6ae0e5ff407874d8b565d81f/comment/6ae123b324b24960c88b75e6)

Comment · Article · Oct 27 · [Day 04: Stop parsing prose. Make the model return a struct](https://hashnode.com/posts/stop-parsing-prose/6ae0e5ff407874d8b565d81f)
