

I think IETF BCP 47 is the way to go for this (and is rougly a superset of what you’re saying). They also define a “more/less specific” selationship between tags so you can ask for “en-CA” and have the system decide “en” is still appropriate.


I think IETF BCP 47 is the way to go for this (and is rougly a superset of what you’re saying). They also define a “more/less specific” selationship between tags so you can ask for “en-CA” and have the system decide “en” is still appropriate.
These days I think OMEMO is a better choice than OTR, if your client supports it.
What makes you think that Christians, as a whole, deny science?
Another application of Parse, don’t validate. The vulnerability isn’t really about the single-line regex, it’s that the validation doesn’t match the use. If the regex extracted (read: parsed) the valid bit with a group, then passed that through, it would be fine.


This is not true. In fact, Guix doesn’t use systemd at all. When managing an operating system installation Guix uses its own init system called the Shepherd.
Elogind is a project extracted from systemd originally for use in Guix systems.


Here you go: https://adnauseam.io/
Zulip is pretty great.