yt-sanegrid
yt-sanegrid copied to clipboard
daviddeutsch
App returning private subscriptions incorrectly.
Up until today, I have been able to use the app just fine. Just today it started returning an error that my subscriptions are now private. I have checked and unchecked the box in my privacy settings but nothing seems to help it. What can I do?
I can confirm this error. The error displayed is the following:
Subscription List Private
The account that you entered has their
subscription list private. If you own this
account, you can go to your privacy settings
page at
https://www.youtube.com/account_privacy and
make it public.
However my subscriptions are not set to private.
It seems every API call to the old YouTube V2 API returns a "403 Forbidden".
Same here, also if I try to click on a video link it just reloads into the enter your username page. I depend on this tool to see my subscriptions because youtube is awful. It's worked great for a long time since google killed the subscription grid.
I'm having the same problem: SaneGrid momentarily displays the previously updated videos, but then reverts to the message chhe quoted, above. My subscriptions are definitely public. It began right after there was a nearly day-long 'outage' when my YouTube Subscriptions page wasn't updating at all. I turned to SaneGrid as a 'life raft' during this period. When YouTube started updating again, SaneGrid went down. I suspect that a change was made at YouTube that stymied SaneGrid, but I'm only guessing.
Getting the same issue now, you guys. Very weird. It might be another one of these temporary API breakdowns. I will investigate.
The page is working perfectly find for me. Must be a thing that only effects some people. (or yt fixed it?)
As of 5:00 PM PST, this issue is affecting me as well - it seems like a lot of things are returning either 404 or 403.
@FakeFurball Me too, I also experience similar issues on YT itself (there are a couple of similar things popping up on r/youtube - people not being able to use their YT subscriber feed in general) and I also have a bunch of other google servers behaving weirdly.
My search so far hasn't come up with anything proper, so I have a strong hunch this is their servers glitching out. I hope it's not an error that leaves us with permanent problems.
Please see the other topic for updates - the v2 API has been completely deprecated. I'm working on a fix right now. Will probably push a few more changes in there while I'm at it.
Seems like the API Access is bonked for now, always getting a 403 - I even submitted payment details and everything... Let's wait an hour or two and see whether it clears.
Bit worried about that billing stuff. I mean - you get 50M credits for free, but when a reddit spike hits, that might mean a few thousand users coming in and trying it out... I will have to check what the usage patterns are.
Also: This means that I can soon make use of all those neat API v3 features... Watch Later etc. Weee!