captncraig

Entertaining, but ironic that I got no less than 3 pop ups from Medium to read this post.

Every time I switch back to exception languages, I get this tendency to "assume everything succeeds all the time, and handle it at the very top level in case any part of it fails". I do not think about what can go wrong at each level nearly as much as I do when I am required to use `if err != nil` soup.

Every time I see a cool post about GitHub actions I get real sad because I've been waiting since the announcement and still have no beta invite. Is there some trick to gaining access?

Would taking down patlive really change anything other than shifting the physical call center to India?

Well its a school. They (or their legal guardians) consent as a condition of using the network.

That payload is... a lot of teslas worth of cargo. It would need to be built in orbit. A project that size would definitely make a lot of jobs and require a major rebuilding of our space problem. So many downsides.

I just really hated the setup. All amazon would repeat was "We're bringing thousands of jobs! Look at all the big projects we promise to do!"

Well why is trusting you to build parks better than just spending your tax money on parks? Why do we need a new indirection in that process?

I'm imagining some kind of machine-learning training set based algorithm for determining the ancestry percentages. Even at 99.6% difference (due to mutations over time or sampling error) over 700k samples there's gonna be ~300 sequencing differences between twins. Enough to make their ML system draw different inferences for sure.

Unfortunately it's much more common for a player to leave from a losing position without resigning. It's hard to solve that problem without hurting commuters in the crossfire. I also play on the subway, but I stick to correspondence or classical depending on where I am. I usually have 10-15 correspondence games open, and long format is an amazing way to improve your game without worrying about time sensitive connection issues.

There's a line that might open you up to being sued over it. Ridiculous as that would be, I wouldn't really be surprised if the right lawyer in the right court could pull it off.

Let's encrypt can issue certs without needing a public route to your machine if you use the dns challenge. Here's what I do:

1. Add a public A record (or host file) local.mydomain.tld to 127.0.0.1.

2. Host my dns with cloudflare (other providers have plugins too), and install the caddy plugin to do the dns challenge for certs.

3. Caddy can then get certs for local.mydomain.tld and serve them locally.

Those licences are only for the binaries. The source is Apache licenced and can be used for commercial purposes for free.

Not Let's Encrypt, but you can run behind cloudflare's free plan for https.

Shameless plug: https://github.com/StackExchange/dnscontrol is a provider independent way to manage your zones with a single dsl style file in source control.

Just changing IPs is not enough if the new allocation is publicly linked to your company. It may help to get IP space through a third party or shell company to anonymize it a little more, and make sure it is never publicly identifiable as yours, either in paperwork or through scans.

Is warp just "railgun" rebranded? That worked well for my company, when it worked.

Go templates are not particularly fast, but I would be astonished if the client-side way one that battle.

There are faster server-side template engines in go though. One approach I particularly like is https://github.com/bouk/statictemplate, which generates code from your standard go templates that makes them quite a bit faster.

Sadly, not completely. A surprising nonzero number of users have isps that insist on using their own root cert to inject this nonsense.

Do you own a huge block of IPs or something? We have a massive monster cert in order to support non sni on a single ip. I hate it.

It's an ad hominem attempt to deflect attention back at the attacker. Being wrong is hard to deal with, so you change the subject. It is a fairly subconscious reaction.

We don't really have the "one class one file" beat into us like in java or c#. That means you gotta think a little to see how a package naturally splits up. Some people are better at that then others.

I wouldn't use that repo as a representative of what "go code looks like". Most go repos are pretty similar in "structure", but I really don't know how to navigate this. The 'src' directory looks like the author is really fighting the gopath concept, but also trying to vendor dependencies. I agree, if my hook was "in xx lines of code" I would try to avoid boilerplate and keep it all together as much as possible.

This is awesome to see. There's been a lot of articles about zork lately, so I started writing my own interpreter, just to see what all the fuss is about. It's a pretty interesting system. I'm currently trying to step/debug through zork too see how they implemented the parsing, game state, and other such things, and it is really quite interesting.

I've considered trying to do a hardware implementation, but concluded it is beyond my skill. Some things like user input can be complicated. It is the interpreter's job to split the input on a program-defined set of delimiters, look up each token in a dictionary provided by the program, and copy a variable number of specified values it finds base on that info into other locations. That's really complicated for a single instruction, and makes it pretty apparent to me that their target from the beginning was interpreters, not any kind of special hardware.

Nevertheless, its an awesome project, and a really fun thought experiment. I'd love to see a physical version of something like this from 74xx chips.

But if you have the phone can't you just put the sim in another phone and read texts?

So they're done, right? Why should we not immediately un-trust their root?

We actually wrote a tool to manage this. We define our desired records in a common dsl format, and the tool can interact with various providers to ensure things match the expected state.

We should be open sourcing this rather shortly, so stay tuned.

Sorry, I'm not who you asked, but that is how we are doing it at stack overflow now.

One major issue with their dns was unpredictable lag while changing records. On most occasions we can change a record and it would propigate immediately. In some rare cases, it could take fifteen minutes, and in a few instances up to eight hours before the change would show up on their nameservers.

Cloudflare was unable to diagnose this or give us any comfort that it would improve.

The tricky part is making sure the apex NS records are consistent across all authoritative nameservers. A surprising number of dns providers do not let you edit those.

We have a pretty cool tool for managing this at Stack. Changing from a single provider to two can literally be done by changing one line of config. We should be open sourcing it very soon, and a blog post on it sometime thereafter.

You are misunderstanding how DNS works. Just because I can get a google cloud name server to point example.com at my server does not mean I own the domain. The gcloud nameservers are not the authoritative nameservers for the zone unless the root .com registry points at them.

Google apps verification only asks the nameservers designated by the registrar for the domain.