00:00:11 alexjurkiewicz, good catch, but you should still use partition; it handles the case when there's no space in the cookie 00:02:39 Unstable branch on crawl.kelbi.org updated to: 0.25-a0-700-g7f8a7979f0 (34) 00:40:20 doh 00:42:25 03Alex Jurkiewicz02 07https://github.com/crawl/crawl/pull/1253 * 0.25-a0-711-g4143bc5: Fix cookie parsing 10(69 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/4143bc5d5179 01:22:06 doh 01:22:08 oops 01:58:45 doh??? 01:58:45 <|amethyst> doh 03:12:03 Unstable branch on crawl.beRotato.org updated to: 0.25-a0-700-g7f8a797 (34) 03:31:08 Fork (bcrawl) on crawl.kelbi.org updated to: 0.23-a0-2999-g24818c1c7b 10:32:46 I wonder if we should consider something like moving tavern off of cdo? 10:33:17 it's really not doing us any favors to have the only moderated / official dcss space semi-closed for long stretches 10:45:54 New branch created: pull/1337 (1 commit) 13https://github.com/crawl/crawl/pull/1337 10:45:55 03Nikolai Lavsky02 07https://github.com/crawl/crawl/pull/1337 * 0.25-a0-698-gb73c826: Fix stash search menu not showing tiles for some dungeon features 10(10 minutes ago, 1 file, 1+ 4-) 13https://github.com/crawl/crawl/commit/b73c826b8a4c 11:00:47 advil: in terms of moving to a new server, or moving to a new auth / login system? 11:02:25 I'd probably be in favour of the former, and for the latter, well... sso 2020? 12:07:06 moving to a new server 12:07:37 (which would probably entail a new auth system) 12:08:42 I mean doing this seems like a huge and painful project (at least if user accounts / post history were migrated), so I can't say I'm excited about it 12:30:49 huge and painful, most likely, but moving might make incremental improvements feasible 12:31:57 what's the current auth system? i had a sneaking suspicion tavern and mantis both used a shared database, not sure how accurate that is 12:34:07 they do use a shared auth system, yeah 12:34:49 napkin could give you some further details 13:15:37 Stable (0.20) branch on crawl.akrasiac.org updated to: 0.20.2-0-g0475c4d 13:22:19 Unstable branch on crawl.akrasiac.org updated to: 0.25-a0-700-g7f8a797 (34) 15:20:30 Would there be a way to query how many people have gotten the (BcadrenCrawl unique) Cracked Rune? an !lm that checks a fork, !lg that checks fork? IDK how those utilities work. 15:23:31 Bcadren: You can download the logfiles yourself and grep them 15:25:10 oof. suppose that's true? not sure how to download a server's entire morgue though 15:26:41 You don't need all the morgues, just the milestones file 15:32:08 03kate-02 07* 0.25-a0-701-gb30f108: Add a missing TAG_MAJOR_VERSION check 10(3 minutes ago, 1 file, 2+ 0-) 13https://github.com/crawl/crawl/commit/b30f108f014a 15:32:55 Do you know where that is? https://crawl.kelbi.org/crawl/ 15:33:19 I've pulled individual morgues for crash logs before, but otherwise I'm not sure how to navigate the online folder 15:33:21 <|amethyst> https://crawl.kelbi.org/crawl/meta/bcadrencrawl/milestones 15:34:34 wow what a file. 15:35:31 <|amethyst> you can download that and grep 'cracked rune' milestones 15:35:35 <|amethyst> I see five 15:35:54 <|amethyst> out of 601 total runes 15:38:46 Yep. Gorgo, Holysushi x2, Winsalot, CanofBees. 4 people have gotten the cracked rune. 15:42:05 Cracked Rune replaces slimy when you kill TRJ...part of the slime rework I did. That's semi-recent in the span of how long the fork's been around (like a month or so ago). 15:47:49 Unstable branch on crawl.kelbi.org updated to: 0.25-a0-701-gb30f108f01 (34) 15:49:02 -!- aidanh_ is now known as aidanh 17:51:35 advil: aidanh: I would happily pay the cost of running a discourse server for DCSS 17:52:05 I agree that migrating existing content would be extremely painful so I would vote "just don't do that". It's not like there's a wealth of referenced knowledge on tavern 17:52:28 you'd have us forget berder's chicken thread? 17:52:29 yeah I was thinking about discourse, though I have kind of mixed feelings about the ui 17:52:47 but something not phpbb 17:53:04 I looked into the shared auth a while ago when trying to migrate the crawl wiki to CDO. iirc the user data all lives in mantis, and phpbb has a php extension written to SELECT into that table and munge the data to what phpbb expects 17:53:20 yeah. Discourse is not my favourite. But it's really the only modern choice for "forum software" 17:53:44 I suppose the alternative is to go all-in on reddit or another "managed" service 17:55:03 reddit would need to be moderated for me to be ok with that 17:55:57 like, with rules and everything 17:59:39 I'm keen to work on this however possible fwiw. I think it's important for dcss community health 17:59:58 if dev team like the idea of migrating to discourse I can spin up a test instance whenever 18:00:01 the only thing about starting fresh is that I'm not sure what uptake there would be 18:00:15 I was wondering about at least importing user info from recently active tavern users 18:02:00 I think 'forgot password' flow is harder than 'use one of the 100 SSO providers discourse supports' for new users 18:05:52 we'd definitely want to keep taverns rules 18:23:52 Unstable branch on underhound.eu updated to: 0.25-a0-701-gb30f108f01 (34) 18:30:09 discourse does seem like it'd be an improvement over phpbb to me, although i guess i wouldn't expect a new official forum to be hugely active, judging from how slow tavern is these days? 18:30:56 maybe that's because of the closed registration stuff but i don't know that i'd expect there to be a ton more activity even if it were open 18:34:23 i'm happy that the forum is considered worth maintaining at all, so many communities have moved to things like discord 18:40:00 yeah, from what i gather the general roguelikes discord is probably one of the more active places for crawl talk these days? but yeah, i would definitely want anything that's considered "official" to be strongly moderated (which is much easier for lower-traffic places like the forums and irc at least!) 18:41:09 right 18:41:12 +1 to that 18:42:50 the worst two community trolls currently run rampant on the reddit and one of them does likewise on the CXC discord, but both are banned from the roguelikes discord (and from a bunch of other discords) 18:43:09 I think it's important that any "official" platform has strong enough moderation to keep people like that out 18:43:47 thankully the roguelikes discord people are reasonably proactive about moderation and have non-harassment rules 18:47:21 ah that's good to hear yeah, i wasn't sure how that was handled on the roguelikes discord so had never ended up joining it 18:47:53 but yeah i'd be happy to 18:48:30 ??roguelikes[3 18:48:31 roguelikes discord[1/1]: The Reddit /r/roguelikes Discord server has a #dcss channel. You can join here: https://discord.gg/9uVbTYH 18:48:33 (oops hit enter early) continue moderating a hypothetical new forum if that ended up happening 18:48:38 ah, yep 18:48:42 as would I 18:51:27 reddit comments are a pain to finnd new discussion in if things go on long enough, because of sorting only applying to top level 18:51:39 getting feedback was much easier on tavern re positional magic 18:51:51 I would prefer a forum over reddit 18:52:23 yeah, agree that forum is better for long-form discussion by far 18:53:59 btw, since you're both here, I was thinking of making Absolute Zero go to fixed ranged 5 and having noise scale down with spellpower, as it did originally 18:54:11 the spell feels a bit "cheap" when you get it to max range 18:54:21 hellmonk seems to support the idea of lower range as well 18:54:31 that sounds better practically, I have a BaIE going that I will try to get it with 18:54:35 though that BaIE went kiku 18:54:51 gotta hope for that lucky book of annihilations 18:56:18 i've not managed to try it yet but i still wouldn't be super concerned about it being too strong i guess, compared to other L9 spells 18:57:11 yeah, I think it's more of a "feel" thing 18:58:14 but fixed range over variable range sounds reasonable, yeah - variable range does have a little weirdness with spellpower breakpoints too 18:59:53 i suppose noise scaling would probably want to be fairly aggressive to make it desirable enough? (although i remember the initial commit already did have it be extremely loud to start with) 19:00:14 yes, starting at 40 19:00:21 I think it did scale all the way down to silent 19:06:26 kate- I'm pretty sure that forum has been hugely impacted by registration closure, this last round is especially noticeable as someone who browses by "active topics" 19:06:44 obv it's hard to know what the counterfactual no-registration-closure would be like 19:09:57 I recently tracked down the history, iirc it was closed something like late 2017 (maybe early 2018)-18, open from some time in late 2018 - sept 2019, closed since then 19:10:06 so registration closed more often than not over the last 3 years 19:12:43 don't mean to blame anyone, I have no doubt that it's super annoying to deal with 19:14:44 yeah, form traffic over that time does feel lower over last few years even taking into account that registrations have periodically been open 19:14:50 I do agree that any forum would always be somewhat low traffic 19:15:37 s/form/forum/ 19:15:59 unless we increase our player base by two or three fold, that is! 19:16:21 obviously we need to do something as big as implementing WebTiles back in 0.9; maybe time for VR crawl 19:17:09 it brought back Half Life, after all 19:17:09 reimplement in the alyx level editor 19:17:15 mmm 3-d moon base 19:18:30 imagine being savaged by a three dimensional cyan 't' 19:21:37 re migrating user info, one concern would be that (based on new server experience) we could expect to see bad actors claiming well-known usernames 19:21:59 so migrating at least some user info would mitigate that 19:22:35 (it is facts like this that make me despair about the community at times) 19:22:35 right, although since we have an on-file email for all current tavern users, is that actually too bad? 19:22:47 obviously if the original person is no longer around 19:23:09 I guess it's more work if someone does that as new service is launched 20:02:55 does discourse require unique usernames? I thought it was like modern gaming services where you get username#1234 20:05:15 it does require unique usernames. Anyway I guess you can easily add a rule "you can claim your old username" and manually remediate 21:06:42 huh discourse is quite resource intensive apparently 21:09:41 and also can't run without sudo? 21:10:44 wow 21:27:01 they provide docker images right? 21:28:52 yeah i guess sudo to install docker? 21:31:01 -!- Amnesiac_ is now known as Amnesiac 21:33:30 yeah i guess sudo to install docker? 21:33:31 oops 23:26:57 advil: aidanh: been running my PR for two days with no errors seen in that time. I'm happy to call it "ready to merge" now 23:30:17 sounds good; I might test it a bit on older tornado versions without a server restart this weekend 23:32:02 does merging this require intervention on the part of server owners if they are using a typical setup and need to restart the webtiles server? 23:33:00 also, does it require me to spend hours coaxing cao into working? 23:34:19 I haven't really looked at this PR so if the answer is anything but "it is utterly guaranteed to work flawlessly" I will need some prep time and I don't know when I can supervise that 23:36:47 it looks like it at least requires server owners to have upgraded tornado a bit... 23:38:20 at least going by the doc 23:40:30 these template changes will definitely require manual intervention 23:40:39 not sure I understand the config changes enough to know what it needs 23:40:51 anyways, I will have to look at this more thoroughly some other time 23:44:45 It wil require manual intervention because the diff includes changes to config.py, which every server has customised 23:45:26 at a minimum, the update process looks like: `cp -r config.py templates/ ~ ; git pull ; cp ~/config.py . ; cp ~/templates/* templates/` 23:45:50 s/git pull/git fetch && git reset --hard origin/master/ (since you'll get merge conflicts if you try and pull) 23:50:02 I think most setups don't run webtiles out of a repository, they copy a subset of the files into place (not including config.py) 23:50:08 I imagine most servers use dgamelaunch-config, so they'll require different instructions 23:50:11 yeah 23:50:54 I'll take a look at some point but right now I'm heading to sleep 23:51:35 yeah, they use a templated config.py, which is published by a dgl command from dgamelaunch-config 23:51:47 published into the chroot, I mean 23:53:08 oh that's cool. I've updated the OP of my PR with a full changelog, as well. The PR thread is a bit cluttered 23:53:24 oh, in fact, they'll have to manually merge in config.py changes, right? 23:53:35 the config.py is typically checked into dgamelaunch-config 23:53:52 which is its own repository 23:54:09 to that end we may need to merge a config.py into that? 23:54:11 none of the changes I've made are backwards-incompatible, so their existing config.py files will work as-is 23:54:41 all the new functionality is opt-in 23:54:41 sure, but still it'd need to be integrated 23:54:50 not sure if aidanh was going ahead with merging that repo into crawl 23:55:10 we sort of discussed that at one point and I know advil was concerned (as was I, but I'll defer to people with more expertise) 23:56:21 yeah, indeed I see on CAO that changes to config.py are commited to dgamelaunch-config checkout 23:57:00 alexjurkiewicz: This is the repo for that, which I think you know of already, but there's a config.py in there that should be updated 23:57:32 hrm, but I guess that one has installations for specific versions, as it's based on cszo's config 23:58:13 I suppose it would be wise to update this with each new version as long as it does remain as its own repo 23:58:18 hm, you're saying I should submit a PR to dgamelaunch-config to use all the new features I'm adding in this PR? 23:58:43 you might want to coordinate with aidanh on that a bit, as he has plans that perhaps intersect with his chroot work 23:59:01 but at some point this should be updated to reflact changes from your branch I think 23:59:24 since this is something each admin must incorporate, probably not a priority to update this before your branch is merged