Sync Broken in Current Snapshot
-
@ayespy said in Sync Broken in Current Snapshot:
Developers do not publish their status/work/progress on unfinished fixes. There's no time.
I see. (heavy British undertone here)
As the Vivaldi user base is growing, maybe this could be reconsidered. Particularly in situations where something has seriously gone amiss.
I got annoyed to the point of uninstalling Snapshot and switching to Stable.I know, you're not the team. But I assume someone will notice this.
-
@s_paternotte I don't think they can reconsider how much time there is in the day. The size of the team vs the size of the job simply means they are always backlogged, and almost nothing gets done on time. That and, Jon's teams, in the more than two decades I have been observing them, have never issued progress reports to anyone - even when he had a team of over 200 (of course, then, he had been growing that project for 20 years or so, and had over 50M users, so devs-per-user was actually even a worse ratio than at present.)
-
@s_paternotte said in Sync Broken in Current Snapshot:
What I truly cannot understand is that the users, Vivaldi's most precious asset, are kept in the dark about the status and progress on the fixing of this serious issue.
I can't say I share the same feeling. Although it's true that there is often very little information about what's planned to do or when it's planned to be released, more often than not serious bugs like this one usually get lots of feedback.
Just from what I've been reading in the posts here in the forum in the last days, I found out that:
- the problem was detected (new builds were corrupting the sync profile or something like that)
- sync was disabled at server side for the faulty builds to avoid corrupting any further profiles
- yesterday a new build was launched that should fix the issue. The know issues section even explains what to do in case your profile had been corrupted: https://vivaldi.com/blog/mobile/android-4-1-2350-3/
I think it can be argued that this information could have been presented in a more organized fashion. What happened was dozens of posts inquiring about the problem (many of them created because people simply don't search before they ask - or at least don't use the right search terms - as in many cases the answer came within minutes pointing them to other posts or to the know issues section in the desktop build blog posts and the users acknowledging that they should have searched better). And the new information, when it arrived, was scattered through those posts, often being posted in the most recent one or something like that. But there was definitely information circulating around, some of which even came from people who have contact with "the team" or are part of the team themselves.
Maybe for scenarios like this, when a critical bug has occurred (and is likely to be fixed soon, as is usually the case with critical bugs), and multiple posts start showing up about it, one of the first posts should be pinned or something similar, so that people would find it more easily and new which one to refer to, avoid asking in multiple places... or creating a new issues section for desktop builds... or one of those forum wide messages, like when there's a downtime scheduled or something similar...
I don't know, just leaving some food for thought. -
@pauloaguia I think rather than just hiding a known issue about it in the description of the desktop snapshot where the issues started - much later than when most people originally read the snapshot announcement! - there should have been a dedicated thread in the "announcements" blog/forum with notifications linking to it in the "support & troubleshooting" forum and at the top of the Vivaldi website.
-
While I agree that the issue was high-impact, we all have to keep in mind that it was in the snapshot releases.
I think we all understand the risks that come when not using the main branch of an application. Vivaldi's team has always been responsive and engaging in the forums.
So then again, don't lose focus that by using the snapshot you should be comfortable with some risks.
-
@mossman said in Sync Broken in Current Snapshot:
just hiding a known issue about it in the description of the desktop snapshot where the issues started - much later than when most people originally read the snapshot announcement!
I would say that the first place to search for problems that you're experiencing when using a snapshot version is the post related to that snapshot version - not sure how that can be considered "hiding it"
Here's a couple more suggestions: in the Support & Troubleshoot categories add something to the description like Please include your browser version when reporting an issue or asking for support or If you're using a snapshot, please check the snapshot post regarding your build first (is it possible to link to the most recent one?)
(on a side note, those category descriptions could probably be reviewed. I can see some recommendations that should actually belong to more than one of them).
-
@pauloaguia said in Sync Broken in Current Snapshot:
@mossman said in Sync Broken in Current Snapshot:
just hiding a known issue about it in the description of the desktop snapshot where the issues started - much later than when most people originally read the snapshot announcement!
I would say that the first place to search for problems that you're experiencing when using a snapshot version is the post related to that snapshot version - not sure how that can be considered "hiding it"
It's hidden because when I visit the forum I then have to click a second link to go to the blog where the main text is kept.
That means I read the blog - no mention of the issue at the time - then read the handful of responses before downloading the new version. Then later I start noticing issues with sync - go back to the forum, check the responses, not much chatter about it, assume it will clear up. Go back to the forum again the next day, check the new reponses, mention it myself. Go back to the forum again some time later, more people mentioning it, still no clarity, check the support forum, see some people mentioning things there.
This goes on for some time before people start mentioning "check the known issues" - which it seems have been updated. AT NO POINT would I have seen the known issues list AFTER I installed the browser!
Yes, I DO consider that hidden from the perspective of an average user installing the snapshot in the first days it came out!!!
-
And here we find ourselves, another four days further, discussing the sync issue that, rumour has it, is fixed internally, but without any news from the Vivaldi team, official or informal.
-
@areynaldos Yep. Is also useful to remark the snapshot is a big branch which actually cover post-alpha, betas and pre-finals builds (RC). Is not a real beta channel where mature snapshots are promoted.
Guess the installer should discourage to use the snapshots as daily driver, but we already know that. -