with atomic swaps that make use of taproot, that wouldn't be distinguishable from, say, opening a lightning channel, but still, there's not enough liquidity there (and this is very recent stuff anyway)
You could have a third bot that posts a comment in the thread each time You could have a second bot that posts a comment in the thread each time with something like: "See, this is why you shouldn't use hosted services for your core infrastructure." Lots of karma to be had there as well.
Maybe I'll sound stupid, but is it possible to force an update of a chrome extension without removing it and then adding it again from the store? Is that application-specific?
> In v5.0 we decided to improve this experience by adding a new active provisioning system that uses config files. This will make GitOps more natural as data sources and dashboards can be defined via files that can be version controlled.
Yay!
For me the best two things of the release:
- dashboard folders
- dashboard provisioning
> In 2017 alone, 434 linux kernel exploits where found, and as you have seen in this post, kernel exploits can be devastating for containerized environments. This is because containers share the same kernel as the host, thus trusting the built-in protection mechanisms alone isn’t sufficient. Make sure your kernel is always updated on all of your production hosts.
I've been using the "same" technique with some projects I have but just to outline specific components of the system such that it becomes more clear what interacts with what.
For me, the best that I got out of it was having to think hard about those relations and improving the documentation of the subject.
I'm particularly excited about the advance of the Container Storage Interface (CSI).
Having developed two custom docker volume plugins I wonder whether Docker is going to adopt it for its cluster offering (swarm mode) or leave it aside as it did with CNI (real question). Anybody knows about it?
When I first read the article I was under the impression that now one would be able to connect a zone with an autoscaling group (and, as you mentioned, avoid allocation internal ELBs), but it looks like it's really just some sugar on top of the existing API.