pullover.2.zip

hi,
can u add this function?
when disconnect,it can auto reconnect each 5 or 10 seconds?

Using Windows 7-64, notifications do not come to the top focus and are displayed behind the open applications.

The initial version of Pullover was created within 3 days to just make it work. Since development continues, the code needs to be refactored and split into smaller files to keep it maintainable. Maybe introducing gulp and js-file concat as well as sass compiling...

• Move WebSocket-code to pushover-client module
• Move autorun code to own model
• Split up app.js and use some sort of js file concat
• Add sass compiling to build
• Make each page(eg. login/settings/status...) a "plugin" with a initFunction, showFunction, maybe closeFunction and #id-name. Then turn them into modules/single files. This might need a new issue.

It's possibile to ignore old notifications not showed by Pullover?
After a long time no run, I'm receiveing a lot of notification and I can't stop it.

If the alert style for pullover in the notification center is set to 'Alerts', Pullover shows the notification twice.

.... seems to be fixed to the bottom right corner of the screen - just not everyone has the task bar on the bottom of the screen ;) where this would also match the taskbar icon position; so either adjusting it to the actual taskbar / taskbar icon position, or even to allow choosing a corner would be nice.

The Open Client API documentation has been updated today to reflect a new "E" frame that is sent upon a login failure, before closing the connection. Pullover should react to this frame by considering it a permanent failure, which should stop its reconnection retry loop and raise an error to the user. This login failure can happen if the user's device is disabled (for licensing or otherwise) or the secret is invalid.

Also, if you could send a User-Agent string of something containing Pullover so it can be identified in our logs, that would help diagnose problems. Thanks!

Hey

Loving the app, the only things I'd like are:

• Respect priority, so if the priority is -2 - it doesn't appear (I use -2 for Infomation Logging that I like to be able to easily see, but I don't need to be pushed to me), likewise if a notification is +2, would be good to see the notification appear red or something.
• Only show last X messages. I had the app closed for a couple of days, when I re-opened it, every single message that it had missed came up one after the other, all of these I had already seen on my other devices, so it would be good if there was some way of stopping this flood.

Thanks!

Send notifications, clipboard, ... to all/some devices using Pullover

The first notification after Pullovers start is not displayed under Windows 8.1

• Fix missing libudev.so.0 (https://github.com/rogerwang/node-webkit/wiki/The-solution-of-lacking-libudev.so.0)
• Create .desktop file

This is a continuation of #19
Sorry, I was't able to re-open that issue

both my friend and I are running 0.3.2 and this persistent failure to reconnect is still evident unfortunately
Manually clicking Reconnect causes the app to produce a recurring Login Failed message
We both need to Logout and Login again and create a new device so it is most frustrating

Any chance of a fix please?

If I have Pullover running, and for some reason I lose my internet connection, it is bad. What happens is:

• Pullover notifies me I am disconnected, and prompts me to reconnect
• I attempt to reconnect
• Pushover informs me the API denied my login request, and I have to login again
• So I login again with my username and password
• I am forced to create a new device
• I can't use the same device name, so now I have several dupes in my Pushover account

It seems that all the images in the app (for Mac) are retina except the menubar icons.

Distribute Mac App as .dmg. Might be as simple as renaming the zip and adding a link to Applications.
Just found this: npm appdmg

Installer for Windows. Maybe take a look at Inno Setup

Currently Windows Notifications look like this:

There is no notification history and if multiple notifications are fetched at once, some can not be seen by the user. Maybe take a look at robrighter/nw-desktop-notifications and edjafarov/node-webkit-desktop-notification.

I saw this crash this morning. I've added a lot more pushover last night. Could it be related?

 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._parseCommand'^M
 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._resetKeepAlive'^M
 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  App      'Conn-status:'   1^M
 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 09:59:40 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._stopKeepAlive'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      '=============== STACK ==============='^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      'SyntaxError: Unexpected token <\n    at Object.parse (native)\n    at validateResponse (/Applications/pullover.app/Contents/      Resources/app.nw/lib/pushover-client.js:744:23)\n    at Request._callback (/Applications/pullover.app/Contents/Resources/app.nw/lib/pushover-client.js:319:4)\n    at Request.self.  callback (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:368:22)\n    at emitTwo (events.js:85:13)\n    at Request.emit (events.js:153:        7)\n    at Request.<anonymous> (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:1219:14)\n    at emitOne (events.js:80:20)\n    at Request.     emit (events.js:150:7)\n    at IncomingMessage.<anonymous> (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:1167:12)'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      '=============== Error Object ==============='^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      '{ stack: \'SyntaxError: Unexpected token <\\n    at Object.parse (native)\\n    at validateResponse (/Applications/pullover.app/  Contents/Resources/app.nw/lib/pushover-client.js:744:23)\\n    at Request._callback (/Applications/pullover.app/Contents/Resources/app.nw/lib/pushover-client.js:319:4)\\n    at     Request.self.callback (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:368:22)\\n    at emitTwo (events.js:85:13)\\n    at Request.emit         (events.js:153:7)\\n    at Request.<anonymous> (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:1219:14)\\n    at emitOne (events.js:80:        20)\\n    at Request.emit (events.js:150:7)\\n    at IncomingMessage.<anonymous> (/Applications/pullover.app/Contents/Resources/app.nw/node_modules/request/request.js:1167:12)\',   message: \'Unexpected token <\' }'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      'Show Modal'   'Fatal error'   'Pullover encountered a fatal error. Please goto <a onclick="gui.Shell.openExternal(\'https://      github.com/cgrossde/Pullover/issues\');" href="#">Github (Pullover/Issues)</a> create a new issue and post the contents of your logfile: <a onclick="gui.Shell.showItemInFolder(\'/  Users/charlie/Library/Application\\ Support/Pullover/pullover.1.log\');" href="#">/Users/charlie/Library/Application\\ Support/Pullover/pullover.1.log</a>'   'danger select-        text'   [ { text: 'Exit Pullover', func: [Function] } ]^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._parseCommand'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._resetKeepAlive'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  App      'Conn-status:'   1^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 09:59:50 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._stopKeepAlive'^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._parseCommand'^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._resetKeepAlive'^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  App      'Conn-status:'   1^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype.lastInteractionDate'^M
 Mon Dec 21 2015 10:00:01 GMT+0000 (GMT)  OpenClient      'OpenClient.prototype._stopKeepAlive'^M

Title says it all. It just loops back to that menu screen indefinitely.

It's been working before on this machine and suddenly stopped. I reinstalled and logged out - same issue. v.0.3.2

Erik

Just installed 0.3.1 DMG for my OSX 10.9.5. I'm trying to send a message, which delivers correctly, but with no sound. I'm using Zapier Webhook to do a POST and it found all the necessary Properties, but sound doesn't seem to be working.

Currently, as described in "Installing on Linux", we need to own the /var/local/Pulldown directory. This can obviously lead to problems, for instance when having multiple users using Pulldown. Also, I can't see why one would run Pulldown as a system daemon.

Can you please change appDataPath on Linux to something like process.env.HOME + '/.local/share'? So that the log path will become ~/.local/share/Pulldown?

Thanks for creating this awesome program!

Make build.js a cli-tool with options to:

• build for different platforms
• bundle builds to .dmg or Win-installer, ... #4, #5
• upload builds to source forge via sftp
• tag them using the REST-API

Hi Chris- first off thank you! the is exactly what I was looking for- a decent desktop application for pushover. Pullover is awesome.
I Installed it yesterday for the first time. One issue that was previously covered was the disconnect coming out of sleep/bad api message. This is occurring for me- except it happens much more regularly in the middle of use so I'm hitting reconnect every 30-45 minutes or so. For example it happened while writing this (attached). I'm on Yosemite, version .2.0. I don't see a log in the support files but please let me know if I can provide any information. Thanks again

Windows: node-winreg
Mac: mabye this module

I would like to see this client have an option to make some sort of sound upon notification in addition to the pop up.

Use the internal notification DB to show a count of received messages

After waking up Pullover an Mac thinks the API-Endpoint gracefully closed the Socket (which usually means the credentials were wrong). In this case a reconnect fixes the problem. Possible solution: On "graceful" disconnect, try to reconnect one more time.

When using OSX native notification setting in Pullover message appear somewhat truncated if they do not contain any subject/title information. Please see the following screenshot of the OSX notification center:

Here you can see that while the first message was sent with a subject/title "TEST1" the second message has an empty subject/title and will be somewhat shown truncated so that the "Vor X Min." is not visible anymore.

Here I am using the latest Pullover 1.0.0-beta.1 on OSX 10.11.4 El Capitan

Using Win 7 Pro - 64bit

Here is the log snippet that might be helpful:

Mon May 18 2015 13:45:11 GMT-0700 (Pacific Daylight Time)  App      'getMessages - try request'
Mon May 18 2015 13:45:11 GMT-0700 (Pacific Daylight Time)  OpenClient      'OpenClient.prototype.fetchNotifications'
Mon May 18 2015 13:45:12 GMT-0700 (Pacific Daylight Time)  App      'getMessages - successful'
Mon May 18 2015 13:45:12 GMT-0700 (Pacific Daylight Time)  App      'New messages: 1'
Mon May 18 2015 13:45:12 GMT-0700 (Pacific Daylight Time)  OpenClient      'OpenClient.prototype.acknowledgeNotification'
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      '=============== STACK ==============='
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      'TypeError: Cannot read property \'style\' of null\n    at setStyleOnDomElement (C:\\Users\\avi\\AppData\\Local\\Temp\

\nw5436_16011\\node_modules\\nw-notify\\index.js:479:16)\n    at Window.<anonymous> (C:\\Users\\avi\\AppData\\Local\\Temp\\nw5436_16011\\node_modules\\nw-notify\\index.js:447:4)\n    at emitNone 

(events.js:70:20)\n    at Window.emit (events.js:147:7)\n    at IDWeakMap.global.__nwObjectsRegistry.handleEvent (node.js:786:26)'
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      '=============== Error Object ==============='
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      '{ stack: "TypeError: Cannot read property \'style\' of null\\n    at setStyleOnDomElement (C:\\\\Users\\\\avi\\\\AppData\\\

\Local\\\\Temp\\\\nw5436_16011\\\\node_modules\\\\nw-notify\\\\index.js:479:16)\\n    at Window.<anonymous> (C:\\\\Users\\\\avi\\\\AppData\\\\Local\\\\Temp\\\\nw5436_16011\\\\node_modules\\\\nw-

notify\\\\index.js:447:4)\\n    at emitNone (events.js:70:20)\\n    at Window.emit (events.js:147:7)\\n    at IDWeakMap.global.__nwObjectsRegistry.handleEvent (node.js:786:26)", message: "Cannot 

read property \'style\' of null" }'
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '
Mon May 18 2015 13:45:25 GMT-0700 (Pacific Daylight Time)  App      'Show Modal'   'Fatal error'   'Pullover encountered a fatal error. Please goto <a onclick="gui.Shell.openExternal

(\'https://github.com/cgrossde/Pullover/issues\');" href="#">Github (Pullover/Issues)</a> create a new issue and post the contents of your logfile: <a onclick="gui.Shell.showItemInFolder(\'C:\\\

\Users\\\\avi\\\\AppData\\\\Roaming\\\\Pullover\\\\pullover.1.log\');" href="#">C:\\Users\\avi\\AppData\\Roaming\\Pullover\\pullover.1.log</a>'   'danger select-text'   [ { text: 'Exit Pullover', 

func: [Function] } ]
Mon May 18 2015 13:45:41 GMT-0700 (Pacific Daylight Time)  OpenClient      'OpenClient.prototype._parseCommand'
Mon May 18 2015 13:45:41 GMT-0700 (Pacific Daylight Time)  OpenClient      'OpenClient.prototype._resetKeepAlive'

When starting on Linux Mint the following error occurred:

./pullover: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

The pushover notifications are set to show up on monitor 1 and I'd rather have them show up on monitor 2 or 3. Please implement an option for this

Resize app icons on Mac to 32x32. Needs the native lwip module.

Hey, so far so good with the rewritten alpha; haven't suffered random disconnects. But initially after logging in, the status remained "STOPPED" and I couldn't figure out how to start it. I restarted the app, and then it showed as being "ONLINE". (However, it lost my "Run on Startup" and "Use Native Notifications" settings, so I had to reset them.) It's been fine ever since.

Somewhat related to #48 I noticed that the official iOS Pushover App displays the user choosen application name or "Pushover" (for default messages) for notifications where no title/subject has been added. Pullover however omits the title/subject completly which actually triggers the problem seen in #48.

Here the output from the native iOS Pushover App:

Here the output from Pullover:

Please note that the official iOS Pushover App is adding an own subject/title based on the Application Name if there is no explicit subject/title added when submitting the message.

I am using Pullover 1.0.0-beta.1 here on OSX 10.11.4 El Capitan

I wonder if there is a way to build a linux 64 bit version. I really want to avoid loading all the libraries below. Is building code on MAC is the only option?

ldd pullover
linux-gate.so.1 (0xf76f5000)
librt.so.1 => /lib/librt.so.1 (0xf76b6000)
libdl.so.2 => /lib/libdl.so.2 (0xf76b1000)
libm.so.6 => /lib/libm.so.6 (0xf766b000)
libgobject-2.0.so.0 => not found
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xf7557000)
libnss3.so => not found
libnssutil3.so => not found
libsmime3.so => not found
libplc4.so => not found
libnspr4.so => not found
libgconf-2.so.4 => not found
libgio-2.0.so.0 => not found
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xf7519000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xf7487000)
libpangocairo-1.0.so.0 => not found
libcairo.so.2 => not found
libpango-1.0.so.0 => not found
libX11.so.6 => /usr/lib/libX11.so.6 (0xf734b000)
libXi.so.6 => not found
libXcursor.so.1 => not found
libXext.so.6 => /usr/lib/libXext.so.6 (0xf7337000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xf7331000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xf7326000)
libXcomposite.so.1 => not found
libasound.so.2 => /usr/lib/libasound.so.2 (0xf723b000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xf7237000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0xf7230000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xf7225000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xf71fc000)
libdbus-1.so.3 => /lib/libdbus-1.so.3 (0xf71af000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf7193000)
libgtk-x11-2.0.so.0 => not found
libgdk-x11-2.0.so.0 => not found
libgdk_pixbuf-2.0.so.0 => not found
libnotify.so.4 => not found
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf70a5000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7088000)
libc.so.6 => /lib/libc.so.6 (0xf6edb000)
/lib/ld-linux.so.2 (0xf76f8000)
libpcre.so.1 => /usr/lib/libpcre.so.1 (0xf6e6a000)
libz.so.1 => /lib/libz.so.1 (0xf6e53000)
libpng16.so.16 => /usr/lib/libpng16.so.16 (0xf6e16000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xf6df3000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xf6def000)

I don't know if this might be a bug or simply a missing feature or me using OSX notifications incorrectly. But here a pushover message is only received with playing the adequate pushover sound if Pullovers' now notification system is used. As soon as I switch to native OSX notifications no sound whatsoever is played.

It would be great if that feature could be implemented for the final 1.0.0 version. here I am using the beta1 version of 1.0.0, btw.

you should be able to publish the builds as "releases" here in GitHub or otherwise use LFS.

I'm trying to download pullover and it's a 41.92MB dl that has taken something like 8 minutes.

Hi, is is possible down the road to add the notification placement option for Pullover? Currently I get them in the lower right corner. Ideally (for me) they would go in the upper right- where my other notifications are placed. Just an idea.

Thanks

History features:

• See all received notifications (since 1.2.0-alpha.1)
• Sort by time or app
• Delete one / all / all of single app
• Disable history in settings
• Remove messages older than X days (settings)
• Group by time (#68)
• Make notifications searchable (#68)

Please provide pullover application in ZIP file, so no installation is requires (only unpacking).
Some kind of 'Portable' version.

I have just noticed that when sending HTML-based notifications around pushover the Pullover client only supports HTML in its own notification window. As soon as I switch to native OSX notifications the HTML code is shown instead of interpreting the HTML tags accordingly.

While this might be perfectly a limitation of the OSX notification engine (is this really true?) it would be great to at least change Pullover that it automatically strips any HTML tags as soon as the OSX notifications are used. Best would be, however, to actually interpret the HTML tags and let OSX notifications also interpret the HTML stuff.

BTW: I am using your latest 1.0.0-alpha version and it works fine so far.

Great work on this project and thanks for open-sourcing it.

I'm trying to use this program as a starter kit for another project, and I'm getting an error when building the windows installer:

Windows installer created
events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: spawn signcode ENOENT
    at exports._errnoException (util.js:837:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:178:32)
    at onErrorNT (internal/child_process.js:344:16)
    at doNTCallback2 (node.js:429:9)
    at process._tickCallback (node.js:343:17)

Looking at the builder file, it looks like I need to have a .crt and .spc in /res , but even if there are files there, the error occurs.

I'm using OS X and have installed the items from CROSSPLATFORM.md

Will fix in next alpha/beta.

Upon receiving a desktop notification, messages are not shown in notification centre, on OS X 10.10 Yosemite.

Cheers
Serg

Topbar icons are not clickable, fix -webkit-app-region: no-drag

Should be caught ... but is not fatal, client recovered without problems.

Sat Mar 12 2016 15:46:33 GMT+0100 (CET)  ConnectionManager      'Connect to WebSocket'
Sat Mar 12 2016 17:28:33 GMT+0100 (CET)  ConnectionManager      'Device woke up after 6108s of sleep'
Sat Mar 12 2016 17:28:33 GMT+0100 (CET)  ConnectionManager      'Reconnect'
Sat Mar 12 2016 17:28:33 GMT+0100 (CET)  ConnectionManager      'fetchAndConnect'
Sat Mar 12 2016 17:28:33 GMT+0100 (CET)  PushoverRESTClient      'OpenClient.prototype.fetchNotifications'
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      'Pullover v1.0.0-beta.1'
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      '=============== STACK ==============='
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      'Error: getaddrinfo ENOTFOUND client.pushover.net client.pushover.net:443
    at errnoException (dns.js:25:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:75:26)'
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      '=============== Error Object ==============='
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      '{
    stack: 'Error: getaddrinfo ENOTFOUND client.pushover.net client.pushover.net:443
    at errnoException (dns.js:25:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:75:26)',
    message: 'getaddrinfo ENOTFOUND client.pushover.net client.pushover.net:443',
    code: 'ENOTFOUND',
    errno: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'client.pushover.net',
    host: 'client.pushover.net',
    port: 443
}'
Sat Mar 12 2016 17:28:35 GMT+0100 (CET)  Fatal      ' - - - - - - - - UNCAUGHT EXCEPTION - - - - - - - - '
Sat Mar 12 2016 17:28:37 GMT+0100 (CET)  ConnectionManager      'Fetch failed - offline'   { [FetchNotificationsFailed: Could not reach Pushover servers]
  name: 'FetchNotificationsFailed',
  cause: 
   { [Error: getaddrinfo ENOTFOUND api.pushover.net api.pushover.net:443]
     code: 'ENOTFOUND',
     errno: 'ENOTFOUND',
     syscall: 'getaddrinfo',
     hostname: 'api.pushover.net',
     host: 'api.pushover.net',
     port: 443 } }
Sat Mar 12 2016 17:28:38 GMT+0100 (CET)  ConnectionManager      'Offline'

Would it be possible to get support for acknowledging notifications? The Android client at least (and I suspect all the official clients) support acknowledging notifications, which allows Pushover to call a callback URL when the notification is acknowledged (this can also be polled). .

If you set a page to be emergency priority (2), and you set a retry and expire parameters, Pushover will send the message over and over (every retry interval) until it's acknowledged or the expire time is reached.

Would be great if Pullover supported being able to acknowledge these types of notifications (we're planning to roll out Pushover/Pullover as an internal paging service).

The menubar icon on Mac is heavily black and still non retina.