In an effort to protect its platform from spam and abuse, Twitter today unveiled a number of changes to the way developers will request and obtain access to Twitter's APIs. First, Twitter is requiring that all requests for access to the APIs go through a new developer account application process.
- Articles (9)
- APIs (48)
- Mashups (4)
- SDKs (17)
- Libraries (1)
- Sample Source Code (7)
- Followers (0)
- Developers (4)
The following is a list of ProgrammableWeb articles that matched your search term. On an nearly 24/7 basis, ProgrammableWeb publishes new articles ranging from news to opinion to tutorials for both developers and API providers. All of our articles are categorized in such a way that you can find your way to related articles, APIs, SDKs, Libraries, Frameworks, Tutorials and Sample Source Code. If you have an interest in contributing any of the aforementioned content to ProgrammableWeb, be sure to read our guidelines for such contributions.
Developers who are still using the Google reCAPTCHA v1 API need to switch to the reCAPTCHA v2 API as the v1 API will shut down in March 2018. The service uses machine learning and its advanced risk analysis engine to figure out if users completing forms and other actions are humans or bots.
YouMail launched its Spam Risk API. YouMail uses algorithms to analyze a database of hundreds of millions of phone numbers to determine the likelihood a particular phone number is spam. Historical call patterns and crowdsourced data are combined to determine an OK, caution, or danger designation.
The Death By CAPTCHA API is one of three CAPTCHA beating APIs posted to our index in just the last week. After taking a look at them I can say that they are just as seedy and sketchy as you would imagine. Even so, I don't see these services going away anytime soon. The existence of super cheap CAPTCHA beating systems begs the question, how effective is the visual CAPTCHA today?
There's nothing more frustrating for the serious blogger than having to constantly deal with an overload of destructive spam. Many are rooting for the technical teams who will win the war and see spam banished forever. TypePad AntiSpam has this very vision and the TypePad AntiSpam API to support it.
No-one likes a spammer, so 'high fives' for the development of more spam-obliterating solutions. Be it blogs, wikis, guestbooks or discussion boards, all have been the victims of spammers' endeavors to increase their search engine ranking. Comments are automatically posted in their dozens on multiple sites, and the process of manually deleting each of these is becoming increasingly tiresome. Comment SPAM Wiper (CSW) and it's SpamWipe API are designed to automatically protect a site from spam comments, posts, track-backs, ping-backs and the like. Hooray!
If you run a website, like many of our readers, and you have an account system, you probably have problems with spam. One of the main sources of spam is users who register using disposable e-mail addresses. These can be generated by spammers programatically, using services like the Guerilla Mail API I covered previously, and used to make tons of accounts to try to get blog spam through. If this is a problem for you, the DEA Filter API can help.
If you are writing a telephony system using the Twilio API, Tropo API, or Cloudvox API, you can interface with YouCantCall.us to shield your system from phone spam. Now wouldn’t it be great if the YouCantCall.us API could be integrated into a “block” button that appeared on standard phones?