Many people, us included, see the web being a complex operating system. A consequence of this is that we embrace the Unix philosophy of small components loosely coupled using streams for data in and out.
With that in mind, for subscribers, Superfeedr is mostly a piece of code which takes a feed URL as input, and a webhook URL as output to create subscriptions which triggers notifications.
Now, if you go even further, there are cases where the user subscribes to a feed, but actually does not care about the notifications at all, because they just want to retrieve it from us. What happens to the callback url (webhook) then?
On Unix systems, when you have an output that you want to ignore, your typically redirect it to the null device:
The null device is typically used for disposing of unwanted output streams of a process, or as a convenient empty file for input streams. This is usually done by redirection.
For example, if you wanted to fetch the home page of this blog to just get latency and bandwidth you would do something like2:
$ curl "http://blog.superfeedr.com/" > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 4871 100 4871 0 0 20901 0 --:--:-- --:--:-- --:--:-- 20905
The last part of this command tells the OS to send the content it’s downloading to
/dev/null/ which is another way to tell “just ignore it!”.
So, using an identical approach, if you need to subscribe to a feed with Superfeedr but you actually do not care about the notifications, you can subscribe using this webhook URL:
https://push.superfeedr.com/dev/null which is Superfeedr’s null device!