## No more re-typing the same comments over and over!

This script adds a little 'auto' link next to all comments boxes. When you click the link, you see a popup with 6 configurable auto-comments (canned responses), which you can easily click to insert.

This script was inspired by answers to this question on meta.

## Features

Note that the dialog only inserts the text, it doesn't send the comment, nor does it flag anything; this is so that you can check the text before posting!

2. Customize the texts

Simply double click on a comment text or description in order to customize it. Hit the 'reset' button if you screw up. This customization is currently per-site. Note that the "Welcome to $SITENAME$" text is automagically inserted if the user is 'new' (member for less than a week), so you don't need to add that to your custom text (but you can if you want to, see '9' below).

If you need more/less than the default 6 comments, just carry on reading...

3. Quick user info

The dialog also includes a mini-summary of the user's activity (because if they haven't been back in months, there's no point writing them a comment).

4. Automatic notification of new versions

The script will also notify you if a newer version is created.

This helps with transferring custom comments between sites. The export/import 'format' is also conveniently presented as markdown, so you can post it in an answer below, and let others benefit from your words of wisdom.

Note that you can also use the Import to create an arbitrary number of comments (the default is 6). If there are too many, you can use the show/hide desc link to gain a bit of space.

If you get bored with copy/pasting your comments between sites and/or computers, you can use the 'remote' button to define a remote source for your comment texts. See here for more details.

If you prefix your comment title with [Q], it will be only displayed for questions ([A] for answers). Non-prefixed comments are displayed for both.

8. [type here], [username] & [OP] (& $MYUSERID$)

If the text [type here] is included in a comment, it will be automatically selected for completion when inserted. [username] will be replaced with the user's name (or just 'user' if nothing was found), and [OP] with the original poster's name (if found, else 'OP'). Also, $MYUSERID$ will be replaced with your user id for the current site.

9. Customise welcome message

The default message is "Welcome to $SITENAME$" - which is shown for any 1-week-old users. By clicking on the 'welcome' link at the bottom of the popup, you can opt to change this message, or leave it empty to show no messages at all. You can also 'force' the message for older users on a one-off basis. This is per-site.

## Installation, other info

Development of this app is being coordinated over on GitHub. Please see the relevant sections over there to review the source code, view the release notes, report bugs or add feature requests, or read the full documentation.

The app is available for installation:

You may also download the code and run the build process yourself to generate the userscript version as well as Chrome, Firefox and Opera extensions that you can install locally if you'd rather not use the store versions.

Note: Can be used in tandem with my other user script.

-
@Derek朕會功夫, because I resent the fact that Google are forcing me to pay to give something away. – Benjol Dec 3 '13 at 5:51
@hexafraction, FYI we've moved to GitHub. – Benjol Mar 3 '14 at 9:58
@MadaraUchiha, if you're interested, we've moved to GitHub as you suggested (though not quite gone the same file-splitting route as you envisaged) – Benjol Mar 3 '14 at 9:59
Don't work for me with firefox and greasemonkey – Jorge B. Sep 22 '14 at 15:35

## Please report new issues or feature requests on our issue tracker!

The work on making this a full-blown Github based project originally outlined in this answer is now complete. All further feature requests and bug reports should be directed at the Github issue tracker.

I have taken the liberty of doing some organization.

1. I have created a full blown Github repo here. The master branch is the latest from benjol's gist and all commit history is included. The master branch can be installed from this alternate location as a userscript using this url. This should make it easier for others to fork and send pull requests with changes back upstream.

2. I have created branches that include all the gists that had been forked off of this and merged in those commits. Most of these are behind master and would need rebasing, but at least no work will be lost in the shuffle and this should make it easier to review and integrate their work.

3. I have created a fork of my own and selectively merged in changes from the branch that came from Izzy's work in gist. His work includes changes so that custom comments are stored and retrieved per-site, but it also included his default comments hard coded in. I cherry-picked just the functional stuff and made a few tweaks. I have tentatively called this 1.4.0-beta1 and can be installed as a userscript from this link. There are some known bugs still but when it's ready I'll submit a pull request and maybe these can be merged into master.

This was just leg work to get everything cleaned up and manageable using a full repo instead of gists which were gitting out of hand.

-

