chore: add louzt to joined.md#127
Open
louzt wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Onboarding Request
Hello Uncoded team! 👋
I am submitting this Pull Request to officially join the organization by adding my name and username to the
joined.mddirectory.I was highly impressed when exploring your ecosystem. Unlike standard starter hubs, your choice to curate and fork production-grade, heavy-duty codebases—such as
SecLists,CyberChef,sherlock, andfreqtrade—is a brilliant way to cultivate real software engineering skills.About Me:
I am a Systems Architect and Software Engineer running LOUST. My day-to-day work centers on Go, Rust, C, and advanced TypeScript (Next.js / Astro / Bun). I focus closely on low-level infrastructure substrates, multi-protocol networks (TCP/UDP/QUIC), and local AI agentic runtimes. I also handle private and public vulnerability triage and upstream core hardening (like patching memory layer vulnerabilities inside NGINX core or solving Wayland race conditions).
How I look to contribute:
I would love to connect with fellow engineers here and act as a technical sounding board or mentor. Given your vast collection of security, networking, and automation repositories, I can offer deep, adversarial peer reviews regarding data isolation, algorithmic execution bounds, and secure protocol compliance. I’d also love to share advanced discovery platforms like CLOTributor (https://clotributor.dev/) with members looking to scale directly into complex cloud-native environments.
Let's collaborate and analyze some excellent architectures! Feel free to audit my open-source tools or connect with me directly on LinkedIn. 🚀