-
Notifications
You must be signed in to change notification settings - Fork 5
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
Implement notifications #12
Comments
Thanks, the client side is implemented already. |
https://bugs.launchpad.net/ubuntu-push/+bug/1522810 PRs for upstream TextSecure server component |
Moxie unfortunately rejected the PRs. Is there any plan b? |
Nothing I am afraid. If the Ubuntu Touch push system implemented (not sure if it is doable at all) GCM compatibility maybe. Or if lightweight background tasks were allowed that would keep a websocket open. But both these would require more work for very little gain - the number of Signal users (even including all potential ones) is very small. |
Hi janimo, I tried to politely ask the openwhisper developers about the state of affairs regarding your both commits. I don't know what to think about Moxie's response, but I must say, I am shocked how he refused it, without giving any reason and also by locking the conversation to collaborators (so I could not ask why he refused it). It would be really interesting to know why the commits were refused. |
It would be just a crutch, but wouldn't it be possible to build a kind of proxy server, which fetches messages from the textsecure server via websocket and pushes them via UPS? Because of the users credentials each user should run his own proxy, but basically this could be a way to make textsecure on ubuntu really usable!? |
Is there any change to use parts of the websocket stuff that has been done for https://github.com/LibreSignal/LibreSignal ? |
Hi Janimo, thanks again for the great Textsecure Client for Ubuntu Touch. I frequently use and enjoy it. Thanks, |
Hi, nothing has changed since last time. On Sun, Aug 14, 2016, 1:58 PM Pete413 [email protected] wrote:
|
Would implementing this proposal potentially solve the issue? |
Thanks for the link. I haven't studied it besides a cursory look, but if/when this is implemented it may be a workaround for the lack of server support for notifications. |
Hi janimo, it seems that the notification support on Ubuntu Touch platform has already improved: "a new telephony-service for a fix for the no-SMS-notifications bug" (https://lists.launchpad.net/ubuntu-phone/msg22596.html) |
The notification support we'd need is the ability to run a background task (either standalone or as a plugin that is part of a system-wide background task ) that could poll the Signal servers and notify the locally running push notification subsystem to have it pop up a notification. The current client notification support on the phone relies on an external server pushing events, which lacking Signal server side support does not suffice for us. |
@janimo have you thought about including a background task and uploading to the Open Store just to make it more useful to people? |
Hey Scott :) |
Hey :-) The Open Store is an alternative app store for Ubuntu where you can upload apps that won't work with the current confinement scheme. There is a tradeoff there in that some of the apps are actually unconfined or don't meet the standards for the normal Ubuntu store. There is at least one other IM service (Loqui) on the Open Store, and I use it for XMPP along with some settings from UT Tweak Tool that lets you prevent an app from suspending. It's not perfect but it will do until the proper messaging framework is released. |
Thanks, so is a background task a new feature or just any process you want to run when unconfined as on a regular Ubuntu? |
I'm not 100% sure, but AFAIK in the open store you can create a "daemon" that runs in the background and is started when the system boots. This daemon that would come "bundled" with TextSecure in the open store would check for notifications at a regular interval (or implement the push notifications from android) and "wakes up" the main TextSecure app when a new notification arrives. I'm sure that Dekko from the open store has an implementation for working around the notification-plugin limitations, so you may wish to look there first. I'm not sure how either of the other two work... |
Let's see if we can get someone with OpenStore experience to jump in. Mike Sheldon, @Elleo , wrote the awesome CuteSpotify app and released it to the OpenStore. I know he's still active with the community even if he isn't active with other projects. Mike, can you jump in and provide some insight for @janimo. Jani has done a tremendous amount of work getting TextSecure/Signal functionality on Ubuntu Touch. Many of us would love to see his work become a core app. Right now, we're just trying to figure out how he can deliver notifications to the phone and possibly use the OpenStore. I've utilized the "Prevent App Suspension" option that "UT Tweak Tools" from the OpenStore provides, but I think @janimo will need to implement an additional polling feature of some sort. So again, Mike, is there any way that you could help expedite Jani's efforts. You've been down the path of the OpenStore before, and your experience would probably save him some headache. |
Hey @janimo, it looks like you've been doing some great stuff here :) I think the best place to get some advice on this would be the Open Store telegram group, the developers of both Rockwork and the Loqui IM port are members and can probably give some good guidance on exactly this sort of thing: https://telegram.me/joinchat/BMTh8AHtOL2foXLulmqDxw |
@sethdc you mention wanting to see this as a core app (it was my hope to when I started working on it). Are there APIs available to core apps that would make the background work easier? |
This discussion has been ongoing for almost a year, and it has me equally optimistic and perplexed. I'm optimistic because I see enduring passion for the project itself and from the community in regard to free speech and encryption. I'm perplexed as to what step we should take next to move forward together. The last thing the community needs is another forked messenger app that is only used by few. To me, this is why @janimo's efforts are so important to Signal's ongoing successes and to the security of the Ubuntu community as a whole. Make no mistake, if @moxie0 were to accept Jani's PR, Signal would have native support not just for thousands of Ubuntu Phone users, but Moxie would be unlocking native support for the over TWENTY MILLION people that use Ubuntu desktop EVERY DAY. We currently have this support with Telegram on our Ubuntu desktops and phones. Thanks, but we want Signal. Two days ago, Moxie made two very important points:
To his first point, I agree. I would gladly spend several thousand dollars every year hosting a federated server that allowed all Ubuntu users to point to and reliably use Signal based upon Jani's work and Moxie's libsignal-protocol/service. However, that is not the optimal solution. Fragmentation and federation only dilute the Signal experience, product, and service. To his second point, if Moxie is open to using clean, well-written, and well-tested code for websocket-only support, then be open to using clean, well-written, and well-tested code for 20,000,000 Ubuntu desktop users. Moxie states that he would be fine with accepting the PR if the service comes with a warning that the websocket-only support is limited and not a reflection of the overall Signal service/experience. I agree. Jani's code and applications should come with a warning that absolves OWS and Moxie of any liability or complaints. However, we are the willing testers and adopters of this important work that is being done. There will always be complainers and whiners, but We The Willing must all continue to strive together for the benefit of the unwilling and the indifferent. I'm sure Moxie is overwhelmed and exhausted with people that complain but never do the work, but here we are saying that Jani has done that work and the rest of us are here willing to do the work of ongoing trial and ongoing testing. We know that there will be setbacks and problems along the way, but only by working together will we succeed. We need dialogue and direction from OWS on how to move forward together. We have the same goals. We have the same motivation. Patience, perseverance, cooperation, and communication will bring about the change we all desire. |
@sethdc After reading your post I have opened this issue. |
WebSocket support has been added to Signal: signalapp/Signal-Android@1669731 |
So is this the part where we remind Jani how awesome he is, and then ask
him to implement it for the good of all mankind??? :)
…On Fri, Apr 14, 2017 at 10:16 AM, kallekruse ***@***.***> wrote:
WebSocket support has been added to Signal: WhisperSystems/Signal-Android@
1669731
<signalapp/Signal-Android@1669731>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANpFfsk4zhwHfVkTAsuVYzbIISmwO7aqks5rv3-8gaJpZM4F8Ye4>
.
|
Thanks, however I am not sure websocket support is enough. We'd need background task processing capabilities in the Ubuntu Phone no? I didn't give much thought to this project in the past year, and with the recent news re Unity, I am not sure the future of the phone is any brighter than it was (and it wasn't that bright to begin with) |
I'll see if I can figure out the procedure for publishing to the OpenStore
to get around the background process situation, and then type up some notes.
…On Fri, Apr 14, 2017 at 11:06 AM, Jani Monoses ***@***.***> wrote:
Thanks, however I am not sure websocket support is enough. We'd need
background task processing capabilities in the Ubuntu Phone no? I didn't
give much thought to this project in the past year, and with the recent
news re Unity, I am not sure the future of the phone is any brighter than
it was (and it wasn't that bright to begin with)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANpFfsTLN3UwuitlAhP43l-jrp_tUPZ1ks5rv4tkgaJpZM4F8Ye4>
.
|
Thanks, but I'd rather work with officially accepted APIs only (patches welcome though for OpenStore compatibility). |
There might be hope - https://forums.ubports.com/topic/273/june-1-2017-app-developer-os-developer-meeting says:
|
This will need a server component as well and likely collaboration with OWS on server infrastructure setup.
The text was updated successfully, but these errors were encountered: