turns out this extension is injecting scripts into pages, and breaks all cloudflare protected sites

Unfortunately I have discovered that the current version of this add-on triggers the Cloudflare 'Captcha of Death' denying access to hundreds of web-sites and as such I have deactivated it.

Super confusing interface. Choosing different user agents causes them to be smooshed onto the default user agent. Doesn't appear to actually work consistently at all.

It was last updated 2 years ago; looks like abandonware.

where is [Apply only this 'website.com' ] ??

not every one wants to use container??

so unusable....

you couldn't have made it any more confusing. i have no idea how to use this shit. this is so sad, i wish user interfaces were real.

Not working. Have watched the YT video and have tested both the white list and i've tried to use it on ALL websites and it isn't doing anything.

Useless. Whitelist doesn't work. If I put YouTube in the Whitelist, and set the add-on to use Whitelist, the icon is still off when using YouTube. It seems to maybe help when manually turning it on, but ain't no body got time fo that.

Abandonware

Doesn't work

Absolute trash addon, could not do the one thing I asked it to do which was TO CHANGE MY USER AGENT FOR A SINGLE WEBPAGE

Doesn't work anymore, no updates in sight to fix this.

I recently started testing this extension. The last version "improved" the extension so much that it stopped working. It doesn't matter what user-agent it shows - browser tests always return the original one.

I started to get blocked by websites as a bot while using this addon. Do not recommend.

This doesn't work at all, with any configuration, and hasn't seen an update in over a year. Version 0.6.1.1 is available on other extension stores, and I would package and install this myself, but there are no releases on GitHub.

Why it's so complicated to JUST SET USER AGENT TO SPECIFIC SITE?

Graphical glitches while add-on was installed and link addresses were showing up in the bottom corner without the /s? Not sure what kind of bug this is? Removed the add-on and everything is fine now. Why would an add-on that is used to spoof the User-Agent mess with graphical and character memory?