XSF Communications Team

00:00:26 emus has left
00:16:25 peetah has left
00:16:31 peetah has joined
03:55:09 SouL has joined
04:30:47 DebXWoody has joined
04:58:05 alacer has left
04:58:12 alacer has joined
05:11:59 alacer has left
05:12:01 alacer has joined
05:26:37 alacer has left
05:26:39 alacer has joined
05:31:03 alacer has left
05:31:06 alacer has joined
05:36:56 Vaulor has joined
05:57:48 Licaon_Kter has joined
06:00:40 jcbrand has joined
06:32:04 emus has joined
06:32:04 peetah emus: I tried, but uploading files requires push access to the repository
06:39:09 wurstsalat maybe we can start a link collection for potential images, and then someone with access pushes them?
06:50:28 arnaudj has left
06:50:59 arnaudj has joined
06:56:08 emus 👋
06:56:38 emus yeah, should be fine. Maybe at the end of the month we drop some links in the PR
06:57:12 arnaudj has left
06:59:42 Nÿco has left
07:00:22 debacle has joined
07:00:52 arnaudj has joined
07:01:55 Nÿco has joined
07:28:06 peetah what should be fine ?
07:41:28 emus Should be fine to do so
07:41:39 emus > maybe we can start a link collection for potential images, and then someone with access pushes them?
07:41:58 peetah ok
07:45:38 peetah so, for now, nobody has the possibility to upload images ?
07:46:11 DebXWoody :-D
07:51:41 arnaudj has left
07:51:47 arnaudj has joined
07:53:04 debacle has left
07:56:25 wurstsalat are there still images needed for the current issue?
07:56:28 wurstsalat emus?
08:02:14 peetah JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsocmblog does not have copyright notice either
08:02:35 peetah JSCX images are free to reuse for "reviews and similar", I'm waiting for permission to resuse screenshot from profanity since their blog does not have copyright notice, and wolfieanmmol gsoc-blog does not have copyright notice either
08:04:01 peetah emus, as an XSF member, could you join him to ask for permission to reuse the gif linked in the july newsletter ?
08:06:45 wurstsalat for the 1.2 release of gajim we could use https://gajim.org/img/news/account-badges.png (which is CC-BY-SA, from the release post on gajim.org)
08:11:45 SouL emus, regarding the other PRs that there are, no, none of the current ones apart from the newsletter belong to commteam, so don't worry
08:17:03 alacer has left
08:17:05 alacer has joined
08:33:53 alacer has left
08:34:10 alacer has joined
08:41:33 arnaudj has left
08:41:43 arnaudj has joined
08:44:48 Alex has left
08:44:52 Alex has joined
08:55:48 alacer has left
08:55:56 alacer has joined
08:59:02 emus peetah: I have the permission I think
08:59:33 emus SouL: okay, but I think there is no one in general
08:59:39 peetah great
08:59:53 Nÿco has left
09:00:01 emus peetah: I think there is a right to quote someones publications?
09:00:22 emus anyway I can contact them
09:01:09 arnaudj has left
09:02:10 peetah reusing images is not the same as quoting someone, and if there is nothing indicating the licence for republication, it is legally required to get an authorization first
09:02:28 Nÿco has joined
09:02:52 peetah so I guess it would be better to ask for it, if not for legal reason, at least for courtesy
09:06:15 alacer has left
09:06:22 alacer has joined
09:06:24 arnaudj has joined
09:11:31 arnaudj has left
09:11:38 arnaudj has joined
09:12:11 emus If I get all that managed by tonight I can do so otherweise I prefer to take it out and we do for the next version this procedure
09:12:41 emus or we just drop our own screenshot... I mean that is allowed, right?
09:12:49 peetah sure :)
09:13:11 emus maybe that is the easiest way^^
09:15:15 peetah then I'll do it
09:15:54 peetah but it will have to be uploaded on the repo
09:22:10 DebXWoody has left
09:22:38 DebXWoody has joined
09:26:16 arnaudj has left
09:26:22 arnaudj has joined
09:26:56 peetah permission to reuse profanity screenshot granted
09:28:32 peetah emus: sorry, when I said I would do it, for whatever reason, I had profanity screenshot in mind
09:30:30 peetah the only image permission missing is now from wolfieanmmol gsoc-blog which I won't be able to reproduce
09:37:55 emus Will ask them
09:38:10 peetah thanks
09:42:51 emus I cobtected him
09:43:00 emus I contacted him
09:51:30 Nÿco has left
09:57:05 alacer has left
09:57:12 alacer has joined
10:05:13 Nÿco has joined
10:09:12 Alex has left
10:13:33 Alex has joined
10:19:50 jcbrand has left
10:19:53 jcbrand has joined
10:56:37 Nÿco has left
10:58:55 Nÿco has joined
11:05:50 arnaudj has left
11:06:08 arnaudj has joined
11:07:43 arnaudj has left
11:07:49 arnaudj has joined
11:17:42 debacle has joined
11:21:13 arnaudj has left
11:21:21 arnaudj has joined
11:49:10 DebXWoody has left
11:49:38 DebXWoody has joined
11:50:58 arnaudj has left
11:51:04 arnaudj has joined
11:55:04 DebXWoody has left
11:55:26 DebXWoody has joined
11:55:48 kikuchiyo has left
12:03:13 Vaulor has left
12:03:15 Vaulor has joined
12:07:55 kikuchiyo has joined
12:22:40 kikuchiyo has left
12:27:58 DebXWoody has left
12:28:20 DebXWoody has joined
12:29:43 DebXWoody has left
12:31:02 DebXWoody has joined
12:33:50 Alex has left
12:35:33 Alex has joined
12:41:29 DebXWoody has left
12:41:49 DebXWoody has joined
12:45:12 DebXWoody has left
12:46:22 DebXWoody has joined
12:48:00 kikuchiyo has joined
13:18:08 DebXWoody has left
13:18:28 DebXWoody has joined
13:49:57 jcbrand has left
14:06:55 kikuchiyo has left
14:08:07 jcbrand has joined
14:18:53 kikuchiyo has joined
14:33:46 kikuchiyo has left
15:00:18 arnaudj has left
15:00:25 arnaudj has joined
15:02:37 kikuchiyo has joined
15:14:35 alacer has left
15:14:38 alacer has joined
15:55:47 emus Apart fromt the picture thing - any last points?
15:59:49 peetah can't think of anything else
16:01:18 arnaudj has left
16:01:26 arnaudj has joined
16:02:49 Wojtek has joined
16:10:51 kikuchiyo has left
16:24:41 emus Hmm, formating is weird. It shows each picture twice
16:24:58 emus things like this: <img src="https://github.com/xsf/xmpp.org/blob/master/content/images/blog/profanity090.png" width="500">
16:25:04 emus are rendered twice
16:25:12 emus waite
16:25:14 emus wait
16:26:03 emus ahh, omg the preview also renders the diff!
16:26:09 emus that really weird
16:26:18 peetah are you inserting the html directy inside the markdown ?
16:26:25 peetah are you inserting the html directly inside the markdown ?
16:26:45 emus ok lets see - the html think usually works in markdown. I need to resize the picture
16:27:07 emus Muy bien: https://github.com/xsf/xmpp.org/pull/714/files?short_path=83d5783#diff-83d5783deabe9450b0964958b7ab9da3
16:27:17 emus so I will release now
16:27:18 peetah you should not, because pelican won't understand
16:27:27 emus Ah wait
16:27:31 emus no tomorrow
16:27:37 emus But I will close now
16:27:48 emus Are you sure?
16:27:59 emus wait, then I have to resize the picutre manually
16:28:04 peetah you should use the markdown formating with: ![[profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9")
16:28:24 peetah you should use the markdown formating with: ![profanity 0.9 screenshots](/images/newsletters/july2020/profanity09.jpg "profanity 0.9")
16:28:52 peetah pelocan will look for the /images path according to its configuration and generate the appropriate html
16:29:01 peetah pelican will look for the /images path according to its configuration and generate the appropriate html
16:29:40 kikuchiyo has joined
16:29:41 peetah and from the current pelican conf, /images is the /content/images path in the repo
16:30:46 peetah there is one blog post that did exactly that... give me a sec to find it
16:31:58 peetah https://github.com/xsf/xmpp.org/blob/master/content/posts/blog/Return_of_experience_on_XMPP_meetup_in_Krakow.md
16:34:42 peetah an we should not put the newsletter related images into the blog directory
16:35:42 peetah we should create a /content/images/newsletters/<monthYYYY> directory and store them there
16:35:48 emus Okay wait
16:35:57 emus ![Piotr Nosek from Erlang Solutions](/images/blog/Piotr_Nosek_MongooseIM.jpg) but they dont use the ending nameing
16:36:49 emus pep. are you here?
16:36:57 emus can you create a folder in here?
16:36:57 emus https://github.com/xsf/xmpp.org/tree/master/content
16:37:10 emus sorr in here: https://github.com/xsf/xmpp.org/tree/master/content/images
16:37:15 emus "newsletter" ?
16:37:33 peetah the text between double-quotes inside the parenthesis is the one used as the image title when you hover it
16:37:41 emus ok
16:38:54 pep. !
16:39:06 peetah of course, the images won't be displayed in the github preview
16:39:09 pep. emus, you can't "create a folder" in git
16:39:14 pep. it doesn't make sense
16:39:33 emus Okay, but how did they do 😀
16:39:35 peetah git does not understand the "folder" concept
16:39:49 peetah you have to create a file into that folder
16:39:59 emus ah okay
16:40:41 emus so that is that I do in the "name file" field on the top?
16:41:22 pep. hmmm, maybe you can enter slashes in there :/
16:41:30 pep. yeah
16:41:38 emus Yes ok
16:43:29 emus but I dont need to add a file in that step, right?
16:43:48 emus I just "commit" the new file (/../...)
16:44:23 pep. what do you want to do? Add an image somewhere?
16:44:43 emus in that location afterwards. but now it just has the editor look
16:44:44 pep. I have no idea how to do that via github's interface
16:44:49 emus ok
16:44:54 emus I just try
16:45:12 peetah if i remember correctly, there is a "upload file" button
16:46:37 peetah add files > upload fil
16:46:41 peetah add files > upload file
16:46:46 peetah add files > upload files
16:46:56 emus Yes, but there I cannot create an location 😕
16:47:00 alacer has left
16:47:02 alacer has joined
16:47:34 pep. Have somebody else upload the first image? and upload the rest
16:47:47 emus yes was wondering
16:48:03 peetah I would go in the /content/images/ folder, then clich on upload files and proceed from ther
16:48:10 peetah I would go in the /content/images/ folder, then clich on upload files and proceed from there
16:48:28 peetah I guess it will ask for a file from your computer and a target folder
16:48:31 pep. emus, wasn't there a desktop client for github? Maybe it's easier to use
16:48:59 peetah but I can't say for sure since I just have a "File uploads require push access to this repository." message
16:49:35 peetah can't you just clone the repo and commit the file from there
16:49:38 peetah then push
16:49:48 peetah ?
16:49:49 emus Ok, now I know how it works
16:49:54 emus give me another 5 minutes
16:52:38 emus everything is ready, you can now commit resized (smaller sized) pictures to the new location: https://github.com/xsf/xmpp.org/tree/master/content/images/newsletter
16:52:43 emus in the future
16:53:25 peetah great ! thanks !
16:53:26 emus Okay guys, we are close! Just the new linking missing ... 🏃‍♂️️
16:56:59 emus ![profanity 0.9 screenshots](/images/newsletter/june2020/profanity090.png "profanity 0.9")
16:57:00 emus ![Desktop client JSXC](/images/newsletter/june2020/jsxc41.png "Desktop client JSXC")
16:57:07 emus ![RTT User Interface](/images/newsletter/june2020/dino_rtt_demo.gif "RTT User Interface")
16:57:09 emus Si?
16:57:24 peetah I guess so
16:57:49 peetah I'm looking for a way to limit image size via pelican conf
16:58:30 emus ok, hmm Github is not rendering - are you sure I cannot use the full link?
16:58:59 emus Shouldnt be a problem or?
16:59:12 peetah if you want pelican to do its job, then I think it has to be this way
17:00:09 emus Okay, then I ignore it and leave it like this
17:00:43 emus ======= Redaction Closing for June 2020 XMPP Newsletter======
17:00:51 emus 🤸‍♂️️
17:02:13 vanitasvitae emus, I guess you have to remove the leading "/" from the image link
17:02:34 emus okay, but also for pelican?
17:02:48 emus I focus on what pelican wants to see
17:03:11 peetah no you have to keep the leading /
17:03:15 emus ok
17:03:40 peetah this is how the blog post linked above did, and it is perfectly rendered on the web site
17:03:41 vanitasvitae okay, havent used pelican
17:04:03 vanitasvitae just for markdown you'd have to remove the slash.
17:04:28 peetah if images was in the same folder as the md, which is not the case
17:04:41 peetah if "images" folder was in the same folder as the md, which is not the case
17:07:55 emus we will see tomorrow
17:09:13 peetah emus: you created the folder in "master" : should'nt have been created in newsletter-july2020 branch and then merged with the rest of your PR ?
17:09:28 peetah I have absolutely no clue about the possible consequences
17:09:49 emus fuck, I knew I did something wrong
17:10:17 emus how was that possible 🙈️
17:10:19 peetah not wrong, open to improvements :)
17:10:59 emus but wait - in the master branch everything is fine?
17:11:09 peetah it is
17:11:28 pep. fwiw, if the image is meant to stay it might be best just to leave it there
17:11:39 vanitasvitae Oh boy, dat commit history 😛
17:12:25 pep. since it's a big binary file, otherwise you're gonna have git storing big diffs
17:12:56 peetah I would have used "newsletters" rather than "newsletter" though
17:13:05 pep. renaming should be fine
17:13:32 pep. I think
17:16:31 emus vanitasvitae: 🙄 I know I know
17:17:12 emus I used newsletter because thats the general top term. details will come if you click it
17:18:24 emus vanitasvitae: If you have well experience you can sqatsch the commits but I rather leave my hands of foe today 🤐
17:18:35 emus vanitasvitae: If you are well experience you can sqatsch the commits but I rather leave my hands of foe today 🤐
17:18:42 emus vanitasvitae: If you are well experienced you can sqatsch the commits but I rather leave my hands of foe today 🤐
17:18:56 vanitasvitae squashing on master is a bad idea
17:19:03 vanitasvitae guess for that it's too late.
17:19:20 vanitasvitae In general, you should work in feature branches and merge those into master once you are ready.
17:19:48 vanitasvitae It may be a good idea to make the master branch protected, so that nobody can directly push to it
17:19:49 peetah can't we just reset master to the latest good commit ?
17:20:23 emus vanitasvitae: Yeah, I wonder actually why that is not the case
17:20:25 vanitasvitae peetah, sure, but maybe someone/something already pulled and will then have to deal with merge conflicts and stuff
17:20:40 emus but on the other side we need someone to continuiously manage this
17:20:54 vanitasvitae protecting the branch is a good thing imho
17:21:15 vanitasvitae that way you can only contribute to it via merge requests
17:21:23 emus yeah
17:23:08 pep. yeah maybe ask iteam. It's also good to do that just to avoid common mistakes
17:23:24 vanitasvitae yup
17:23:33 emus Now I ruined it for everyone 😄
17:23:38 pep. haha
17:23:45 emus No fun anymore guys ¯\_(ツ)_/¯
17:23:55 vanitasvitae quick! hide it under a ton of good commits!!!
17:24:19 peetah :D
17:24:54 emus Haha - actually I wonder how I commited to the wrong branch. it is hard in the Github interface 🤔
17:25:19 vanitasvitae 😀
17:28:08 emus Enough crazy commits for today. Thanks everyone for helping out and create the release for tomorrow. The new draft PR is already open. From now on only wonderful perfect commits 🙂
17:28:45 peetah thanks emus for your work on this new newsletter
17:31:12 emus Sure - now we all dance XMPP like YMCA:
17:31:14 emus 🙅‍♂️️🙆‍♂️️🤦‍♂️️🤦‍♂️️
17:31:32 emus 😄️
17:32:25 emus uhh, you have icon duplication? I do in Conversations
17:32:53 emus Dino is doing weird things maybe?
17:34:39 Licaon_Kter has left
17:34:44 Licaon_Kter has joined
17:54:55 arnaudj has left
17:55:03 arnaudj has joined
17:57:56 kikuchiyo has left
18:02:38 alacer has left
18:02:40 alacer has joined
18:18:31 kikuchiyo has joined
18:18:48 kikuchiyo has left
18:20:02 kikuchiyo has joined
18:20:15 kikuchiyo has left
18:21:30 kikuchiyo has joined
18:21:43 kikuchiyo has left
18:22:59 kikuchiyo has joined
18:23:13 kikuchiyo has left
18:24:28 kikuchiyo has joined
18:28:43 arnaudj has left
18:28:49 arnaudj has joined
18:34:58 la|r|ma interesting. So dino sends [person gesuring no][join][male symbol][emojify][emojify] This makes sense to some degree, but [emojify] is often not needed. [male symbol] = ♂ [male symbol][emojify] = ♂️ [person gesturing no] = 🙅 [person gesturing no][join][male symbol] = 🙅‍♂ [person gesturing no][join][male symbol][emojify] = 🙅‍♂️ [person gesturing no][join][male symbol][emojify][emojify] = 🙅‍♂️️ [person gesturing no][join][male symbol][emojify][emojify][emojify] = 🙅‍♂️️️
18:36:06 la|r|ma ahaa it's not getting better when trying to send these things from dino 😀
18:36:38 la|r|ma where is my unicode codepoint input field 😀
18:37:11 ldkjgoiwe has joined
18:40:59 ldkjgoiwe has left
18:41:01 ldkjgoiwe has joined
18:43:25 la|r|ma emus, file a bug with Conversations, something is very weird with Conversations here...
18:43:39 la|r|ma https://logs.xmpp.org/commteam/2020-07-06#2020-07-06-87caed30d601b091
18:50:21 arnaudj has left
18:50:27 arnaudj has joined
18:54:22 arnaudj has left
18:54:28 arnaudj has joined
18:55:52 arnaudj has left
18:56:17 arnaudj has joined
19:00:42 arnaudj has left
19:01:01 arnaudj has joined
19:03:22 alacer has left
19:03:24 alacer has joined
19:05:50 DebXWoody has left
19:06:44 DebXWoody has joined
19:18:16 ldkjgoiwe has left
19:18:17 ldkjgoiwe has joined
19:19:45 DebXWoody Hi. I think it would be much easier for the team if the commteam would have an own repository where they can work. Maybe it's possible to give just access to this reposiory and the team would be able to work on master for the daily work.
19:28:05 ldkjgoiwe has left
19:28:06 ldkjgoiwe has joined
19:30:15 kikuchiyo has left
19:31:00 ldkjgoiwe has left
19:31:01 ldkjgoiwe has joined
19:35:52 arnaudj has left
19:35:58 arnaudj has joined
19:36:16 kikuchiyo has joined
19:37:14 kikuchiyo has left
19:37:38 emus la|r|ma: ouh you are seeing this :D pep. can you imagine I got that far 😂😂😂 (yesterday I made actually the joke to him with the emojis)
19:38:13 jcbrand has left
19:38:17 kikuchiyo has joined
19:38:18 pep. Yeah I had to open Conversations because I wouldn't see it properly in poezio, but I'm used to that anyway :p
19:39:19 emus DebXWoody: yes, I think we try to keep it easy. I will wait if there is any outcome of the Gitlab question. But lets keep that in mind fir the september release
19:40:16 DebXWoody question?
19:41:03 DebXWoody What is the question?
19:41:05 emus DebXWoody: jonas was evaluating if Gitlab is interesting for XSF
19:42:08 DebXWoody Ah,... +1, this would be nice. I would also start to help on some topics for XSF.
19:43:32 peetah I'm not sure if being interesting is really the question… the real question is rather what burden will it bring and who is going to administrate the beast.
19:44:17 DebXWoody administrate the beast?
19:44:32 pep. peetah, it's not gitlab but gitlab.com
19:44:37 pep. So same as github.com
19:44:42 pep. "same", admin-wise
19:44:55 peetah I mean , being independent vs depending on a microsoft owned closed source forge => no brainer
19:45:25 peetah ahhhh I thought we were talking about an independant instance of gitlab
19:45:49 DebXWoody I think is not requiered to have an own server. gitlab.com would be fine.
19:46:40 pep. DebXWoody, well.. moving from github.com to gitlab.com because you want to stop depending on Microsoft is somewhat missing the point :p
19:47:01 peetah not for me: I've been there and fled when they changed their ToS to include sharing data with third parties
19:47:11 pep. There are other reasons to do this move, but this is not really one IMO
19:48:38 DebXWoody pep.: It's not only Microsoft. GoogleAPI, closed software, etc. I prefer codeberg.org, but gitlab has more features and is also quite nice.
19:49:27 peetah what is codeberg ? I see several projects moving there, but I did not take the time to gather information about this platform.
19:50:04 DebXWoody peetah: Is't Gitea hosted by a german e.V.
19:50:51 emus Guys --> offtopic, didnt wanted to provoke a discussing 👨
19:53:40 ldkjgoiwe has left
19:53:40 ldkjgoiwe has joined
19:58:23 kikuchiyo has left
20:06:54 vanitasvitae emus: by the way, "Redaktionsschluss" is "copy deadline" or "editorial deadline" ;)
20:07:49 emus The German helps the German 🙂
20:08:44 emus https://github.com/xsf/xmpp.org/pull/714 😉️
20:12:18 vaulor has joined
20:13:41 vaulor has left
20:13:42 vaulor has joined
20:14:36 vaulor has left
20:14:38 vaulor has joined
20:24:50 debacle has left
20:25:11 jcbrand has joined
20:27:17 DebXWoody has left
20:35:53 kikuchiyo has joined
20:36:24 kikuchiyo has left
20:40:32 kikuchiyo has joined
20:42:20 vaulor has left
20:44:02 Martin has left
20:44:40 Martin has joined
20:47:19 debacle has joined
20:47:43 debacle has left
20:47:48 debacle has joined
20:57:52 kikuchiyo has left
21:04:52 ldkjgoiwe Suggestion: I think the "Help us to build the newsletter" part would fit better in the end of the newsletter. It's rather long and has a rather narrow target group. With the current layout, everything I see when opening the newsletter is not actually news content. I'd also consider moving the "Subscribe to the newsletter" to the end - after the reader has seen how great the newsletter is and not before. ( cc emus )
21:06:09 emus Okay, interesting point. I would be okay to change this. Other opinions?
21:06:11 pep. Yeah I think I agree with both points
21:07:52 pep. I'd be interesting to know if putting "subscribe to the newsletter" at the top is actually efficient in terms of getting people to subscribe, and also in terms of getting people to read the article (not close it because "pff I don't want to subscribe" or similar)
21:07:56 emus ldkjgoiwe: Lets see if most agrees or have other suggestion - then - if you want create a PR and suggest the actual changes. Would that be possible for you?
21:08:12 emus ldkjgoiwe: Lets see if most agrees or have other suggestions - then - if you want create a PR and suggest the actual changes. Would that be possible for you?
21:08:45 emus ldkjgoiwe: Lets see if most agrees or have other suggestions - then you can create a PR if you want and suggest the actual changes. Would that be possible for you?
21:09:54 emus pep.: I think that does not really happen. people have educated good filters for stuff they dont care about in the internet
21:10:14 emus But I think its okay to first give peopl what they wanna read
21:18:17 wurstsalat emus: I'd put the 'help us' part at the end as well. don't know about the subscribe part
21:27:45 emus ok, I think both is fine. most have subscribed anyway and if they want to they likely will fine it there aswell. so we dont both readers with stuff they know
21:30:13 pep. Tbh I'm not subscribed to it as I'll see it anyway either here or on mastodon or.. I wonder what is the target of the newsletter really, and who actually subscribes :p
21:31:16 pep. Talking of Mastodon, did Nyco share credentials with anybody else in commteam?
21:31:21 pep. Nÿco, ^
21:31:37 pep. It's very inactive at the moment
21:31:44 Nÿco Nope
21:31:53 pep. Is it possible?
21:32:52 emus pep.: there are people subscribed
21:33:55 kikuchiyo has joined
21:40:15 arnaudj has left
21:40:21 arnaudj has joined
21:43:17 arnaudj has left
21:43:26 ldkjgoiwe has left
21:45:31 arnaudj has joined
21:46:48 arnaudj has left
21:47:01 arnaudj has joined
21:48:06 kikuchiyo has left
21:49:41 kikuchiyo has joined
22:09:03 jcbrand has left
22:43:11 kikuchiyo has left
22:43:40 debacle has left
22:59:22 Vaulor has left
23:04:40 kikuchiyo has joined
23:48:08 emus has left
23:53:17 kikuchiyo has left
23:57:24 alacer has left
23:57:26 alacer has joined