03:33:21 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-5208-geafff8c3b6 05:21:34 Unstable branch on crawl.akrasiac.org updated to: 0.33-a0-223-g0945138 (34) 07:09:41 <09gammafunk> @icoson Someone pointed this out about the future of the io TLD. It's sort of spooky, although the authors of this article claim that it's nothing to worry about in the short term: https://www.computerworld.com/article/3552692/is-the-io-top-level-domain-headed-for-extinction.html 07:11:41 03nicolae02 07* 0.33-a0-224-g21dfed3d1e: Make a scroll shop always ID the scrolls lying around 10(3 minutes ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/21dfed3d1ea2 08:44:29 <06mumra> It sounds to me like most likely a non-issue. Near the end the article says Edwards’ advice to any organization that might be impacted is this: “There’s no need for anyone with an .io domain to panic. The IANA may decide to fudge their own rules and keep the domain going, perhaps assigned to Mauritius instead, or by turning it into a generic, non-country domain. Even if they decide to deprecate it, this will be managed over 08:44:30 multiple years.” I think one of those first two is by far the most likely, they will just keep it going in some form. Retiring a tld that is so heavily used seems like such a problematic move. Best option is to make it a non-country domain (since that's basically what it gets used as anyway) 09:11:01 <09gammafunk> Yes, I read that, but as the article says, precisely what will happen is very unclear at the moment. Other articles I read were a bit less rosy about the future. However I agree that it seems unlikely that the TLD continues on with a different ownership and configuration. But it's certainly reasonable to consider moving off of io (as the article mentions at the end) 09:12:16 <09gammafunk> I just really want to keep the CDI designation, so clearly I'd just have to find another TLD beginning with i and register the dcss domain on that one 09:13:25 <09gammafunk> (I am not actually doing this but if it somehow came to that, I would) 09:32:12 <06mumra> The difficulty is, even if you migrate to a new tld and presumably put a forwarder in place, there are still 1000s of places on the internet that still link to the old domain. So this move would effectively create billions of broken links across the whole internet. You could consider putting something special in globally at the DNS level to forward the old tld to the new one, but this relies on everyone having migrated to exactly the 09:32:13 same domain name on the new tld, which is far from guaranteed. And the whole thing would be completely unprecedented. Instead of creating all that effort and upheaval, and having a crazy DNS exception in there anyway, surely it's simpler for them to make a different exception and just keep .io alive however that is implemented? Which is why I believe that's what will happen in the end. Still, it's an interesting situation -- but apparently not 09:32:13 completely unprecedented: https://snapshot.internetx.com/en/these-tlds-do-not-exist-anymore/ Seems a variety of strategies are used on a case-by-case basis but the .su domain is most interesting as it's another case of a territory ceasing to exist, but ICANN kept the old tld going by request. So the article is misleading to begin with when it says "IANA bases TLDs off ISO 3166 country codes. If a code stops existing, in theory, they follow suit and 09:32:14 kill the TLD". There's already a precedent for TLDs to not exactly follow 3166. Would be really surprised if they didn't do a similar thing in this case honestly. 09:33:31 <09gammafunk> cool, thanks for the extra info and link 09:34:04 <09gammafunk> but I am thinking about ge0ff's suggestion of .it and the potential mario-zelda CDI crossover memes 09:35:20 <06mumra> But ... what if Italy ceases to exist? 😂 09:54:30 <09gammafunk> Mario, no! 09:54:41 Only one thing for it. Someone will have to apply for the .crawl TLD. 09:54:58 <09gammafunk> Aliscans gets it 09:55:07 <09gammafunk> my server can be CCC, crawl.crawl.crawl 11:39:47 -!- kenzie1 is now known as kenzie 11:46:59 <06mumra> .crawl should legit be a TLD 12:19:59 <09gammafunk> another pass at the ideal crawl hostname and TLD: dungeon.crawl.stone.soup We need to fully bikeshed this for the dcss 1.0 release 13:00:20 -!- prokopus is now known as tf16 13:00:30 -!- tf16 is now known as tf17 13:15:00 -!- aoei is now known as theWeaver 14:09:19 <06mumra> to modernise the name a bit it needs trimming. "dungeon" is really superfluous at this point, 1.0 should just be "Crawl: Stone Soup" 14:30:45 <06pleasingfungus> do we really need the stone..? 14:40:09 <09gammafunk> delicious crawl soup 14:41:21 <06mumra> "Soup 1.0" 15:37:24 Unstable branch on underhound.eu updated to: 0.33-a0-224-g21dfed3d1e (34) 18:53:12 I found a call to exercise.practise_being_hit(), which seems to follow the old method of training skills. That is, train a skill by using it. 18:53:13 But as far as I know these days crawl simply distributes experience points to skills. 18:53:13 Does someone know if my understanding is correct? 18:54:57 sefie: The skill menu lets you choose between automatic and manual skill training. The former works something like the old method, training more of a skill you use. This might be a question better for #crawl, the new Tavern... 19:24:49 <06pleasingfungus> eh, it’s a question about code 19:24:54 <06pleasingfungus> seems reasonable to ask about code here 22:35:21 Unstable branch on crawl.develz.org updated to: 0.33-a0-224-g21dfed3d1e (34) 22:57:36 Windows builds of master branch on crawl.develz.org updated to: 0.33-a0-224-g21dfed3d1e 23:13:01 Unstable branch on cbro.berotato.org updated to: 0.33-a0-224-g21dfed3d1e (34) 23:55:12 Monster database of master branch on crawl.develz.org updated to: 0.33-a0-224-g21dfed3d1e