I have a web app that generates RSS feeds. I would like to offer users the ability to subscribe to these RSS feeds by email.
I know I can use Feedburner to manually burn my feeds and offer email subscriptions. The problem is I offer hundreds of RSS feeds and don’t want to manually burn a feed just for this one feature.
Does anyone know of a service or API (preferably free) that allows you to create an RSS feed to email sign up on the fly? Any help is much appreciated. Thanks.
-Ace
You can use the Feedburner Managment API to programatically burn your feeds - and then enable email subscription.
Related
I get this user agent Feedfetcher-Google; (+http://www.google.com/feedfetcher.html; 1 subscribers; feed-id=17582163705065100568) in my logs coming from a google domain even if there is no way you could read rss feeds through google and still I see there is 1 subscriber.
Even though the Google Feed API has been deprecated, it's still possible that some people are subscribed to your feed(s) thru that? Also, don't forget that Google uses RSS as a discovery mechanism for its search engine.
As far as I know, in order to get RSS in real time (i.e be pubsubhubbub subscriber) , the one who generates the RSS feed, must be a pubsubhubbub publisher, which means the RSS feed must include a tag which includes the HUB address.
However, there are lots of RSS feeds (published using RSS 2.0 only and not pubsubhubbub) which I can subscribe to via Feedly.
How is it possible?
Thanks,
Qwerty
So, Feedly does use PubSubHubbub, thru Superfeedr (and other hubs, such as Google's or Wordpress).
Fir the feeds which do not support PubSubHubbub, Feedly polls feeds at regular intervals. You may want to check this other question for more details.
Also, please note that Superfeedr can also be used as a "default hub" which works even for feeds which do not support PubSubHubbub.
I have a Drupal website, and I am currently using Feedburner, mainly to get statistics about the number of subscribers and methods of subscriptions.
However "burning" my feed is complicated, it's hard to restrict people from accessing the original feed, and it only does one feed, as opposed to various tag feeds, user feeds, etc.
How would you have Drupal collect and present feed access and subscription satistics?
Are you using the Feedburner module? It will do redirection from the original feed URL to the FeedBurner feed URL (FeedBurner itself will still have access to the original). You can do it for multiple feeds, though I think you still have to add those manually, which will be cumbersome for all the various tag feeds.
We are thinking to implement RSS feeds at the company i work with as a form of banking /transaction alerts to users.
Does anyone know if this has been done in e-banking apps? Anyone knows any possible security threats? Any articles, haven't found that much on the net.
Possible threat: How do you control access to the feeds? Usual RSS feeds are unprotected; you could have a RSS feed over HTTPS + Basic auth, but is it sufficient for your security guidelines (since it's a bank, I doubt it)? Even if it passed muster, are you sure you want to have two different access paths into the system? More specific ways of authorization will break most RSS readers (as they don't have significant support for more complex authorization schemes).
Also, some people use web-based readers (Google Reader); how do they authorize? Once you allow a web-based RSS reader to spider your RSS feeds, how do you prevent it from sharing this content with other users?
Feedburner(http://feedburner.google.com) provides statistics about RSS feed of subscribers and reaches. This is interesting.
It is easy to understand that Feedburner can count visits (reaches) to a RSS feed. But, how does Feedburner get to know subscribers to a RSS feed.
In my understanding, each requests to RSS Feed URI is independent. There are no cookies or identity validation. So, how does feedburner know how many subscribers to a RSS feed?
The easy part is Google tell it the number of Google Readers, and so do the other Reader/Aggregators.
For individual users polling the RSS/Atom feed, there are http headers involved in the request, so users are tracked by IP address, and when behind proxies, a number of proxies include original IP in header, this helps sort between proxied sources.
Failing that you could read the FeedBurner help on that topic.
I wonder if it knows anything at all.
--- end sarcasm ---
Seriously, my sub numbers for my blog will jump from about 2k to about 3k at the drop of a hat.
Determining subscriber count is an inexact science at best.
It does rely on reporting from other services, and sometimes these services go down, or they change how they report.
Services like FeedBurner are actualy a proxy feed to your blog's feed. So when you use FeedBurner (or alike) users subscribe to a feed hosted on Google's servers that is fed from your feed.
Thusly people are really subscribing to the feed hosted by Google and they can then get statistics just as if you were visiting a site.