Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Xymph

Members
  • Content count

    132
  • Joined

  • Last visited

About Xymph

  • Rank
    Junior Member

Recent Profile Visitors

639 profile views
  1. Xymph

    DSDA api

    As predicted, it took many hours spanning two weeks to update over 5700 invocations of the dsda template into dsda2, but it's done now. Remaining uses are for files not imported into the current site, and old discussions. Phew.
  2. I have no idea, Manc hosts multiple community services (e.g. the SLADE site) so that's up to him. But from my chats with Quasar, it seems more likely that the main obstacle is the need for an active Linux admin who can configure and maintain a modern OS (probably on a new server), and which Quasar seems too busy/shy to try and recruit from the community. Although he did mention it in some discord (dunno which or to whom) and nobody seemed interested there. So I'm just tossing it out here now. Fact is that not only the OS is outdated and no longer supported, so is the MediaWiki version. So the wiki really could use help from someone who'll stick around.
  3. What I understand from Quasar is that the crufty old server suffers from two types of problems: Apache/php5-fpm lockups, which have been happening occasionally for a long time but are easy to solve by restarting them; and, more recently, "other" problems that prevent ssh connections, and require attention from Manc who hosts the wiki and has access to the server's control panel. Currently we're in the latter situation, so waiting for Manc to address it. Edit: And... it's back. :)
  4. Xymph

    DSDA api

    Ok, that's what I suspected, thanks for the confirmation.
  5. Xymph

    DSDA api

    Yes, some two dozen wad paths (relevant to the Wiki) needed updating, including most Master Levels entries. Oddly, https://dsdarchive.com/wads/diamonds is missing (for https://doomedsda.us/wad1598.html) - why is that? Thanks again, here is my fixed list: dsda_wads-fixed.zip
  6. Xymph

    Problem with downloads

    Don't you think, when reporting possible link problems, that it would, maybe, be handy to include source and destination of the links this pertains to? ;-)
  7. Xymph

    Problem with downloads

    It was retired late last year. Well, in September already, but I gave Manc a few months to sort it out, to no avail.
  8. Xymph

    idgames archive problem with google chrome

    gamers.org simply doesn't support HTTPS yet, so nothing is "messed up" as such. The type of content has nothing to do with it, and they're zipped up anyway. As others have observed this is Chrome being finicky. No need to panic. :) First, there are plenty mirrors including several with HTTPS support. Second, our server needs an OS upgrade one of these months anyway, after that I'll set up Let's Encrypt.
  9. Xymph

    The Next Iteration of DSDA

    https://dsdarchive.com/wads/hellbnd and https://dsdarchive.com/wads/hellbnd_old show Zoltán Sófalvi misimported as Zoltßn S¾falvi.
  10. Xymph

    The Next Iteration of DSDA

    https://dsdarchive.com/wads/grnmchn is ranked under the doom2 IWAD, but its text file states it was designed for Final Doom: Plutonia.
  11. Xymph

    The Next Iteration of DSDA

    https://dsdarchive.com/wads/perdgate has a double-escaped apostrophe in the <title> tag, "Perdition&amp;#39;s Gate". It's single-escaped in <meta name="description"> and the <h1> header. There might be more such cases, I didn't do an exhaustive search.
  12. Xymph

    DSDA api

    I can take it from here, thanks.
  13. Xymph

    DSDA api

    Yup. Except the old ID of Scythe is 789. :)
  14. Xymph

    DSDA api

    I see. Perhaps we need to rethink whether to maintain record tables per map article, but that's a wiki discussion. The WAD links need to be updated regardless, but I momentarily blacked out on the fact that I already mapped the player IDs/names, at least for the speedrunners covered in the wiki. So that part of the request is dropped. Meanwhile... ... I'd really want to approach the WADs from the ID angle, which are configured separately in the bot .ini files for this very purpose, and not filenames or anything else. If you could just export that one table in any format that's easy for you, without manual reorganizing on your end, then I can first automatically update/verify templates and second deal manually with any stranglers/mismatches. Then I'll let you off the hook on the redirects and the API. :-) Please do at least this one little thing for the wiki?
  15. Xymph

    DSDA api

    Now that Andy's site has shut down, this has become vital for the wiki, which had 9100+ links pointing into the void. I've archive.org-ed links in relevant templates but demo zips are typically not archived there, so the templates should really point to the new site, with the numeric wad/player IDs getting redirected to the new names. That would only be the short-term solution of course. The longer-term solution is to provide two mapping tables (in .[ct]sv or .json format?) of old IDs to new names, so that all old dsda* templates on the wiki can be changed into new dsda2* ones via XymphBot scripts. And then the API would need to be finished and documented, so that record tables (with zip links) can be updated script-wise, like I've already done for all Compet-n record tables. Can I ask to please prioritize this for the wiki's sake?
×