No Script- Our only hope for the future

[Tom T.]

after 23 years on IE

Yeah, sure…
What does this have to do with Noscript? I believe that this thread belongs rather to the "Web Tech" subforum.

Or the dustbin. Maybe better to let this one just fade away.

Guess I saw the glass as half-full, and was grateful for the kind words that OP gave to NoScript. Silly me.

Silly you. One of us has to see the glass as half empty.

@ dhouwn and Alan Baxter:

Such negativity! .... you catch more flies with honey than vinegar, and solve more problems, too.
Cheers.

[CrlyWrly]

Apologies for re-activating an old thread but thought that might be less confusing than starting a new one.

Yoono has reintroduced ads after dropping them for a while. They are no longer "in the stream" but present as the first post in a stream. I have tried "hovering" with mouse over the ad but I can't seem to get any clues to the target url. The one I see now contains a Stumble Upon shorturl and there is text stating "Ads by 140 Proof".

The ads just appeared after I restarted Firefox though Yoono has been rolling them out to users for a while.

Using a Mac.

Any ideas how to block these new Yoono ads would be much appreciated!

Best wishes,

Liz

[GµårÐïåñ]

I don't have an account with them and not interested in making one, so I can't help you directly. However, I can give you some tips if you are savvy enough to figure out what to do, ok? Load it in a browser, using Fx is fine, but you'll need DOM inspector (or view source if you know how to wade through it all) or you can use Chrome and use their inspect element and find out the source of that item.

Now if its a location (URL or resource with a domain) then you can write up a ABE rule to just nuke it and be done with it. If its not and somehow has been embedded in a manner that would break usability if you do, then if you happen to use ABP you can narrow down the rule to more precisely (and probably easier) to nuke it. Even if you can't nuke it completely by blocking the feed or source of it, you might be able to at least hide it or visual clarity.

If you have an account that you don't mind sharing for testing purposes, you can send me the info through PM, or to Giorgio and we can try and log into it and analyze the code and give you a resolution. Good luck.

[GµårÐïåñ]

Giorgio,

Are you aware of this statement by Yoono and is it true and should it be there?

Q: I have lots of Firefox Add-Ons already installed - will Yoono conflict with any of them?

We've tested Yoono with many other popular add-ons but of course there are lots of add-ons for Firefox so it is impossible to test them all. The only conflict we are currently aware of is with the "NoScript" add-on which causes the Yoono Share feature to not work correctly. If you discover other incompatibilities, please let us know so that we may try to find a solution to the issue.

*emphasis added by me

[Giorgio Maone]

Are you aware of this statement by Yoono and is it true and should it be there?

1. Not aware
2. No idea
3. Since nobody at Yoono ever contacted me about compatibility issues (nor I had user reports about them, on the other hand) I don't believe is very nice from them, but frankly I will start caring only as soon as some NoScript user actually complaints about Yoono issue.

[GµårÐïåñ]

1. Not aware
2. No idea
3. Since nobody at Yoono ever contacted me about compatibility issues (nor I had user reports about them, on the other hand) I don't believe is very nice from them, but frankly I will start caring only as soon as some NoScript user actually complaints about Yoono issue.

Ok, that's what I figured. It just bothers me that we may not be hearing complaints from the users because of this statement and they assume, oh well just got to live with it and since they never told you or contacted you about it, they are creating misinformation. I think its unprofessional to say the least to throw another developer's product under the bus without any attempt to confirm, resolve or even notify them about it. For all we know they had a problem with their code causing the issue and they used NoScript as a scapegoat in this matter, again bothers me. But hey, your baby, your call, I will respect that. Just felt it was worth you knowing since I investigated the previous poster's issue on their site and found this in the FAQ section. At least we are now aware they are claiming this.

[CrlyWrly]

GµårÐïåñ - many apologies for not replying and thanking you before now! I must not have ticked to receive notification of replies.

I am not sure if this is still an issue, ie. the adverts. I got fed up with FF running so slowly so have been using SeaMonkey and Yoono does not work with SeaMonkey.

Just yesterday I tried FF again and it was faster so I will use it again for a while and will try what you suggested if the adverts are still there.

I noticed the other messages above and agree that it is rather rude of Yoono to attribute a problem to NoScript but not bother to get in touch.

Thank you again for your help,

Best wishes,
Liz

[Tom T.]

One possible work-around would be to block that displayed URL, and also www dot 140proof.com (that site exists -- just checked) in the HOSTS file.

Editing HOSTS file in Mac

Something like:

Code: Select all

0.0.0.0  (the shorturl.com)
0.0.0.0  www.140proof.com

... and any other sources that you can find.

Please note that the first entry in the HOSTS file must never be altered:

Code: Select all

127.0.0.1  localhost

Just a thought.

[GµårÐïåñ]

GµårÐïåñ - many apologies for not replying and thanking you before now! I must not have ticked to receive notification of replies.

I am not sure if this is still an issue, ie. the adverts. I got fed up with FF running so slowly so have been using SeaMonkey and Yoono does not work with SeaMonkey.

Just yesterday I tried FF again and it was faster so I will use it again for a while and will try what you suggested if the adverts are still there.

I noticed the other messages above and agree that it is rather rude of Yoono to attribute a problem to NoScript but not bother to get in touch.

Thank you again for your help,

Best wishes,
Liz

Liz, there have been many changes, so I would say if you are coming back to Fx, try it and run the latest NS and see how it goes but the original issue per se is no longer an issue IIRC. Good to have you back and good luck.