Stack Apps is a question and answer site for apps, scripts, and development with the Stack Exchange API. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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.

Thumbnail

Features

  1. Read your comment before you post it!

    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.

  5. Import/export of custom comments

    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.

  6. Remote source for comments

    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.

  7. Differentiated comments for questions/answers

    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.

    Screenshot

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.

share|improve this question
    
+1+ for the great resource! It was my own answer to this meta I asked in WPSE. Thanks again for assembling this utterly useful tool! – brasofilo Jul 9 '12 at 10:39
    
@Benjol This broke again today. I think it has something to do with the new flagging system.. Maybe. – Seth Sep 12 '13 at 20:10
    
@Seth, on which site/browser? I just tried programmers, SO and here with FFx and it seems ok. – Benjol Sep 13 '13 at 4:48
    
Why isn't the Chrome extension hosted on WebStore? – Derek 朕會功夫 Dec 3 '13 at 2:58
3  
@Derek朕會功夫, because I resent the fact that Google are forcing me to pay to give something away. – Benjol Dec 3 '13 at 5:51
    
@Benjol - I can put extensions there for free actually, because I joined it (opened a webstore developer account) at the beginning. – Derek 朕會功夫 Dec 3 '13 at 7:56
    
@Derek朕會功夫, well it's open source, so you have my blessing if you want to invest the time to do it. Then post a link here (or update the text of this 'question'). – Benjol Dec 3 '13 at 8:19
    
@Benjol - I have packed it into an extension: chrome.google.com/webstore/detail/… :) – Derek 朕會功夫 Dec 3 '13 at 21:53
    
@Derek朕會功夫 awesome! Would you consider including a link back to here, rather than to git (or as well as to git)? That way people can get all the information necessary. Also: is this going to be 'auto-updating'? I'm guessing not, so you may have set yourself up for more work... :) – Benjol Dec 4 '13 at 5:37
    
@Derek朕會功夫, also, is there any chance you could give it the same version as the current one here (1.2.9)? That could avoid confusing people. – Benjol Dec 4 '13 at 5:48
    
@Benjol - Sure I've changed the version to 1.2.9 and modify the description so that it is showing both links. The extension won't be updated automatically unfortunately so it has to be done manually (basically it is just copying the script and paste it into the extension) and re-upload it. – Derek 朕會功夫 Dec 4 '13 at 8:04
    
@Benjol - One thing is that do you want to remove the updateCheck in your script? Since the extension will be updated automatically for the client and there's no need to display the "new version" message. – Derek 朕會功夫 Dec 4 '13 at 8:06
1  
@hexafraction, FYI we've moved to GitHub. – Benjol Mar 3 '14 at 9:58
1  
@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
3  
Don't work for me with firefox and greasemonkey – Jorge B. Sep 22 '14 at 15:35

54 Answers 54

up vote 23 down vote accepted

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.

share|improve this answer
    
If we have raised a feature request in the answers below, should we now create an issue in GitHub? – Duncan Mar 18 '14 at 9:23
    
@Duncan Yes please! We actually fixed/added many of the features requested an answers here and the few we didn't get to yet we tried to transfer over to issues already, but if we missed one or if you have new ones by all means open an issue on the Github project page. – Caleb Mar 18 '14 at 9:41

Future ideas: use HTML5 storage to allow users to create/modify their own messages.

enter image description here

  • double click on a title or description to modify
  • save/cancel
  • 'reset' link at bottom of popup (not shown above) resets all custom messages to default

Important

  • The 'Welcome to SiteName!' text is prepended automatically if the user has been member for less than a week.
  • This uses HTML5 Storage, so custom texts only work on the site where they were entered.

NOTE

With this modification, there is no longer any reason that this userscript should be strictly limited to 'review'.

share|improve this answer
    
