Almost perfect Rated 5 out of 5 stars
Really awesome work. It works perfectly & flexible enough to add newer country TLDs : D
There are 2 domains that Google forces TLD according to IP location. One is blogspot.com and the other is google.com.
Please (pleaaassseee) add google.com as well.
I think that is a good idea. The procedure is the same for google.com so it makes sense to add it too and allow the user to toggle what domains to use in the options. I'll do it when I have some time.
Support for *.blogspot.it domain Rated 5 out of 5 stars
Could you please add this feature for the *.blogspot.it (Italian) domain? ThxThis review is for a previous version of the add-on (2.1-signed.1-signed).
There is a new version waiting for approval with .it domain. You can try it here: https://addons.mozilla.org/en-US/firefox/addon/no-more-blogger-redirect/versions/
interesting but does not work when used together with some essential privacy add-ons Rated 1 out of 5 stars
this add-on does not work for me. i tested it with the url that the author supplied in the add-on's announcement. the add-on may conflict with other add-ons i use (noscript,requestpolicy,ghostery). i hope the developer can look into this, since i would like to see a working solution to this redirect nonsense
thx for looking into the cited issues.
the new version makes no difference, even when disabling requestpolicy, noscript and ghostery.
I know it has a problematic reputation but you can opt out of the tracking .
I'm also using adblock but there are some pages where adblock is not enough and ghostery quiet nicely cleans what adblock does not get .
First update to version 2 of this addon if you have not done so (it is waiting for mozilla's approval): https://addons.mozilla.org/en-US/firefox/addon/no-more-blogger-redirect/versions/
I've looked at your problem and there is not much I can do. The security these addons provide is based on breaking websites and other addons' functionality. The workaround I can recommend you is: update to RequestPolicy 1.0 ( https://www.requestpolicy.com/1.0.html ). It looks that it has better whitelists, and at least with the default configuration it doesn't seem to bother my addon.
The problem with noscript is: the FIRST time you go to a website you will not get unredirected (but you will the rest until you clear the cookies). It looks like the functionality called ABE from noscript is blocking my addon from redirecting the page. You can disable ABE (in noscript's advanced options). I will ask Maone if he can provide a rule for ABE to whitelist what my addon does (it looks like he's providing rules to whitelist other addons that noscript is breaking: http://noscript.net/faq#qa8_3 )
Update: This platform is not ideal to communicate. If you want me to look into the problem send me a message to dyeray at gmail. Send me all the information you can about the problem, and also start disabling addons until it starts working to see what addon is exactly conflicting. If it doesn't work with all the addons disabled try with a new firefox profile. I think you are probably blocking redirects with some other addon/option, if that is not the case let's see if I can reproduce the problem somehow.