I feel you. I've written quite a lot of Common Lisp over the years and I've tried to show off its capabilities to co-workers, often in comparison to the language used that that job.
Often I just get "huh, that's neat, now let's get back to mining the coalface".
I think the biggest issues involved around knowledge/skills/intelligence being potentially linked to genetics is that it often draws the eugenics proponents into the discussion and it's obvious how that conversation ends.
Even in binary you can see patterns. Not saying it's perfect to show binary diffs (but it is better than showing nothing) but I know even my slow mammalian brain can spot obvious human readable characters in various binary encoding formats. If I see a few in a row which doesn't make sense, why wouldn't I poke it?
Pure speculation but my guess is a specific state actor ahem is looking for developers innocently working with open source to then strongarm them into doing stuff like this.
I find the standard blackbox_exporter far too limiting and static so I wrote an exporter which queries DNS zones from the Google API and creates targets dynamically from that.
It also has a feature which will query internal databases to find expected targets (kinda like service discovery). This covers more specific checks than what the DNS-based targets will provide.
These together mean that essentially no endpoint in our infrastructure is missing from being monitored in some fashion.
The exporter performs SSL checks (lifetime remaining etc) as well as providing HTTP/TCP latency metrics.
Not American but I can't stand using the toilet in places which don't have bidets. I feel disgusting and it ruins my day completely. I'd rather be uncomfortable and wait til I'm home or not go out.
I think this mostly comes down to whether applications can handle downtime if their workloads are restarted, scale up/down based on demand.
It happens shockingly often that applications only support working with a single replica and even worse when those applications cannot run concurrently with replicas of themselves which prevent smooth rolling updates.
IME if applications are fault tolerant of restarts, or support concurrent replicas then scaling up and down to meet demand is absolutely fine.
TVR back in the day was literally for British hooligans. The car was built on a small scale in Blackpool of all places to compete with much higher-end manufacturers.
The fact that the end game for TVR was handled so poorly doesn't and should never retroactively change what the company's mission was, which was to build powerful British-style sports cars for enthusiasts.
Being a Blackpool lad myself - the first day I saw a TVR Tuscan roll out of the Bispham factory will be something I never forget.
They were working class heroes back in the day. They were approaching affordable for a lot of people, raw, powerful and styled in an otherworldly way.
The loss of TVR is a loss for all car enthusiasts. I don't think we'll see another manufacturer like them.
> Most likely Snapchat's E2EE is just a facade, they probably have a dictionary of "funny" words on the device (and/or the server) and automatically flags the message in the internal systems when certain stopwords are being used.
Reminds me of whenever I used to phone a friend during my teenage years I would always start with "BOMB QUEEN, BOMB QUEEN."