Timeline for SE Comment Link Helper
Current License: CC BY-SA 3.0
50 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2021 at 21:24 | answer | added | zcoop98 | timeline score: 0 | |
| Mar 3, 2020 at 0:12 | answer | added | Peter Cordes | timeline score: 3 | |
| May 31, 2019 at 16:58 | answer | added | Rubiksmoose | timeline score: 0 | |
| Dec 8, 2018 at 10:02 | comment | added | iBug | Hello, Tim Stone. The repository doesn't contain any open-source licensing information, which means others just can't legitimately use the code. Would you mind adding one? MIT and Apache 2.0 are good ones to start with. | |
| Apr 5, 2018 at 19:52 | answer | added | robe007 | timeline score: 0 | |
| Apr 3, 2018 at 2:19 | answer | added | Gaurang Tandon | timeline score: 0 | |
| Apr 1, 2018 at 11:27 | answer | added | Gaurang Tandon | timeline score: 3 | |
| Oct 17, 2017 at 18:18 | comment | added | NotThatGuy |
[a-z]+=1 should be ([a-z]+=1)(&[a-z]+=1)* or something like that. Linked posts are ?noredirect=1&lq=1, which doesn't work with the former.
|
|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Mar 20, 2017 at 10:29 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Oct 10, 2016 at 19:16 | history | edited | Tim Stone♦ | CC BY-SA 3.0 |
added 280 characters in body
|
| Oct 10, 2016 at 19:13 | comment | added | Tim Stone♦ | @SevenSidedDie That is a very good point, hahah! I'll add to the updates list here too, thanks! | |
| Oct 10, 2016 at 19:11 | comment | added | SevenSidedDie | @TimStone I looked for an update here first in the post text and didn't see one, so no. I will update now, thanks! | |
| Oct 10, 2016 at 19:10 | comment | added | Tim Stone♦ | @SevenSidedDie Have you updated to the latest? If not, someone reported this on GitHub and I fixed it the other day. I need to look into proper updating...will add to the todo list | |
| Oct 10, 2016 at 19:09 | comment | added | SevenSidedDie | This script appears to have been broken recently; from the timing I suspect by SE's recent jQuery update: meta.stackexchange.com/questions/284996/… (See? I shouldn't be able to post a bare link like that. ;) | |
| S Jan 30, 2016 at 17:50 | history | edited | Brock Adams | CC BY-SA 3.0 |
deleted 60 characters in body
|
| S Jan 30, 2016 at 17:50 | history | suggested | Michael Freidgeim | CC BY-SA 3.0 |
User Scripts extension needs to be installed on your browser
|
| Jan 30, 2016 at 12:19 | review | Suggested edits | |||
| S Jan 30, 2016 at 17:50 | |||||
| Jan 30, 2016 at 12:12 | comment | added | Michael Freidgeim | @LưuVĩnhPhúc: You should have User Scripts extension installed on your browser | |
| Jan 31, 2015 at 9:18 | comment | added | phuclv | How can I install this script? I clicked the install/update link but it just displays the js file | |
| Dec 30, 2014 at 15:48 | comment | added | Konrad Rudolph | @Tim So what’s happening is that the first click on “Add comment” or “return” is discarded, and hitting the button/key again appears to submit the form, but no comment is posted. | |
| Dec 30, 2014 at 15:39 | comment | added | Tim Stone♦ | @KonradRudolph Hmm, it shouldn't, but I'll test. Even in a worst-case scenario it shouldn't prevent the comment, so I'll make sure that's handled correctly too. | |
| Dec 30, 2014 at 15:33 | comment | added | Konrad Rudolph | I think (but I’m not entirely certain) that this script has an issue with comment links which refer to different SE sites. Is this possible? Exhibit A: I couldn’t post the comment at stackoverflow.com/q/27707987/1968 without first disabling the plugin. | |
| Oct 20, 2014 at 20:37 | history | edited | Tim Stone♦ | CC BY-SA 3.0 |
added 58 characters in body
|
| Jan 5, 2014 at 15:45 | history | edited | Tim Stone♦ | CC BY-SA 3.0 |
added 92 characters in body
|
| Jan 5, 2014 at 15:39 | comment | added | Tim Stone♦ | @MartinSchröder HTTPS isn't officially supported by the Stack Exchange network yet, but I've updated the script to work with it now regardless. Thanks for pointing that out! | |
| Jan 5, 2014 at 11:13 | comment | added | Martin Schröder |
Stackoverflow finally seems to support https, but your script is hardcoded for http://.
|
|
| Nov 14, 2013 at 15:42 | comment | added | Martijn Pieters | @TimStone: I see API quota throttling a lot more lately, perhaps because I also started using this script from time to time. | |
| Dec 8, 2012 at 17:55 | history | edited | Tim Stone♦ | CC BY-SA 3.0 |
added 245 characters in body
|
| Nov 28, 2012 at 1:24 | comment | added | Tim Stone♦ | @doncherry I'm indirectly involved with it, I'll take a look. | |
| Nov 28, 2012 at 1:18 | comment | added | doncherry |
@TimStone stackapps.com/questions/2378/se-comment-link-helper works, thanks :). Are you also involved with SEReputationAuditHelper.user.js? That only works on Stack Overflow, but on none of the other sites I'm registered at, even though it is supposed to act on all of them.
|
|
| Nov 27, 2012 at 16:06 | comment | added | Tim Stone♦ | @doncherry Pushed out changes just now, so if you grab the latest you should be good to go. Let me know if you have any other issues. | |
| Nov 27, 2012 at 16:06 | history | edited | Tim Stone♦ | CC BY-SA 3.0 |
edited title
|
| Nov 26, 2012 at 21:36 | comment | added | doncherry | @TimStone No problem, I'm glad it'll be working again, thanks for your work! | |
| Nov 26, 2012 at 21:11 | comment | added | Tim Stone♦ | @doncherry Ah...apparently this is an issue with Firefox and jQuery's handling of a change I made two months ago that neither side seems inclined to fix. Looks like I can work around it, so I'll do that when I get home today. Sorry for the inconvenience, and I'll make sure that next time I test thoroughly in Firefox. | |
| Nov 26, 2012 at 20:38 | comment | added | Tim Stone♦ | @doncherry Hmm, I haven't had any issue in Chrome, but let me check Firefox and get back to you if I need more info. As far as the title goes, I'll take care of that, sorry about the confusion! | |
| Nov 26, 2012 at 20:32 | comment | added | doncherry | @TimStone The script hasn't been working for several weeks, if not months. I'm using Firefox 17 on Win, and I just reinstalled the script. Is this expected? Can I provide any more helpful information? (Also, it is confusing that the titles of this StackApp and of the UserScript don't match.) | |
| Sep 23, 2012 at 1:33 | answer | added | Gilles 'SO- stop being evil' | timeline score: 1 | |
| Jul 25, 2012 at 23:39 | comment | added | Gilles 'SO- stop being evil' | @TimStone I do have SE modifications. Updating Comment Link AutoPrettifier to the version you just uploaded makes it work. Thanks! | |
| Jul 25, 2012 at 23:34 | comment | added | Tim Stone♦ | @Gilles Oh, and if you have SE Modifications -- Username autocomplete in comments, inline revision source, and utility links installed, it was causing an error as a result of this change that may impact the setup for this script. I've patched that issue now, so be sure to update to the latest version if applicable. | |
| Jul 25, 2012 at 23:31 | comment | added | Tim Stone♦ | @Gilles Hmm...it seems to still be working for me, so I don't suspect anything changed on the sites...Are there are any error messages in the console? It looks like I never got around to registering for an API key for this script (I've now made a note to do so), so there's a very small chance you've exceeded the anonymous API quota somehow, I suppose. | |
| Jul 25, 2012 at 23:22 | comment | added | Gilles 'SO- stop being evil' | Since today (I think), this doesn't work for me any more: stackapps.com/questions/2378/comment-link-autoprettifier I've been using Chrome 20.0.1132.57 for weeks, it used to work in this exact browser version. Is there anything I can do to trace why links in comments are no longer prettified? | |
| Jul 11, 2012 at 20:43 | comment | added | doncherry | @TimStone: I didn't know that! Then my proposal is void, of course. Thanks for letting me know. | |
| Jul 11, 2012 at 19:53 | comment | added | Tim Stone♦ | @doncherry Thanks! You don't receive credit if the link was clicked inside of the Stack Exchange network anyway (as would be the case with comments), which is why it removes the referral slug. | |
| Jul 10, 2012 at 20:02 | comment | added | doncherry |
@TimStone: Love the script! Could you implement an option to append the urls with one's user account number so that links contribute towards the Announcer etc. badges? So instead of having x.stackexchange.com/q/31415, it'd be x.stackexchange.com/q/31415/4746 (4746 being your user account number for stackapps).
|
|
| Jun 8, 2012 at 15:54 | answer | added | Kevin Vermeer | timeline score: 3 | |
| May 23, 2011 at 22:41 | comment | added | Tim Stone♦ | @FredNurk Ah, I forgot to regenerate the HTML from the actual README document. Sorry about that, I'll make sure that gets updated later this evening. | |
| May 21, 2011 at 6:16 | comment | added | Fred Nurk | There is no information about this at that README link. | |
| May 1, 2011 at 18:03 | comment | added | Tim Stone♦ | Note: The script doesn't use an API key at the moment, so I'll need to fix that in the near future. | |
| May 1, 2011 at 17:58 | history | asked | Tim Stone♦ | CC BY-SA 3.0 |