Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
The preview also doesn't show that urls will be automatically converted from http://domain.tld/path/to/page to a link that doesn't show the protocol like domain.tld/path/to/page.
Better off using @match so that http/https and domain+subdomains can all be covered by a single rule per domain. e.g. //@match *://*.stackoverflow.com/* covers Stack Overflow & Meta Stack Overflow, and //@match *://*.stackexchange.com/* covers all sites at subdomain.stackexchange.com, and their meta sites.
Also, it seems marked is throwing Uncaught Error: Infinite loop on byte: 10 when a new line (entered by pasting something with multiple lines, or pressing Shift+Enter) is in the comment field.
When certain characters (<, >, &) are inside code blocks (text surrounded by backticks), they appear as the associated html entities (<, >, &) instead of the character that they are (and will be in the actual comment) in the preview.
@Filnor: The same person also said a little later in the same thread that scraping info from the website is OK if it only happens when someone clicks a button on a website. So, (assuming you cache what you find so it doesn't happen every time someone clicks it), couldn't the "numeric site ID" of every site be scraped from stackexchange.com/leagues if someone tries to check one that's not already known?
@Filnor: At the time I was just thinking I'd like to use it on SuperUser, but for those of us who aren't Jon Skeet, we're more likely to actually be in a decently high top x% of the smaller sites. I see no reason why others wouldn't want to use this with whichever beta sites they frequent (as I start to gain some more rep, I know I would). It's too bad that "we can't read the numeric site id from the API". I feel like that should be available, don't you?
As noted by HyperNeutrino, Mr. Xcoder and j-f1, this no longer works because of the 'new top bar'. Do you have plans to fix this? or is the project dead now?
