Multi-Account Containers
-
Yes this is a must have feature and should be top priority along with any privacy and encryption initiative within vivaldi components.
-
@iqaluit It can't be a top priority, because it would mean completely changing the architecture of the browser and hiring significantly more staff. Everything cannot go on the back burner to service a single feature that most people don't even use.
-
@Ayespy I wish you wouldn't say most ''people don't use.'' A few people in power position opposing in one single forum definitely do not reflect the reality on the ground. That I know!
Besides we never know if the leadership could change direction towards a superior path and find revenue sources for more privacy...
-
@Ayespy said in Multi-Account Containers:
@iqaluit It can't be a top priority, because it would mean completely changing the architecture of the browser and hiring significantly more staff. Everything cannot go on the back burner to service a single feature that most people don't even use.
I started this feature request some years ago and at that time it wasn't clear to me how embedded into the heart of the browser such technology/feature had to be implemented in. In the case of Vivaldi, the change would have to be done at the browser engine level of which they do not absolute control and maintaining such changes clearly is not part of their priorities. Such decision and maintenance they leave up to the Blink developers of which have not shown any interest for such technology.
What I hope to see is Vivaldi moving towards is hardening Vivaldi. As it currently stands, the level of privacy and security Vivaldi provides is not that far apart from Google Chrome.
Brave does this but they have their own agenda of which a lot of web-users don't agree nor want to deal with (crypto, etc) Furthermore, no web browser GUI beats Vivaldi's.
At this point a hardened Vivaldi or a Vivaldi that allows for the same level of hardening that Brave has brought forth to the Chrome line of browsers would be a great deal.
If done properly, will gain the favor of privacy and security advocates and thus more promotion.Another option would be bringing forth a Vivaldi Gheko flavor browser. This, without a doubt would be a top notch browser killer.
It will dominate over all Firefox forks browser and it would cater to every online users.It would place Vivaldi with all the tools for regular users and privacy and security advocates to set Vivaldi with the level of security they want and expect from a browser.
-
Hello all,
As mentioned earlier, implementing this would be an immense undertaking which we do not have the resources for.
It would probably take a dedicated team several months to develop the necessary changes in the Chromium code base, and possibly several more months to shepherd it through Chromium's patch submission system.
So, here is a suggestion: Many features have been implemented by people who want that particular feature, perhaps some of you are able to take on this project?
For reference, here are some links to resources:
-
Contributing code to Chromium (including the legal stuff):
-
@yngve Excellent !
-
This functionality not being available is sincerely the only reason I can't use Vivaldi as my browser. Like others, I've been using it for years and it's a must have for anyone who has multiple accounts on services.
I saw the "well just add it to chromium yourself" comments and it seems those folks are ignoring that not everybody has the ability to develop or write code. If you want a product to be used by people who are not developers, that's not the way to handle feature requests, especially feature requests that were opened 7 years ago and have 19 pages of replies.
-
@yngve Ohhh... Vivaldi is my favorite browser even though the function doesn't exist... I hope that people who have the knowledge get together to try to do something
-
@poisonous The suggestion to write something was obviously intended for those who CAN write code. There are some thousands who use Vivaldi as their default who can also write code. Vivaldi has, in the past, accepted contributions from users who are coders, and they might very well do so in this case. That the problem is built into the browser engine and that presently they do not have the resources to develop this in-house and still develop and maintain the browser per plans does not seem to have been absorbed by many of the commenters on this thread. The closest thing to a solution seen on a Chromium-based engine seen so far is a development to treat certain new windows as tabs, which took a development team twice the size of Vivaldi's to build and maintain. It is still something a few very slick coders might be able to do. It would certainly produce "containers" in Vivaldi faster than posting here.