Unsubscribing without the hub.callback

Unsubscribing without the hub.callback

We love getting feedback from our customers on our API and improve that API to match their needs and comments.

Most recently, one of our new customers indicated that asking for both hub.topic and hub.callback was redundant when removing a feed from their subscription list. This is true… if and only if the user has a single subscription to that topic.

So, starting today, it is optional to submit the hub.callback when you unsubscribe from a feed, as long as you have a single subscription to that feed, obviously.

Of course, this change is perfectly downward compatible and compatible with the PubSubHubbub protocol as well if you use a library that implements it.

What else would you change in our API to make it easier to use?

Liked this post? Read the archive or

On the same topic, check json pubsubhubbub notifications, http raw body and top feeds list.

Previously, on the Superfeedr blog: DNS Optimizations with Unbound.