It does matter -- he was one of the first "network developers". He published RFC 896 over 35 years ago; he has more experience on this topic than almost anyone.

> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.

This is not the strongest plausible interpretation of what he said --

He's not asking for people to not develop async code. He's asking for them to not hide it in synchronous code.

If you're expecting a blocking system call, and actually get a brand new background thread that's polling, it's quite reasonable to be frustrated.

You're replying to John Nagle, as in https://en.m.wikipedia.org/wiki/Nagle%27s_algorithm -- perhaps it would be worth considering his words further, before dismissing his concerns?

Surely we can all agree that spinning up unnecessary threads is undesirable?

YubiHSM 2 has worked fantastically well for us as a root of trust in a variety of applications, at a very reasonable price ($650) (I am unaffiliated with Yubico other than as a very satisfied customer).

Accessible over USB or HTTP, it supports every major crypto algorithm [1], and keys can be backed up onto another HSM via a wrap key (if they are marked as exportable -- you can also control what can and cannot be exported -- in fact, every operation may be allowed or disallowed per key).

Every operation is logged for audit, of course, and the device may be setup to require logs to be read before they are overwritten. In combination with configuring a special authentication key to access the logs, you can ensure that every operation on the HSM is logged to a remote store before additional operations may be completed.

It does depend on your existing physical security, so that has to be taken into account when designing architectures including it. The micro form factor at least makes it trivial to put into an internal USB port.

And of course, if you require a more enterprise grade tool, you may want to use an HSM in combination with a tool like Hashicorp Vault to manage your keys throughout your orgnaization.

[1] https://developers.yubico.com/YubiHSM2/Product_Overview/

You're absolutely right about the various advantages of pagers over cell phones.

On the other hand, all of that medical information goes over the air in plain text. It is trivial to capture and decode POCSAG [1], requiring less than $100 of hardware: a Raspberry Pi 3 has enough horsepower to handle the 2 RTL-SDR's needed to capture both the 929MHz and 931MHz bands.

Modern security simply demands that pagers go away (or at least be heavily modified). This is not a theoretical concern [2][3].

[1] https://github.com/pvachon/tsl-sdr

[2] https://www.rtl-sdr.com/art-installation-eavesdrops-on-hospi...

[3] https://openprivacy.ca/blog/2019/09/09/open-privacy-discover...

Levenshtein distance is a metric [1] and discrete metrics can be indexed with BK trees, taking advantage of the triangle inequality. For a detailed explanation, see [2].

I know of no real world implementation of this, however.

[1] https://en.wikipedia.org/wiki/Metric_(mathematics) [2] http://blog.notdot.net/2007/4/Damn-Cool-Algorithms-Part-1-BK...

It's possible to configure git so that git ush becomes git push; for example, this .gitconfig correct many common misspellings: https://github.com/AgalmicVentures/Environment/blob/master/c...

Obviously such corrections should be used judiciously.

Thank you so much for writing this. I've struggled with positioning for a long time, and although I have a niche, it was a challenge to communicate the value I offer in a succinct way. This nails it:

> You don't just deliver code. You deliver complete end-to-end solutions that don't require the customer to specify everything in excruciating detail. Instead, you're like an amazing machine to which customers only have to insert high-level business requirements.

Reading over the website, The Positioning Manual seems to have more actionable information than the sum of all other source I've found, so thank you for that too.

Yepkit [1] makes these! They have 3 port hubs for USB 2 and 3, as well as single port "hubs" -- all controlled through a simple command-line interface or Python API. They also have other good stuff like USB controlled relay boards and upstream USB hubs to switch devices between hosts.

I've used their products in a variety of automation projects for clients and at home, and have only good things to say.

[1] https://www.yepkit.com/

Would this still be covered under the original patent until 2029 [1]?

[1] https://www.google.com/patents/US8213745

Disclaimer: I am not an accountant and I am definitely not your accountant.

You are correct to say that you can contribute 25% of compensation. However, your wages are different than your profits, even as a self-employed person.

Let's say you are self-employed and you make $1 of profits and pay yourself $0.80 of wages. You can contribute the other $0.20 you have to your SEP-IRA, since it's 25% of your wages (or 20% of your profits).

Because of this, you need $275K of profits to generate $220K of income and a corresponding $55K SEP-IRA contribution.

For more, see: https://en.wikipedia.org/wiki/SEP-IRA#Reduced_rate

Disclaimer: I am not an accountant and I am definitely not your accountant.

Heads up that you can only contribute 20% of your earnings up (up to the limit) to a SEP-IRA. This is because you can contribute up to 25% of your taxable income, but your contributions are deducted from your income.

For example, if you make $1, and put $0.20 in your SEP-IRA, your taxable income is $1 - $0.20 = $0.80, so the $0.20 you put in is the full 25% of your income.

To contribute $55K in 2018, you will need to generate $275K of income.

Expanding on this, for anyone who wants to read more, http://www.2uo.de/myths-about-urandom/ is a good resource.

And to extend your thought further, should US based VC's be backing this? NSO is backed by San Fransisco based Fransisco Partners [1].

[1] http://www.reuters.com/article/us-nsogroup-m-a-idUSKCN0SR2JF...