Can the mods please ban this person?

@ry_brink , your posts would be more interesting to me and perhaps others if you published the source, and spoke about interesting challenges, nice solutions to problems, stuff you learned, nice things the API’s you’re using do, etc. etc.

This really excited me, so I bought the pro version, but it crashes the moment I sign in

What are you asking? If Bob is “subletting” an IP to Joe, how could you possibly detect that reliably? Providers are supposed to include accurate information in whois, but the system relies entirely on trust and many people submitted false information even before the days of AWS.

I like this idea, but on busy release days don’t you find it a little noisy? I’ve never tried using ForceCommand - I’m guessing it would work the same for automated connections via ansible as it would for interactive use?

Also, I’d put the ssh-wrapper script somewhere like /usr/local/bin and make it writable only by root.

I’d almost be tempted to filter out automated connections so that only the rare/notable interactive logins are posted to Slack. But then maybe the gain of not desensitising the channel to regular harmless logins isn’t worth the risk of an attacker disguising their harmful interactive session as a regular deployment.

At first I saw the “How it Works” section and thought “Hey! They are going to ruin the connections for the rest of us!” but then I read the blog post and the claim is it won’t increase congestion. I guess by providing a smarter congestion algorithm that uses more information than packet loss for determining congestion.

I guess the main idea is don’t slow down if you see packet loss if other signs point to no congestion. And that seems really cool.

How does this work? The “How It Works” section is too high-level for lobste.rs, but if there’s a paper or something else more technical I’d love to read it.