I probably could find out using the API. But I'm just chatting with you elephant! Also just leave me a note, whom to kill first from these EU politicians. I'll mention you in a letter claiming responsibility if that went successfully. /sarcasm off
I don't want to involve "killing" at any point! /sarcasm off
@Catija Yum!
@Shog9 "the wasabi" Well, yperite is banned as a weapon for reasons. I love horseradish to watercress for my personal use a lot. But that doesn't mean I'd not ban that kinda gases from gathering upon SE's business model.
As you can try yourself, sometimes searching for a number redirects you directly to a question with that id: https://meta.stackexchange.com/search?q=129674 or https://meta.stackexchange.com/search?q=129093. But sometimes not: https://meta.stackexchange.com/search?q=129094 or https://meta.stackexc...
Already exists. Searching for a specific question ID will take you to that question.
Proof? Try searching for "43410" right now.
This does not work for answers, however.
Huh I didn't know search even did this. I'm not sure why it does this. Seems like a fairly useless feature, especially if it's not consistent. — animuson ♦Nov 24 '17 at 5:03
@AdamLear Can you close the above question as a duplicate, then?
not sure if it's actually useful in practice, but it seems like we should just stick to returning a matching question as part of the search results rather than redirecting
I think that feature should be removed. I'm not sure it has much utility these days, and for those who do want to access a post with that ID, one can simply manually access the URL for it.