[Feature] Add support for Crosshare crosswords

[krt222]

Hello!

It would be nice if support for Crosshare's puzzles was added to xword-dl. Crosshare is an open source website with its source code published on github.

Source code: https://github.com/crosshare-org/crosshare
Website with example puzzle: https://crosshare.org/crosswords/cYidP5pm3pv4Slh7lkVd/mini-4-thursday-17

Note that the open source browser extension named Crossword Scraper (https://github.com/jpd236/CrosswordScraper) can successfully parse the page and produce a .puz file.

Thank you!

[thisisparker]

Hi there! I've actually considered this one for an application where I use xword-dl, and IIRC might have even built a working prototype, BUT I pulled it out when I learned you can use the API to get a working puz file. E.g. for the example you provided, https://crosshare.org/api/puz/cYidP5pm3pv4Slh7lkVd should trigger a puz download.

It looks like thta's what the Crossword Scraper extension does at least some of the time, too, though it does try to get the info from the JSON on the page first maybe.

This may be too precious but I've previously limited the scope here to actual scraping. Would it be useful to you if xword-dl itself made the substitution? What I really wanted to avoid is a situation where somebody adds a downloader that just pulls from an existing puz source, but this seems a little different.

[krt222]

Hey!

I didn't know that a Crosshare .puz could be download in that way. Thank you for pointing it out!

I'd argue that Crosshare is more or less the equivalent of AmuseLabs in the indie crossword community; that is, puzzles uploaded there frequently get embedded (https://crosshare.org/articles/embed-crossword-puzzle) in crossword setters' sites and blogs. So, it would be really useful if a xword-dl https://blog.example.org/my-new-puzzle.html would download the .puz from the embedded Crosshare puzzle.

I think this is in line with the description of the app ("... or arbitrary URLs with embedded crossword solvers"), although I can understand, respect, and support the notion of scope as a developer decision.

Thank you again.