@JourneymanGeek of course. Here is the link, it's done on purpose so people will have to work hard to find it.
Or just a test, to see if anyone actually reading their blog posts and/or care enough to report "Hey, this is a podcast but where's the link?".
I surely don't. lol
@SPArcheon doing what?
@user16217248 well generally speaking, ordinary user should never get the 500 Internal Server Error, assuming that's what you mean, so yes worth a bug report. Don't understand what you mean about 404, if you mean bug report about 404 Not Found error then no, unless of course it's coming for something that should exist.
@SPArcheon oh, I keep forgetting the script he's using also move all commands, not only spam feedback. Almost makes it useless to use the fun commands, but just almost. Coffee serves its purpose and can be discarded, so it's fine. I guess. :D
@SPA but I'm pretty sure the !!/hats command didn't work last year when WB was still active, i.e. long dead anyway. Maybe they predicted the future.
@ShadowWizardIsSadAndAngry Now, it won't happen and it would require a lot of work... but it would be VERY funny if Codidact announced a Winter Bash like event....
Anyway, I was correct, nobody read the blog. Long hours after the podcast post posted without link to, well, the podcast, not a single bug report and of course SE staff didn't check/see/fix it. So sad, but so typical.
They just post and forget without reading what they posted. This latest one is total proof for that.
Yeah. In theory - see if somebody posted a command like "tp", follow that to the post that was replied to, see if that post mentions a URL, find a report for that, apply the TP to the report.
But it could also be incorrect.
@terdon Well, we've seen that even editors haven't read it in the past, so you're right! /s
