That is funny imagining the sheer noise! Luckily it's just me in the room with the keyboard.

Great to hear you like yours! The different Ctrl key location and no super/windows key have been the most noticeable for me so far.

Yes, the lack of a windows key can be a little annoying - I have F8 mapped to it in my soarer's converter config, which seems to be a pretty convenient location. And I have yet to encounter any software where F8 does something super critical that can't be remapped

Coincidentally, there was a HN post about it today: https://news.ycombinator.com/item?id=25025035

I just dropped a blog post covering how I restored one of the original Model F keyboards: https://news.ycombinator.com/item?id=25029571

Article was perfect timing for me. The company I work at started one of these and I'm in the middle of trying to grow an idea/product. Great food for thought for long term strategy / positioning if it does go anywhere.

A very beta Python API client to interact with Gumroad's API for sweet automation workflows. Not all of the endpoints and HTTP verbs supported by the Gumroad API have been added yet.

It's refreshing to see the page focused on security and your approach/philosophy: https://abridge.io/security/

Did you proactively add that or have customers requested it?

Thanks! It's nice to get that feedback.

It's proactive, but I've been working in various security-oriented IT roles for ~15 years now, and I'm trying to take my own advice [1], so I'd hope I can do it justice. :)

[1] https://chair6.net/startups-and-security-questionnaires.html

Good stuff, thanks for the link!

Yeah, realized that a few months later...must have unconsciously suppressed the nightmare of taking those tests.

Didn't know renaming a repo was this straightforward in Github: https://help.github.com/en/github/administering-a-repository...

Scantron is a distributed nmap and masscan scanner comprised of two components. The first is a Master node that consists of a web front end used for scheduling scans and storing nmap/masscan scan targets and results. The second component is an agent that pulls scan jobs from Master and conducts the actual nmap/masscan scanning. A majority of the application's logic is purposely placed on Master to make the agent(s) as "dumb" as possible. All nmap/masscan target files and nmap/masscan results reside on Master and are shared through a network file share (NFS) leveraging SSH tunnels. The agents call back to Master periodically using a REST API to check for scan tasks and provide scan status updates.

There is also a Python client for interacting with the Scantron API and driving automated workflows.

> It puts the onus on the employee, rather than the Security team to stop phishing attacks

Hits the nail on the head right there. Phishing simulation training (both externally paid and internal) is a way for organizations to say they are at least trying to do something to minimize the #1 attack vector. Plus, it's cheaper than actually tackling the problem at the technical level (tweaking/updating email rules/settings) with whatever email defensive appliance is (or isn't) being used.

I launched PhishBarrel (https://phishbarrel.com) based on the thesis that most phishing emails can be identified using technology, and if one gets by, having a robust API for investigations, security automation, and/or remediation is table stakes in today's security products. If you're serious about upping your organization's email phishing defensive capabilities, please reach out to me (email is on phishbarrel.com site). I'm looking for forward thinking infosec folks that are looking for a partner to tackle this problem!