Timeline for StackInbox - a Chrome/Firefox Extension that Preserves New Stack Exchange Inbox Messages Until They Are Actually Read
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 9:43 | history | edited | CommunityBot |
replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
|
|
| Aug 7, 2014 at 6:52 | comment | added | Jason C | +1. Feature request; ability to not have this applied to chat notification (it's useful in theory, but in practice I've observed it is often tedious to click all notification links when a conversation generates many notification and not as useful in that case since visiting the chat room is usually enough to see all of these at once). | |
| May 6, 2014 at 1:23 | history | edited | Tim Stone♦ |
edited tags
|
|
| Mar 17, 2014 at 19:49 | comment | added | Gilles 'SO- stop being evil' | A nice idea, but middle click on an unread item opens it in the same tab (Chrome 33). This makes it unusable for me. | |
| Feb 22, 2014 at 10:02 | comment | added | jmort253 | @terdon - This is live for both Chrome and Firefox. | |
| Feb 22, 2014 at 9:58 | history | edited | jmort253 | CC BY-SA 3.0 |
updated StackInbox to work with the new top header; updated screenshots, updated new repository; added Firefox extension to Mozilla Add-Ons site.
|
| Feb 17, 2014 at 0:20 | comment | added | jmort253 | Hey @terdon, I'm still working on updating this, but if you have Chrome/Chromium, you can checkout from github.com/jamesmortensen/stackInbox and then run unpacked from the extensions folder. If a week goes by without any major issues, I'll publish to the Chrome Web store and update this post. Hope this helps. | |
| Jan 14, 2014 at 23:59 | comment | added | terdon | Does this work with the new inbox top bar thingie? | |
| Dec 9, 2012 at 0:24 | history | edited | jmort253 | CC BY-SA 3.0 |
Added in the Firefox version of StackInbox
|
| Dec 4, 2012 at 6:08 | answer | added | JamesTheAwesomeDude | timeline score: 6 | |
| Nov 23, 2012 at 15:41 | comment | added | jmort253 | @user2428118 - I should probably edit out the userscript headers, since I converted this to a Chrome Extension. This would eliminate confusion. With that said, I still have my original userscript and am thinking of including it here. It's not as good as the extension since the inbox data can't be shared across the different SE sites due to same-domain policy... | |
| Nov 23, 2012 at 11:40 | comment | added | user2428118 |
I was checking the source code directly, actually. Because of my experience with userscripts, I thought the script would only run on @included locations. I forgot to check the manifest file. Sorry.
|
|
| Nov 23, 2012 at 1:19 | comment | added | jmort253 | @user2428118 - I just tried on meta.bicycles, and I don't see a problem. You could edit the stackInbox.js file in the extension and replaceAll '//console' with 'console' and that will let you see the logs and/or send them to me. However, I just noticed you don't have an account on bicycles SE! Are you logging into Bicycles using another account? | |
| Nov 22, 2012 at 17:05 | comment | added | user2428118 |
Your extension does not run on the meta sites of http://*.stackexchange.com/* sites. (For example: http://meta.bicycles.stackexchange.com/)
|
|
| Nov 22, 2012 at 0:19 | comment | added | jmort253 | @Jonathan - I agree. But SE isn't going to do it, at least that's what Jeff said. Maybe they might do it if this gets a lot of usage. Some add-ons do eventually make their way into the core system. | |
| Nov 20, 2012 at 6:16 | history | edited | jmort253 | CC BY-SA 3.0 |
StackInbox is now on the Chrome Web Store
|
| Nov 18, 2012 at 9:39 | history | edited | jmort253 | CC BY-SA 3.0 |
added known issues and the link to the ZIP file in the installation instructions
|
| Nov 18, 2012 at 9:23 | history | asked | jmort253 | CC BY-SA 3.0 |