You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d702f99
Browse filesBrowse the repository at this point in the historyBrowse files
fix(i18n): name unsafe links by kind, not by the threat feed's code
The phishing and screened-message notifications joined each flagged
link's threat detail with a hard-coded ", " and an English "malware"
fallback, so users read feed codes like verified_phish,
feed_domain_match or known_spam_domain (found by the refuting review).
urlThreatLabels() now names each link by kind in the app language
(phishing, malware, spam, otherwise dangerous), once per kind, joined
with the language's separator. The phishing notification takes the kind
as its "contains a %s link" word; the screened-message notification
wraps it as "phishing link". The local spam-domain threat gets a named
constant, and the zh-rCN phishing text no longer credits URLhaus for
feeds that aren't URLhaus. zh-rCN floor ratchets to 78.9.
Tests: LocalizedSystemTextTest adds the zh-rCN labels for all four kinds
from five feed codes. SmsReceiverRobolectricTest asserted the phishing
notification contained the raw "known_spam_domain" code, which is the
defect itself; it now expects the "spam" label and rejects the raw code.
fun List<String>.joinSignalLabels(context: android.content.Context): String= distinct().joinToString(context.getString(R.string.signal_list_separator))
84
86
87
+
/**
88
+
* What the unsafe links in a message are, in the app language, each kind
89
+
* once ("phishing, malware"). It fills the "contains a %s link" slot of the
90
+
* phishing notification. The feeds' own detail codes ("verified_phish",
0 commit comments