7heo

It's being DDOSed. Too many users. Too many submits. The rendering code is light enough on the server that it still works (most of the work is client side, the sever just serves a bunch of json files), but the submitting code definitely crashes.

Cool, but it's now impossible to submit anything, as the server is being DDOS'd. Not out of malice, mind you, there are just too many geeks out there, and this is a Sunday...

Still, one can read the titles of the already posted rooms with:

env URL=https://incredible.xkcd.com \
curl -SsL $URL/machine/current \
| jq .grid[][] | grep -v '^null$' | tr -d '"' \
| while read uuid; do printf '%s: ' "$uuid"; \
curl -SsL $URL/folio/$uuid \
| jq .blueprint.title; done

(Useful to find out if your room made it to the public set)

I didn't know if it is traveling, or if this is another.

They seem to be unrelated. (This one, as per the video (1:22), was inspired by "a similar exhibit in the US")

Me want. You should host a cooking show on aNONradio. 😋

The human body as a subway map

The male body as a subway map

Larger might be acceptable too, not sure

It should.

Also, work off of the copy. Never touch the source.

A then C. If you know how to do it[^1] ofc. If you don't, then assume it is. Very different situation if the weapon is loaded. Both require C, but one much more intensely than the other.

[^1]: Hopefully /s is obvious enough here, but I'm not taking chances: /s, OK?

Usually that's about when I strace the process before running it through gdb...

Yes, I get that point, but I also think that it's tempting for the privacy-minded novice to think "the less information I provide, the better!", while in actuality, it is better to provide "more" information: the most common UA, even if it means lying about your featureset. In this case, truly, more is less.

Glad someone noticed 😋

Oh gee, I wasn't aware there was more to it than the UA. Thanks for opening my eyes.

Edit: I checked your link, most of the parameters on the test require client side execution. That (client side tracking) is absolutely unrelated to what (server side tracking) I was talking about, and is something you can control (by not allowing JavaScript, for example). Please do not confuse the two. There is literally nothing you can do against server side tracking.