3 ms·

If only Google would hire you, I'm sure you could solve all our spam problems (including the one I work on) in an ethical and competent way. :) Sometimes there

by endtime 14y ago

If only Google would hire you, I'm sure you could solve all our spam problems (including the one I work on) in an ethical and competent way. :) Sometimes there are different classes of users with conflicting interests, and no algorithm or ML model or abundance of good intent can resolve them.

harshreality 14y ago
I thought SOP for mitigating IM spam was to require user confirmation before delivering the suspect IMs? Google doesn't have to perfectly solve the spam identification problem in order to make IM usable without rejecting all remote messages. Why won't this work: - Allow IMs if the sender's address is anywhere in the recipient's contact list, or in a separate IM-specific whitelist (see next point). - Have a separate IM whitelist that supports user@domain or @domain for special circumstances. - Automatically add any foreign outgoing-IM recipient either as a new contact in the sender's contacts (if an IM field is added) or in the separate IM whitelist, so return IM from the same address is guaranteed. - Have a list of unconfirmed senders from the last N hours/days (after which they expire and are dropped), with a web-based interface... (clarification) notifications of these requests would NOT push through to the Google user's IM interface. - Optionally reply to unknown senders: "You are not a confirmed sender of this recipient. Contact recip OOB to ensure future delivery." - Optionally add an IM field to google contacts, for instances where a remote address doesn't function as an email address.
- enjo 14y ago
  The requests themselves are spam. In the last couple of months I was seeing an increasing frequency in "lisaxxxhotone wants to chat with you" requests. I always ignore them..but it's a very annoying problem. You can simply ask for user confirmation, you're bothering me about something I really don't want to deal with.
  - deleted 14y ago
    [deleted]
- endtime 14y ago
  I was responding generally to OP's general statement. I don't work on Gchat spam, and don't have any particular insight into their problem.

by endtime 14y ago

harshreality 14y ago

I thought SOP for mitigating IM spam was to require user confirmation before delivering the suspect IMs? Google doesn't have to perfectly solve the spam identification problem in order to make IM usable without rejecting all remote messages. Why won't this work: - Allow IMs if the sender's address is anywhere in the recipient's contact list, or in a separate IM-specific whitelist (see next point). - Have a separate IM whitelist that supports user@domain or @domain for special circumstances. - Automatically add any foreign outgoing-IM recipient either as a new contact in the sender's contacts (if an IM field is added) or in the separate IM whitelist, so return IM from the same address is guaranteed. - Have a list of unconfirmed senders from the last N hours/days (after which they expire and are dropped), with a web-based interface... (clarification) notifications of these requests would NOT push through to the Google user's IM interface. - Optionally reply to unknown senders: "You are not a confirmed sender of this recipient. Contact recip OOB to ensure future delivery." - Optionally add an IM field to google contacts, for instances where a remote address doesn't function as an email address.

enjo 14y ago
The requests themselves are spam. In the last couple of months I was seeing an increasing frequency in "lisaxxxhotone wants to chat with you" requests. I always ignore them..but it's a very annoying problem. You can simply ask for user confirmation, you're bothering me about something I really don't want to deal with.
- deleted 14y ago
  [deleted]
endtime 14y ago
I was responding generally to OP's general statement. I don't work on Gchat spam, and don't have any particular insight into their problem.