You can vote this one up if you really like it. (I'm working on it anyway) – Benjol Feb 26 '11 at 19:40
5  
How can I make it so that it doesn't say "Welcome to Stack Overflow!". I really don't want this. – casperOne Dec 29 '11 at 23:12
    
@casperOne, no, not at the moment, sorry. You could hack it out of the script manually. (It only shows for 'new' users) – Benjol Jan 3 '12 at 6:43
    
I second @casperOne's request. I'd really like that "Welcome" noise to be optional. Can this be made an option? Either global, or using [magic] tags for each comment as you do elsewhere? – Cody Gray Mar 28 '12 at 3:26
    
@CodyGray, it's status-planned (hidden in the comments here), no promises about when, though (to be honest, the main 'problem' is deciding how to present the option). Do you think that making it optional/configurable per comment makes sense? – Benjol Mar 28 '12 at 4:58
    
Not necessarily. I just thought that might be easier to implement; you know, the "lazy developer's response", as you put it. I'd be perfectly content with it being a global setting. Maybe better yet, this would all be configurable per site. So I could disable the welcome text on Meta.SO, but leave it enabled on the SE 2.0 sites. In the same way, the name used for each site would be customizable to make Jon Ericson happy. – Cody Gray Mar 28 '12 at 5:16
    
@CodyGray, ok, thanks for the feedback. Pending implementation, you could comment out line 234... BTW, while I have your ear, what would you think of the idea of providing a per-site option to dynamically load comments from an external source (e.g. Dropbox)? – Benjol Mar 28 '12 at 6:18
    
You mean so that the comments could be shared with other users on that site; for example, so that moderators could easily synchronize with one another? Or do you mean for each person's private use? The former would be really cool, but I don't think I'd get much use out of the latter. Not sure what it would hurt, though. People might like to share their customized comments between multiple machines, like home and work. – Cody Gray Mar 28 '12 at 6:34
    
Mostly the latter two reasons, though the first use case would be covered too. If you have broadly the same comments across multiple sites (and machines), currently you have to copy/paste manually every time you modify something. I did experiment with using global storage for this, but the code is very unwieldy (and it needs two scripts) – Benjol Mar 28 '12 at 6:55
    
@CodyGray, stackapps.com/a/3281/876 :) – Benjol Mar 29 '12 at 9:46
    
@casperOne, forgot you'd left that comment, your welcome message request is not status-completed, if you hadn't already noticed! – Benjol Feb 9 '13 at 22:06

(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.

share|improve this answer
    
You said it yourself :) If you catch balpha in chat, please try asking him (he helped me last time they 'screwed up'). If I see him first I'll do so... – Benjol Jul 25 '13 at 4:37
    
I may have found a culprit‌​, following up now :) – Benjol Jul 25 '13 at 6:34
    
You were not suppose to read that chat message ;-) In all seriousness I doubt the fact there is console output is what makes things go wrong. Then again I suck as you noted so I may be wrong about this :-D – PeeHaa Jul 25 '13 at 7:59
    
By status-planned, does it mean that we'll have to reinstall it after it's completed, or automatic? And will the customisation be reset to the default? . – dimensio1n0 Jul 27 '13 at 9:09
    
This doesn't work for me in Firefox 22 – Cody Guldner Jul 28 '13 at 17:03
    
@CodyGuldner Have you tried with a higher timeout? – PeeHaa Jul 28 '13 at 17:09
    
Whoops. Forgot to enable greasemonkey ;) – Cody Guldner Jul 28 '13 at 17:28
    
You can hardly blame me for that ;-) @CodyGuldner – PeeHaa Jul 28 '13 at 17:59
    
Worked fine for me, too, with FF 17 on Ubuntu and Vista (default timeout kept). – Izzy Jul 29 '13 at 8:33
    
Works well. Chrome Ubuntu. – Madara Uchiha Jul 30 '13 at 15:48
    
Worked for me. FF22 Win8 – Jamiec Aug 2 '13 at 14:29
    
+1 It works in Icewasel 24.0a2 (aurora build) – Braiam Aug 4 '13 at 20:03
    
@Dimension10, it means I was hoping for a tip from the dev team to help me avoid this hack. None forthcoming, so I'll go with this from PeeHaa, holding my nose at the same time :) Sorry I didn't answer sooner, you didn't @ me... – Benjol Aug 12 '13 at 10:24
    
@Benjol: So does that mean I have to reinstall, and that the customisation will be set to the default? – dimensio1n0 Aug 12 '13 at 10:39
2  
@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

(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?

example

share|improve this answer
3  
I just came here to ask the same thing - yes please. – user1150 Jul 19 '13 at 15:56
    
Yes, also iin (suggested) edit summaries . – dimensio1n0 Aug 14 '13 at 13:29
    
This feature request has been migrated to this issue on Github (and thanks Duncan). – Caleb Mar 18 '14 at 9:53

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.

'Broadcasts'

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)

share|improve this answer
    
Where do you recommend storing the comments for the external source? Github maybe? – Kit Menke Apr 5 '12 at 16:20
    
@KitMenke, for testing I used DropBox, the poor man's web server. – Benjol Apr 5 '12 at 17:59
    
If you could have it automatically update the remote sources, that'd be great. – James May 15 '12 at 22:44
    
@jrg, I'll bear it in mind. For the moment, you could try this (I haven't tested): at line 581 add this code: LoadFromRemote(GetStorage("RemoteUrl"), function () { WriteComments(popup); }); – Benjol May 16 '12 at 4:54
1  
@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 I'm glad I did try that then. :P – James May 23 '12 at 12:28
    
Has this evolved any? Is local storage used? I probably don't want a remote call every time I use the script (which is often), but once per browser session would be great. (I plan on using an Github Gist, btw.) – Raphael Jan 19 at 14:22
    
@Benjol, could the remote comment source be expanded to sync all md files in a given github repo? – SmokeDispenser Mar 11 at 23:22
    
@SmokeDispenser, you'll get more luck on github (though I haven't done much work on the extension recently) – Benjol Mar 14 at 7:09
    
Has anyone managed to get this to work with a GitHub repository, I have tried to get this to work with this repository but when I try and use the plugin to pull the jsonp down it never completes. – Richard Slater May 6 at 21:28
    
Just in case anyone else is looking to do this, if you want to store your JSONP on GitHub you will need to use the file extension .js and then use RawGit to serve the content up using the correct, executable, mime type. – Richard Slater May 6 at 21:37
    
Where is the "remote" link this comment asks me to click on? All I see is the "auto" link next to the comment box. – Noumenon Jun 6 at 16:07
    
@Noumenon, it's after you've clicked on the auto link that you'll see the remote link. – Benjol Jun 7 at 5:16

I'll drop my setup here.

###Comment as answer
__This is not a forum. Please only use the 'Post Your Answer' button if you can answer the asker's question; <a href="http://gaming.stackexchange.com/privileges/comment">post a comment</a> otherwise.__ We require some <a href="http://gaming.stackexchange.com/faq#reputation">reputation</a> before you can comment others' posts to prevent abuse; why don't you try and get some by <a href="http://gaming.stackexchange.com/unanswered">answering a question?</a>

###Question as answer
__This is not a forum. If you have a different question from the asker's, please use the <a href="http://gaming.stackexchange.com/questions/ask">Ask Question</a> button__ instead. You don't even have to login!

###Upvote as Answer
__This is not a forum. If you wish to thank somebody, you should <a href="http://gaming.stackexchange.com/privileges/vote-up">vote him up</a>.__ We require a little bit of <a href="http://gaming.stackexchange.com/faq#reputation">reputation</a> before you can do that to prevent abuse; why don't you get some by <a href="http://gaming.stackexchange.com/unanswered">answering a question?</a>

###Not a Real Question
This is not a forum; __this is a questions and answer site, and I'm afraid your post isn't really a question, because <a href="http://blog.stackoverflow.com/2011/01/real-questions-have-answers/">real questions have answers, not items or ideas or opinions</a>.__ <a href="http://gaming.stackexchange.com/faq">Please read the FAQ for more information.</a>
share|improve this answer
    
They should automatically generate such 'comments' when you flag something – Ivo Flipse Mar 2 '11 at 14:30
1  
watch out, because the "Welcome to SiteName" is automagically added if the user is 'younger' than a week. – Benjol Mar 2 '11 at 16:54
    
