This project welcomes all high-quality contributions regardless of authorship method. However, we have some rules regarding the use of AI models. They basically come down to two things:
Humans must be the face of all communication with project maintainers and assume final responsibility for all contributions.
Tool-assisted contributions must include commit trailers noting what tools
| #!/usr/bin/env bash | |
| set -xeuo pipefail | |
| APPIMAGE_URL="https://updates.signal.org/desktop/signal-desktop.AppImage" | |
| SIGNATURE_URL="https://updates.signal.org/desktop/signal-desktop.AppImage.gpg" | |
| KEY_URL="https://updates.signal.org/static/desktop/appimage.asc" | |
| # Signal's published AppImage signing key fingerprint. | |
| EXPECTED_FINGERPRINT="4B16B7232DFAA439AD791002EF9F501F13EED94C" |
These standards use RFC2119-style keywords to denote requirements, with the understood caveat that interpreting many of these requirements requires greater subjective judgement than would be typical of an IETF standard. I have endeavored to restrict to the use of "MUST" and "MUST NOT" to those requirements that are both fairly objective and unlikely to admit any reasonable excuse for violating them. Nonetheless, this document cannot foresee every possible circumstance, so exceptions to "MUST" requirements may, rarely, be justifiable. However, in any such cases you MUST include a code comment which cites by its [TAG] what rule is being violated and how, and why conforming to it would be impractical.
Violations of "SHOULD" / "SHOULD NOT" requirements do not require such code comments, but similar justification SHOULD be mentioned in PR comments or (if you are an AI model) in the session transcript.
| ________ ________ __ __ ________ | |
| | \| \| \ | \| \ | |
| \$$$$$$$$| $$$$$$$$| $$ | $$ \$$$$$$$$ | |
| | $$ | $$__ \$$\/ $$ | $$ | |
| | $$ | $$ \ >$$ $$ | $$ | |
| | $$ | $$$$$ / $$$$\ | $$ |
Written in March 2023, predicting the state of the world in March 2028. Percentages denote confidence levels.
AI will be an enormous contributor to economic growth over the next five years, as important as the Internet was to the '00s. However, it will continue to be the case that AI's ability profile is spikey and
ΤΗ ΚΑΛΛΙΣΤΗΙ!
This is a sketch of a proposed NTPv5 design (by no means a complete spec, but hopefully good enough to make the concepts clear). It's a fairly ambitious step forward from previous versions, almost but not quite a green field design. I say "almost" because it retains a couple limited backward-compatibility constraints: