Hot answers tagged inbox
Very good. I've been looking for something simple like this for a while. Thanks. As potential future features; Growl integration would be great An option to temporarily disable notifications (i.e. when you want to get some work done and don't want to get distracted by revisiting your answers etc!) A 'run on startup' option Maybe have the default menubar ...
I like the current logos of SENotifier, but, I was bored, and decided to have a go at making some SENotifier logos as well. And, well, here they are! Tell me if you like them, or any comments! I don't know if the pictures will keep their formatting, though. Oh well. 1). (.png) 2.) (.icns)
Any way of porting this to iOS?
status-completed Can somebody please port this to Firefox? I would definitely appreciate it. FF Desktop Notification support: https://code.google.com/p/ff-html5notifications/
It would be really nice if somebody could rewrite this as a Greasemonkey script using Desktop Notifications, so that I could use this with Firefox. In case that last part left you thinking that there's something wrong with me, take a look at this. :)
I don't believe that that route accepts POST requests (as it's non-actionable), so you should have better luck sending a GET request instead. Routes that require auth tokens necessitate HTTPS, but still expect GET for read requests, and POST for writes.
I really like this too. It is great! I second @pastylegs' comment. Growl notifications would be very nice. I also wanted to add another comment. If you look at the SE inbox on the actual website, you'll notice that it displays past, read notifications: It would be nice to have several (maybe 5 or so) read notification in the menu bar. I find myself going ...
I've been recently running into a problem with SENotifier where it updates when a message is directed at me, but it always shows an old message rather than the lastest message.
Bug report here. It's not working on CoreDuo MBP/10.6.8 I suppose because it's 64-bit only but you didn't mention system requirements anywhere here.
This should be fixed now, we weren't properly considering the since parameter when fetching results from the cache. In effect if you ever asked for unread inbox items twice, once with and once without since, you'd get the same result back until the cache cleared.
The URL in the link field is sufficient to uniquely identify an inbox message. Each kind of notification has a different format of URL, and you only get one inbox notification per event.
Update: Op followed the advice, below, and changed the question from a bug to a feature-request. This is not really a bug. Right at the top of the API documentation, it states that the API is read-only, in bold letters: Stack Exchange API v2.0 This is the documentation for the v2.0 read-only (with optional authentication) Stack Exchange API. If ...
I added support for OSX Notification Center and made a pull request.
I have forked your source code, and enabled Retina display support. I have also recreated all the icons. Check it out on GitHub.
As described in the /me/inbox documentation, the route is ...effectively an alias for /inbox. It is provided for consumers who make strong assumptions about operating within the context of a single site rather than the Stack Exchange network as a whole. Since it's just more or less a convenience route for the global /inbox method, it doesn't actual ...
Provided you don't do anything "evil" (which basically means leaking user messages to people/apps they haven't authorized), we have no objections to a generic push service. Yes, the per-minute throttle is for the same request; changing the parameters counts as separate requests. Do note that the 30 requests/second cutoff is by IP (it's a DOS prevention ...
This is an awesome app, great job. But I think you forgot to make the extra text after "Check Now" change white when you hover over it, see: I'm not a Mac App Developer (not yet, anyway) so I don't know if it is possible to change that but I just wanted to let you know about that.
A fix for this will go out with the next build.
Only top voted, non community-wiki answers of a minimum length are eligible