Open GoogleCodeExporter opened 8 years ago
[deleted comment]
I couldnt reproduce the issue with my username - it displays everything
normally unless I disable specifically some sharing options, but I believe YT/G
may start more and more requiring logins as you describe.
Before going further, please verify your sharing settings.
http://www.youtube.com/account_sharing
Some features could be disabled for public sharing there. Enable everything and
try again.
-------------------------
If this is not the case, could you check what I did here
http://code.google.com/p/media-translate/issues/detail?id=66
and try identical user-agent replacement for test, say if you have wget on your
pc or the one in media player.
Just check how to use the WGET command line parameters and save outputs of
links you reported with your username without and with modified user agent
emulation.
If the one with modified agent outputs your lists, we can make some fix.
If not ... maybe some JS and smart script will be needed to maintain full
logins in future.
Regards
Original comment by lorolo...@gmail.com
on 10 Jan 2012 at 4:16
Thank you. I checked off the corresponding account sharing options for
favorites and subscriptions (in Youtube section) and the issue has resolved.
However user-agent replacement like in the issue 66 didn't resolve my issue
before.
Example of wget output wihout user agent emulation:
Connecting to gdata.youtube.com[209.85.148.118]:80
wget: server returned error 403: HTTP/1.1 403 Forbidden
I couldn't emulate user agent in this version of wget.
Original comment by andr...@gmail.com
on 12 Jan 2012 at 1:55
Yes, the stuff has nothing to do with issue 66.
If you "disable" some sharing features, the correspondent links with <username>
will not be accessible anymore by others, including mediaplayer "client" (msdl,
wget, main RSS engine, etc) unless they support modern browser's login
mechanism (js/cookies ...)
I think Serge is working already on javascript handling (a binary was added to
repository).
Hopefully, such web logins with password would be possible in the future.
Original comment by lorolo...@gmail.com
on 12 Jan 2012 at 2:44
Original issue reported on code.google.com by
andr...@gmail.com
on 7 Jan 2012 at 9:34