[02:54] Oh that's annoying. I went through it with both `ftp` and `curl`, and with both the old (/Public/UCD/latest/ucd/) and new (/Public/UNIDATA/) paths, and none of them work directly. [03:02] However it appears that an FTP `ls` command at least *shows* the link destinations, so perhaps it's a matter of parsing the file listing. Here's what I see when I just curl against the directory containing the symlink: [03:02] $ curl --ftp-method nocwd -s ftp://ftp.unicode.org/Public/UCD/ [03:02] lrwxrwxrwx 1 ftp ftp 41 Sep 16 15:16 latest -> /Public/18.0.0 [03:03] Then replacing UCD with 18.0.0 gives a full listing. [03:03] So it probably just needs a new routine to parse out the symlink destination and patch the URL with it [03:39] Using Filezilla I saw 550 permission errors, so I assume the server just set up the symlinks wrong. What I decided to do was swap over to HTTPS since that would be easier than swapping to a more low-level use of FTP. [03:41] I also get the impression that perhaps the FTP server isn't really intended for use anymore, given you'd be hard-pressed to find any mention of it on the Unicode site (I could only find a reference in a fossilized page from 2005). You also can't establish a secure connection to it, which enhances that "old and unmaintained" feel. [06:32] but you don't need all files I think: https://github.com/MoarVM/MoarVM/blob/main/tools/UCD-download.raku [06:34] if I'm reading that right and picking right file, it could simply use `https://unicode.org/Public/` instead of `ftp://ftp.unicode.org/Public` [06:35] eh, right, nevermind MAPPINGS are a folder, not a file [06:44] ah, but if you look closely, it just fetches 2 files from mappings [06:50] just using `"https://unicode.org/Public";` mostly works, and if you need the latest files, `wget -np -r` would work [06:50] (due to structure changes etc.) [08:02] *** vrurg_ joined [08:04] *** vrurg left