Youtube, can't respond to comments?

[huldu]

I've been having a problem since yesterday on youtube, I can't respond to comments at all. The first problem was adblock plus, which the solution was to disable fanboy's social blocking list, doing that allowed to me at least see the comments. Then next problem came up, I wasn't able to post or respond to comments. The only way for me to do this was to disable noscript entirely in the browser and restart it. It didn't help just by allowing everything on youtube.

Anyone have a solution to this problem? For now I have to run chrome just for youtube, which seems a little bit too excessive.

[Giorgio Maone]

It's working for me. Is google.com allowed?

[Giorgio Maone]

BTW, if the problem is about initial posting, rather than replying (seen in a different thread), please check latest development build 2.6.8.5rc2, thank you.

[huldu]

That release you posted works, thanks a ton!

[joesi]

Huh that's strange. I wonder why a newer version would work.

Hope you don't mind the thread consolidation/hijack:

I had very similar issue but my issue is due to ABE. At first I was very confused because Enabling scripts globally via NoScript still didn't solve the problem (because it doesn't stop ABE from working, but disabling the plugin does of course).

My problem is with the following ABE script:

Code: Select all

Site .google.com .google.ca
Accept from .google.ca .google.com
Deny INCLUSION(SCRIPT, OBJ, SUBDOC)

I've tried doing all sorts of things such as adding " gstatic.com youtube-nocookie.com googlevideo.com ytimg.com youtube.com" to the accept from list, as well as "site youtube.com[/s]
D'oh forgot to add the . before youtube.com !! (I typed youtube.com instead of .youtube.com!)

Well FINALLY I fixed my problem, did it myself too, but man I really bamboozled myself in two ways.

So the recent incorporation of Google+ to youtube comments requires google script (or object or something) to run on youtube, meaning for the script I posted to only allow google on google pages, you'll need to add .youtube.com as well.

[joesi]

Wow so after all that I get another problem related to Firefox.
With "accept 3rd party cookies: never", you can't compose a comment or like/dislike comments.
You have to manually add an exception for .google.com

... so now my browser is accepting all cookies from Google regardless of where I am on the web!
WTF can I do about this? is there maybe an add-on that will allow 3rd party Google cookies only for Youtube?

I have the same issue with Disqus (doesn't work unless you allow 3rd party cookies).

[Thrawn]

You could write an ABE rule to strip cookies off requests going to Google unless they come from YouTube.

In your USER ruleset:

Code: Select all

Site .google.com
Accept from .google.com .youtube.com
Anon

[joesi]

Thanks. I did do that and I was happy with that, but either I never went to a Google groups page much since then, or they relatively recently (last month or two) changed Google groups. I'm having problem with Google Groups now.

For some reason I cannot access Google Groups pages when that rule is enabled. Any ideas?
As far as I saw the only cookies came from google.com domains, and gstatic.com and google.com are the only listed domains available to control in noscript's menu. I don't know the details of what else anon does and how it could possibly cause a problem (namely when .google.com is accepted and nothing else is appearing)

(FYI I did add .gstatic.com to the accept list just in case and it didn't do anything)

I would like to know how to fix this sort of problem myself in case it somehow turns up again somewhere, so insight into the problem debug/resolution methodology, or just how and why this has happened would be nice.

[Thrawn]

There should be messages from ABE in the Browser Console (Ctrl+Shift+J) when this occurs. Can you copy and paste them here?

If the spam filter blocks them, you can send them to a moderator via private message.

[joesi]

Ohh... thanks. I should have been a bit more thorough with my rules I guess.

A couple things:
1. before checking the console, I noticed that the Google Groups page wouldn't load when it was from a Google search page; It would work otherwise. That should have tipped me off

2. Because of that it makes perfect sense that the console showed the localized country Google domain (localized top-level domain instead of ".com") as the triggering domain. So I just need to add that into the accept list and I will be able to access Google Groups from a Google search.

I do dislike what Google is doing though. Seems like it would be tracking when I visit any of their own sites from Google and [accidently/intentionally] deny access if that information isn't provided. It doesn't seem to make any sense. Why does it need to do that when it could presumably do that just by following the visits of the PC footprint and/or IP address?

[Thrawn]

it makes perfect sense that the console showed the localized country Google domain (localized top-level domain instead of ".com") as the triggering domain. So I just need to add that into the accept list and I will be able to access Google Groups from a Google search.

Yep, that should work. Actually, I should have thought of it when I first suggested the rule. Glad you found a solution .

I do dislike what Google is doing though. Seems like it would be tracking when I visit any of their own sites from Google and [accidently/intentionally] deny access if that information isn't provided.

No, that's not what they're doing. Cookies for eg Google Groups will be sent whenever you visit Google Groups, regardless of where you came from. It was the ABE rule that changed things so your origin matters.

It doesn't seem to make any sense. Why does it need to do that when it could presumably do that just by following the visits of the PC footprint and/or IP address?

Ack, let's not suggest that Google start fingerprinting our browsers! There's plenty of tracking going on without that, thanks. At least cookie-based and script-based tracking are easy to block.

And by the way, cookies are a much simpler, easier, and more effective way of tracking a session than browser fingerprinting, and tracking via IP address is useless when someone is behind a (corporate/Tor/whatever) proxy.