Obscure URLs (new FAQ)
-
Continuing the discussion from Obscure URLs:
Just added a new FAQ for easily discoverable URL modifiers. Discuss....
-
Is the raw URL mentioned in another FAQ? If not, it should probably be here.
-
How about that self-one-boxing requires fucking up the topic name in the url? Apparently you have to remove at least a dash because just typoing a letter doesn't work.
See:http://what.thedailywtf.com/t/obscure-urls-new-faq/2089/3
http://what.thedailywtf.com/t/obscure-urls-new-fuq/2089/3
-
Is the raw URL mentioned in another FAQ? If not, it should probably be here.
It's in:
http://what.thedailywtf.com/t/viewing-source/780
though it couldn't hurt to cross reference it, and add in /p and the other foibles such as the /t/this_bollocks_ignored/topic_id/post_id mentioned in the above post..
You (personally, and anyone else who hasn't yet) may find it useful to at least scan all the posts in /meta/faqs - most (if not all) is stuff I didn't know when I first came to DC, and couldn't find documented in an easily to find [central] place - hence my creation of that category to begin with...
-
How about that self-one-boxing requires fucking up the topic name in the url?
http://what.thedailywtf.com/t/x/2089/3
:http://what.thedailywtf.com/t/x/2089/3
http://what.thedailywtf.com/t/obscure-urls-new-faq/2089/3
:http://what.thedailywtf.com/t/obscure-urls-new-faq/2089/3
Hmm. Interesting. Don't recall seeing that mentioned before, I'm assuming it's in /t/1000 ;) Did it make it to bugs or meta.d? I'm assuming not...
-
Hmm. Interesting. Don't recall seeing that mentioned before, I'm assuming it's in /t/1000 Did it make it to bugs or meta.d? I'm assuming not...
I doubt they'd care, self one-boxing is a silly thing to do.
But it doesn't make it any less bizarrely broken. It's all about how their JS parses things, and tricking it into thinking it should do something when it really shouldn't have.http://what.thedailywtf.com/t/obscure-urls-new-faq/2089/5
-
futureboxed require edit of original post or no?
yep - requires editing original post apparently.
-
http://what.thedailywtf.com/?search=poop (reload)
http://what.thedailywtf.com/?state=muted
http://what.thedailywtf.com/?state=tracking
http://what.thedailywtf.com/?state=watching
-
also see:
-
You (personally, and anyone else who hasn't yet) may find it useful to at least scan all the posts in /meta/faqs
I thought I had. However, it's easy to miss stuff there, because Discourse seems to treat pinned topics specially* in the latest topics list. Nothing ever seems to update the latest activity timestamp, so they get pushed down the list, never to be seen again.
Even if I did read it, which I probably did, that doesn't mean I remember it. My memory seems to work best for things I'd rather forget, like that embarrassing incident in high school, but not for important things like the task I was assigned before lunch.
* As in "ride the short bus" special.
-
pinned topics [...] get pushed down the list, never to be seen again.
And here I was thinking that there was no way Discourse could B*****m up such a basic forum feature.
-
You'd be surprised what Discourse can break.
-
Not any more. Not any more…
-
/srv/status
Replies 'ok' if the server is running. 100% useful in every way.
-
What does it reply if it's not running?
Edit: I guess the server doesn't like being trolled. 500 error trying to post this.
-
I presume this is either a "it returns ok" or a "it doesn't return" sorta thing? :)
-
Precisely - that endpoint is used by our server monitoring script to spam the chat when Redis goes down.
It will also supposedly return 500 "
shutting down
" if the global$shutdown
variable is set, but.... in my experience it doesn't take too long to stop the server, so you'll probably never see that.
-
Thanks, RubyMine!
So apparantely,
touch /var/www/discourse/tmp/restart
will cause the web workers to drain requests, start replying "shutting down" to /srv/status, and SIGHUP itself.Never heard about that.
-
.../tmp/...
Interesting choice of location....
-
That's handy for shit like AWS load balancing, which requires a URL of some sort to hit to see if instances are still responding or not. Sadly, I have to defend Discourse on that one.
-
##
/srv/status
Replies 'ok' if the server is running. 100% useful in every way.
Reminiscent of:
-
/?x
(or whatever instead of x)
shows a nice 0 byte page with a 500 response code.
Filed under: I don’t even want to know
-
Reminiscent of:
Also http://www.haiku-os.org/legacy-docs/bebook/TheKernelKit_SystemInfo.html#is_computer_on
-
New obscure URL for you, @PJH!
/about
Lists the admins and moderators, and includes some quick stats about the forum.
This was introduced because sending topic count data along with a version check is a breach of privacy, so therefore it must be better to expose those stats to everybody.
</sarcasm>(It kinda is better, actually - any forums inaccessible from the internet will remain wholly private from data collection for venture capital purposes. And CDCK doesn't have an unfair advantage in being the only one able to collect those stats.)<sarcasm>
-
Is it really obscure if there's a link to that page in the hamburger menu?
-
Oh, didn't realize that was added too. Whooops.
-
Is it really obscure if there's a link to that page in the hamburger menu?
Discodiscoverability!
-
-
Is it really obscure if there's a link to that page in the hamburger menu?
Do people actually click that thing?
Filed Under: obviously not me
-
Apparently but I haven't gotten a hamburger out of it. False advertising!
-
I only do if I want to jump directly to a category, because it's quicker.
-
I click it to look at the badger list every now and then.
-
I think the last time I looked at it was before when the badges were put there. I tend to edit the url. Though usually I click through to my profile, click on a badge and chop some off of the end.
Filed Under: That's what Lorena Bobbit said
-
that reminds me, I need to make it so editing
/admin
in front of a badge url does something sane