New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push notification to Desktop or Smartphone if download need interaction #14
Comments
Smart idea! With focus on Android "Android Cloud to Device Messaging Framework": I also thought about doing this proposal some months ago, but stopped at this border: The sender of Push-Notifications needs a Google GCM-Account (http://developer.android.com/google/gcm/gs.html). As each running Python-Instance also is a sender of Push-Notifications we require either: a) Each user to register for the GCM-Service Please note, Google changed its API from C2DM to GCM in July 2012. Just a small information package for you and the developers! ;) ( This is where I got my GCM/C2DM information from: |
👍 The first way, where every instance needs an own GCM-Account would be my favorite. Users, who need it, will create it! Also a single GCM-Account is limited in sending notifications per timespan, without further blabla to google.inc. So beside the challenge of providing it, that wrapping server is in my eyes not a good idea doe to that limitation. Remember, we need to fork both, pyload-server and the android app to do that token stuff. If I knew where to get that captcha-event from... (sadly it isn't prepared at ./scripts) I already would have started it. Yes I didn't do a deep code exploration, it should be easy. :-) |
Using independent accounts would be my opinion, too! Also, providing a "bulletproof and stable" server is difficult, if you are doing open-source software ;) I already went through the android code twice, each time starting a modification and just before committing, I noticed that @RaNaN was faster and better doing the same! :D I have difficulties to integrate it in an elegant way.. |
I really doubt that using individual accounts for each user is an option. The preferred way would be that we setup GCM and also host the server for the push messages. I think the hosting would not be the problem, but currently there are different priorities and we don't have the time for the implementation. |
How about desktops? A quick google search resulted in some html5 stuff, but it seems it's either webkit specific or not implemented. I'd really like to have this feature, especially on the desktop and it seems easier to implement there than on mobile. |
@Nippey we should implement a service, not a separate app. Can you share you work? @RaNaN yes the android app will be bound to an specific GCM Account when the app register itself. But I don't think that this has to be the account of the app-publisher. The GCM_SENDER_ID should just be user-configurable in the app in my eyes and we are fine. The pyload-server side especially handling that PROPERTY_REG_ID is that stuff I can't handle. @stickell & @ajs124 I suggest splitting this issue as an desktop and the android application are two different topics. !gm |
@exclamationgm: With "Android-Code" I meant the pyload app. But since the last merge from the main repository it keeps crashing when I try to use my modifications... :( @exclamationgm & @RaNaN An android app must not be bound to a specific GCM account on compile time. So there would be no difficulties to have on GCM account per user. |
Today I had seen, in pyLoad 0.49 is already implements an XMPP Notification Hook (Can't see the end of the submenu in webclient). So we doesn't need a push function. :D But the hook is a little bit buggy. E.g. no reconnect method. ;) I try to fix it in version 0.49 and hope you implements this method in 0.5. |
Maybe it is possible to integrate https://pushover.net via https://github.com/erniebrodeur/pushover to achieve this enhancement easily? |
From their FAQ: But did I see it right, that I have to install their Android app? |
As far as I understand the push notification is a "nice-to-have". Pushover seems to be integrable with little effort and and provides an existing infrastructure/solution. Yes, the apps are not for free, still pushover is a quite convenient way for notification. |
I suggest to simply add "PLAY SOUND ON CAPTCHA ARRIVED" to the webinterface. |
On OSX 10.9 a website can send the OS a notification (locally or through a server). |
@rnhmjoj But only in Safari. ;) I prefer notification via Jabber. It's easy and all Operatingsystems can handle this and if your Client support XEP-0231, you can send the image inline of notification. (Okay, this feature isn't implement yet, but it's possible. ;)) |
sry for commenting here if this is not up to date any more. I stumble upon this thread via google. I'd vote for email. Every client supports them. If you don't like keeping them you can implement a rule in the mail program of your choice. Keep the Emails short and give the user choices as to what notifications are to be sent. Other remote programs in need of long-lasting reliability (like RAID clients, Linux cron jobs in general) use them too. |
This ticket has been automatically marked as |
This ticket has been automatically closed. |
Use push notifications to alert the user for needed interaction.
E.g. tipping a captcha code.
The text was updated successfully, but these errors were encountered: