You can probably use luksHeaderBackup and luksHeaderRestore to make sure your recovery key will always work with the volume. Although I've never tried it so don't take my word for it, it should be pretty easy for you to try out.
Not that it will prevent any dedicated user with root rights from locking you out of the data if they wish to. It just raises friction from a simple luksRemoveKey
Apparently the AGC only had 36,864 words of rom. Looking at a random file from the github repo, each page seems to contain 50 lines. So if you put one instruction (one word) per line you could fit the whole rom inside 738 pages (assuming there's no optimization during assembly). Add some space for the comments and blank lines, and 1516 seems about right.
In any case it's doubtful a single program spanning the whole pile could fit in the AGC rom.
Their workaround of "To communicate with other people that don't use End-To-End, you will need to either generate a key in GnuPG and then import it" wouldn't make much sense if ETE wasn't able to import and interop with RSA keys already. You can also find an rsa implementation in the repo (https://code.google.com/p/end-to-end/source/browse/javascrip...) that would indicate that they do support RSA encrypt/decrypt. However I can't find any DSA implementation, I think there could indeed be issues with people using DSA/ElGamal keys. (which is weird because there is an implementation of ElGamal, probably the DSA implementation is still being worked on)
The OP might have stumbled upon this while searching the web for apple's metal, if that's the case it shows that the naming collision could be a good way to have people discover the product unexpectedly.
There are also some translations, you can compare with this translation : http://books.google.fr/books?id=ThC5OoAisaMC&pg=PA21&lpg=PA2... of the same page: on the last line, page 21, you can read "Il cache à la fois le dieu des mers et cette faible mortelle" (It hides both the god of the sea and this weak mortal) and on the mystery document, left margin : "Il cache le dieu et la mortelle" (It hides both the god and the mortal). There are a few other plain Greek -> French translations.
I think you would ask yourself : can I compute this at compile time? (And is it useful to do so?) I don't really see how you could use that for a database driver, but for example you could create a library that uses macros to generate custom serialization/deserialization code to/from json (or whatever format) for your data structures.
(Edit: after a quick check this use case seems to be already covered by #[deriving(Encodable, Decodable)] in rust.)
You could use macros to perform compile-time checking of SQL query strings (and checking of any arguments bound to the query, as long as they're bound immediately instead of being bound later).
What if the signals emitted from inside the horizon do reach your head, but only once your head have crossed the horizon?
Basically, you can change your reference point and consider that the signal is not moving, but your head is still moving towards the signal. This way, you're still seeing your legs.
(Note that I have no idea what I'm talking about)
The way I read article 4 3 b) I think the registry is allowed to terminate a ___domain name when the ___domain holder stops being eligible.