Minor update (2) for Vivaldi 2.4
because I'm blocked.
Strange – why blocked? Do you use a VPN or other proxy?
@gwen-dragon: Like I said in the beginning: "the chromium update causes my companies proxy to block my browser"
"the chromium update causes my companies proxy to block my browser"
Bad for you to have such "security officers".
But you can change the user-agent in a command line paramater of a desktop shortcut:
vivaldi --user-agent=" Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36"
and start Vivaldi wit a faked UA.
Now you should be able to install the extension.
@gwen-dragon: that's actually a very good tip, I'll try that. Thanks.
Works like a charm.
Pesala last edited by
lord-chaos last edited by lord-chaos
@Ayespy a year is plenty of time. It's not like I am impatient.
@lord-chaos Yeah, not really.
The time scale of development and bug-fixing on a large project with a small team is not what you think it is, and the way developers prioritize bugs (and why, when and where they arise and how to address them) is not what you think it is.
My favorite browser deficiency that I have always agitated for, and wanted addressed from the beginning, is now over four years old. And I have the ear of the developers. I understand why this is, and I get that users on the outside will not understand. But factually, the developers' priorities are not misplaced. They are working hard, getting a lot done and slaying up to 50 bugs a day. I decline to criticize them for not yet addressing the matter that, to me, "obviously" deserves priority.
rseiler last edited by
OK, what about user agent issues for various sites (long-since reported)? There seems to be a resistance to doing that in at least some cases, when it wouldn't even require a new build to do. Opera was all over that kind of thing via one simple text file periodically pushed out.
Yes, we can workaround it, but that's a solution for the .1% in the know.
@rseiler In many cases, user will have to address this for themselves, in particular cases.
I happens I do not, ever, have UA issues on the web. I guess I don't have occasion to go to sites that do sniffing. (well, over the years there were two tax-payment sites that sniffed)
UA issues have to be hard-coded in, site-by-site. To the degree that Vivaldi is not recorded as visiting a site (UA spoofing), browser revenue is reduced. In the extreme, if UA spoofing were universal, it would be clear to the publishers of browser use statistics that no one uses Vivaldi on the internet, and all income would cease. Vivaldi would close its doors.
We'd like to see Vivaldi continue in operation, no? At some point, we'd actually like to see the company operating in the black. So the solution is not UA spoofing, but getting sites to stop blocking Vivaldi.
rogerconductor last edited by
The update did not respect my settings (tabs behaviour, home page, start page, and possibly more I haven't hit yet), but overwrote them. Please can this be corected for future updates - it is extremely annoying to have to go through and change again.
@rogerconductor You are the first user I have seen who had this problem. It is not a normal part of the Vivaldi update routine. Could you say what your operating system is? (We did have a user with a similar situation, due to a Windows setting).