Google engineers find a way to filter robocalls the way Gmail filters spam


Recommended Posts

google_robocalls_large_verge_medium_landscape.png

The Federal Trade Commission just announced the three winners of its Robocall Challenge, a contest meant to crowdsource the solution to the robocall scourge that prompts more than 200,000 consumer complaints every month. The first-place award was split between two individuals, programmers Aaron Foss and Serdar Danis. The "technology achievement award," reserved for a submission affiliated with a large company, went to two Googlers, Daniel Klein and Dean Jackson.

"It's really up to the private sector now."

When complaining to the FTC, consumers often wondered why it wasn't possible to screen robocalls with the same effectiveness as Gmail screens spam. Klein and Jackson's solution is not unlike Google's email spam filter, which prompts users to report bogus messages. Their system allows users to instantly report originating phone numbers to an online database; on the other side, phones or external hardware automatically check the database every time a call comes in. It also includes a mechanism that blocks "spoofed" numbers, which obfuscate the true origin of the call, and weighs additional factors such as call volume, frequency, and inbound-to-outbound ratio.

Danis's first-place solution was similar to Google's. He suggested an external device (which could also be implemented as a mobile app or provider feature) that "autonomously compiles whitelisted, blacklisted and graylisted numbers databases." The system also detects whether the caller is using a spoofed number.

Foss's solution, Nomorobo, proposes to automatically hang up on robocallers. When a call comes in, Nomorobo uses conditional call forwarding ? a feature most phones already have ? to ring simultaneously for the recipient and Nomorobo. Nomorobo picks up first and hangs up on robocallers.

The initial response to the FTC's cry for help was not encouraging: many of the submissions were technologically thin, duplicative, or overly simplistic, and the entire endeavor seemed to attract a certain type of politically-engaged, stay-at-home crazy person. Stopping robocalls is a difficult problem, as technology has made it easy for spammers and scammers to mass-dial from around the world for pennies. However, the winning proposals offer some hope for those who want to enjoy an uninterrupted dinner.

The FTC received almost 800 submissions, which were judged based on functionality, viability, and ease of use. However, there is no guarantee that these solutions will ever go to market. "It's really up to the private sector now," said Charles Harwood, acting director of the Bureau of Consumer Protection.

Danis and the Googlers were not available for comment, but Foss, a veteran of multiple New York City startups, is committed to ending robocalls for good. He hadn't considered building a robocall blocker until the FTC announced its challenge in October. Now he has decided to use his $25,000 in prize money as seed funding while he looks for investors and partners in the telecom industry. He's hoping to cut deals with major carriers like AT&T as well as newer industry players like Twilio.

"I'm really hoping to circle the wagons and figure out the right way to launch this and get it into the hands of families and individuals as quickly as possible," he told The Verge.

http://youtu.be/JgQVZeIrbB0

http://www.theverge.com/2013/4/2/4174282/google-engineers-filter-robocalls-like-gmail-filters-spam-ftc

When complaining to the FTC, consumers often wondered why it wasn't possible to screen robocalls with the same effectiveness as Gmail screens spam. Klein and Jackson's solution is not unlike Google's email spam filter, which prompts users to report bogus messages. Their system allows users to instantly report originating phone numbers to an online database; on the other side, phones or external hardware automatically check the database every time a call comes in. It also includes a mechanism that blocks "spoofed" numbers, which obfuscate the true origin of the call, and weighs additional factors such as call volume, frequency, and inbound-to-outbound ratio.

I would have thought that was common sense but most phone companies wouldn't implement it because it hurts their bottom line and/or without charging for it.

Hell a lot of carriers and home phone companies still charge you for call blocking (though with most new phones you can get around that by just adding it to the phone's database).

"please enter 71" .... I see companies that make robocalling software implementing voice recognition software like ACD systems already use, and then using it to send the DTMF code required back....or maybe I should make that system and sell it to the robocall companies.

This topic is now closed to further replies.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!