petrobitcoins are the standard View quoted note →

Added a gallery view to my jumble fork View quoted note →

Believe and obey. View quoted note →

Summary of what Signal metadata can and might be visible to Google: - Phone-number account presence: If you register with a phone number, Google already knows that number on the device (via contacts, Play account, etc.)—not Signal-specific, but correlatable. - Push notification routing tokens: When Signal on Android uses Firebase Cloud Messaging (FCM) or Play services for push, FCM tokens and their delivery events (which device token received a message and when) are handled by Google. Google can see that a push was delivered to a particular FCM token at a given time; they do not see message contents. - Connection metadata: Basic network-level metadata (IP addresses, TLS connection timestamps, volumes) are visible to any network provider, including Google if traffic is routed via their infrastructure (e.g., on-device services). This can reveal approximate time and IP-based location when the app connects to servers. - App-install and Play-store telemetry: Google Play records install/update events, package name, and usage statistics; it knows that the Signal app is installed on that Google account/device. - Crash/analytics data (if enabled): If a user opts into sending crash reports or analytics through Google Play or Play services, those reports may include device model, OS version, stack traces, and timestamps — potentially linking app usage to the device. - Contacts sync (if used via Google): If a user syncs contacts with Google or grants Google access to contacts, Google can see contacts (and thereby infer who might be Signal users), though Signal’s own contact-matching is done via hashed lookups to Signal servers, not Google. - Indirect correlation: Combining the above (FCM delivery timestamps, IP/location, install/usage records, contact lists) can let Google link a device or phone number to push deliveries and times, producing lightweight metadata like "this device received Signal pushes at these times" — still without message content or the identities of correspondents as provided in Signal’s server logs. - Using Signal with Play services increases exposure of typical mobile metadata (push tokens, delivery events, Play-store telemetry) compared with a fully Play‑services‑free setup (e.g., Signal on a de‑Googleed Android or with proprietary push alternatives), which reduces what third parties see. View quoted note →

Benevolent View quoted note →

nostr needs more pkdns relays View quoted note →