**** BEGIN LOGGING AT Wed Jan 11 03:00:02 2017 Jan 11 03:22:05 http://venturebeat.com/2017/01/10/inside-project-ara-googles-revolutionary-modular-phone/ Jan 11 06:56:43 pabs3: people still occassionally come here; I'd prefer #openmoko to be redirected to #openmoko-cdevel. Jan 11 06:59:08 I'd redirect both to something else Jan 11 07:02:12 btw, totally offtopic but I can't just figure it out, the Debian wiki recommends to use subkeys and to store the primary signing key somewhere offline in a secure place. But should it be protected by a passphrase? And if yes, how to remember it if it's used so rarely? Jan 11 07:03:57 one option would be diceware and or storing the passphrase on paper with copies in a few secure places Jan 11 07:05:41 I also do not understand if it makes sense to store it on external stm32 device with gnuk (and flash reading protected) or if I'll just have more problems than it's worth. Jan 11 07:08:43 And I should have at least two devices like that to have a backup? Jan 11 07:09:01 I'm clearly missing some "best practices" document. Jan 11 07:09:45 there is this, but it doesn't cover anything like what you are asking about: https://help.riseup.net/en/security/message-security/openpgp/best-practices Jan 11 07:09:55 Yes, seen that. Jan 11 07:10:06 But I'm struggling with practical implementation :) Jan 11 07:10:57 paperkey is another example of a backup solution Jan 11 07:11:15 I'm considering using http://wiki.stm32duino.com/index.php?title=Blue_Pill as I do not see how e.g. FST-01 is any better. But I can't understand if it's worth it at all. Jan 11 07:11:27 also https://joeyh.name/code/keysafe/ Jan 11 07:16:38 Even if I did have a safe at home, then I guess I'd keep the key at home as well, so it'd not be really secure either. Jan 11 07:25:53 Another related question: http://pgp.mit.edu/pks/lookup?search=fercerpav%40gmail.com&op=index&fingerprint=on how it might have happened that the 8-bit key id is the same? I do not remember doing anything special. Jan 11 07:28:11 IIRC someone uploaded the evil32 dataset to the keyservers: https://evil32.com/ Jan 11 07:28:25 so you may have got caught up in that Jan 11 07:31:07 pabs3: aha, thank you, that explains it. Jan 11 15:00:53 pabs3: how does it make sense to "close" a channel and redirect users to a new non-existing one? Just because of channel name?? :-o Jan 11 15:01:11 that's plain silly Jan 11 15:02:05 channel "renaming" is one of the most complicated and futile actions on IRC Jan 11 15:03:24 even more fultile and complicated than domain name change for a well established URL/site Jan 11 15:04:15 for the latter you at very least have CNAME. which you can sustain forever. No similar thing on IRC Jan 11 15:05:55 doing what you suggest would result in 2 channels becoming 3 (2 old ones plus the new one) Jan 11 15:07:27 PaulFertser: redirects are always only temporarily Jan 11 15:58:35 I'll eventually set up a forward from this channel to #openmoko. This may (and will) fail for some users under certain circumstances - e.g. they might have blocked forwards Jan 11 16:00:13 please consider reconfiguring your autojoins accordingly. Keeping both channels on autojoin doesn't usually hurt - can get cleaned out after a few months when this channel moved over to #openmoko completely Jan 11 16:02:27 please contribute to merging both chan /topic into one, not losing relevant info. Simply post suggestions to #openmoko Jan 11 16:03:29 thanks! Jan 11 16:59:22 DocScrutinizer05: uh... did you capitalise #Openmoko in the topic on purpose?... Jan 11 16:59:53 no, except for nicer looks. It doesn't make a difference Jan 11 17:00:34 meh, I think it's more confusing than anything :-) **** ENDING LOGGING AT Thu Jan 12 03:00:01 2017