(but not much time in the immediate future, if someone else wants to try...)

Now tracked as a GitHub issue.

## Feature Request

Can we have the auto link appear when completing a custom "off-topic" closure reason?

Bonus points if we can declare certain auto-comments to apply in this scenario (e.g. mirroring the "A" and "Q" prefix for answers and questions). Perhaps "C" for closure reasons?

-
I just came here to ask the same thing - yes please. – user1150 Jul 19 '13 at 15:56

Being active on multiple sites, I've had some special requirements. So I've made a fork based on v1.3.0, which includes the following additional features:

• a variable $MYUSERID$ in the comments gets replaced by your userID on the current site
• you can have site-specific messages

The latter is done by adding an (optional) Site: "<hostname>" part to the defaultMessages. In import/export, this shows as an additional line starting with §§§. Importing from the "original script" here still works (but obviously has no site-specifics), exports from my "fork" must have the §§§ lines removed to import them into the "original one".

It's not yet "heavily tested", but in use by at least 3 people. Feel free to drop me a note (comments to this answer, for example) for feedback/questions. I'd be glad to see my "enhancements" integrated with the "master" (also to profit from future updates). so feel free doing so :)

Current version of the code hides behind the link above (a pastebin).

-
@Benjol In countless comments and chats (LOL), Caleb bombed me to create a Gist fork: AutoReviewComments - Pro-forma comments for SE (Izzy's fork). This should make it easier for you to merge as well – if you decide so, that is :) – Izzy Feb 25 '14 at 11:03

The script doesn't work when sites are accessed via https. I believe you simply need to change

// @include http://*stackoverflow.com/questions*

to

// @include http*://*stackoverflow.com/questions*

I've changed this locally and it now works. I use the HTTPS Everywhere extension in Google Chrome so most sites I access are via https.

-

I would like to see some improvement to the "import/export" dialogue. Inserting any whitespace character (like a space) will result in something very undesirable. Example:

###Title 1
Text of comment 1

###Title 2
Text of comment 2


(note the space on the blank line) will, after clicking "save", turn into:

###Title 1
Text of comment 1

###Title 2



i.e. the space has replaced the text of my second comment (and the text has now vanished). It might also occur with multiple line breaks between two comments.

I got kind of frustrated when I lost most of my hand-crafted comments by this unexpected behaviour.

It is particularly nasty when editing one's comments in an editor (to avoid clicking outside the dialogue and losing all one's work) that uses CR+LF line endings -- the default for Windows.

Lastly, I'd like to have an easier way to add a new comment to my list -- this is currently only possible through the "import/export" dialogue, which can give rise to above drawbacks.

With that said, this script has saved me a lot of time, and I thank you for maintaining it!

-

(I think)

marked as duplicate Dec 12 '13 at 16:36 UTC

This bug has been reported before and has already been heard. If those tags don't satisfy you, please don't ask the same question again.

'The previous bug is thankfully fixed, but...

When I import or write the comments, and click "save", the wrong titles are matched to the wrong comments, and some of them just lose their comments.

Also, the "A" and "Q" features do not work.

I'm using Chrome 30.0.1599.47 (Official Build 223717) beta-m, in case that matters.

###1
Please don't add "thanks" as answers. With just a bit more <s>money</s> reputation, you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like!!! You will also, then, be able to comment on the answers to say "+1! Thanks for the answer!" or something on the lines of that. Now, I'm just flagging this for deletion.

