Posts - noperator| noperator.dev
I wanted to write this before I’ve been out longer than I’d been in. I agonized over my decision to leave the Air Force—largely because I experienced it as an issue of professional identity. Why I joined After wrestling at a high school math and science academy, I wanted to keep up physical fitness and develop leadership skills in a technical environment. I also needed financial assistance to fund college.| Posts on noperator
Google recently launched the .zip TLD, and Twitter has been up in arms. It’s hard to imagine that .zip domains would be used for anything legitimate, and would instead give way to more creative phishing attacks. Accordingly, I quickly snagged source-code.zip while these domains were rapidly being bought up, and showed an example of how it might be used to trick a software developer into downloading a malicious ZIP file—yet there are still some that quite reasonably ask, “Should we reall...| Posts on noperator
Or, using a content aggregator like it’s 1999. Daniel Miessler writes a lot—and a lot of that lot is about RSS. Daniel inspired me to curate my media intake with RSS (and also more generally to start writing learning in public). Here are a few RSS-related tools and principles I’ve picked up over the past 6 months. It essentially boils down to discovering new content sources via Twitter, etc., and using a content aggregator (and supporting tools) to bring those many sources into a single...| Posts on noperator
I recently (finally) started using online appointment scheduling software. There are many players in this space, but Calendly is the most popular and featureful. It’s awesome—but in order to use it, you have to give it direct access to whichever calendars you want it to check for conflicts. That means access to all sensitive details like online meeting URLs, attendee information, etc.—and it gives me the creeps. This isn’t unique to Calendly as most booking software works exactly this...| Posts on noperator
There are two claims I’d like to make: LLMs can be used effectively1 for listwise document ranking. Some complex problems can (surprisingly) be solved by transforming them into document ranking problems. I’ve primarily explored both of these claims in the context of using patch diffing to locate N-day vulnerabilities—a sufficiently domain-specific problem that can be solved using general purpose language models as comparators in document ranking algorithms. I demonstrated at RVAsec ‘2...| noperator.dev