search

oxen-io / session-android

A private messenger for Android.
https://getsession.org
GNU General Public License v3.0
1.85k stars 170 forks source link

Support for UnifiedPush #558

Open FireMasterK opened 3 years ago

FireMasterK commented 3 years ago

This way, we do not require FCM for quick notifications without manual polling.

The user is also given alternative choices instead of FCM, which are more privacy-friendly, and can be self hosted.

I got this from official F-Droid account on Mastodon about the notification situation. Just posting it here if it's useful.

They could take a look at UnifiedPush. That way the user can decide which notification service to use, if any. Supports 3 of them, whichever is available on the device: FCM, Gotify or NoProvider2Push. And it's f/loss. https://unifiedpush.org/

Originally posted by @adnan360 in https://github.com/oxen-io/session-android/issues/73#issuecomment-800271079

japtain-cack commented 1 year ago

This issue is a bit old, but still relevant I think. This, and many other apps that are centered around security/anonymity, imho, should offer gotify/ntfy (choose best one) support. Heck, I'd even take pushover support at the "very" least. I use Element, Threema, Signal, Session, etc. It would be really awesome of the developers of said apps to collude a bit and decide on a common, open source and possibly self hosted, push notification service. Having all of these apps with their own polling service is very suboptimal for battery life and efficiency; not to mention all the un-dismissible notifications that pile up triggers my OCD.

There is great benefit in having maybe one or two options for a universal push notification service and I'm sure may others would agree.

Please let me know which option would be the best for this use case and I'm 100% willing and able to be a test subject. I have a production ready kube cluster running in my personal rack, so spinning up whatever server software is decided upon would be trivial. At the very least, I think feature request warrants a discussion, due to the nature and values of this app. Many of us are trying to fire google/big tech from our lives and features like this will only help in that regard.

Also, thank you for the great app. Firing signal over Session because I'm tired of the dependency on SMS/phone numbers. My phone was stolen and signal us useless until I get a new phone/sim, really irritating.

osering commented 5 months ago

Hello guys! I really appreciate this opensource project, but got something to say. Agree that presently this is critical dilemma and issue for degoogled gear users. User of such gear is most privacy oriented and Session has the same priority - so perfect match. It's pretty bd user experience without notifications, but it's counter logic pair such a privacy oriented software as Session with Google spy-crap (even with MicroG implementation). NTFY is great service, opensource, stable (public server used for years), responsive developer, easy and versatile & well documented API, clients for Android, Linux. Opensource apps: SchildiChat (matrix), MercuryGram (telegram) uses ntfy successfully. Why it takes so long to integrate such important element (and ignore such pressing need of degoogled users) as opensource privacy safeguarding notifications? Some other tasks with higher priorities for 3 years? This pushes prospective users to other messengers (as daily drivers), having Unified push...

IzzySoft commented 1 month ago

Transferring this over from the issue that just linked itself above:

Using UnifiedPush would make it easy to maintain a FOSS build. You could include their FCM distributor with the build flavor for PlayStore, while simply leaving that out of the FOSS build – so with the latter, those preferring not to have Google connections could use their own distributors (e.g. NTFY) while for those using the PlayStore build, there'd be no noticeable change. As a nice side-effect, this would also solve #169 :smiley:

You can also find some notes here.