You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As explained in #83 (comment), 55d4d23 made it impossible to download secret Pinterest boards since those require authentication. The current error goes like this
> gallery-dl https://pinterest.com/user/SECRET/
[pinterest][error] NotFoundError: Requested board could not be found
Even though the board, in fact, exists.
Related to authentication, here's what I've found after digging into php-interest-bot's source.
Default headers are similar to the ones used in this project: link
When building the request, setTokenFromCookies is called: link
Use php-interest-bot's authentication approach. I don't know if there are similar implementations in this library, still.
Bring back the code removed in 55d4d23 as an alternative back-end, but this time using a custom user token. i.e. the current implementation would stay, but it could switch to the old one if the user supplies a token or the board is not found.
The text was updated successfully, but these errors were encountered:
resolritter
changed the title
[Pinterest] Allow for downloading secret boards
Pinterest - Allow for downloading secret boards
Oct 10, 2020
"username" and "field_set_keys" follows this and this.
And yes, the token is valid since I'm getting it from the browser. It could be missing a cookie somewhere... Have to dig more into the PHP source I guess?
As explained in #83 (comment), 55d4d23 made it impossible to download secret Pinterest boards since those require authentication. The current error goes like this
Even though the board, in fact, exists.
Related to authentication, here's what I've found after digging into php-interest-bot's source.
Default headers are similar to the ones used in this project: link
When building the request,
setTokenFromCookies
is called: linkAnd here is
setTokenFromCookies
: linkFinally, the token is included in the headers: link
As for logging in and getting the token: 1, 2, 3
Currently I see two implementation paths
The text was updated successfully, but these errors were encountered: