The main site was moved to a new server as the old one had a dying disk. We are now on a much more modern system with SSDs, a faster CPU etc. You probably will not notice much of a difference though.
For debugging: The old IP starts with 136., the new one with 23.
There is no IPv6 support yet.
I decided to switch over quickly and without much testing, if there are any issues please report them. So far everything seems to work.
Uh, not sure what is wrong right now, I am on it.
I have pointed the domain back at the old server for now.
Back on the new server.
The old hosted pages’ subdomains (blitz, daz, dsp, kell, necros, negke, nntt, pulsar, qurnel, rudl, speeds, than, vigil) need fixing and I will do that in ~2 weeks due to reasons…
Hi, Spirit. I am still working my way back in time through maps on the old site so I am not going to run out of maps to play any time soon. But I’ve noticed that the last new release on that site ( sm226.zip - Speedmapping pack 226 - Grisly Grottos) is from 19 September 2023. In other words, in only ten days, it will have been a full year since a new map appeared on Quaddicted.
Do you have any sense of when new material will start to appear again? I’m worried that Quaddicted will lose traction if it’s missing all the new hotness.
While they are not viewable by the general public yet, there are many maps that have been submitted through July of this year that are in the database. I am not answering for Spirit, but at least I know that much. And although it’s taken a while, in the long run, Quaddicted will still have plenty of traction in the years ahead. picture of db
Thanks, Dumptruck, that is really good to know.
But I do hope you can find some way to make them visible RSN, even if it’s an inelegant, hacky way. I fear that the longer Quaddicted looks devoid of new maps, the more people will leak to other sites.
I am trying to figure out what is broken with the comment embedding in the beta site and once that is done, I will simply publish it. There is still tons to do but it is usable (which is better than a stale site) and perfection can suck it.
Edit: haha, nice previews, found another todo 
Howdy Spirit and Co.!
I’ve been working on a new Map of the Day bot (Bluesky and Mastodon/Fedi) that uses the new database via the web frontend that’s presented to users on the website.
Just wanted to get permission before I set it loose “in production” – also just in case the current landing site (/db/v1) that was referenced in the TODO here isn’t going to be what the public winds up using.
tech notes: current new implementation turns the HTML table at /db/v1 into a hash/array, randomizes the shortened sha256 column, picks out the …/files/ and …/maps/ entries for json schema and screenshot resources.
Old version just downloaded the XML db once in a blue moon and parsed that for just about everything. 
Thanks for all the hard work!
Awesome, thank you!
The /db/v1/ will contain more than just maps in the future, so best use a filter like https://www.quaddicted.com/db/v1/?include=metadata->tags.cs.["game=quake"],metadata->tags.cs.["game_mode=singleplayer"],metadata->tags.cs.["type=map"]
The maps URLs should stay as they are I hope, so e. g. linking to https://www.quaddicted.com/db/v1/maps/cc8005e4aa7df6b1f1a33c60a1060cf1e0e4314f5710dbbe6f21d72dcbd6b174 should be future-safe. https://www.quaddicted.com/db/canonical/cc8005e4aa7df6b1f1a33c60a1060cf1e0e4314f5710dbbe6f21d72dcbd6b174 is meant to become a canonical page for a file in the future but you probably want the “map rendering” of it so that would be a distraction.
There is also a PostgREST endpoint but not at its final location yet. That would give you JSON directly and I think you could also shuffle server-side. PM me if that would be interesting for you.
Awesome stuff; would definitely be interested in a raw JSON digest as it would make things a lot less convoluted on my end!
Let me know when things start congealing and I’ll work with what you’ve got!
Cheers
