Integration with Mercury Parser?

[jesse-troy]

I have noticed that the Mercury parser is pretty good at getting some content that Wallabag fails to get. An example of this would be newyorker.com.

Would it be possible to utilize the Mercury parser either within Wallabag or as an external service?

I'm not really a coder, so I don't know where to start work on this but I have an idea for how it could work. Could I have a container with Mercury running and Wallabag would send the URL to the Mercury container, which would return the full contents to be saved in Wallabag? This would just be an alternative to the built in fetcher.

[j0k3r]

This might be an idea.
Maybe we can define a setting to enable it as a fallback when the default parser can't retrieve the data.

But for example, Mercury parser can't handle paywalled content when you define your credentials in wallabag.
As Mercury parser can be either in a docker or in an AWS Lambda, we only need to define the url of the parser.

[tcitworld]

As Mercury parser can be either in a docker or in an AWS Lambda, we only need to define the url of the parser.

Also through CLI https://github.com/postlight/mercury-parser#the-command-line-parser