| Time |
S |
Nick |
Message |
| 09:45 |
|
|
sivoais_ joined #openknot |
| 09:55 |
|
|
sivoais joined #openknot |
| 10:05 |
|
|
sivoais joined #openknot |
| 10:15 |
|
|
sivoais joined #openknot |
| 10:25 |
|
|
sivoais joined #openknot |
| 10:35 |
|
|
sivoais joined #openknot |
| 10:45 |
|
|
sivoais joined #openknot |
| 10:55 |
|
|
sivoais joined #openknot |
| 11:05 |
|
|
sivoais joined #openknot |
| 11:15 |
|
|
sivoais joined #openknot |
| 11:25 |
|
|
sivoais joined #openknot |
| 11:35 |
|
|
sivoais joined #openknot |
| 11:45 |
|
|
sivoais joined #openknot |
| 11:55 |
|
|
sivoais joined #openknot |
| 12:05 |
|
|
sivoais joined #openknot |
| 12:15 |
|
|
sivoais joined #openknot |
| 15:09 |
|
|
sivoais joined #openknot |
| 15:11 |
|
dotplus |
pdurbin: I don't think that this is really in the area of openknot. Openknot is about allowing user-preferred messaging protocols. While there could be an analogue that allows user-preferred authn/authz, this isn't it. at least not yet. and given how little progress we've made on what *is* in scope, we're not in any position to expand the scope |
| 15:12 |
|
raucao |
hey, would anyone mind if we log this channel to a #kosmos #remotestorage account? |
| 15:12 |
|
raucao |
it would enable us to offer offline logs to kosmos users |
| 15:18 |
|
dotplus |
I don't see why not. It's already logged to http://irclog.greptilian.com/openknot |
| 15:19 |
|
dotplus |
you'd just be providing Linus-style backups:) |
| 15:20 |
|
raucao |
:) |
| 15:20 |
|
raucao |
ok, cool |
| 15:22 |
|
|
sivoais joined #openknot |
| 15:26 |
|
|
gregkare joined #openknot |
| 15:27 |
|
|
botka joined #openknot |
| 15:32 |
|
|
sivoais joined #openknot |
| 15:35 |
|
pdurbin |
yep, extra logging is nice. prologic even runs two of his own loggers in #circuits :) |
| 15:35 |
|
pdurbin |
gregkare: hi! |
| 15:37 |
|
pdurbin |
dotplus: but! you said I'd be able to use my preferred agent and paradigm! ;) https://github.com/openknot/openknot/blob/master/README.md |
| 15:40 |
|
gregkare |
Hey :) |
| 15:42 |
|
|
sivoais joined #openknot |
| 15:42 |
|
pdurbin |
here's where the extra logging goes: http://waves.kosmos.org/logs/freenode/openknot/today |
| 15:46 |
|
dotplus |
pdurbin: yes, but one step at a time, eh? |
| 15:48 |
|
dotplus |
I'm not saying that your suggestion is not desirable, it is. Nor am I saying that it's off-topic or inappropriate for openknot. I'm just sayig let's avoid scope creep until we actually have something to expand:) |
| 15:48 |
|
pdurbin |
yeah. I agree. you're good to point out that I'm really talking about auth |
| 15:49 |
|
pdurbin |
I guess I'm thinking back to when StackOverflow was launched in 2008 and Jeff Atwood was all like "why would we make people create a one off account?" He was right. |
| 15:52 |
|
|
sivoais joined #openknot |
| 15:55 |
|
dotplus |
sorta. But the other side of the argument has weight too: "We (that is, any serious service provider) should not rely upon mytwitface+in to provide authn services because their goals are not aligned with ours. Since it might be convenient for (some) users to use their mytwitface+in creds, perhaps it might be nice to support these authn services as an *additional* option, we must also provide our own". |
| 15:55 |
|
pdurbin |
dotplus: I knew you'd be willing to talk about auth. :) |
| 15:56 |
|
pdurbin |
it's fundamental to any communications platform |
| 16:02 |
|
dotplus |
yes, but in practice we can decide the issue (if not complete the work) with "we'll use authn that is abstracted/modular enough that our mvp has simple, self-provided auth as the first of a list of authn providers which can easily be extended to support others as people care to do so. |
| 16:02 |
|
|
sivoais joined #openknot |
| 16:04 |
|
pdurbin |
sure. that sounds great |
| 16:07 |
|
prologic |
pdurbin: haha |
| 16:08 |
|
prologic |
yeah that bot and it's code has proven to be rather stable :) |
| 16:08 |
|
prologic |
but yeah I do |
| 16:08 |
|
prologic |
kdb and irclogger |
| 16:08 |
|
prologic |
both capable of logging |
| 16:08 |
|
prologic |
kdb just has way more plugins |
| 16:11 |
|
pdurbin |
prologic: do they both write to the same place? |
| 16:12 |
|
|
sivoais joined #openknot |
| 16:22 |
|
|
sivoais joined #openknot |
| 16:32 |
|
|
sivoais joined #openknot |
| 16:42 |
|
|
sivoais joined #openknot |
| 16:51 |
|
prologic |
they actually kind of do - yes |
| 16:52 |
|
prologic |
well I mean they are both just as configurable |
| 16:52 |
|
prologic |
teh same code that irclogger uses |
| 16:52 |
|
prologic |
just got wrapped up into a plugin that kdb now incorporates |
| 16:52 |
|
prologic |
The nicer thing though is that kdb has a builtin web interface so you can view the logs pretty much striahg tup |
| 16:52 |
|
|
sivoais joined #openknot |
| 16:56 |
|
pdurbin |
prologic: they write to the filesystem right? (rather than a database) They don't clobber each others' files? |
| 16:56 |
|
prologic |
oh |
| 16:56 |
|
prologic |
I understand now |
| 16:56 |
|
prologic |
haha |
| 16:56 |
|
prologic |
no; both of those bots are running independently |
| 16:56 |
|
prologic |
it *is* possible to have distirbuted logging setup |
| 16:56 |
|
prologic |
but that would be distributed on the circuits event'ing side |
| 16:57 |
|
|
sivoais joined #openknot |
| 16:57 |
|
prologic |
i;e: connect two or more bots to different parts of the network; single process; *and* whichever event wins; writes to the log files |
| 16:58 |
|
pdurbin |
prologic: so currently they write to different files. ok |
| 17:55 |
|
prologic |
well they're running on different servers :) |
| 17:55 |
|
prologic |
I think |
| 18:27 |
|
pdurbin |
:) |
| 21:54 |
|
|
derbumi joined #openknot |
| 21:55 |
|
|
derbumi left #openknot |
