What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 143 Stack Exchange communities.

Ask yourself how many times you typed the following in a Comment:


Me, personally, I'm sick of it. Can we have some data.stackexchange.com-style "magic links" inn comments? (inn~iff)

Very, very good idea, especially the FAQ#name one. –  Pëkka May 20 '11 at 13:18
Please, please, pretty please? –  Ghost User May 20 '11 at 13:30
Why inn? At least on meta they'd be very useful in answers –  Michael Mrozek May 20 '11 at 20:30
Instead of alternate forms (as you have for edit), why not provide generic text? [edit "edit it"] [faq#bounty "Read about bounties in the FAQ"] –  Fred Nurk May 21 '11 at 6:35
Don't see the need for combining [user:] with notification. –  Fred Nurk May 21 '11 at 6:35
Requiring a colon in the syntax is less likely to have false positives. Instead of Stack Overflow and [x.se], use [site:XXX] where XXX is SO, SU, SF, or the subdomain of SE. [faq:all] and [faq:section] work, but that leaves nothing for edit except [edit:], which I dislike. Maybe [link:] instead of [site:], then you can include "faq", "meta", and "edit" in [link:]. –  Fred Nurk May 21 '11 at 6:38
@fred no, you type [@fred] (like user notification) and it turns into a link - Fred Nurk. –  Won't May 21 '11 at 14:57
I've actually never typed that in a comment. Then again, I'm not a mod... –  Mehrdad Jun 8 '11 at 15:51
I made a similar feature request some while ago: meta.stackexchange.com/questions/77351/… . I guess I added to much text ;) –  Felix Jun 8 '11 at 16:06
I wonder if edit works? –  Won't Aug 26 '11 at 14:35
Oh super super! I love you with totality and Tootsie-Rolls. With our collective saved-time we shall ascend to Mars, Pluto, and Milky. –  Adel Oct 23 '11 at 2:25
test tour tour tour –  nicael Sep 21 '14 at 9:06

9 Answers 9

up vote 187 down vote accepted

Most of these now work. My comment below has the following markdown source:

