If it's JSON it sounds more like config than code. Does it actually need to live in the GitHub repo? Could your application read it from an external location (where ever the rest of your configs live) and reload it on an API call or periodically?
The certificates have a validity window that sshd also checks. So the CA can sign a certificate for a short window (hours), until the user has to request a new one.
To tag onto this, modern means OpenSSH 7.2 (released February 2016) or newer. Currently running an enterprise-wide SSH certificate service, and trying to push people along to update their old VMs in preparation for this deprecation.
I think not quite everyone was affected, it was supposedly 147M people. You can check if your information was included in the breach on the settlement site.
Yeah, but they got to gradually develop "Slack Kit" and release a blog post patting themselves on the back for doing so to fulfill a 5 year old feature request. You can't just do that in CSS!
The whole field feels like such a mess to deal with what basically boils down to text/numerical data. You could probably spend the rest of your life just writing parsers to consolidate different data formats. I truly don't believe healthcare will be solved by technology until there is a single ubiquitous format. It's really a problem of policy, and I won't purport to know the answer or who should be solving the issue, but I don't think it's ever going to be solved by one person at a keyboard.
There are standards such as HL7/FHIR, but in my experience, most companies incorrectly or partially implement the spec, and then it might as well be something else.
"Obviously a few notifications were dropped. If a few notifications weren’t dropped, the system may never have recovered, or the Push Collector might have fallen over."
How many is a few? It looks like the buffer reaches about 50k, does a few mean literally in the single digits or 100s?