-
Notifications
You must be signed in to change notification settings - Fork 6
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
authenticated site support #2
Comments
How should this work? Feedability can only fetch articles that are available to you anyways. |
Well, assume a subscription. But beyond that, I really don't know; just thought I'd ask. |
Ahh okay now I understand what you meant. It depends on the way the authentication is handled. I guess most sites would use some kind of cookie session management, the easiest solution would be to just use the existing cookie jar of the browser (like firefoxs cookies.sqlite). That way feedability should be able to see the articles. The more difficult way would be to actually implement the login procedure itself, so the user just provides the login credentials in the settings. However, since I don't own an account, the latter would require someone with an subscription providing me with information in order for me to implement a specific login procedure. |
Yes, I think they typically use cookies. I was trying to figure out how to implement login of, for example, the new york times, using https://github.com/jnunemaker/httparty (mechanize can do this as well) but couldn't figure out how. |
I've just added firefox 3/4 cookie support, it is now possible to use the cookies from a firefox profile in feedability. If you are (in firefox) signed-in a news site with subscriptions, and you configure the For more detailed documentation on how to setup the new cookies configuration options: https://github.com/4poc/feedability/wiki/Settings (section cookies) |
Not sure how hard this would be, but it'd be nice if feedability could grab content behind paywalls (say the Wall Street Journal, or soon again, the New York Times).
The text was updated successfully, but these errors were encountered: