SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Oh and if you think this is all too complicated you could just use our alternative install script to install into your home directory with full desktop integration, plus uninstall and update support. If you want the stable rather than the snapshot just call the script with ‘-f’.
If I understand you correctly......you are suggesting that Vivaldi already provide a diff file for point updates
your term ....deltas.....can you confirm please?
your reply 315 does not IMHO show a delta but I could be wrong
Sorry then I have explained everything badly. I was trying to point out that a tar is not a requirement and indeed you could argue that we already provide a tar (just wrapped up inside a deb). I was also trying to make it clear that unpacking and starting Vivaldi (outside of a traditional install) also, already works.
And yes I am using the term delta for what you call a diff update.
Quote:
Originally Posted by Wikipedia
A delta update is an update that only requires the user to download the code that has changed, not the whole program.
To more clearly answer this part of your question. No, we do not currently provide delta updates on Linux (only windows). We have looked at various options to provide them, such as via snap packages but have not yet settled on what our preferred approach would be. At some point in the future however, it seems likely that we will offer something as we see the benefit.
Recently I started streaming through my cable provider, and Waterfox (classic) will not work for any streams. That is not my only complaint about Waterfox that has changed since I first used it, but I will spare everyone.
While I am still using Waterfox on my main laptop, Vivaldi will now be the only browser on my HTPC.
The only thing that is holding me back from going full blown Vivaldi, I would like to be able to audit the settings better, similar to how I can with about:config. I would like to be able to see all, exactly where and the ability to edit links to where Vivaldi is contacting.
The big change is its user agent now identifies Vivaldi as Chrome. Vivaldi claims they did this for compatibility reasons, but I've never had a problem when it ID-ed itself as Vivaldi. Being somewhat of a cynic I wonder whom is paying who for what.
The big change is its user agent now identifies Vivaldi as Chrome. Vivaldi claims they did this for compatibility reasons, but I've never had a problem when it ID-ed itself as Vivaldi. Being somewhat of a cynic I wonder whom is paying who for what.
I agree. I think that a better option would be to keep the Vivaldi string, but let the user set/change it for specific sites.
If that doesn't answer the question for you, just ask Ruari here.
For the record, I don't use Vivaldi on Linux or BSD. I sometimes (about 1/10 of my browser time) use Vivaldi on Windows 10 at work as a Chromium-based alternative to Chrome whenever I'm not using Firefox. I don't need the configurability (in fact, I could easily and happily use a browser with many fewer options), but its usability there is top-notch, and some Chromium-based browsers' websites are flagged by our IT gods as bad places to go, so I can't even try some of others I wanted to unless I try a workaround.
The reason you did not see these issues before was simply because we were already working around a bunch of issues like this. Rather than do this forever we removed all the workarounds for 2.10 and simply reset our user agent to match Chrome.
There is no value to Google wanting us to have their UA because there is no value to UAs! Every single one is a lie
I would also like to add that if we were doing this because Google paid us off I hope they don't look at my twitter feed over the last few days as I spend most of my time complaining about them. Here are some examples:
I guess that big pay off (that does not exist outside of cwizardone mind) might not come through now.
Oh and if you want to test a well known site that was still UA blocked in Vivaldi 2.9, try Microsoft Teams (their chat and collaboration website). There are a ton of others but this is something well known.
The fun thing with that block was that it is old but since none of the testers here used it, we overlooked it for a while. I also screwed up the initial testing when I did look at it and thought it was not UA related but it was. The even more interesting things is that if I look back to the timing of the original reports I can see that while MS were busy complaining about this
You missed the last part of my question... Why would Google even care to pay them to change it? Google already has the largest market share of browsers by a long shot... is paying Vivaldi to change their user agent really going to make any difference? Plus Vivaldi will miss out on being separated into a distinct browser in regards to marketshare.
The only benefit I see here is for Vivaldi users who have a less than pleasant experience on those sites that don't display properly because it's not a browser they detect or they specifically display a different site if detected, so the user gets a basic or broken experience.
It seems Vivaldi is willing to forego being detectable in regards to marketshare for a better experience for their users. It may still be something nefarious, but unless you can provide some valid reasoning on why Vivaldi would've changed this for money grabbing reasons, I'm going to continue to believe they're doing what they feel is best for their users.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,061
Rep:
Just upgraded to latest stable using ruario's excellent script install-latest.sh
Almost everything is great, but Vivaldi's widevine still causes trouble - open.spotify.com doesn't work.
Replacing the symlink to /var/opt/vivaldi/WidevineCdm with one to /usr/lib64/chromium/WidevineCdm (Eric's chromion and widevine packages), and spotify works just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.