[02:51:33] EARNINGS WITH BITCOIN [02:51:34] https://t.me/joinchat/AAAAAE34IZIJY5TkcD4MKg [02:53:57] ...and again (re @Thecladis: Hehe) [02:54:58] It happens. Wikimedia general gets a couple of those a day, but with enouch timezone spread admins it is not a major problem [02:55:11] Much smaller problem than on wiki vandals fwiw [09:01:25] The Glossary says: [09:01:25] linearizer : a function to convert a ZObject to a string. [09:01:26] parser : a function to convert a string to a ZObject. [09:01:28] Is it correct to also add that a parser is the opposite of linearizer and vice versa? [09:01:29] The same is done for abstract <-> concrete and some other glossary entries. [09:10:33] Another Glossary question: [09:10:34] pair : a compound ZObject that contains two ZObjects of specific (but arbitrary) type. [09:10:35] The words "specific (but arbitrary)" are a bit confusing. [09:12:55] And in "an ID denoting the underlying object, i.e. the string "Z11" refers to the Type Z11/Monolingual text", I suspect that it was supposed to be "e.g." and not "i.e." :) [09:12:59] (But I might be wrong.) [09:14:08] /me [09:14:12] I think both i.e. and e.g. work, but e.g. would probably be better [11:57:30] I've just done it. Revert me if I'm wrong :) (re @amire80: The Glossary says: [11:57:31] linearizer : a function to convert a ZObject to a string. [11:57:32] parser : a function to convert a string to a ZObject. [11:57:34] Is it correct to also add that a parser is the opposite of linearizer and vice versa? [11:57:35] The same is done for abstract <-> concrete and some other glossary entries.)