@libcub I would recommend installing the Snapshot as a standalone in its own folder. Disk space is rarely an issue these days so you can easily update 1.15 Stable to 1.16 Stable whenever it is released. After installing the standalone version copy your profile folder over from the Stable installation. Set whichever one you wish to use the most as your default. The Snapshots are usually stable enough not to cause major issues, but there are no guarantees.

Este lançamento do Vivaldi tem 22 novas features.

@Gwen-Dragon I'm thinking about some not-too-complicated process, like // the bug needs to be properly indexed in the database first function CheckBugsDatabase("SomethingDoesn'tWork") { var TheBug = get BugReport("SomethingDoesn'tWork"); var duplicates = CheckForDuplicatedReports(TheBug); // checking if it was already reported if (duplicates>"x") { // if it was reported at least "x" times var bugData = getBugBasicData(TheBug); // get the basic info about the bug exportToTheList(bugData); // send it to the "known issues" list } else if (duplicates==0) { // if it wasn't already reported saveToBugReportsDatabase(TheBug); // just save it to the database } } // this is just a primitive example of how it could be done, it's not an actual code This is pretty much how I imagine those companies doing their "known issues" lists. I mean, it's obviously doable. "Where there's a will, there's a way"... 😉 @Gwen-Dragon said in A place for a "Known Issues List" of the current stable release of Vivaldi: (...) It is not a easy-to-do-i-5-minutes job to filter information which should not go into public. (...) I think that the "reported x times" condition is good enough for that matter. If an issue has been reported at least several times, there's a pretty good chance that it's already been made public somewhere on the forums or on the team blog. But they can always decide not to publish a certain bug report - despite it's being reported frequently - for any reason. And they should obviously publish only the most important (from a user's perspective) information about the bug (like what it causes and whether it's fixed already or not just yet), not the whole report and technical data (especially if it's a security flaw or something like that). @Gwen-Dragon said in A place for a "Known Issues List" of the current stable release of Vivaldi: (...) that all this public list would bind too much human power which would be better invested in more features and bug fixing. ... and managing duplicated bug reports. 😉 PS. By talking about "thousands" of bugs, you look to me like an optimist. 😁