00:19:37 *** zest has quit (Ping timeout) 01:06:01 *** monod (none@cryto-41046937.retail.telecomitalia.it) has joined #crytocc 01:06:18 loggy, pointer? 01:06:18 http://wire.cryto.net/logs/crytocc/2014-01-11#T01-06-18 01:06:50 hi all 01:18:20 *** mama has quit (Ping timeout) 01:28:31 gotta go 01:28:33 *** monod has quit (User quit: ) 01:42:08 *** iceTwy has quit (Input/output error) 01:48:11 *** joepie91 (joepie91@cryto-3E6002EF.direct-adsl.nl) has joined #crytocc 02:39:09 *** Thor (numz@cryto-70E29873.torservers.net) has joined #crytocc 02:54:16 *** joepie91 has quit (Ping timeout) 03:05:05 *** tmbucky (tmbucky@cryto-A7509DED.us-west-1.compute.amazonaws.com) has joined #crytocc 03:06:26 *** tmbucky has quit (User quit: Connection closed) 03:28:48 *** joepie91 (joepie91@cryto-3E6002EF.direct-adsl.nl) has joined #crytocc 04:12:36 MK_FG: hai, your tahoe node seems down? 04:30:45 joepie91, Yeah, hdd bricked with some "ata2: SError: { UnrecovData 10B8B BadCRC }" 04:30:57 MK_FG: :( 04:31:07 Not the one with tahoe data though 04:31:18 Just the properly backed-up system 04:31:36 well to be fair, tahoe HDD bricking shouldn't matter :) 04:32:05 In theory ;) 04:32:17 Lots of tahoe repairs are pain! 04:33:42 It's weird how hdds are supposed to be better than ssd in lack of that "suddenly brick" scenario, but nope - same crappy controllers are now in both 05:30:50 *** Thor has quit (User quit: Quitte) 05:59:46 *** DrWhat (KepiaGod@cryto-270C699F.threembb.co.uk) has joined #crytocc 05:59:58 *** DrWhat has quit (User quit: Powered by fIRC v1.0.1 (r130) the Android IRC client.) 06:00:02 *** DrWhat (KepiaGod@cryto-270C699F.threembb.co.uk) has joined #crytocc 06:14:45 *** mint (mint@cryto-1DE70A98.dyn.optonline.net) has joined #crytocc 06:15:21 What is everyone's thoughts on Linux Mint? 06:16:16 I am curious. I've seen Joepie's blog a few times and I like his post on why windows doesn' 'work fine' 06:24:39 mint, its ok, i find it basic. 06:25:02 i last used it 3 years ago 06:35:24 battlelog.battlefield.com/bf3/servers/show/pc/b6a25a57-3129-44a2-a81a-cccae8b39bb6/Webhallen-01-Ziba-Tower-1000-tickets/ 06:35:34 how have they done that then 06:35:47 its a ranked server with punkbuster disabled 06:35:58 thats impossible 06:36:08 if pb is off ranking is diabled 06:47:24 any idea how to find all the places where my PATH is set? 06:58:10 DrWhat: Now it looks amazing. 06:58:25 The menu popup is awesome and slightly transparent 06:58:35 and terminal windows are low in opacity 06:58:37 mint: I've heard a few good things about Mint, but personally it's a turn-off for me that it's based on Ubuntu 06:58:51 pzuraq: how do you mean? 06:58:54 joepie91: It really isn't Ubuntu at all 06:59:08 all the places that your PATH is set to _in your current session_, or all possible PATH settings on your system? 06:59:35 mint: afaik they use a bunch of upstream stuff, and I don't like the (lack of) stability of Ubuntu :) 06:59:35 joepie91: Was trying to remove RVM but it kept showing up in the path. Restarted my computer and it's all good now :) 06:59:41 shoulda done that sooner 06:59:42 The windows look completely different, the settings are different, the bottom bar looks different 06:59:48 not even the same settings 06:59:49 I also don't think Mint has something like the opensuse build service 06:59:57 mint: don't care about looks, I run XFCE anyway 07:00:06 it's about the technical/functional aspect 07:00:14 in particular stability 07:00:23 pzuraq: RVM? 07:00:33 isn't that a Ruby thing 07:00:37 it's a ruby version manager 07:00:41 urgh 07:00:41 I prefer rbenv 07:00:42 yeah 07:00:44 well 07:00:48 I'm not sure which of the two it was 07:00:57 but either RVM or rbenv was a complete disaster last time I used it 07:01:10 rbenv is nice and simple 07:01:18 RVM seems to be terrible 07:01:22 I'm sure it makes sense to Ruby devs 07:01:29 but I'm not a Ruby dev and have no intention of becoming one 07:01:32 I just want to run $thing 07:02:04 anyway, mint, the issue I'm constantly seeing with Ubuntu is poor quality control of updates 07:02:10 both package updates and distro upgrades 07:02:36 my personal experience has been them shipping a non-wubi-compatible kernel to wubi setups 07:02:42 thus bricking the entire OS 07:02:47 (and they did that several times in a row, too) 07:02:57 joepie what distro do you like most? what is your linux of choice? 07:03:06 I've heard many update woes from others, and even package updates tend to wreak havoc apparently 07:03:12 mint: for desktop usage, openSUSE 07:03:14 Debian for servers 07:03:31 lm really looks like openSUSE i think 07:03:52 mint: it's important to realize that opensuse is not a single-environment distro :) 07:04:00 (and not, despite what people often say, a "KDE distro") 07:04:12 linux mint is primarily based on Cinnamon 07:04:20 and that is what you're assumed to use in most cases 07:04:33 opensuse ships with GNOME3, KDE, XFCE and LXDE 07:04:37 and all are basically equally supported 07:04:55 it used to be a KDE distro but that's a loooooong time ago 07:05:04 I think they stepped off that in 10.x 07:05:04 true 07:05:46 afaik Mint's "flavours" (XFCE etc.) are like Ubuntu's flavours 07:05:51 joepie91: Are the instability issues in Ubuntu that common? I've never had issues, always had it work ootb 07:05:51 technically they exist, as a separate distro 07:05:55 but you're not assumed to use them 07:06:02 and they're treated as "alternatives" rather than "options" 07:06:13 pzuraq: yes. 07:06:27 you might want to knock on wood :P 07:06:40 do you guys do foo == false or false == foo? 07:06:56 foo === false 07:06:58 >:P 07:06:59 :P * 07:07:27 Ari: the first one 07:07:41 most people do 07:07:48 second is just typo padding i guess 07:08:45 Ari: the idea behind value == variable is to prevent accidental assignments instead of equality testing 07:08:57 because false = foo will throw a compile-time error 07:09:02 yeah exactly 07:09:09 but like 07:09:10 why not 07:09:16 !foo 07:09:31 I dot that a lot 07:09:39 but given that A. that makes no semantic sense and B. one of the languages I work in lets you redefine True and False (Python) and C. there's no such thing as "compile time" in the languages I use.... that is kind of pointless for me 07:10:03 also, is fugly 07:10:06 :p 07:10:09 wait what 07:10:12 pzuraq: see A 07:10:23 I thought they removed assigning to t/f in python.. 07:10:30 Ari : in Python 3, yes 07:10:31 I use Python 2 07:10:46 aah. 07:10:47 why not 07:10:47 !foo 07:10:51 this is not always as raedable 07:10:52 readable * 07:10:52 so 07:10:54 if not foo 07:10:58 instead of 07:11:01 if foo == false 07:11:02 it's sometimes better to write it out explicitly, for clarity and ease of reading 07:11:12 not seems even clearer 07:11:12 False, not false 07:11:13 but yeah 07:11:14 but yes 07:11:15 not 07:11:15 i understand 07:11:17 is the way to go really 07:11:19 mhm 07:11:28 but in languages where it's !, that's often not very readable 07:11:32 it depends on the language really 07:11:39 there's not one right cross-language answer 07:13:19 I read ! as not now 07:13:28 so if there is no not, I go for ! 07:13:43 but that's because I have spent too much time with JS 07:13:51 pzuraq: keep in mind that you should be writing what is most readable to _people_, not to _you_ :) 07:14:02 similarly, always keep in mind that you're developing for others, not yourself 07:14:09 true 07:14:22 (which is almost always the case - even personal projects tend to be copypasted into public stuff later on) 07:14:29 and I like to think my code is very readable and sensible 07:14:45 so which would you use, !foo or foo == false? 07:15:01 I normally go for foo === false in PHP/JS 07:15:10 in Python, usually 'not' 07:15:27 mm 07:15:33 oh, by the way 07:15:37 pzuraq, http://thejh.net/misc/website-terminal-copy-paste 07:16:38 joe does cphp support mod rewrite 07:16:55 DrWhat: define "support mod rewrite" 07:16:59 joepie91: Yeah, saw this once 07:17:00 also cgit is 500 ing 07:17:05 slightly terrifying 07:17:12 DrWhat: quite possibly, cgit is kind of shit 07:17:38 there, fixed 07:17:43 pzuraq: indeed 07:18:05 i want to make a minamilstic blog both in code and looks 07:18:27 but also want to make it seo freindly eith uri rewriting 07:18:32 DrWhat: look into Haml and Sass 07:18:34 it's beautiful 07:18:46 ok tha ks 07:19:01 DrWhat: you don't need URL rewriting for that 07:19:13 but yes, CPHP does what you want 07:19:16 that's what the router is for 07:19:48 only httpd config is a FallbackResource (Apache 2.4+), fallback mod_rewrite rules (older Apache), server.error-handler-404 (lighttpd) or whatever the equivalent in nginx is 07:19:58 CPHP handles the rest of the parsing etc. 07:20:55 ok 07:47:22 *** Ari has quit (User quit: Leaving) 08:12:53 *** ElectRo` (x@cryto-11FFD52D.foebud.org) has joined #crytocc 08:16:29 *** Cryto111 (Cryto111@cryto-596113D.rev.sfr.net) has joined #crytocc 08:18:46 *** mint has quit (User quit: Leaving) 08:19:32 *** Cryto111 has quit (User quit: Page closed) 08:43:58 lol 08:44:05 there was a guy i. here called mint 08:44:18 i bet hese pissed with how many times you guys said mint 09:00:13 never knew you could do this as a file: http://www.cyberciti.biz/faq/linux-add-a-swap-file-howto/ 09:37:26 *** zest (zest@F1987B83.AC927571.8EAF9109.IP) has joined #crytocc 09:48:40 *** zest has quit (Ping timeout) 10:12:20 *** DrWhat has quit (Client exited) 10:23:56 *** zest (zest@cryto-14F170CB.snydernet.net) has joined #crytocc 10:27:30 *** zest has quit (Ping timeout) 10:40:28 *** Moh has quit (Ping timeout) 10:42:33 *** iceTwy (iceTwy@iceTwy.users.cryto) has joined #crytocc 10:43:57 ah, well, this is one of those sad days again 10:55:23 *** Amineddz (Amineddz@B9CDCD9A.715D7A33.1896E47.IP) has joined #crytocc 10:57:09 *** oka (oka@7CB60438.4DDE2936.AC87F901.IP) has joined #crytocc 10:57:39 هيه 10:58:17 hi oka 10:58:23 صحيت 10:58:44 IP rahi hexadicemal kho 10:58:55 مايهمش 10:59:00 اي بلاد ميكي 11:01:31 wth wach dkhl blad micky yaw 3bad micky 11:02:13 منعرف بصح يبان سخون الحال ليوم 11:03:51 قالك باربعاد راح يجي البرد 11:03:56 سميقري ربي يستر 11:04:24 ان شاء الله 11:04:41 ياي مابقاش لمان ياو 11:04:59 مع برنامج يصور الشاشة ماتسلكش خلاص 11:05:23 ويندوز يصور وحدو تلقائيا ساعات 11:09:00 ايفون وﻻ اندرويد كيفكيف 11:09:47 what 11:10:06 oka, amanda_s4942, I'm pretty sure you're in the wrong channel 11:10:26 ههههههههههه 11:10:49 اسمع انا مانيش مالف ندردش هنا بزاف 11:11:16 بسك الناس مايعرفوهاش 11:11:51 oka, I have no idea what you're saying 11:11:55 but this is an English channel 11:12:33 علاه ماتروحش تبيع اللفت مش خير؟ 11:12:41 اي بلاد ميكي 11:18:21 *** crytoweb372 (crytoweb37@7CB60438.4DDE2936.AC87F901.IP) has joined #crytocc 11:18:38 *** crytoweb372 has quit (User quit: Page closed) 11:18:45 *** oka (oka@7CB60438.4DDE2936.AC87F901.IP) has joined #crytocc 11:18:59 بصح مش حكاية خلاص 11:19:07 oh jesus christ 11:19:30 hi all what you have for subject here ?? 11:19:36 .welcome Amineddz 11:19:36 Amineddz: welcome to #crytocc! Please be aware that this channel is publicly logged, and make sure to read the rules in the channel topic. You may hide messages from the public logs by prefixing them with [off]. 11:23:44 *** foolex has quit (Ping timeout) 11:24:08 http://owely.com/01nlLyB 11:24:10 whoop 11:25:58 *** crytoweb207 (crytoweb20@cryto-91A00DD0.torservers.net) has joined #crytocc 11:26:14 صاي رجعت !! 11:26:23 *** foolex (foolex@5D6B0912.EC145393.9A74EEF1.IP) has joined #crytocc 11:26:41 علاه مايسيبورتيوش العربية هذو 11:27:24 you have got to be fucking kidding me 11:27:37 crytoweb207: get the fuck out 11:27:55 لاه تع باباك هذي؟ 11:28:40 مليحة نحط روبو هنا ونخليك تودر وقتك معاه 11:29:42 *** foolex has quit (Ping timeout) 11:29:57 *** crytoweb824 (crytoweb82@5F0885F8.545AC356.4472014D.IP) has joined #crytocc 11:30:28 HI 11:31:24 .welcome crytoweb824 11:31:25 crytoweb824: welcome to #crytocc! Please be aware that this channel is publicly logged, and make sure to read the rules in the channel topic. You may hide messages from the public logs by prefixing them with [off]. 11:32:33 what do you talk about here ? 11:33:05 i think about D-Link Devices UPnP SOAP Telnetd Command Execution ! 11:33:09 crytoweb824: programming, mostly. 11:33:26 Amineddz: read the rules in the topic 11:34:00 where is Topic ! joepie91 11:34:15 ... 11:34:21 Amineddz: it's on your screen. 11:34:29 at the top of the page. 11:35:04 Ok im sorry , 11:35:41 Cryto Coding Collective 11:36:38 kach ZD's hna 11:38:03 *** Amineddz has quit (Ping timeout) 11:38:48 ) 11:38:56 *** crytoweb824 has quit (User quit: Page closed) 11:45:04 *** foolex (foolex@5D6B0912.EC145393.9A74EEF1.IP) has joined #crytocc 12:05:03 *** ttmbRAT (ttmbRAT@cryto-705F0D89.us-west-1.compute.amazonaws.com) has joined #crytocc 12:06:24 *** ttmbRAT has quit (User quit: Connection closed) 12:09:41 *** zest (zest@cryto-5270CF27.rev.poneytelecom.eu) has joined #crytocc 12:31:23 *** zest has quit (Ping timeout) 13:00:24 *** foolex has quit (Ping timeout) 13:04:53 erm. 13:10:27 *** foolex (foolex@5D6B0912.EC145393.9A74EEF1.IP) has joined #crytocc 13:24:26 hai iceTwy! 13:24:43 iceTwy: http://remotestorage.io/ 13:26:22 joepie91: wtf Intel: http://www.theverge.com/2014/1/6/5282472/intel-announces-edison-a-computer-the-size-of-an-sd-card 13:30:09 iceTwy: tbh, I don't see what the fuss is about 13:31:21 bb 13:31:22 brb * 13:34:45 *** DrWhat (KepiaGod@cryto-270C699F.threembb.co.uk) has joined #crytocc 13:34:53 weeee 13:49:27 back 13:49:28 hai DrWhat 14:25:28 *** DrWhat has quit (Client exited) 15:08:35 *** iceTwy has quit (Ping timeout) 15:17:48 *** foolex has quit (Ping timeout) 15:20:30 *** foolex (foolex@5D6B0912.EC145393.9A74EEF1.IP) has joined #crytocc 15:29:59 Every single sd card kinda have a computer in it already ;) 15:37:40 *** hrh23 has quit (Input/output error) 15:38:03 *** hrh23 (trubo@hrh23.users.cryto) has joined #crytocc 15:43:49 The information that a client needs to receive in order to be able 15:43:49 to connect to a server SHOULD reach the client as described in the 15:43:49 'bearer token issuance' sections below. It consists of: 15:43:57 why do they always need to use complex grammar in specs 15:44:05 absolutely no need for that 15:48:24 Hm, are you writing remotestorage.js backend? 15:52:32 MK_FG: planning to, yes 15:52:47 my brain tuned out at section 11 15:53:09 I think they actually simplified it since 2011 draft 15:53:22 Recall it being much longer 15:53:30 When the user gestures she wants to use a certain application whose 15:53:31 manifest is present on the dashboard, the dashboard SHOULD redirect 15:53:31 to the application or open it in a new window. To mimic coming back 15:53:31 from the OAuth dialog, it MAY add 'access_token' and 'scope' 15:53:31 parameters to the URL fragment. 15:53:37 ... URL fragment? 15:53:46 that makes no sense 15:53:56 That means after # 15:54:01 I know 15:54:01 Accessible to js 15:54:20 Oh, you mean why it's "MAY"? 15:54:24 is it even possible to issue for example a 301 redirect to something with a URL fragment 15:55:13 I'd think it should be rather 302 in this case 15:55:21 er 302 15:55:26 question remains 15:55:27 But should be possible, of course 15:56:50 To prevent man-in-the-middle attacks, the use of https instead of 15:56:51 http is important for both the interface itself and all end-points 15:56:51 involved in webfinger, OAuth, and (if present) the storage-first 15:56:51 application launch dashboard. 15:56:51 bah 15:59:02 Where the use of bearer tokens is impractical, a user may choose to 15:59:02 store documents on hard-to-guess URLs whose path after 15:59:02 starts with '/public/', while sharing this URL only 15:59:02 with the intended audience. That way, only parties who know the 15:59:02 document's hard-to-guess URL, can access it. The server SHOULD 15:59:02 therefore make an effort to detect and stop brute-force attacks that 15:59:02 attempt to guess the location of such documents. 15:59:06 ................ 15:59:08 why 15:59:11 Amazingly enough, 2011 spec seem to be still supported, just "deprecated" 15:59:11 for $deity's sake 15:59:14 is there not a 'public' flag 15:59:35 I do not like security through obscurity being literally in the spec 16:00:11 Is it really? 16:00:18 MK_FG: yes, see aove 16:00:20 above * 16:00:24 I mean, token is also part of the same http request 16:00:26 Same as url 16:00:27 everything is available through a public URI 16:00:28 no 16:00:32 tokens don't count for public reqs 16:00:37 that relies entirely on not being able to guess filenames 16:00:40 and does not allow listing dirs 16:00:51 public reqs are 'anonymous' in that they do not require any form of auth 16:00:56 and apparently all docs are public by default 16:00:57 And tokens rely on not listing tokens 16:01:00 and there is no way to make them not be 16:01:09 Tahoe also relies on unguessable urls, for instance 16:01:17 MK_FG: not quite 16:01:28 tahoe separates the unguessable URLs from the human-readable filesystem 16:01:35 remoteStorage does not 16:01:42 thus you get to pick 16:01:45 either sensible names 16:01:50 or unguessable gibberish 16:02:12 Um 16:02:29 So you have unguessable gibberish as an url of some file in both cases 16:02:43 MK_FG: no, you don't 16:02:47 Sure, you can build a nicely-titled link wherever 16:02:51 in tahoe you can have a base directory 16:02:58 with a sensible filesystem structure 16:03:07 you cannot do that with remoteStorage without foregoing security 16:03:08 Base will still have gibs 16:03:14 which is fine if it's hardcoded 16:03:17 in a config 16:03:18 or whatever 16:03:36 the problem is the lack of an abstraction 16:03:48 from a developer point of view, this is a nightmare to do securely 16:04:01 because you need to keep track of all your files separately 16:04:51 and that doesn't even touch on the fact that tahoe-lafs has secure random cap generation 16:05:00 Hmmh 16:05:02 remoteStorage provides 0 resources for that 16:05:02 *** hrh23 has quit (Ping timeout) 16:05:05 and in almost all cses 16:05:07 cases * 16:05:11 people will end up doing insecure crap 16:05:18 this is an awful idea 16:05:20 *** hrh23 (trubo@hrh23.users.cryto) has joined #crytocc 16:05:33 brb 16:07:48 I think I see your point 16:09:21 Wonder if you can even address such thing sanely in a spec though - describng some specific algo to generate such caps and store file metadata sounds almost like a book of tahoe docs in the spec ;) 16:20:35 MK_FG: hence, public flag 16:20:43 entire problem solved 16:20:54 you already have to store the content-type anyway 16:20:59 so some kind of metadata store is required 16:21:15 might as well have a 'public' flag that indicates whether it may be accessed over the public URI 16:22:58 Um, but the whole thing with unguessable urls is to be able to link the thing from wherever directly 16:23:07 MK_FG: ? 16:24:52 Well, the way I kinda-remember it, /public/ is for stuff you want to link directly, and it's app's or user's (if app delegates that) pick if you use (or should use) unguessable name there so it won't be that kind of public 16:25:23 MK_FG: and a flag is a worse solution because...? 16:25:28 So sure, you either get security or a nice name there 16:26:02 And if you store stuff under "/wherever/guessable_whatever", you don't get security with a flag either? 16:26:13 (if you still want it to be linkable) 16:26:33 ... 16:26:37 (if you still want it to be linkable) 16:26:42 the point of it not having a public flag 16:26:45 is that it isn't linkable 16:26:49 :| 16:26:58 and only accessible over an authenticated interface 16:27:36 Mmm 16:27:47 Still trying to parse that 16:28:34 By "public flag" I think you mean some attr you can set for URL so it'd be "public", no? 16:28:55 by public flag I mean that the object can be accessed over the /public/ interface which does not require authentication 16:29:06 Any object? 16:29:08 if it is not set, it can only be accessed over the regular (authenticated) private interface 16:29:15 any file node 16:29:18 or data node, rather 16:31:11 And url of that node under /public/ should be generated securely as specified in spec? 16:31:36 not necessarily 16:31:39 Or it'd be /public/my/data/node 16:31:40 if it's public, it's public 16:31:47 so the guessability won't matter 16:31:55 if it's not public, it wasn't accessible through the interface in the first place 16:33:02 Oh, so you argue that there only needs to be fully-public-or-not thing, no "public if you get a link only" thing 16:33:30 So no point in such obfuscation 16:38:41 MK_FG: https://github.com/remotestorage/spec/issues/57 16:38:45 MK_FG: pretty much 16:38:52 hell, add ephemeral URLs if you want 16:38:55 but it's not even necessary 16:39:03 that would significantly complicate the spec 16:39:13 as you'd have to deal with expiry and all that crap 16:39:46 Also two urls to same thing doesn't sound like a good idea in general 16:40:20 Hmm 16:40:54 I didn't get "was somewhat unpleasantly surprised to find that apparently all files stored in a remoteStorage endpoint are publicly accessible by default" from all of the above ;) 16:41:16 ah 16:41:19 oh 16:41:20 sarcasm? 16:41:20 idk 16:41:24 sarcasm + internet = boom 16:41:34 brain failure beep beep beep 16:41:42 "Where the use of bearer tokens is impractical, a user may choose to store documents on hard-to-guess URLs whose path after starts with '/public/' ..." 16:42:01 I hope I'm misreading 16:42:06 So unless you choose to store stuff as public, you most certainly don't have to 16:42:28 I actually recall addressing the similar thing for performance... 16:42:56 https://github.com/remotestorage/django-remotestorage#storage--webdav -- check out "Do not" at the bottom there 16:43:45 man 16:43:48 this is all too confusing 16:43:51 they really need to clarify this :P 16:43:59 So you can misconfigure stuff to not check Auth header, but otherwise you can't just access anything... 16:44:13 it's also not like the /public/ interface is documented in the API docs or anything 16:44:16 :| 16:44:39 MK_FG: I'm still torn on how to interpret it 16:45:47 I'm probably as confused at this point by all above as you are and not sure what we're still talking about :P 16:46:02 haha 16:46:04 So guess I'll shut up to not add any more of it 16:46:26 *** x (foobar@C35CA8A8.589C91BA.8F6A2B14.IP) has joined #crytocc 16:47:14 https://storage.5apps.com/joepie91/public/shares/140111-1646-housey.png 16:47:15 meh 16:49:12 Actually, I think I might be misleading you as I only know 2011 spec, and latest one might just allow everything - I just don't know it 16:49:29 That django thing is for 2011 spec, never got around to updating it to support latest one 16:49:42 mmm 16:49:56 MK_FG: unrelated, do you know of anything for Tornado in terms of OpenID server 16:50:10 or am I going to implement my own again 16:50:10 lol 16:50:18 not sure I want to but okay 16:50:19 No, never touched openid really 16:50:44 Did you look at Persona thing btw? 16:51:20 meh 16:51:28 OpenID iirc forces a rather inferior (to Persona) schema with some extra unnecessary lock-in, but I don't recall more specifics 16:55:18 mm 16:55:24 guess I'll have to read more tomorrow 16:57:12 I probably was reading it bad, but iirc I got "aha! that's why it's better" moment not while *reading* how it works, but watching Dan Callahan (of mozilla) talk about it at some conf 16:57:46 I think it was like 30min and explained it perfectly, but that's just my xp, of course ;) 16:58:45 (or maybe it was more useful because there was explicit openid comparison and brain works better at comparing to something known already) 16:59:54 MK_FG: https://github.com/remotestorage/spec/issues/57#issuecomment-32100963 17:00:00