Introduction

Feedr is a service for parsing RSS and Atom feeds. You just pass the URL
of an RSS/Atom feed and the service will return the parsed feed as JSON.
Feedr was originally designed as a drop-in replacement for Google's Feed
API, which has been deprecated and taken offline on December 15th, 2016.

Usage

Feedr has to be requested with the query parameterqthat contains the URL of the to-be-parsed RSS/Atom feed. An example request looks like this:

curl 'http://www.feedrapp.info/?q=http://www.ebaytechblog.com/feed/'

The result will look like this (please note that the output is slightly truncated):

Introduction

\n

Algorithms based on machine learning, deep learning, and AI are in the news these days. Evaluating the quality of these algorithms is usually done using human judgment. For example, if an algorithm claims to detect whether an image contains a pet, the claim can be checked by selecting a sample of images, using human judges to detect if there is a pet, and then comparing this to the results to the algorithm. This post discusses a pitfall in using human judgment that has been mostly overlooked until now.

\n

In real life, human judges are imperfect. This is especially true if the judges are crowdsourced. This is not a new observation. Many proposals to process raw judgment scores and improve their accuracy have been made. They almost always involve having multiple judges score each item and combining the scores in some fashion. The simplest (and probably most common) method of combination is majority vote: for example, if the judges are rating yes/no (for example, is there a pet), you could report the rating given by the majority of the judges.

Options

In addition to theqparameter, Feedr supports other optional parameters.

Parameter

Description

callback

Wraps the answer in a function call, which makes it compatible to JSONP calls

num

Number of entries to load

Hosting

Since the publicly available version of Feedr can be used by everybody,
it might be unstable from time to time. If this is unacceptable for you,
you can run your own dedicated version of the API yourself. The easiest
way to get started is probably via Heroku:

Caching

Since v1.5.0 every requested RSS feed is cached for 30 minutes.
This value might be configurable in the future. Pull requests are welcome.
The change was introduced because the app received too much traffic to function
fine on Heroku – and because it just makes sense.