- moparisthebest has left
- moparisthebest has joined
- Lance has joined
- Lance has left
- Tobias has left
- Tobias has left
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- jere has joined
- Zash has left
- jere has left
- Zash has left
- SamWhited has left
- ralphm has left
- moparisthebest has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- Flow has joined
- ralphm has left
- daniel has left
- daniel has joined
- Kev has joined
- Tobias has left
- Tobias has left
- daniel has left
- daniel has joined
- Zash has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- jere has joined
- jere has left
- jere has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- Tobias has left
-
Tobias
I won't be able to make it to todays council meeting. Would be great if someone else could chair the meeting this time.
- jere has left
- jere has joined
- daniel has left
-
Tobias
or we postpone it to next week if there's nobody else to chair
-
SamWhited
I'll do it
-
SamWhited
Unless someone else wants too; but happy to so that we can have a meeting
-
Tobias
great, ta. Will read the logs tomorrow then.
- ralphm has left
- jere has left
- jere has joined
- daniel has left
- peter has joined
- Flow has joined
- Zash has left
- Tobias has joined
- Zash has joined
- Flow has joined
- peter has left
- Flow has joined
-
SamWhited
The time is come.
-
SamWhited
Who's here?
-
daniel
Me
-
Link Mauve
Me too.
-
SamWhited
I see no Dave
-
SamWhited
But we can muddle through
-
SamWhited
1. Minutes Taker?
-
daniel
since JC isn't here I can do it
-
SamWhited
perfect
-
SamWhited
2. Entity Caps 2 ProtoXEP https://xmpp.org/extensions/inbox/ecaps2.html
-
SamWhited
Any discussion before we vote?
-
daniel
+1
-
SamWhited
I'll be on list
-
daniel
SamWhited, do you think there is something that should be discussed?
-
daniel
regarding just updating entity caps 1?
-
SamWhited
daniel: Not in particular; I still need to read it again, I only briefly scanned it
-
Link Mauve
daniel, whether we accept it as a new XEP or as an update to 0115, mostly.
-
SamWhited
Since 0115 is already in draft and this is radically different in some ways (I think?) I'm inclined to think this needs to be a new XEP personally.
-
SamWhited
But since it's only the three of us, maybe we should save that for list discussion along with the outstanding votes?
-
daniel
ok
-
Link Mauve
I am of the same opinion, other XEPs currently “depending” on 0115 should be updated to say something like “use 0030, or any caching mechanism like ecaps2.”
-
Kev
I maintain that I think a new XEP here is more trouble than it's worth :)
-
Kev
I don't think it's conceptually any different to 115, is it?
-
Link Mauve
It’s not.
-
SamWhited
Let's discuss on list since so many people aren't here. Link Mauve: will you create a thread for this in response to the minutes being sent out?
-
Link Mauve
Ok.
-
SamWhited
Thanks
-
SamWhited
3. LC for XEP-0333
-
SamWhited
The LC has ended, but I think Daniel wants to submit changes before we vote?
-
daniel
SamWhited, just let it fall out of LC back to experimental again. i need more time than a week or so
-
SamWhited
Will do; moving to the editors column.
-
daniel
i guess we can formally vote -1 if necessary
-
Link Mauve
WFM.
-
SamWhited
If the author (or steward) says it's not ready that sounds like enough to me personally :)
-
SamWhited
4. Vote on advancing XEP-0233 version 0.5.1 to Draft
- Holger has left
-
SamWhited
I'm +1
-
daniel
+1
-
Link Mauve
I’m +1 too.
-
SamWhited
Others to vote on list; excellent.
-
SamWhited
5. Several PRs relating to CSI/Carbons state after SM resumption
-
SamWhited
https://trello.com/c/IR0c5nfq
-
SamWhited
I think the PRs listed on this card need our attention
-
SamWhited
I'm not sure that there's anything to do but mention that they exist
-
SamWhited
Only the 0198 one needs council, if I understand this correctly
- ralphm has left
-
daniel
i'm not sure that's a good idea
-
SamWhited
Which one? Maybe I should have broken this up
-
daniel
by adding that you are basically forcing the carbons ns bump
-
daniel
the one about 0198
-
daniel
by delegating the responsibilty to the individual XEPs you requrie namespace bumps on those xeps
-
SamWhited
I'm unsure if I think it helps or hurts, but I sort of think the 0198 change is unnecessary either way.
-
daniel
i'm not even sure where the idea that a carbon state or a csi state is undefined after a resumption comes from. is it really?
-
daniel
did this ever cause unexpected behaviour in real life?
-
daniel
or a dissagreement between server developers?
-
Link Mauve
This sounds more of a design problem of nonza than something that needs to be specified that way, actually.
-
SamWhited
I'm not sure if it's ever actually caused problems, but I do think it's undefined (and we should probably not leave behavior undefined)
-
Kev
I'm not entirely sure I understand why this is an issue at all.
-
Kev
Sure you're resuming everything in the same state it was in before?
-
Kev
The point of 198 resumption is to pick up where you left off.
-
Kev
*Surely
-
SamWhited
That was always my assumption
-
daniel
but you enable feature X (csi, carbons what ever) for a *stream*. and then you resume a s*stream*
-
daniel
why would that be gone after a resume?
-
Kev
Surely this is a one-line editorial fix in 198 to make this clearer, if it's possible to misread it if you squint hard?
-
daniel
so i don't agree with the notion that this is undefined behaviour
-
daniel
or what Kev that
-
SamWhited
I think I agree with Kev; do we want to vote on the 198 changes in their current form today (even if we're all on list) and then consider an alternative if necessary later?
-
daniel
but it should be up to the carbons or csi xeps
-
daniel
SamWhited, we are talking about #429 right?
-
daniel
just to be sure
-
SamWhited
Yes, sorry
-
Holger
The CSI state has to be reset because the CSI nonzas cannot be acknowledged.
-
daniel
*but it should NOT be up to the (in case that wasn't clear from the context)
-
Holger
So if a CSI nonza was sent before resumption, the client wouldn't know whether the server processed it.
-
SamWhited
ah right, that makes sense
-
Holger
This was the reasoning for resetting the CSI state on resumption.
-
Zash
Is the CSI state attached to the TCP-bound stream or the resource/long lived session?
-
daniel
Holger, but that's an orthogonal problem
-
moparisthebest
how can you *ever* be sure the server got the nonza and enabled CSI though? if you go down that rabbit hole do you just have to continually send it every minute or something?
-
SamWhited
That still sounds like a 1 line change to CSI saying "after resumption, update the state since we're not sure if it stuck"
-
Link Mauve
moparisthebest, the next stanza you send will be acked, and then you know the csi one got sent.
-
daniel
Zash, i think in general CSI applies to the stream. the fact that you can't be sure if the server got the active/inactive is a different problem
-
daniel
that will basically force you to resent it every time
-
moparisthebest
Link Mauve, so then only re-set it after stream resumption if you didn't get an ack for your next message?
-
SamWhited
I thihnk that makes #427 wrong, even though the behavior is correct. It explicitly says that the CSI state is *not* restored: https://github.com/xsf/xeps/pull/427/files
-
SamWhited
If there was a next message at all
-
Holger
moparisthebest: That's completely weirdo.
-
Holger
It must be reset.
-
daniel
SamWhited, yes i think it is wrong
-
daniel
imho
-
Holger
If you don't want that use stanzas instead.
-
moparisthebest
sounds like nonza's in general are completely wierdo Holger :)
-
SamWhited
So, action items thus far:
-
moparisthebest
kinda like using UDP when you want TCP guarantees... anyway
-
SamWhited
1. Comment on the CSI PR (#427) and say we think it needs work (although it's actually between the author and whomever made the PR)
-
Holger
moparisthebest: They might be the wrong choice for CSI (some argue this way), yes. But as long as we stick to them the CSI state must be reset.
-
SamWhited
Daniel: Can you comment there and mention this, or maybe bring it up for discussion if there's disagreement?
-
daniel
SamWhited, on the #427 one?
-
SamWhited
daniel: yes
-
daniel
yes i can do that
-
Link Mauve
SamWhited, 2. review the CSI discussion for nonza vs. stanza, and potentially switch to stanza?
-
SamWhited
Link Mauve: Yah, that might be where that discussion goes, but for now we can get the quick fix of just tweaking that PR and merging it
-
Link Mauve
Yeah.
-
SamWhited
2.1: Vote on #429 (even if we're all just on-list)
-
daniel
i'm fine with voting right now. i'm going -1 on that
-
SamWhited
I'm also -1
-
Link Mauve
-1 too.
-
SamWhited
cool, that only leaves #428 from that discussion. Do we actually want (or need) to discuss it?
-
daniel
i think we already did discuss this?
-
SamWhited
Did we? Oops, in that case, we can probably move on.
-
Link Mauve
428 is basically “this is a stanza, no problem here”.
-
SamWhited
5 (I think). Add <x/> tag to MUC-PMs: https://github.com/xsf/xeps/pull/436
-
SamWhited
I do not fully understand this yet, but it appears to bump the carbons version in expectation of that carbons PR being merged
-
Link Mauve
Didn’t we already vote on that last week?
-
daniel
i honestly have no hard feelings either way. I've personally given up on MUC
-
SamWhited
Link Mauve: Did we? I really can't keep track of this stuff, it was just listed in the Trello…
-
Link Mauve
Let me check.
-
SamWhited
oh no, I'm sorry, this does not change the carbons namespace, ignore me.
-
SamWhited
I wasn't even looking at the right PR.
-
Link Mauve
SamWhited, section 2) of the previous minutes.
-
daniel
the thing is that #436 removes one side effect and introduces another
-
daniel
(arguably minor one?)
-
daniel
i actually don't think MUC can be fixed
-
SamWhited
cool, so it's apparently still just missing a few votes. I'll vote on list, apologies for the confusion.
-
SamWhited
Does anyone else want to vote (looks like we didn't vote, just said we'd vote next week)
-
SamWhited
Except for Link Mauve, he's ahead of the game :)
-
Link Mauve
(I just fixed that on trello.)
-
SamWhited
Perfect; official vote. I'm on list. daniel?
-
daniel
i don't know. i'm really torn. i think i should maybe block this... i'll vote on list
-
SamWhited
Alrighty
- Zash has left
-
SamWhited
This was put on the agenda, but I'm not sure why: https://mail.jabber.org/pipermail/standards/2017-February/032328.html
- Zash has joined
-
SamWhited
Since we just voted on ecaps2, I guess moving on?
-
SamWhited
Or maybe we are supposed to come up with a migration plan for SHA-1 in general (although it's worth noting that it doesn't really affect anything yet, or XMPP possibly at all)
-
SamWhited
(that's 6. I guess)
-
SamWhited
Let's call it mentioned and move on unless anyone objects
-
SamWhited
I'm hearing crickets.
-
SamWhited
7. IEEE IoT email
-
daniel
no objections
-
Link Mauve
I have on my TODO list to start reviewing every usage of SHA-1 we have, but haven’t done anything yet.
-
Link Mauve
(Sorry, re 6.)
-
SamWhited
Link Mauve: Perfect, let's call that an action item for you then: SHA-1 review and migration plan. Thanks!
-
Zash
Link Mauve: Like https://xmpp.org/extensions/xep-0300.html#existing ?
-
Link Mauve
SamWhited, what is this email about?
-
Link Mauve
Zash, right.
-
SamWhited
RE 7: A motly crew of random people got CCed on an email from the IEEE IoT working group (or something) asking us to fast track the IoT XEPs which are currently deferred. Arc apparently had coffee with the person who sent the email, and it was decided that we should probably interact with their WG
-
SamWhited
since they're using XMPP for all IoT things, but don't actually have any XSF members
-
SamWhited
Dave suggested we assign a council liason to the IEEE
-
Link Mauve
Wasn’t that the purpose of the IoT SIG already?
-
SamWhited
and the board requested that we work with Rikard and the IoT SIG to come up with a strategy for the current IoT work
-
SamWhited
yes, I think the idea was just to get council involved.
-
SamWhited
I think since no one's here, we should just send out an email about this and discuss on list, unless anyone wants to suggest a specific plan or volunteer to work with the IoT SIG?
-
SamWhited
Either way I'm happy to write that email
-
SamWhited
Any volunteers?
-
SamWhited
(I'm happy to write the email, I am not volunteering to be the IoT liason)
-
Link Mauve
Didn’t we already elect stpeter as the representative of the council to the SIG?
-
SamWhited
I think we did, but since then Peter has gotten busy and not really involved right now, I don't think we can actually burden him with more work (and he's not on the council)
-
SamWhited
I'll send out an email to council@ and we can discuss specific plans (or we can discuss again next time we're all here). I'm not 100% sure what Dave et al. had in mind, so we can wait for their feedback before addressing this.
-
SamWhited
8 (maybe). Date of Next
-
Link Mauve
I won’t be here at all next week, fyi.
-
SamWhited
Same time next week?
-
daniel
wfm
-
SamWhited
2017-03-15 1600Z it is
-
SamWhited
9. AOB
-
SamWhited
I have some, but it's brief and can be last
-
daniel
i don't have any
-
Link Mauve
Me neither.
-
SamWhited
Cool, mine is just pending vote reminders:
-
SamWhited
XEP-0368 to draft: Link Mauve, SASL2: Link Mauve, IBR2: Link Mauve, Daniel. Please vote; thanks!
-
SamWhited
*gavel*
-
Link Mauve
Thank you.
-
SamWhited
Thanks everybody
-
daniel
thank you
-
moparisthebest
I think XEP-0368 to draft times out to day anyway✎ -
moparisthebest
I think XEP-0368 to draft times out today anyway ✏
-
SamWhited
yah, I thihnk you're right
-
SamWhited
Link Mauve: You have until EOB central time when I'm going to put my editor hat on and call it :)
-
moparisthebest
or times in, but that sounds odd
-
Link Mauve
Alright, I’ll take a few more minutes off work to handle that then!
-
moparisthebest
now that meeting is over, so Holger what I'm asking is with a nonza how can I be sure the server *ever* got it, even not counting stream resumption now?
-
Holger
moparisthebest: You have this guarantee (as Link Mauve or someone mentioned): https://xmpp.org/extensions/xep-0352.html#in-order-processing
-
Holger
moparisthebest: You no longer have that if the stream is resumed after sending a CSI element and before a following stanza was acknowledged by the server.
-
moparisthebest
so then as horrible as it sounds, why not mark csi as 'acked' in the client when you recieve the next 'ack' for your next stanza?
-
SamWhited
Link Mauve: Thanks! Don't forget the 0115/ecaps2 email too (not that that has to happen right away). Also reminder to me: I'm going to go draft one about the IEEE IoT stuff.
-
moparisthebest
right
-
Holger
moparisthebest: The server would have to know whether the client has marked this as 'acked' in order to decide whether to reset the CSI state :-)
-
Link Mauve
SamWhited, ok.
-
moparisthebest
but yea in general, nonzas sound like they are useful for here is this but I don't care whether you get it or not, and not in any way appropriate for modifying state on either side, or keeping state in sync
-
Holger
moparisthebest: Just reset it or use stanzas. I agree that resetting the state doesn't feel elegant, but I think that's a purely academic issue, I don't see the problem in practice. If protocol elegance is what you're after, you should not be doing XMPP :-)
-
moparisthebest
so what your saying is we should all re-invent the wheel with our own json over http protocols?✎ -
moparisthebest
so what you're saying is we should all re-invent the wheel with our own json over http protocols? ✏
-
Holger
If you want elegance, yes. I find compatibility way more important, which is why I'm doing XMPP rather than Matrix.
-
moparisthebest
what is the history for using a nonza there in the first place?
-
moparisthebest
I feel like I'm missing some context
-
SamWhited
I think it just makes sense; it's a thing you only ever need to send to the server, so it doesn't need to be routable, and it's not mission critical, so fire-and-forget is fine.
-
SamWhited
It matches the nonza use case perfectly, I think.
-
moparisthebest
it modifies state though? and is mission critical if your mission is please don't murder my phone battery
-
Holger
moparisthebest: Find a room where both Ge0rg and Flow are joined, prepare yourself with some popcorn, mention the topic, and you'll have the context.
-
Zash
Holger: What have you done!
-
moparisthebest
I'll wait for flow to join prosody and have at it haha
-
Kev
SamWhited: Actually, I think it's telling the server to do something on your behalf, so an iq to your bare JID (no to=) is probably pretty sensible too.
-
Kev
Stanzas are the building blocks of XMPP. Investing new top level elements is possible, of course, but there are implications (see the current discussion on interactions with 198).
-
SamWhited
Kev: Yah, that makes sense too, I just don't see the need for an ack, and I like it when things aren't routable.
-
Kev
I don't know what my opinion was in the past, but right now I think my opinion is largely that this should have been an iq.
-
Holger
I agree, but I'm not sure switching to stanzas now is worth the trouble.
-
Kev
I think 'not routable' isn't really much of an argument. If it's an iq to your bare JID, your server already understands how to deal with it. If it's a new element type, that means new code paths (probably, maybe, potentially, depending on server design).
-
SamWhited
If it is routable, but not intended for anyone else but the server, that's a chance for an XMPP library to break in unexpected ways
-
SamWhited
(to break in unexpected ways when I try to send them a CSI IQ even though technically they shouldn't ever get one as a client, for instance)
-
SamWhited
I generally just like keeping the scope of things as limited as possible
-
SamWhited
But I agree, it's not likely to be an issue in this case
-
Holger
CSI elements don't need to be routed but I do see need for an ACK, so we don't have a perfect fit for this.
-
Kev
SamWhited: I don't buy that, really. Receiving stuff you don't expect is kinda a core part of extensibility.
-
SamWhited
Yah, but that doesn't mean we can't limit that possibility on the server as much as possible if it doesn't cause any other problems
-
SamWhited
Which I think it doesn't in this case, but obviously others disagree
-
moparisthebest
good call Holger , that's a perfect fit for a nostanza
-
moparisthebest
which doesn't get routed, but does get ACKd
-
Holger
Given limited manpower, I think we should try to distinguish between real problems and cosmetic issues and concentrate on the former as long as we have those :-)
-
moparisthebest
nonstanza maybe, I'm not married to the name, everyone wants a new top level element right? :P
-
moparisthebest
but yea about the issue at hand it seems fairly clear CSI needs to be a stanza, or re-sent on session resumption if something didn't get acked after it was sent before, or something, yuck
-
moparisthebest
or you just re-send it on every session resumption and call it a day
-
Kev
FWIW, I don't think there'd be significant pain in migrating to iqs instead of non-stanza elements.
-
Holger
I'd rather avoid spamming the code of implementations with both solutions for no good reason.
- Lance has joined
-
Kev
I think that's fair.
-
Kev
It's Experimental though, right? :)
-
Holger
I'm in the Council room so I was expecting this response :-)
-
SamWhited
Yah, but it's one of those experimental XEPs that we left until everyone was using it; at that point it's practically defacto draft and we should be careful with changes, I think (I'm not saying we should treat it exactly like draft, but we should be careful not to leave stuff in experimental this long until it's so widely used)
-
Holger
Yes looking at such issues from a practical perspective rather than blindly applying formal rules sounds like a great idea to me :-)
- Holger goes AFK and therefore stops trolling, have a nice evening everyone.
- Holger has left
-
Kev
I think a line saying "Look, this should have been a stanza (take note future authors), but it's not, so we need to reset it on a new stream just in case" is probably not daft.
-
SamWhited
Yah, I don't think that would be a problem
-
SamWhited
Although I also disagree that it should have been a stanza; but mentioning that you may need to send it again on stream restart seems fine.
-
Kev
I think that this discussion shows that in practical terms pretty much everything needs to be a stanza, so that 198 works.
-
SamWhited
198 does work; if the server got the CSI thing, then the stream state will remain the same and no reset is necessary. If it didn't, then it's exactly the same as if it didn't get it and the stream wasn't resumed: the state just never got changed (which I think is fine in this case)
-
daniel
SamWhited, +1
-
Kev
Yes, it works in the sense of it will not be broken.
-
Kev
But in terms of you needing to resend it after a restart because you don't know whether it was received isn't exactly 'working'.
- jere has left
- jere has joined
-
SamWhited
I just don't think that's a problem; however, if it is, the fix is easy: just always send it after a restart. I don't think it's necessary, but I also don't think it's a problem. It's an easy fix.
-
Kev
Changing to something much less bikesheddish:
-
Kev
https://github.com/xsf/xeps/pull/436/commits/cde2abe151ac8ecaacf46ad5d0cc43caae5b9a62
-
Kev
Surely we can't merge that?
-
Kev
It renders existing implementations non-compliant, and poses a potential interop problem.
-
daniel
you said *less* bikesheddish?
-
SamWhited
It is a SHOULD, not a MUST (but I'm leaning that way too)
-
Kev
Yes, this is a real issue, rather than cosmetic.
-
Kev
SamWhited: A SHOULD means you can rely on it, pretty much, because anyone not doing it made a deliberate decision.
-
SamWhited
Kev: What I heard there is "you can't rely on it" :)
-
Kev
SamWhited: Then it should be MAY.
-
daniel
we could just bump the muc namespace :-)
-
Kev
SHOULD means you can rely on it.
-
Kev
At the least it needs text saying that while a service/client SHOULD attach it, receiving entities can't assume that it'll be present, because $REASONS.
-
Kev
If we really do want to make it either SHOULD or MUST without further explanation, then yes, you're needing a namespace bump.
-
Kev
I suggest a namespace bump would be ludicrously stupid, and instead we need wording that doesn't introduce interop concerns.
-
SamWhited
yah, I agree; if it requires a namespace bump I'm absolutely -1
-
SamWhited
But I'm also fairly convinced that we should take MUC out behind the chemical shed and shoot it (and by that I meant that MUC is always going to be a bad experience, and there is nothing we can do about it, so we shouldn't bother)
-
SamWhited
But we definitely shouldn't make it *worse* (which a namespace bump would do)
-
Kev
I think that an additional sentence saying something approximately "Note that this requirement was added late in MUC's life, when implementations were already stable, and thus clients MUST NOT rely on receiving this element".
-
Kev
would probably be sufficient to get this text in there, while not breaking anything.
-
SamWhited
yah, that seems sane
-
daniel
i think everyone (including the author of the PR) will probably be fine with MAY
-
SamWhited
or that
-
Kev
MAY would not introduce an interop concern, so I'm far less opposed to it.
-
Kev
But I think better would be to make it clear that it's a good idea to do it.
-
daniel
can someone create a comment on the PR basically pasting the last couple of lines
-
daniel
because i really agree with SamWhited that MUC needs to die already and we shouldn't spend hours discussing these things
-
SamWhited
(I can't copy/paste easily from mcabber or I would)
-
daniel
:-)
-
Kev
I suggest someone Council does it, but I'll do it if not.
-
daniel
ok i'll do it
-
Kev
Thanks.
-
Kev
I think my suggested text is the best option, but I'm far fewer Fs about that than about not merging the PR as-is.
- daniel has left
- daniel has left
- Holger has left
- daniel has left
- Kev has left
- daniel has left
- Lance has left
- daniel has left
- Lance has joined
- daniel has left
- daniel has left
- daniel has left
- Tobias has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- Lance has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- Lance has joined
- daniel has left
- daniel has left
- daniel has left
- moparisthebest has joined
- Tobias has left
- moparisthebest has left
- moparisthebest has joined
- moparisthebest has joined
- moparisthebest has joined
- SamWhited has left
- daniel has left
- jere has joined
- moparisthebest has left
- moparisthebest has joined
- Lance has joined
- Lance has left
- Tobias has left
- Tobias has left
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- jere has joined
- Zash has left
- jere has left
- Zash has left
- SamWhited has left
- ralphm has left
- moparisthebest has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- Flow has joined
- ralphm has left
- daniel has left
- daniel has joined
- Kev has joined
- Tobias has left
- Tobias has left
- daniel has left
- daniel has joined
- Zash has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- jere has joined
- jere has left
- jere has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- daniel has left
- daniel has joined
- Tobias has left
- jere has left
- jere has joined
- daniel has left
- ralphm has left
- jere has left
- jere has joined
- daniel has left
- peter has joined
- Flow has joined
- Zash has left
- Tobias has joined
- Zash has joined
- Flow has joined
- peter has left
- Flow has joined
- Holger has left
- ralphm has left
- Zash has left
- Zash has joined
- Lance has joined
- Holger has left
- jere has left
- jere has joined
- daniel has left
- daniel has left
- Holger has left
- daniel has left
- Kev has left
- daniel has left
- Lance has left
- daniel has left
- Lance has joined
- daniel has left
- daniel has left
- daniel has left
- Tobias has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- Lance has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- daniel has left
- Lance has joined
- daniel has left
- daniel has left
- daniel has left
- moparisthebest has joined
- Tobias has left
- moparisthebest has left
- moparisthebest has joined
- moparisthebest has joined
- moparisthebest has joined
- SamWhited has left
- daniel has left
- jere has joined