Sounds too complicated to do with a reasonable type system and autocomplete, should probably use ML.

Can we then write off the motorcycle sim racing rig as office equipment?

One of the problems with forcing strictly disparate domain/service is that each one introduces its own security context and authZ handling. That's a lot of places for mistakes.

My platform team supports devs with a proxy that handles authN & authZ. Service to service is secured using mTLS automatically.

I’ve stated it previously in the thread - you need to enforce conventions through tooling - which is where “devops” (ugh, I know, but really...) comes in to play.

We try to view the tooling platform as just another DDD domain.

I think they stated that distributed security is more work / harder than monolithic security. I would tend to agree.

In my experience, the reason it is more work is because you end up with something much more well defined and robust.

Each service having well scoped and defined RBAC or AuthZ for its focused set of features makes the whole architecture as a whole much easier to reason about from a security standpoint. I've done successful pen testing and auditing of some monoliths in my time where the critical security issues arose out of untested and unexpected execution paths that were only possible because the surface area is so large.

Maybe in theory a "well written" monolith would be superior but I'm only going but what I have seen in practice. I think the extra work is worth the trade off.

just use auth0

Looks like you can sign up just fine with only an email address.

This looks pretty close to a clone of the Sequel gem.

http://sequel.jeremyevans.net/ https://github.com/jeremyevans/sequel

Sequel has much more advanced features than this Python library.

I learned about it from creack (lead contributor according to github) @ a startup meetup in SF.

Things that impressed me:

1. super passionate

2. he was very receptive and quick at squashing bugs I reported (real or not)

3. docker was super portable (the same across all linux distros)

4. they (the docker team) had real solutions for the long application deployment times that were plaguing me

Everyone seemed to know it would succeed, which is rare around here.

I assume when Jordan gave them his address they knew he would actually want the stuff...

The primary downside to a small TTL is cost. For many DNS providers you are allotted a number of requests per month that DNS will resolve. On particularly popular websites having a ton of DNS requests can cause the cost of DNS services to inflate significantly.

It takes just as many people to fly a robo-F16 as it does to fly a manned F16. Only difference is that the pilot is on the ground instead of in the air.

Also the unmanned F16 provides 0 advantages over a purpose built UAV (plus is bigger, slower, and more expensive), I highly doubt anybody would seriously consider these for warfare applications.

It's cool tech, take it at face value.

I imagine it can carry a bigger payload, so there's that advantage. Apparently we have a bunch of them in storage too, so it might be cheaper to convert them than to build new UAVs. It must be, if they're cheap enough to use for live target practice. Better to turn them into UAVs than let them rust while we build new UAVs, or sell them to other countries.

I don't know how much bigger that payload will be. Assuming the components to turn it into a UAV weigh 0 lbs, you're talking about a ~160 lb pilot in a 26,000 lb jet.

In case you ever see my reply: I was thinking that the F-16 is much larger and more powerful than a typical UAV, so it's built to carry more ordinance. But, I know next to nothing about the different military jet versions. I've since read in other comments that the F-16 was primarily a fighter-intercepter and not a fighter-bomber, so I guess it carries guns and air-to-air missiles rather than heavy bombs.

You are forgetting about all the life support systems that no longer need to be included / maintained. Oxygen tanks, ejector seat, etc.

>Only difference is that the pilot is on the ground instead of in the air.

Seems that removing humans from harm's way on one side of the conflict would have pretty big implications wrt high level decision-making.

>I highly doubt anybody would seriously consider these for warfare applications.

Are you saying that Iarger fighters no longer have utility as opposed to purpose-built UAVs?

Beyond all the life support you can now remove, the unmanned can now pull G's that would be unsustainable for a manned plane.

Isn't that the point of OAuth? (versus HTTP basic auth)

Your secret key shouldn't be compromised, because you're supposed to keep that secret. Also if you use HTTPS for requests you'd still get a cert error even if DNS was routing incorrectly. You're probably fine.

Indeed, I misspoke and meant to say tokens/refresh tokens. A similar thing happened for Evernote a while back and knocked down all tokens and required re-authentication across the board.