@Benjol Oh, I guess I shouldn't have messed around on a totally random post after all :) – badp Mar 2 '11 at 16:57
1  
Posting setups is a good idea though – Benjol Mar 2 '11 at 17:02
2  
I've added an import/export function which will make pasting setups like this easier, and also allow you to copy between sites (and/or browsers). I'm starting to like your list more than my own :) – Benjol Mar 4 '11 at 10:29
    
How can I import your list? – RolandiXor Sep 17 '11 at 16:24
    
@Roland Copy paste? :/ I no longer have this extension installed. – badp Sep 17 '11 at 21:50
    
Either way, importing comments doesn't seem to work for me :(... thanks for the "help" – RolandiXor Sep 17 '11 at 22:09
    
Love it. Thanks for the additional comments. Using them now! – Brian Sep 29 '11 at 18:09
    
@badp - You now have to log in to ask questions; I've fixed this for you. – Kevin Vermeer Dec 1 '11 at 0:05
    
@KevinVermeer That's SO only – badp Dec 1 '11 at 0:07

I felt limited by only six comments, so I made some small improvements.

Implemented the following features:

Head list items are intended for users, sub list items are intended for developers.

  • Allow the user to enter an unlimited amount of comments. (Add them in import/export)

    • Based the script on the local storage, while using comments only for initial data or to reset.
    • Refactored duplicate code & checks as comments behavior is replaced by localStorage.
       
  • Scrollbar for when the amount of comments exceeds the standard height.

  • Added a link to allow the user to toggle the visibility of descriptions.

    • This is remembered by using the local storage.
       
  • Improved see-through behavior by hiding title and buttons and making it more transparent.

  • Fixed invalid info: "User info detection doesn't work on CW answers, nor with deleted users."

    The box now either shows "This user is not registered." or hides.

  • Fixed greeting consistency, it's now added again after editing comments.

Old version:

Please make sure that both versions do not conflict.

Download Old Version | Source

This has been implemented by Benjol!

share|improve this answer
    
Fixed a bug with incorrectly loading the visibility of descriptions. Works 100% now... :-) – Tom Wijsman Mar 5 '11 at 21:27
    
Fixed a bug where you were unable to click the option bullet or edit the entry after import/export. – Tom Wijsman Mar 5 '11 at 21:45
    
Attempted to fix a bug where "Welcome to SITENAME!" was inserted twice, doesn't reoccur... – Tom Wijsman Mar 5 '11 at 21:46
    
Spotted a bug: In-line editing a greeted comment saves the greeting within the comment. I won't fix this... – Tom Wijsman Mar 5 '11 at 21:55
1  
Tom, they say imitation is the sincerest form of flattery, so I'll forgive you suggesting people remove my script! :) Not sure if I'll have time to look at this today, but I'll work through your modifications and see whether/how I might integrate them. I think it would be interesting if you could 'export' your comments and paste them here, like @badp did. – Benjol Mar 7 '11 at 7:19
    
Pastebin - Still an early version as I haven't made much auto-comments, but it does the job. Yeah, I don't mean to replace you work, made some improvements to make it more usable to me and thought about sharing the changes. Also, I learned how local storage works in extensions because of you... :-) – Tom Wijsman Mar 7 '11 at 15:47
2  
@TomWij, V1.0.8 integrates all your modifications (except that I just hide userinfo if I can't find any). – Benjol Mar 17 '11 at 13:30
    
@Benjol: V1.0.8 has a bug re: greeting, opening the dialog a second time prepends a second greeting. – Hasturkun Mar 28 '11 at 17:02
    
@Hasturkan: Oh, it's still there? Can you tell us how to reproduce this? I thought I got it fixed here‌​... – Tom Wijsman Mar 28 '11 at 17:09
    
@Hasturkan, @Tom. OOps! Must have missed that one. Fixing now... (Another side effect is that if you open the second time on an 'old' user, you still get the greeting) – Benjol Mar 29 '11 at 4:37

Can comment text please be collapsed/hidden by default and only expanded for the currently chosen option? This would work kind of like the 'more info' link in the faq which pops out when you click it. (My dialog is getting pretty big now and this would really help!)

Example mockup

As already said by many others - thank you so much for this script!!

share|improve this answer
3  
status-completed – Benjol Jul 20 '11 at 5:17
2  
Epic turnaround time and awesome script! – Kit Menke Jul 20 '11 at 13:36

Doesn't work on superuser.com (only www.superuser.com) because it includes only domains with a period like so:

http://*.superuser.com

and should be

http://*superuser.com
share|improve this answer
    
[status-completed], let me know if you find any others. – Benjol Mar 4 '11 at 6:09
    
@Benjol Great and fast response! ;) – BloodPhilia Mar 6 '11 at 13:07

