Extractor problem about fullyfeedly HOT 5 OPEN

That's another possibility, but this change would significantly affect the permissions of this extension. See my comment on #38.

If we really want to use a built-in parser, I would prefer to create a new extension and avoid disruption for existing users.

from fullyfeedly.

Thanks for the inputs!
I haven't checked boilerpipe in a while, but I agree it could be removed if not working properly.

When we do that, we should make sure users are automatically/transparently moved to a different extractor.

from fullyfeedly.

Thanks for raising this issue, I was not aware of the problem with boilerpipe.
I suspect that by deploying this code on a different cloud service we will run into the same quota limits, unless we decide to pay for increased capacity.
On the other hand, I am happy to consider other free APIs in case there are new solutions released after I created this extension.

from fullyfeedly.

What if add a built-in parser as another choice? Like: https://github.com/ndaidong/article-parser, https://github.com/Tjatse/node-readability & https://github.com/mozilla/readability, and maybe an option to support setting customized Mercury/Boilerpipe service url for self-hosted service could help tolerate the quota issue. (Don't know if it's easy to setup one, yet.)

from fullyfeedly.

Looks like the GitHub repo of boilerpipe is no longer under maintenance, the issues and pull requests are just stale, and the web version started to return 500 error for a while, also saw a bunch of tweets asking about boilerpipe but got no response. Maybe should just consider to remove it for now?

from fullyfeedly.