5 ms·
With the dependence on Superfeedr, this seems like it’d be difficult to scale and provide as a service.
by ghostinthebash 4y ago
With the dependence on Superfeedr, this seems like it’d be difficult to scale and provide as a service.
- PaulHoule 4y agoHard to say. Right now Superfeedr feels like a great value (less than $5/month) with the caveat about low-volume feeds. I think the API to add and remove feeds is silly (wet not dry) but getting updates through a webhook is nice. If I had a lot of people using it I wouldn't mind a $500/month Superfeedr bill and I know their pricing goes down if I have a lot of feeds and I'm sure they'd love to talk if I was a bigger customer -- but there are all the agency problems that come up when one business depends on another business. That said, web crawlers, scanners, and things like that were a subject I was interested in in the aught's and the last thing I want to work on now and Superfeedr frees me up to focus on the models and UI now.
- kevincox 4y agoSuperfeedr also seems completely unmaintained since Medium bought them. The blog is dry, other feed-related projects are frozen, they still don't support newer WebSub standards and the offical Medium hub for Medium blogs doesn't send updates. I suspect that Medium doesn't care about feeds anymore now that they are big so they are doing just enough to keep the current service running. I wouldn't want to build a service on top of them. But I guess if it does shut down switching to polling youself wouldn't be the hardest thing to do.