###2
Whilst this may theoretically answer the question, [it would be preferable](http://meta.stackoverflow.com/q/8259) to include the essential parts of the answer here, and provide the link for reference.

###3
This is really a comment, not an answer. With a bit more    rep, [you will be able to post comments](http://$SITEURL$/privileges/comment). For the moment I've added the comment for you, and I'm flagging this post for deletion.

###4

###5
If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button.

###6
If you have a NEW question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. If you have sufficient reputation, [you may upvote](http://$SITEURL$/privileges/vote-up) the question. Alternatively, "star" it as a favorite and you will be notified of any new answers.

###7

###8
Please note that Non-mainstream questions are prohibited. Any instance of refuting currently accepted mainstream theories, such as General Relativity, or the Standard Model, is not allowed. Do not promote your own (or anybody else's, for that matter.) non-mainstream ideas. Anything which has not been published in a reputable journal is not mainstream. Physics is based on Mathematics. Popular Science is not real Physics. For more details, please see the [Non-mainstream Policy](http://meta.physics.stackexchange.com/questions/4538/is-non-mainstream-physics-appropriate-for-this-site).

###9
In future please reply to a user by using "@username", as I  have done here as an example. Else, they won't be notified. For example, to reply to me,  "@Dimension10", etc.

###10
You are asking for too many things in a question. You should ask each question as a separate question.

###11
Note that MathJax is supported here. Use it to render equations. If you are not familiar with MathJax, it is essentially LaTeX code (but it ***must*** be surrounded by $ signs for inline equations and $$ signs for other equations. E.g. $$E=\sum_{j=1}mc^3$$ results in$$E=\sum_{j=1}mc^3$$and $E=\sum_{j=1}mc^3 results in $E=\sum_{j=1}mc^3$. For a documentation of LaTeX, see [LaTeX](http://tobi.oetiker.ch/lshort/lshort.pdf)..

###12
If you have enough reputation to participate in [Meta](meta.physics.stackexchange.com) (that is 5 rep), you can try formatting at the [Sandbox](http://meta.physics.stackexchange.com/questions/389/formatting-sandbox). However, MathJax isn't supported at Meta (only on the main site, which is this), yet.

###13
You are expected to do a small search for the answer before asking questions here, as this way, it will be no effort on your part.

-

It would be nice to have a place other than in these answers for us to share setups. Could you provide one and link it to the main post?

I thought about posting another question to deal with this, but wasn't sure if it belonged in stackapps or meta.stackapps.

-
– Benjol Mar 3 '14 at 10:03

I forked the script to create some quick-insert buttons.

Given how often I make use of this, I wanted to save the extra click.

-

(I won't deploy just yet, I'd prefer to group this with other updates)

Mini suggestion: Open the update link in a new tab.

-

(used this fix in V1.2.9)

Some people are experiencing a problem where the auto link does not appear. This has to do with the fact that the DOM elements on which the selector is based are dynamically loaded into the DOM.

The workaround for this is to change line 683 to:

setTimeout(function() {
$('#' + divid).find('.comment-help-link').parent().append(newspan); }, 10);  Basically this is just a minor time out before trying to add the link, which should not be noticeable. I'm not 100% sure about the 10 milliseconds, but it works for me (Chrome Canary). If it still doesn't appear for you try 100 milliseconds or something like that. - @Dimension10: the script auto-checks for updates everyday, so you can just wait. A new version will not override any customization of comment texts, no. – Benjol Aug 12 '13 at 11:28 As posting setups was mentioned being useful, here is mine: ###[Q]App recommendation Please note that recommendations like *Is there an app for X* are off-topic here (see [What topics can I ask about here?](http://$SITEURL$/help/on-topic) for details). For where your question might fit better, you might want to look into [Where can I ask questions that aren't Android Enthusiast questions?](http://meta.android.stackexchange.com/q/371/16575) ###[Q]Development question This site is for users of Android, which means that questions about development/programming are off-topic here (see [What topics can I ask about here?](http://$SITEURL$/help/on-topic)). Development questions are on-topic on our sister site [Stack Overflow](http://stackoverflow.com/questions/tagged/android). ###[Q]More than one question asked The question-and-answer format of this site works best if you put each question in a separate question post. Please edit your post down to one question, and create new posts to ask any further questions. You'll get better answers that way. ###[Q]OP providing facts in a comment The best way to add additional information to your question is by editing it, with the **edit** button. It is better visible that way, and comments are mainly for secondary, temporary purposes. Comments are removed under a variety of circumstances. Anything important to your question should be in the question itself. ###[A]OP adding a new question as an answer Remember this is a Q&A site - so keep on editing your question with new information - this section is for actual answers. If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. ###[A]OP using an answer for further information This is a question-and-answer site, not a forum. Please use the **Post answer** button only if you have a solution to the problem, so that other users can see your question is not yet answered. You can click **edit** on the question to add more information to it. ###[A]Answers just to say Thanks! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like, which is the$SITENAME$way of saying thank you. ###[A]Nothing but a URL (and isn't spam) Whilst this may theoretically answer the question, [it would be preferable](http://meta.stackoverflow.com/q/8259) to include the essential parts of the answer here, and provide the link for reference. ###[A]Comments as an answer (new users) Please don't add comments as answers. Invest some time in the site and you will gain sufficient [privileges](http://$SITEURL$/privileges) to upvote answers you like, or to add actual comments when seeking clarification of any issues. ###[A]Comments as an answer (experienced users) Please don't add comments as answers. Use actual comments when seeking clarification of any issues. ###[A]Answer that is a question If you have another question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. Include a link to this question if it helps provide context. ###[A]Requests to OP for further information This is really a comment, not an answer. With a bit more rep, [you will be able to post comments](http://$SITEURL$/privileges/comment). For the moment I've added the comment for you, and I'm flagging this post for deletion. ###[A]Another user adding a 'Me too!' If you have a NEW question, please ask it by clicking the [Ask Question](http://$SITEURL$/questions/ask) button. If you have sufficient reputation, [you may upvote](http://$SITEURL$/privileges/vote-up) the question. Alternatively, "star" it as a favorite and you will be notified of any new answers.  Entries #1 & #2 are specific to Android Enthusiasts, but similar cases might exist on other stacks, too. - ## Feature Request Have a selector that is similar to [OP] but it would select the poster of the answerer instead of the question. This would obviously only apply to comments on answers. It could look something like [OAP] // stands for "Original Answer Poster" [AP] // stands for "Answer Poster"  - (sort of) Google Chrome is now making it harder to install the script for security reasons. Upon clicking on the install link, a warning pops up refusing to install it. There's a Learn more link, recommending you use Google's oh-so-convenient distribution mechanism. (There is a workaround for the user hidden in the text, which I am about to try.) - I have the problem that whenever I change or add any comments, my changes are gone after restarting my Firefox and all comments are back to the default values. Has anybody a hint what this could be caused by? I use FF19 on Ubuntu and Autocomments 1.2.8. I also wonder if the noscript addon of FF could have any influence but for the SX sites all scripts are allowed. Any hints or ideas? - ### Bug Report I managed to install this with Tampermonkey on Google Chrome (Windows 7) along other scripts, except this script isn't working for me on Chrome (Firefox does work). - I am excitedly using the "much-requested override for the new user Welcome message." in V1.2.6, as one of those requesters. The save function doesn't appear to be sticking. It works immediately, but when I come back later, it has returned to the default message. (Chrome, Windows) - Oddthinking, thanks for letting me know. Fixed (or should be!) in 1.2.7 – Benjol Jan 22 '13 at 6:03 At the moment the Welcome message for new users is not displayed if the question was migrated from a different SE site and the user does has an account on the target site yet. The message should be inserted in this case. - There should be a method to force the insertion of the Welcome message. This can be required because some new users might have and account for 2-3 weeks already but just now started to post questions or answers. They might have found SE, registered an account but then didn't return for a while. Often these people still are new to the site and a Welcome message is appropriate, especially if it got changed to include a link to a special Welcome meta page (which I did for my site TeX.SE). - Can $SITENAME$ be changed for Christianity? Here's what a comment to a new user reads: Welcome to Christianity! ... Which sounds pretty creepy. For one thing, most folks who stumble into the site are already affiliated with some faith, which might or might not be Christianity. For another, it sounds like we are a cult or a church. We aren't. Could $SITENAME$ be changed to "Christianity—Stack Exchange" or "Christianity.SE"? (I haven't tried to adjust the messages myself, but besides being a bit tedious, it probably would be best to not have new users of the script sending the wrong signals.) It's less of a concern, but I think it would be odd to see messages like: Welcome to English! ... or Welcome to Parenting! ... I forked a version and made the following changes at line 67: if(sitename == "Stack Exchange"){ sitename = arr[arr.length - 2]; //workaround for SE sites.. greeting = 'Welcome to ' + sitename + '—Stack Exchange! '; sitename = sitename + '.SE'; }  That way, the "Answers just to say Thanks!" comment reads: Welcome to Christianity—Stack Exchange! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Christianity.SE way of saying thank you. The same comment on SO reads: Welcome to Stack Overflow! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Stack Overflow way of saying thank you. - Typically lazy developer's response, how about *%SITENAME%*? – Benjol Mar 7 '12 at 7:13 the way I'm thinking about it right now, I think I'd be tempted to make the whole greeting configurable (there are some people who don't like it). I've got a few other changes in the pipes, so this may take a while. In the meantime, if you want to do a personal hack while you're waiting, you need to track down the user-script file, go to line 66, and replace sitename = arr[arr.length - 2]; with sitename = arr[arr.length - 2] + 'your_suffix_here';. After saving, you'll need to F5 in your browser to see the difference... – Benjol Mar 9 '12 at 6:44 Looks good to me, watch out, I've got a new version coming up, you'll need to rebase your fork :) – Benjol Mar 23 '12 at 14:56 (You can now override this if you don't like it) Another bug: Every comment is prefixed with "Welcome to StackOverflow!" since recently. Doesn't seem to happen on all pages; http://stackoverflow.com/questions/9729546/jquery-script-being-executed-before-all-each-has-completed is one where it does happen though. - (something equivalent, anyway) I see a couple of comments here suggesting that Benjol is thinking of making the Welcome message configurable. This is a formal request for that feature. On Skeptics.SE, we have a meta-post which is a Welcome to New Users FAQ, and explains some of the ways Skeptics.SE differs from other Stack Exchanges. I have experimentally forked this code, just to make the Welcome message include a link to this meta-post. Unfortunately, my JavaScript skills are too dodgy to make it customisable and offer it back to you as a patch. (The customisation strikes me as particularly tricky for the troublesome few that moderate multiple Stack Exchanges.) ## Suggested presentation: This is only a suggestion - incorporate it into the existing options file. It is a bit ugly, but I think better than having a whole separate config system. ~~~ This is comment text. This line represents the default. Welcome, my dearest new friend, to$SITENAME.

~~~[skeptics] Using the same 'restriction' notations as [Q] and [A], this overrides the default for one site.
[Welcome to Skeptics](http://meta.skeptics.stackexchange.com/questions/1505/welcome-to-new-users)!


An alternative would be to put it all on one line, but then the [qualifier] notation would conflict with the [link]() notation.

-

The following message breaks stuff (results in HTML being inserted) etc.:

[**Please, don't use mysql_* functions in new code**](http://bit.ly/phpmsql). They are no longer maintained [and are officially deprecated](https://wiki.php.net/rfc/mysql_deprecation). See the [**red box**](http://j.mp/Te9zIL)? Learn about [*prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).

-

## Here's a bug report.

I've attempted to add the following comment:

[**Please, don't use mysql_* functions in new code**](http://bit.ly/phpmsql). They are no longer maintained and the [deprecation process](http://j.mp/Rj2iVR) has begun on it. See the [**red box**](http://j.mp/Te9zIL)? Learn about [*prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).


Which should render like so:

Please, don't use mysql_* functions in new code. They are no longer maintained and the deprecation process has begun on it. See the red box? Learn about prepared statements instead, and use PDO or MySQLi - this article will help you decide which. If you choose PDO, here is a good tutorial.

Instead, right after saving, it renders to

[**Please, don't use mysql_* functions in new code***](http://bit.ly/phpmsql)*. They are no longer maintained and the [deprecation process](http://j.mp/Rj2iVR) has begun on it. See the [**red box**](http://j.mp/Te9zIL)? Learn about [</a>*<a href="http://j.mp/T9hLWi">prepared statements*](http://j.mp/T9hLWi) instead, and use [PDO](http://php.net/pdo) or [MySQLi](http://php.net/mysqli) - [this article](http://j.mp/QEx8IB) will help you decide which. If you choose PDO, [here is a good tutorial](http://j.mp/PoWehJ).


Which renders as

Please, don't use mysql_* functions in new code*. They are no longer maintained and the deprecation process has begun on it. See the red box? Learn about prepared statements* instead, and use PDO or MySQLi - this article will help you decide which. If you choose PDO, here is a good tutorial.

I suspect the asterisks are derailing it, but why should it care about it anyway? Does it attempt to also fix the comment before saving?

## Edit

Seems like the Comment's markdown is parsed into HTML and then remapped to Markdown (why?!). Using's Chrome's console and editing the localStorage directly with

<a href="http://bit.ly/phpmsql"><strong>Please, don't use <code>mysql_*</code> functions in new code</strong></a>. They are no longer maintained and the <a href="http://j.mp/Rj2iVR">deprecation process</a> has begun on it. See the <a href="http://j.mp/Te9zIL"><strong>red box</strong></a>? Learn about <a href="http://j.mp/T9hLWi"><em>prepared statements</em></a> instead, and use <a href="http://php.net/pdo">PDO</a> or <a href="http://php.net/mysqli">MySQLi</a> - <a href="http://j.mp/QEx8IB">this article</a> will help you decide which. If you choose PDO, <a href="http://j.mp/PoWehJ">here is a good tutorial</a>.


Appears to fix the problem.

-
to be honest, I can't remember when or why I decided to store it as HTML. Whatever, I've got a pseudo-correction in the works (very pseudo, it skips transformations of * and ** if it finds a backtick in the middle). – Benjol Oct 25 '12 at 8:54

(sort-of, you can now customise the welcome message)

Bug observed with 1.2.4 and 1.2.5:

On some sites, instead of having the automatically-extracted site name in the comments, I get the question title. For example:

Welcome to Is Category Theory useful for learning functional programming?! Please don't add "thanks" as answers. Invest some time in the site and you will gain sufficient privileges to upvote answers you like, which is the Is Category Theory useful for learning functional programming? way of saying thank you.

This happens on Computer Science and Travel but not on Stack Overflow or Security or Stack Apps, so my guess is that whatever you're scraping there is a bit different on beta sites.

By the way, I would prefer to see Stack Exchange there (without the site name), at least on the sites which don't have a distinct branding (i.e. perhaps excepting SO, SU, SF and AU). Sentences like “Welcome to Computer Science!”, “the Travel way of saying thank you”, … don't make much sense.

-

Bug report:

Prefixing entries with [A] no longer shows these entries when adding a comment to an accepted answer. Only entries without a [A] or [Q] prefix are shown on such posts currently.

For my canned-messages set, where each entry is has either a [A] or [Q] marker, that means nothing is shown at all for accepted answers.

-

Can you add support for an Enter or Return keystroke to allow for insertion of the currently selected option? This would be really helpful! I have several custom comments and it can be a pain to scroll down to find the insert button.

-

Request: I see a lot of newbies post a comment saying "Thanks this worked perfect for me. It's exactly what I need" on an answer to their question, yet they do not mark the answer as accepted. [username] plugs in the username of the answerer when posting on an answer, but it would be helpful to also include an [OPusername] (or something to that effect) to be able to @ the original question asker on a specific answer.

i.e.

"If this answer is helpful to you, [OPusername], then please consider marking it as the accepted answer so others may more easily find it in the future. This is also a polite way to thank the person answering your question for helping you out."

-
Implemented, but using [OP] instead of [OPusername] – Benjol Nov 1 '12 at 6:38

It seems like it isn't compatible with the new review system.

-

There are two 'major' changes to V1.2.2

### 'Remote' comment source

You can now define an external source for your comments, and 'import' them. This means that you don't have to manually copy comments from site to site and PC to PC.

To do this, you click on the 'remote' link; enter the url for your data source; then click on 'get now'.

The data source must be formatted as jsonp. There is a new 'jsonp' link in the import/export dialog which will create the appropriate jsonp from your existing comments.

It is also possible to automatically invoke it every time you open the dialog, by selecting the auto-get checkbox. I'm interested in feedback on this.

I've added a function to be able to 'broadcast' messages without changing the code. The intended use for this will be to ask for feedback on proposed future changes. Taken this off-line again, it was not completely thought-through and you had to dismiss on every site... (sigh, no global storage)

-
@jrg, actually, don't. There seem to be problems with parallel ajax queries here. While trying the next version I found the comments sometimes just disappear and never come back. – Benjol May 23 '12 at 12:21

@Benjol You could add the extra set of comments that I use in-tandem with Phrase Express:

@<username> Please don’t use signatures or taglines in your posts. Every post you make is already "signed" with your standard user card, which links directly back to your user page

Shopping questions are off-topic as per the FAQ: it is not about a shopping or buying recommendation

-