On [main], you are expected to write proper English (as advertised on [english.se]), but here on [meta.se] it's more important to have freehand circles, so please [edit] your post, otherwise I'll have to flag you (see the [FAQ#flagging]). If you're unsure how to use your keyboard, [su] is the right place to ask. There's no Q&A site about unicorns yet, but you can suggest one on [area51.se].

Supported magic links:

  • [meta] – link to the current site's Meta; link text is the site name (e.g. "Super User Meta"). Does nothing if the site doesn't have (or already is) a Meta site.

  • [main] – like [meta], just the other way around.

  • [edit] – link to the edit page for the post the comment is on, i.e. /posts/{id}/edit. Link text is "edit" (capitalization is respected).

  • [help] should be obvious. [meta-help] links to "What is meta?" (/help/whats-meta), [help/on-topic] links to "What topics can I ask about here?" (/help/on-topic), [help/dont-ask] links to "What types of questions should I avoid asking?" (/help/dont-ask), [help/behavior] links to "What kind of behavior is expected of users?" (/help/behavior). Link text for all of these is "help center" .

  • [tour] and [meta-tour] – equivalent to the FAQ version, but links to the site's Tour page (resp. the meta site's Tour page). Link text is "tour" (capitalization is respected). Legacy names [about] and [meta-about] are still supported.

  • [ask], [answer] – link to the "How to Ask" / "How to Answer" page.

  • [so], [su], [sf], [metase], [a51], [se] – link to the given site (Stack Overflow, Super User, Server Fault, Meta Stack Exchange, Area 51, the Stack Exchange portal). Link text is the site name.

  • [something.se] – link to something.stackexchange.com, if that site exists. Link text is the site name. Use [ubuntu.se] for Ask Ubuntu. [meta.something.se] links to the meta site.

  • [chat] – link to the current site's chat site (http://chat.stackoverflow.com/ for SO, http://chat.meta.stackexchange.com/ for Meta SE, http://chat.stackexchange.com/ everywhere else, that last one showing a list of active rooms from the referring site), the link text being "{site name} Chat".

Except for [chat] and [edit], and with the addition of [chat-faq], these also work in chat.

On [main], you are expected to write proper English (as advertised on English Language & Usage), but here on Meta Stack Exchange it's more important to have freehand circles, so please edit your post, otherwise I'll have to flag you (see the FAQ). If you're unsure how to use your keyboard, Super User is the right place to ask. There's no Q&A site about unicorns yet, but you can suggest one on Area 51. –  balpha Jun 6 '11 at 11:48
Very nice, but what about user pages and links to specific posts? Like [main#12345] or [meta.user#12345]... –  fretje Jun 6 '11 at 12:06
@fretje: Nope, we're not doing that. It'll take longer to copy the id out of the URL into your [main#...] markup than just copying the whole link. (Besides that, there's also a technical reason: Comments are rendered on the fly, so you'd have to do a DB lookup everytime such a comment is displayed) –  balpha Jun 6 '11 at 12:11
@fretje: Do you really have the ids of posts you frequently link to memorized? –  balpha Jun 6 '11 at 12:16
And apparently my above comment doesn't work... even the Stack Overflow only hasn't been "translated"... I suppose that's because there have to be spaces around it... could you also translate when there's a '/' after it? –  fretje Jun 6 '11 at 14:41
Oh, ok, just to test then: Stack Overflow/q/6254529 –  fretje Jun 6 '11 at 17:28
Oops... not as I had in mind... Ok, but I understand adding "/q/6254529" to the url would be easy, but then the problem would be what to put as the link text? In that case you could simply expand the url to stackoverflow.com/q/6254529 but that might make this feature indeed be too "complex". I was just thinking out loud... forgive me ;-) –  fretje Jun 6 '11 at 17:34
Yay! Two more requests: [how-to-ask], [how-to-answer] (and the anchored versions when they're created). –  Gilles Jun 6 '11 at 20:05
@jcolebrand: the former –  balpha Jun 7 '11 at 15:36
sweet. muchos danke. or is it gracias schoen. or something. ;) –  jcolebrand Jun 7 '11 at 15:37
And [user:@balpha] adds more awesome to SE :) –  Benjol Jun 8 '11 at 7:46
The site-links are nice, but inconsistent: why don't [superuser.se] ([superuser.se]) and [askubuntu.se] ([askubuntu.se]) generate links? Sure, [su] (Stack Exchange) and [ubuntu.se] (Ask Ubuntu) work, but why do I have to remember these special cases? Thanks! –  sarnold Jun 24 '11 at 8:56
Could we also have [stackapps] (or [stackapps.se], or even [sa]), please? –  Gilles Jul 18 '11 at 0:27
Hey, just found myself wanting [stackapps]. Poor, stackapps, it gets no love. –  Won't Oct 28 '11 at 14:23
Can we puhhlllease have [mso] instead of [metase]? Or [meta.so]? No one remembers the [metase], it doesn't even make sense. –  slhck Nov 3 '12 at 12:29


Some more ideas, since this seems to be still active.

Maybe it could also be useful to add things like:

  • [dupe:92060] for "possible duplicate of "
  • [inbox]
  • [review], but I think this is marginal
  • [privilege:name] to link to a specific privilege description


I think this idea can be improved in a generic way like:



  • SITE is SF, SO, SU, meta, metaSU with default to the current site
  • type can be user, post, faq with default to post
  • anchor/id can be the id of a post, of an user and anchor a HTML anchor like in the FAQ, or a comment, or a anwser.

You can only use default values from the left. If you specify SITE you have to specify all.

So on this post:

  • [92060] would link to [meta:post:92060]
  • [92060#answer-92061] would link to my answer (need way to identify the answer's numbers)
  • [SU:post:286219] would link to Unix : List children processes for a given pid
  • [user:1228] will link to the user with ID equal to 1228 on meta
  • [SO:user:1228] will link to the user with ID equal to 1228 on Stack Overflow
  • [SO:faq:#bounty] on the "bounty" section of the SO's FAQ
I especially like the privilege and dupe idea. –  Octavian Damiean Jun 8 '11 at 15:49
I'd really like to link to specific posts, especially on meta. Would be super handy in executing moderator duties. Prefer syntax of [meta:92060] or [main:667]. –  Alex Angas Jun 29 '11 at 0:05
up vote 22 down vote

In addition to [so], [su], [sf], etc. I would suggest adding [careers] with link text of "Stack Overflow Careers".


I would like an [ACCEPT] which would link to How does accepting an answer work?


A chat room link could be useful I think.


This wouldn't be that useful, more like a fun thing, linking to yourself.

[self] or [this]? :) –  balpha Jun 8 '11 at 15:33
Semantically [self] would make more sense in my opinion. :) –  Octavian Damiean Jun 8 '11 at 15:34
[this] would refer to the current chat room or comment in my weird logic. :D –  Octavian Damiean Jun 9 '11 at 8:22
I would prefer [this] for linking on the chat room and [self] for linking on myself. –  CSchulz Jul 28 '11 at 14:25
[chat:ROOM_NAME] might also be useful –  Merlin Sep 11 '11 at 9:49
[me] would be quicker and more IRC-esque. Though less obvious to OO programmers ;D –  Merlin Sep 11 '11 at 9:50
@Merlin [me] would be a link to your SO or chat.SO profile. –  Octavian Damiean Aug 24 '13 at 14:58

From the meta sites, I think we most often want to link to the FAQ of the main site, not of the meta site.

Can we have a magic link along the lines of [mainfaq#dontask]?

Alternatively, do it just like we do with tags - have [faq] link the Main one, and [meta-faq] link the Meta one, whether you're on Main or Meta. –  Grace Note Jun 9 '11 at 15:18
We're going with @GraceNote's suggestion. –  balpha Jun 13 '11 at 17:28

I'm not convinced that new markdown is needed, this could be handled by having a better interface to insert these links.

There are already a few of useful user scripts in this domain:

Programmers are always fond of mardown. It's like command line over GUI: faster. –  M'vy May 21 '11 at 22:33
@M'vy: 1. Stack Exchange isn't specifically for programmers. 2. I'm more of a command-line advocate than the average programmer, and I still think we don't need more markdown here. 3. Just because every problem can be solved by adding a level of indirection doesn't mean it's the best way. –  Gilles May 22 '11 at 9:06
Yes of course. I got your point. Nevertheless, when I answer on my mobile phone as an example... GUI stinks. I already have some difficulties to validate my anwsers. Or copy/pasting isn't easy as well. So if I can avoid doing this by typing instead, I'm in. –  M'vy May 22 '11 at 9:50

A lot of the answers under What sites should have hyperlinking (onebox) support in chat? would also be good here. Perhaps some could be site-specific; the English Language and Usage folks probably don't link to MSDN very often.


Some more for the melting pot:

[#12345] for questions

[me] to link to users profile in chat

[chat:ROOM_NAME_OR_ID] for linking to chat rooms

@USERNAME twitter-style user tags which currently work in chat but not comments

the first has been declined (see the comments on my answer); for the second and third see meta.stackexchange.com/questions/92060/… (although both are unlikely to happen); the fourth does work very well: meta.stackoverflow.com/editing-help#comment-reply –  balpha Sep 11 '11 at 11:07
it would be very handy to have something like [chat:android] but I understand that these are trying to be kept to a minimuum. Thanks for the link to comment-reply. That is getting bookmarked ;) –  Merlin Sep 11 '11 at 11:22
... and the equivalent id version using # i.e [chat#15] is equivalent to [chat:android]. –  Merlin Sep 11 '11 at 11:33

This site is currently not accepting new answers.

Not the answer you're looking for? Browse other questions tagged .