sup.

@prologic (#nsvyaxq) Makes me wonder what you’re referring to with Configuration. Is this a live flag that splits application’s code paths? Is this a plumbing piece that teaches a proxy how to reach the backend? Is this a declaration of dev/stg/prod? What’s the scope?

(#nsvyaxq) and then has the ability to cobble together informative outputs in order to aid that sticky communication issue problem. eventually, the process is so complicated that you're better to just make a whole new deployment to change a single config value and, frankly, that becomes the safest, most repeatable, most understood method and easiest to assign to the owning dev team. I think it's a big reason for K8's growth: avoid the communication issues.

(#nsvyaxq) the one we need is the one that resolves sticky communications issues between arbitrary deployment technology choices with completely skew practices. that is to say, take beanshells for the worst example, you suddenly need: 0) declarations to point to arbitrary executables that give 0/1 responses 1) endpoint to check the live deployment status 2) endpoint to flush current configs to disk 3) audits all config changes 4) endpoints to load configs from a spot on disk or from the expected config file 5) source control history of config values and changes, like a ChainMap

So many best parts of Bluey. I love all the neighbors just rolling with it. The whole show follows the rule of improv: "yes, and..."

(#3wfr7ba) @kt84 means the same thing over here, and Hi! good seeing you! :D

@prologic (#tgmogmq) :D don't have an account

@prologic (#tgmogmq) this is to say, FEC & data duplication solve different problems. Disaster Recovery is possible with data duplication, but a bug in your FEC code and no duplication will prevent it. Use case matters because is your def of HA going to be 99.99% or 99.999%? The first can be single-instance mysql. The second, a cluster. More, and you start stepping into things like TiDB or Spanner.

@prologic (#tgmogmq) my read on reed-solomon erasure encoding is its the generalized implementation of raid 5, that replication factor is about the data stored's complete replica count ignoring any capabilities of recovery through FEC. If you're trusting your FEC, then you'll be happy with replica-counts of 1. HA, of course, is dependent on use case. CAP teaches us to sacrifice Availability, but you can make very HA systems and keep C & P. Block size? I assume that's about compression's effectiveness - you'll get better compression with more data.

pi-hole up and running :D todo: learn about DHCP, use dns-over-https, expand raspberrypi responsibilities to route all traffic through it and have it use a vpn, ensure I can switch what endpoint I'm using from my phone.