Feedback:

The definitions of the sites are not all-inclusive. For instance, the link doesn't show up on stackapps ;)

share|improve this answer
    
Thanks, [status-completed] (for stackapps anyway) :) – Benjol Feb 24 '11 at 18:39

Another future idea: expandable groups of comments similar to the way Close>Off-Topic opens a list of sites.

share|improve this answer
1  
Implementation thoughts: See my answer for a local storage based extension. Use a new syntax (eg. ##) that when read is stored as a comment with description "header", then when reading such comment you could embed all subsequent non-header comments and easily have expandable groups. – Tom Wijsman Mar 4 '11 at 18:19
    
This is how I do this now. Not going to implement this myself because I dislike an extra click... – Tom Wijsman Mar 4 '11 at 23:23
    
this is [status-completed] if you accept Tom's way of doing things (which I've integrated into my script) – Benjol Mar 27 '11 at 8:13

(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.

share|improve this answer
    
Yes, it's planned for vNext, just not sure quite how to present it yet. – Benjol Apr 16 '12 at 21:23
    
@Benjol: Just bringing your attention to my edit, that didn't fit in a comment. – Oddthinking Apr 28 '12 at 3:59
    
+1 would really really like this. If I knew how to write anything and could gain some reps, I'd set a bounty for it. I don't care how it's presented in the UI... – Cody Gray Apr 28 '12 at 7:35
    
I second the feature-request. On TeX.SE we also have a special Welcome meta post we link to. I hacked my local copy of the script to use it, but making it configurable is much better. – Martin Scharrer May 16 '12 at 16:39
    
@CodyGray, this is done now. – Benjol Jan 9 '13 at 12:49
    
@Benjol: Where can the option be configured? – Amal Murali Jan 3 '14 at 18:59
    
@AmalMurali: When you bring up the main screen, there is a link to "welcome" in the bottom right corner. – Oddthinking Jan 4 '14 at 0:44

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.

enter image description here

share|improve this answer
    
Nice, I'll 'advertise' it above, and consider including it in the next version (if I can work out how to pull/merge!) – Benjol Oct 16 '13 at 4:38
    
@Benjol The implementation is dirty. If you would want to put this in your version, it could be improved. You can check the diff to see what I did. I had actually forgotten to push my changes :P – Oliver Salzburg Oct 16 '13 at 10:35

Can you also add the auto link on the flag review page of 10k+ users? Especially when going through the "not an answer" flags there are tons of "thanks" and "question instead of answer" posts.

Update: To get it working, there are only minor changes needed:

  • Enable the script for /tools* on the various sites
  • Add .mod-post-header to the delegate list for the click event:

    $(".question, .answer, #questions, .flag-container, .mod-post-header").delegate(".comments-link", "click", function () {
    
share|improve this answer
    
For that you'll either have to a) wait a few months until I hit 10k, b) hack the script to get what you want and send me the correction :) – Benjol Mar 26 '12 at 4:39
    
What about me sending you a screenshot of the HTML code of the 10k page after an answer has been loaded (they are loaded via AJAX)? ;) – ThiefMaster Mar 26 '12 at 7:55
    
eh... I guess you could try... – Benjol Mar 26 '12 at 8:12
    
@Benjol: I've updated my post to include the needed changes. – ThiefMaster Mar 26 '12 at 8:32
    
ThiefMaster, can I assume you've tested that? :) – Benjol Mar 26 '12 at 9:05
    
Yes, works fine for me – ThiefMaster Mar 27 '12 at 11:58
    
ThiefMaster, included in V1.2.1 – Benjol Mar 27 '12 at 12:19

Small bug: I haven't figured out at which point this happens exactly, but the script seems to be over-enthusiastic adding the "Welcome" prefix:

Welcome to $SITENAME$! Welcome to $SITENAME$! Welcome to $SITENAME$! The code you show is vulnerable to SQL injection. Use the proper sanitation method of your library (like mysql_real_escape_string() for the classic mysql library), or switch to PDO and prepared statements.

Unless you already know what causes this, I'll keep an eye on it and report back.

share|improve this answer
    
I've been using this script for a while, and I've never seen this. Strange. Where did it happen? – Kevin Vermeer Dec 1 '11 at 0:07
    
@Pekka, I'm convinced I never saw this post in my inbox. I only just discovered it now! I corrected this bug a while back, I believe.... – Benjol Mar 29 '12 at 8:21

Future idea: include an 'auto-update' function which polls for new versions and notifies user (with anti-nagging functionality).

share|improve this answer
    
[status-completed], but I've just this minute thought of a bug. It uses localStorage, so it's going to nag you on every single site where you use it :( – Benjol Mar 1 '11 at 14:57
    
Fixed that bug in v1.0.5 – Benjol Mar 3 '11 at 7:38

Bug: if my comment contains &, when I insert it it will insert &amp; instead.

Preview

enter image description here

Result

enter image description here

Import/Export

enter image description here

share|improve this answer
    
I've got a correction for this, I'm just waiting a bit to see if there aren't some other fixes that I can fit into the next version too. – Benjol Jul 3 '12 at 11:16
    
@Benjol good to hear, thanks! – Oak Jul 3 '12 at 17:24
    
@Benjol am I supposed to do anything for the script to update? Because I still experience the issue. – Oak Jul 17 '12 at 17:46
    
Oak, the script should check for a new version every day, and send you here to install it. If you've clicked on this link and it's still not working, then yes, there's a problem somewhere. – Benjol Jul 18 '12 at 6:07
    
@Benjol right, my bad. Reinstalled and it's now fixed :) – Oak Jul 18 '12 at 6:16

Can you add multiple pages of comments? Currently if you have a lot of auto comments, you have to scroll to see them, but it would be nice to be able to click next and previous to see lists of about 5 comments.

Also, the "see through" feature is cool, but it should be activated by a click, instead of on mouse over.

One more problem: Importing the comments seems not to save them.

share|improve this answer
    
Thanks for the feedback. Have you tried the show/hide description option? That should give you more room for seeing your comments without scrolling. Concerning importing the comments, they should save, but only on the current site. I haven't got cross-site sharing working yet. Maybe local storage is not blocked for you? – Benjol Sep 18 '11 at 11:13
    
@Benjol the import didn't work even on the site that I imported on :(. Local storage is available (using Firefox 9). – RolandiXor Sep 18 '11 at 12:54
    
and how about 'normal' edits (double click on a title/description)? – Benjol Sep 19 '11 at 13:20
1  
Hang on, is that Firefox 9 an upside-down six?! – Benjol Sep 19 '11 at 13:32
    
@Benjol I didn't know about that before. – RolandiXor Sep 19 '11 at 13:32
    
@Benjol nope; it's Firefox 9. I am from the future. You will have a good day tomorrow :). P.S. it works editing existing ones. – RolandiXor Sep 19 '11 at 13:41

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."

share|improve this answer
1  
Implemented, but using [OP] instead of [OPusername] – Benjol Nov 1 '12 at 6:38
    
@Benjol The current [OP] implementation copies the user's name directly. Could you maybe add another one which adds it in a way usable as a @ tag (e.g.: [@OP])? – minerz029 Feb 14 '14 at 11:00

In GreaseMonkey the Name of the Script is AutoReviewComments but the name of the StackApp is Pro-Forma comments.

This makes it very hard to find the app (once you forgot its name :D).

Maybe those could be named equally?

share|improve this answer
    
Good point. Done! – Benjol Nov 22 '11 at 11:55

@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


share|improve this answer
    
did you see that you can customize (per site) your messages (double-click to edit), or do you mean that 6 isn't enough? – Benjol Mar 2 '11 at 18:06
    
@Benjol oops, feel like a doofus now - I missed the customization note – Sathya Mar 2 '11 at 18:10
    
it's my fault, the 'documentation' isn't keeping up with the development - fixing now... – Benjol Mar 3 '11 at 5:38

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

enter image description here

share|improve this answer
    
By the look of things, the question/answers are loaded dynamically, after the user script has been 'run'... I'll see what I can do... – Benjol Jul 17 '12 at 5:31
    
@Benjol Oh, it's already completed :D Cheers mate! – Oliver Salzburg Jul 17 '12 at 9:21
    
The problem is back. – dimensio1n0 Jul 27 '13 at 4:18

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.

share|improve this answer
    
The answer to the 'why' bit is that I display the HTML in the popup. As to the fix... I'll look into it. – Benjol Oct 25 '12 at 4:55
    
@Benjol wouldn't it make more sense to store the Markdown version as well? (Or at least implement a more robust HTML parser)? – Madara Uchiha Oct 25 '12 at 8:48
1  
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
    
@Benjol it seems as if the bug still persists! Even after updating to the latest version! – Madara Uchiha Nov 7 '12 at 17:32
    
Oh dear, you're right. I was sure it worked. Maybe I broke my correction, or didn't test it properly... – Benjol Nov 8 '12 at 5:44
    
OK, I've tracked it down, but I'd like to wait a bit before doing a new version (in case new bugs crop up). If you want to correct this locally, go to line 343 and replace the first [^`] with .. – Benjol Nov 8 '12 at 6:24
    
Alright, you should really consider packing it and shipping it over at the Chrome Market. It allows you to do stuff like push updates automatically etc etc. – Madara Uchiha Nov 8 '12 at 18:06
    
yes, maybe. At first glance it looks like a lot of administrative gumph. If I read correctly, I have to pay $5 upfront for something that I'm intending to give away? Or am I not looking in the right place? – Benjol Nov 9 '12 at 5:37
    
@Benjol: Also, I've notice your extract function works the same (HTML vs Markdown wise), shouldn't it be presented in markdown rather than HTML? It would be lighter in file-size, and much closer to the intended result. – Madara Uchiha Jan 24 '13 at 9:20

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.

share|improve this answer
    
Welcome to Stack Apps! 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 Apps way of saying thank you. – Jon Ericson Mar 6 '12 at 21:30
1  
Typically lazy developer's response, how about *%SITENAME%*? – Benjol Mar 7 '12 at 7:13
    
OK, that won't work for the Welcome bit (I'd have to code that up), but would it be a viable alternative? – Benjol Mar 7 '12 at 7:15
    
Welcome to Stack Apps! 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 Apps way of saying thank you. – Benjol Mar 7 '12 at 7:15
    
I'm loath to do more than that, because there's a risk of getting negative feedback from other users who are happy with the current functionality (unfortunately I haven't yet coded a 'feedback' function in this script!). Let me know what you think. – Benjol Mar 7 '12 at 7:37
    
@Benjol: Yes, that would help. In fact, it would clarify some of the other messages, now that I see it in action. ;-) I wonder if it would be possible to add a variable suffix (which would default to the null string) at least for the Welcome portion. (I really do like the work you've done with this. If I have to type a few extra letters once in a while, it will still be a huge win for me.) – Jon Ericson Mar 7 '12 at 16:55
    
Jon, how do you see the variable suffix? Could you give me some examples, and maybe an idea of how/where you'd modify it? – Benjol Mar 8 '12 at 5:50
    
@Benjol: I was thinking of something like: 'Welcome to ' + sitename + sitesuffix + '! ' in the place where you construct the greeting. Then I would want to configure it somehow (I don't really know JavaScript) to set sitesuffix = '—Stack Exchange'. Does that make any sense? – Jon Ericson Mar 8 '12 at 17:15
1  
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
    
@Benjol: Thanks for your help. I'm not sure how widespread the script is outside of SO, but I think my change will help me on other Stack Exchange sites. – Jon Ericson Mar 9 '12 at 20:06
1  
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
    
+1. I don't use this app, but I think it's an awesome bug report. – Andrew Grimm Apr 14 '12 at 2:03

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"
share|improve this answer
    
[username] should work for that (except on community wiki questions like this one). – Benjol Apr 30 '13 at 5:21
    
I totally don't understand your edit, did you mistake this answer for something else? – Benjol Jun 26 '13 at 7:34

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.

share|improve this answer
    
Or meta Stack Overflow? Depends on whether you think there are standard cross-site messages. Some users seem to prefer to tailor their comments for specific sites. And, that aside, I think it is probably preferable for each person to craft their own, because that avoids the appearance of 'robo-commenting' - which seems to be the main fear that prevents this script being integrated into SE. – Benjol Jan 9 '14 at 6:24
    
On reflexion, I think this should be done per site on their own meta. @Izzy did this very recently on SR – Benjol Feb 27 '14 at 6:19
    
@Benjol if a robot can comment, then the comment should appear before the user can submit their post; However if everyone were to use and revise the "preferred language" I would think that would only add clarity as to what action needs to be taken and why. – virtualxtc Feb 28 '14 at 8:26
    
@Benjol, site specific sets should also be kept; but given that most new users run into problems with the general SE format, I'd suspect there's still plenty of room for a pan-site list. – virtualxtc Feb 28 '14 at 8:28
1  
see here: github.com/Benjol/SE-AutoReviewComments/issues/6 – Benjol Mar 3 '14 at 10:03
    
@Benjol that would work for me! – virtualxtc Mar 3 '14 at 11:24

Somehow, it doesn't show the "auto" link any more here... re-installed already. FF 4.0.1 using latest version of Greasemonkey.

share|improve this answer
    
That's a shame. I can reproduce, looking for bug/fix now. Can't reproduce in Chrome, so it looks like it's a firefox/gm thing, not a change in SE markup... – Benjol May 11 '11 at 4:45
    
OK, I've tracked something down, but no idea what the root cause is. If you add an alert('anything'); at line 414 (before adding handlers to click on the comment links, it works, as long as you don't dismiss the alert immediately. Must be some kind of timing issue. If anyone has any ideas... – Benjol May 11 '11 at 5:31
    
In full.js, this looks like the guilty candidate: $("a[id^='comments-link-']").unbind("click") – Benjol May 11 '11 at 5:42
1  
Fixed this in V1.1.0 – Benjol May 11 '11 at 7:45

Since you're fetching user info from the userpage, could you add in something to show whether the user is registered or not?

share|improve this answer
    
I can, but could you find me an example of a user who isn't registered, so I can test first? – Benjol Sep 15 '11 at 6:30
    
@Benjol E.g. crypto.stackexchange.com/users/637/asd – waiwai933 Sep 15 '11 at 23:42
    
ok, tested. in V1.1.3 – Benjol Sep 16 '11 at 4:45

There appears to be a bug with the [edit] magic link.

Using this text:

Question needs more information

We need more information to answer your question. Please [edit] your post and add details as requested by the community. It will be closed for now, but don't worry - once you have improved the question flag a moderator and it can be reopened. See How do I ask questions here? for general guidelines.

Gives a broken preview:

enter image description here

The comment still inserts OK however.

share|improve this answer
    
Well spotted! Fixed. It was a regex... – Benjol Jul 21 '11 at 5:17

The same way we press Esc to close the list can we have Enter to add the comment directly instead of the button bellow the list?

My list is getting a bit big and every time I need to select a comment (in a small laptop screen mind you) I need to scroll to the comment, click, scroll down to the end, click to add the comment and the scroll back up on the page to where I was before.

Can this be fixed so Enter adds the comment directly without needing to scroll all the way down?

share|improve this answer
    
Not a bad idea, I'll look into it. – Benjol Mar 23 '12 at 13:36
    
@Benjol great scrip, think it saves me 3 hours everyday! thx ;) – Bruno Pereira Mar 23 '12 at 13:51
    
Done in V1.2.0, let me know if you spot any problems! – Benjol Mar 23 '12 at 15:01

You must log in to answer this question.

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