@Zalex108 , yes, you need a fast pendrive, but even with this, it only make sens in old PC with very low resources, but a fast pendrive is a less problem as to buy a new PC, and cheaper.
And if this fails too, try a small Linux distro before this
Saw your latest posts about that.
Here, saw the Temp is on %User% Local Temp with a random number if I recall.
All the AutoUpdates work fine, and since less than a month there are 2 different Snaps and Stables versions altogether.
AutoUpdate is launched manually till now, need to check the New Task.
It appears with a random number as well.
Saw entries for the Latest, maybe the latest versions updated, as you comment, but since doing other tasks didn't looked deeply to understand the routine.
Will check in next days, and between next updates.
Bothered? Cricket 🏏?....
@luetage said in Google Extensions - Crypto Token [What it Does]:
It surely was a mistake, the only thing that could rectify the situation is either hiding the option to disable the extensions, or showing a popup on trigger, with a text warning the users about what exactly will break.
I partly agree. But like I said I hope Vivaldi will still give us the option of disabling components and system extensions we have no need for. Maybe only for advanced users, i.e. hidden under experiments.
One of the (many) things I dislike about Chromium is its tendency to sneakily introduce new Google experiments like FloC, Crowd Deny, Zxcvbn and so on. Apparently the latest one (just noticed it in User Data) is "hyphen-data".
Some of these might be innocent, others are clearly ways for Google to experiment with different data-collection stuff, like FLoC which thankfully seems to be broken in Vivaldi, possibly intentionally by the team.
The way Google sees things, Chromium is not meant for casual users, so it can be used as a platform for publicly testing stuff before it's put into Chrome. The result of this is of course that Vivaldi users (at least Snapshotters) end up as lab-rats for various Google experimentation.
With Vivaldi you don't need a mac, OpenBSD, FreeBSD or any extension.
Just hover Over the image
Rt Click, or however you get the context menu
use Image Properties (the image will open in a New Tab)
Again hover over the image, get the context menu and Copy Image
open your favourite image manipulation program (IrfanView is a good one and works well with Wine on Linux)
Create a new (empty) image and Paste
I believe many programmes have hundreds of formats you can Save As...
Very handy way to use the filters, though we have had this since before UB/UBO existed.
The Opera extension "ContentBlockHelper" was always geared for blocking user defined elements..
Thankfully it was ported to the new API so is available as a chrome extension
I don't see what this has to do with security or privacy.
This is a convenience tweak, just like blocking *.gif and animation elements.
@poto Thanks for making a guide on this 👍
However, not completely sure why it's needed - after all, the Vivaldi password export is a Chrome-format CSV file, and Keepass supports import from Chrome CSV. I do it regularly myself and it works fine out of the box:
The big problem is that Keepass lacks an export into the same format, so I can't (easily) export a backup to import back into Vivaldi (should I ever need to). But the standard Keepass 1.x CVS export works with a bit of command-line cut and sed - or just importing the CSV into a spreadsheet and rearranging the columns works as well.
It would be good in to add in the guide that to access the CSV importer in your example you need to choose "Generic CSV Importer" from the Import menu.
Another possible parameter would be the number of results displayed, Vivaldi only display suggestions 5 maximum anyway, so if available, limit this list to 5 elements (setting it higher won't make more suggestions appear)
Is this 5 maximum suggestions limitation still in place?
for current Chromium 93 policies with ...WhiteList... in name are renamed to ...AllowList.... Similar with …Black… changed to …Block…
Please investigate more on your side - if you know news on changes, feel free to answer.
@lonm From the reddit Mixpanel quotation:
Note that Mixpanel indicates the 'harvesting' was inadvertant (and I have no direct reason to disbelieve them). However, it raises the issue of companies that can do the same sort of things deliberately... or of 3rd-party scripts in popular website code that can do it.
As for me, I'll continue to keep my script-blocking shields up except in certain, carefully-vetted, specific situations.