Basically, they didn't do this:

(I'm on Android, so I don't know what the options look like in iOS, but they should be identical.)
This is a most excellent place for technology news and articles.
Basically, they didn't do this:

(I'm on Android, so I don't know what the options look like in iOS, but they should be identical.)
It would be nice if Signal let you do this per conversation.
It's sort of a victim of its own success, I use it for both things that do and don't require opsec
and on some level it's important for good opsec that things that don't require opsec be done with good opsec
You also don't need to do this on Android unless you are concerned about random people seeing the messages on your screen. Signal on Android does not use Google's push notification service
You most certainly do. I looked in my notification history in my founding of signal messages.
Then I turned off my notification history.
It's not about how it's pushed. It's how it's displayed (and stored) on the phone.
It’s both. Governments have started subpoenaing the push notification servers for data, instead of targeting individual devices. That little pop-in that says who the message was from, and maybe a little bit of the body of the text? Yeah, the push notification server handled that, and the government has access to that server. So any notification you see on your screen, you can be pretty positive that the government has also seen.
But this is about the notification data being stored in a part of the phone that isn’t encrypted. Signal is (or at least claims to be) E2E encrypted, so it shouldn’t be possible for a warrant to get access to the messages in the app. But since the phone is storing those notifications in a separate area (which isn’t encrypted), the warrant was able to read them.
The point is that there are two different attack vectors, and you should harden your device against both.
as far as i know signal uses Google's notification service and if you want it to not you need to use Molly
Signal on Android does not use Google's push notification service
Source? I'm pretty sure it falls back to a different mechanism when it doesn't find google services. And that is only on the version downloaded from their website.
They are similar
Thank you internet stranger. I'm going to do this but fuck me if I can get my family to change their settings. They don't even know they can create a poll.
Don't ask me. I made all of you admins do I don't have to answer questions like how do I make a poll. Click the + button. Yeah. The one on your fucking screen right now.
No grandpa. We are not trying to figure out who is trans. No popop none of are naxies (I hope)
Anyway, click the +. Right there. That is how you create a poll.
They shouldn't have have to do this though.
there's a lot of things under fascism that shouldn't be needed

This is the problem, not what is shown in the per-app notifications. Don't turn on notification history.
I learned about this a couple of months ago and I've since disabled previews in notifications. It's unfortunately the nature of how notifications are delivered to you. You should be fine by disabling message previews in your notification settings.
Yup,
https://www.privacyguides.org/articles/2022/07/07/signal-configuration-and-hardening/
Among other things
I think on android, signal do not use Google's push notification. They simple send a dummy push, and the signal app wakes up to retrive the latest message directly from signal server.
So Google never have your notification content. I am not sure if they do the same on iOS.
That being said if your attack model includes people reading your notification lock screen, then you should disable showing signal notification.
The message preview notification is handled similarly in IOS and Android. The issue isn't people seeing the notification, it's that the content of the message being passed to the phone's launcher. Which is unencrypted.
Does that actually prevent the app from sending the content through Apple’s servers or does it just prevent iOS from showing it in the notification area?
The only way apple is seeing it is when the notification is displayed. It only sees the contents of the notification itself. So it would still see who sent you a message, but it wouldn't say what it was
It's worth noting apps can avoid this on Android: https://tuta.com/blog/google-push-alternative#alternatives-to-google-push
Any FDroid app cannot use Firebase for push notifications since it's proprietary: https://forum.f-droid.org/t/firebase-allowed-in-fdroid-apps/7540
It's not because of push notifications. the message is not sent to firebase, just a signal that the app should do a refresh.
It's because the system saves the notifications apps posted to the notification menu.
but yes. don't use firebase push notifications if you can avoid it. use a unifiedpush based system. base signal app does not support it, only molly. there are some difficulties though with that that are unique to signal.
That’s my biggest issue with notifications. Notifications should just notify you that something happened and you need to open the app to find out. Carrying actual data ON the notification is a no-no.
But what do I know, I’m an old developer not one of these modern vibe kiddies.
Signal already has that setting. It’s up to the user to decide their level of convenience vs security.

A notification doesn’t have to carry any data in its payload; Signal devs could take care of that.
Signal has supported this for many years. Users can choose full content notifications, name only, or no-content notifications.
So you are telling me an app is encrypting the shit out of every message so it can secretly delivered to another person. An then the persons phone decrypts the message and broadcasts it to an apple server, so it can get send back and make the phone go 'ding'?
Shouldnt the notification be handled inside signal somehow, so this is the only app with the decrypted message?
What is next, everything from my ram needs to go through google servers to be transmitted to my display?
The Signal server would send a backend notification to the client app via the Apple Push Notification Service. The app is then able to wake up, at which point it fetches new messages (securely) from the Signal servers. The app then generates a local notification with a preview of the received message. iOS is then logging those messages.
This is not always the same on Android. Any app from FDroid will not use Google's push notification service because it is proprietary, meaning it violates the rules for FDroid. Signal does not use Google's notification service
It's not because of push notifications. the message is not sent to firebase, just a signal that the app should do a refresh.
It's because the system saves the notifications apps posted to the notification menu.
I'm pretty sure Signal has two builds: one with Google service and one without.
Well, of course. All notification contents go through Apple's servers (or Google's in case of Android).
Not all, no. There are alternatives on Android:
The good news is that alternative methods for push notifications are available, namely SSE (Server Sent Events) and WebSockets.
Additionally, a new open source project, UnifiedPush is becoming increasingly popular. UnifiedPush is an open source, private alternative to Google for notifications.
https://tuta.com/blog/google-push-alternative#alternatives-to-google-push
Signal for android uses web sockets for notifications
Why would a notification need to leave my device at all?
Because it's FAANG
This has been done before and is already pretty well known.
When I saw it hit the news before, it was because they were reading notifications off Google servers, which contained at least part of the message. Not because they were reading the device's notification history.
Honestly I have a much much much MUCH MUCH bigger issue with the fact that it is an American and Centralised service.
FBI still can't access it though.
Is there a good decent e2e messenger not in the US? Would love an alternative.
There's Matrix which is selfhostable but "good" is pushing it and the cryptography is a bit iffy (probably more incompetence than malice). Though selfhosting it means you don't need the end to end encryption quite as much... until the court gets involved of course.
-- Frost
Just more evidence that Apple is not that concerned about privacy as this is a hole they absolutely could close.
Added the full content of the original post to the body of this thread.